8 troubleshooting – HP Plug-in for SAP NetWeaver Landscape Virtualization Management for Storage User Manual
Page 22
8 Troubleshooting
This chapter lists the known issues in the HP Storage plug-in and their workarounds.
Q1. The list_app command does not list the SCA file after deployment.
A1. This occurs due to timeout during deployment in the environment. The current default timeout
is 15 seconds.
Perform the following steps to increase the default timeout to an appropriate value:
1.
Login to NWA (NetWeaver Administrator) portal.
2.
Click Availability and Performance
→System Overview→AS Java, and then click Nodes.
3.
Click Started, and select Manage Java Server nodes.
4.
On the Start & Stop: Java instances page, click the Java Instances tab, and then click More
Actions
→View System Properties.
5.
On the Java System Properties: Overview page, navigate to the Services tab under Details
for the instances of the selected Java.
6.
Select Timeout, and click Modify under the Extended Details section for Timeout. Enter a higher
value as appropriate.
Q2. Failure with the NOT_AUTHENTICATED message.
This error might occur due to any of the following reasons:
•
Invalid credentials provided for the HP Storage Provider—re-enter the credentials, and test the
configuration.
•
A timeout between the SAP NW LVM adapter and the HP Storage Provider makes the current
session invalid. Perform the following steps to increase the timeout to an appropriate value:
1.
Navigate to
configuration/standalone.xml
2.
Under
/> The current default value is 1800 seconds. Increase the default timeout to an appropriate Q3. After you reboot the hosts in SUSE environment, the existing logical volume groups become A3. You must re-activate the logical volume groups after every SUSE reboot. To re-activate the vgchange –a y Q4 The CS (Central Service) instance is down and the Enqueue server stopped after a System A4. Add all the SAP ports (for example, SAP System Dispatcher Port, SAP System Gateway Port, file of the source to the target. Restart SAP manually in the target system. The CS instance will start after the restart. Q5. The CI (Central Instance) is down as the J2EE server stopped due to invalid license in the A5. To resolve this, perform the following steps: 22 Troubleshooting
value.
inactive.
logical volume groups, manually run the following command after every reboot:
Clone operation in HP-UX.
SAP System Dispatcher Security Port, and SAP System Gateway Security Port) from the /etc/
services
target.