HP Matrix Operating Environment 7.3 Update 1 Installation and Configuration Guide for Provisioning with Virtual Resources

The Unmanaged system type indicates systems that have no management protocol that HP SIM
can detect, for example, systems with no SNMP, WBEM, DMI, or SSH. The Unknown system type
indicates that none of the built-in or STM tasks could identify the system. However, some management
protocol was detected on the system.
Checking log files
The following log files can help you understand system activities:
• Matrix infrastructure orchestration C:\Program Files\HP\Matrix infrastructure
orchestration\logs
◦ hpio-controller.log
Rolling logs–
– Search for WARN, ERROR
◦ hpio.log
– Service startup
– Shutdown
– Logins
• Matrix OE C:\Program Files\HP\Virtual Server Environment\logs
hp_lsa_service.log◦
– Service starts
– Stops
◦ vselog.log
◦ vselog.lsm.log
• LSM utility logs
LSMUTIL is a script that you can run from the command line or from a DOS bat file. LSMUTIL
reads information from the logical servers tables in the Matrix OE database. Based on the
option you select, the script exports information about logical servers, storage pool entries,
or managed resources.
◦ For a list of logical server, enter lsmutil –list –ls –xml –file ls.log
◦ For a list of storage pool entries, enter lsmutil –list –spe –xml –file spe.log
◦ For a list of managed resources, enter lsmutil –list -cr –xml –file cr.log
• VMware logs
HP recommends checking the VMware logs on the ESX hosts, which are managed by HP SIM.
VMware logs are located on the ESX server at /var/log/vmware/hostd.log. For
information about uploading the VMware log files, see the VMware Knowledge Base article
Collecting diagnostic information for VMware Infrastructure SDK at the following website:
http://kb.vmware.com/kb/1001457.
To collect VMware log files, execute the vm-support –a command.
Troubleshooting tools 135