README - HP Systems Insight Manager 5.3 with Update 1

HP-UX Performance
To implement manual performance improvement on an HP-UX system, configure HP SIM to run with additional
Java heap space configured on an HP-UX system:
1. Stop the HP SIM service by running the mxstop command.
2. Expand the heap size in native applications of HP-UX 11.0 and 11.11 (11i v1) PA-RISC:
HP-UX 11.11 (11i v1) PA-RISC Install Required Patch (and dependent patches: PHCO_30544.depot
(or its superseded path)
For 1500 MB to 2400 MB of Java heap:
cd /usr/bin chatr +q3p enable mxdomainmgr
For PA-RISC systems running HP-UX 11.11 and later:
./chatr +q3p enable /opt/mx/lbin/mxdomainmgr
For Integrity systems running HP-UX 11.23 or later of Java heap greater than 1500 MB:
./chatr +as mpas <executable name>
3. Edit the globalsettings.props file and set JVM heap size larger:
vi /etc/opt/mx/config/globalsettings.props
a. Insert the following:
JVMMAXHEAP=750
b. Save and exit.
4. Start the HP SIM service by running mxstart.
Identification
Unable to identify ESX 3.x classic servers to have the appropriate system types and subtypes, or no virtual
machines can be discovered from the ESC 3.x hosts.
Symptoms:
The host is not identified correctly in HP SIM with the type Server and subtype as "VMware ESX Host",
"Virtual Machine Host"
The host is discovered correctly in HP SIM with the appropriate types and subtypes. However, no guests
are discovered. The Vman page shows the host, but no guests. The Virtual Machine Management Pack
property page is the one place on the CMS that does show the guests.
On the ESX host, when attempting to start the WBEM server, the following error is given (log is attached):
# service pegasus start
Processing /var/pegasus/vmware/install_queue/1 [FAILED]
ERROR: See log - /var/pegasus/vmware/install_queue/1.log
When running HP SIM discovery, the following information appears:
Checking for known running web servers.
Checking for System Management Home Page and other HP web agents.
The System Management Homepage is not supported on this system.
Checking for WBEM support on system.
This system has WBEM protocol support
This system has at least one SMI-S CIMOM installed
26 Known Issues and Workarounds