README - HP Systems Insight Manager 5.3

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.
Symptons:
• 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
This system doesn´t have a server CIMOM installed locally, or cannot connect
to it using all credentials specified
Running WBEM rules based identification.
Cannot get ComputerSystem WBEM/WMI data from the system
Running VM Identification
The system is not a VMware ESX Host, or WBEM credentials may not be
specified, skipping VM Identification
Running WS-Man identification.
The system did not respond to WS-Management, verify credentials.
Checking for SNMP support on system.
The system responded to a SNMP request, it supports SNMP.
Running SNMP base Cluster identification using common cluster MIB.
This was not a system with the common cluster MIBs supported.
Running HP ProLiant management agent identification
System has the SNMP ProLiant server (foundation) agents installed, adding
system type.
Running HP NetServer identification.
System supports the NetServer SNMP agent, adding system type
Running HP-UX SNMP identification.
System does not have the HPUX SNMP agents installed.
26 Known Issues and Workarounds