XP Performance Advisor might not collect configuration or performance data for XP disk arrays though the installation, or upgrade completed without any errors.
Following are the typical causes:
• The Command device is not created or presented to your host (probability of occurrence is higher with installations)
• The Windows firewall is configured
• The Java heap size is not set or set with incorrect values
• The available disk space on your management station is low
• The upgrade log file,xpslperf_UpgradeScript.logis created (with errors), or has not been
created (occurrence is only with upgrades)
• TheStd*out.logfile increases in size
• The JRE versions installed on the management station and host are the same
• Check that the GUID is created properly, if it is on a Windows host (probability of occurrence is higher with installations)
• User level understanding on how to collect configuration and performance data
Resolution
The solution for your issue might be one or a combination of the following actions. Perform the steps listed for the following actions to verify and complete the required procedures:
• Creating and presenting command devices to the hosts. For more information, see “Creating and presenting command devices to hosts” on page 35.
• Configuring Windows firewall settings. For more information, see “Configuring firewall settings on a Windows XP Professional management station” on page 30.
• Setting JAVA heap size values on the management station and hosts. For more information, see “Increasing the maximum number of LDEVs” on page 116.
• Creating free disk space on your management station. For more information, seeReleasing disk space on a management stationon page 118.
• Verifying whetherStd*out.logfile has grown in size. For more information, see “Checking
std*out.log file size” on page 118.
• Verifying whether the JRE versions on your management station and hosts are the same. For more information, see the Software sections in “Verifying the supported configurations for XP Performance
Advisor” on page 23 and “Verifying the supported configurations for XP Performance Advisor host agents” on page 33.
• Creating GUIDs on Windows hosts. For more information, see “Assigning GUIDs for command devices on a Windows host” on page 31.
• Understanding how to create configuration and performance data collections. For more information, see “Collecting configuration data” on page 98 and “Collecting performance data” on page 100.
Setting the heap size to view and collect data
To ensure optimal performance and results, the maximum number of LDEVs is restricted to 6000. To increase the maximum number of LDEVs to 16000, increase the memory allocated to the JVM when you start the host agent and management station services. These values must be set if you want to view the performance of XP disk arrays with large number of LDEVs (64K binary (65,536)). NOTE:
To ensure optimal performance and results, the maximum number of LDEVs for data collection is 6000. This is the total number of LDEVs across all XP disk arrays that are visible to a particular host agent. You can decrease the total number of LDEVs visible to a host agent, by restricting the LDEVs that are visible to the host. You can increase the maximum number of LDEVs visible to a host agent, by increasing the number of LDEVs that are visible to the host. For information on increasing the number of LDEVs that are visible to the Host Agent, see “For the management station” on page 116.
Setting the heap size for management station
To set the heap size value on a management station:
1. Copy theheap.batfile from thejava_heapfolder to a location of your choice on the
management station. Thejava_heapfolder is available on the XP Performance Advisor Installation
disk 2.
2. In the command prompt, navigate to the location where you copied theheap.batfile.
3. Executeheap.bat.
4. Enter theMIN JAVA HEAP SIZE IN MBs:(For example, you can set the minimum java heap size value to 512 MB).
5. Enter theMAX JAVA HEAP SIZE IN MBs:(For example, you can set the maximum java heap size value to 1024 MB).
NOTE:
The minimum and maximum java heap size values that you set depends on your system's configuration.
6. The batch file automatically stops and starts the XP Performance Advisor Tomcat services. It also sets the specified minimum and maximum java heap size parameters in XP Performance Advisor.
Setting the heap size values for Windows and Unix host agents
By default, the heap size value is set toXmx1024Mon a Windows or UNIX host agent.Xmx1024M
is also the maximum heap size value recommended by HP, if you are monitoring the performance of XP disk arrays with large number of LDEVs (64K binary (65,536)).
However, you can also increase or decrease the heap size value based on the maximum heap size that your system supports. For more information, refer to your operating system guide to know the maximum configurable heap size value.
To modify the heap size value on a UNIX host agent:
1. Stop the UNIX host agent services.
• To stop the HP XP Performance Advisor Hostagent service, type/opt/xppa/hostagent/ sbin/xppa stopin the command prompt window.
• To stop the HP XP Performance Advisor Realtime Server service, type/opt/xppa/realtime/ xprealtime stopin the command prompt window.
2. Open the file,/opt/xppa/hostagent/sbin/xppa.
3. Edit the maximum heap size value,-Xmx1024Min the following code snippet to a value that is
required, depending on your UNIX or Linux host configuration:
RUNJAVA="/opt/xppa/jre/bin/java -Xmx1024M -DXPPA=1 -Djava.net.preferIPv4Stack=true”
RUNJAVA_IPv6="/opt/xppa/jre/bin/java -Xmx1024M -DXPPA=1
-Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true"
4. Save the changes and close the file.
5. Start the UNIX host agent services.
• To start the HP XP Performance Advisor Hostagent service, type/opt/xppa/hostagent/ sbin/xppa startin the command prompt window.
• To start the HP XP Performance Advisor Realtime Server service, type/opt/xppa/realtime/ xprealtime startin the command prompt window.
To modify the heap size value on a Windows host agent:
1. Stop the Windows host agent services.
• To stop the HP XP Performance Advisor Hostagent service:
a. SelectStart>Runand typeservices.mscin the command line.
b. In the Services window, right-clickHP XP Performance Advisor Hostagent.
c. ClickStopin the drop down list.
• To stop the HP XP Performance Advisor Realtime Server service:
a. SelectStart>Runand typeservices.mscin the command line.
b. In the Services window, right-clickHP XP Performance Advisor Realtime Server.
c. ClickStopin the drop down list.
2. Open the file,C:\Program Files\Hewlett-Packard\xppa\hostagent\config\ wrapper.conf.
3. Edit the maximum heap size value,-Xmx1024Min the following code snippet to a value that is
required, depending on your host configuration:
JAVA_OPTIONS="-Xmx1024m -Djava.library.path=lib -DXPPA=1 -Djava.net.preferIPv4Stack=true -Xrs -Djava.class.path=classes/xpdevicemap.jar;classes/ bccaservice.jar;classes/utils.jar;classes /paxpservice.jar;classes/xmltoolkit.jar;classes/pa_security_client.jar;classes /cssisec.jar;classes/xmlrpc-1.2-b1-applet.jar;classes/xmlrpc-1.2-b1.jar;classes /tzupdater.jar"
5. Start the Windows host agent services.
Follow the steps (a and b) mentioned under stopping the Windows host agent services. Click Startin the drop down lists to start the HP XP Performance Advisor Hostagent service and HP XP Performance Advisor Realtime Server service.