README - HP Systems Insight Manager 5.3 with Update 1
Running node communication diagnosis
System identification done with this system.
Workaround
Go to http://communities.vmware.com/message/914939#914939. Note that the fix above references
3_files in the install queue. However, the number might vary by installation.
-------------------------------------------------------------
I am unable to identify Windows XP targets through WBEM if 'Simple File Sharing' is enabled.
Uncheck Simple File Sharing by navigating to Tools→Folder Options→View or set the security policy
Network access: Sharing and security model for local accounts to Classic: Local users authenticate as
themselves.
-------------------------------------------------------------
The new SSH identification method cannot be used to form associations between DL100 series systems; such
as the DL160 G5 and DL180 G5 and their management processors. There is an incompatibility between
the system UUID presented by the system and the UUID presented by the BMC (management processor)
firmware.
-------------------------------------------------------------
To get basic hardware data, such as model, serial number, and UUID, from non-HP x86 servers running
VMware ESX Server or Linux, you must configure the ‘root’ user as the Sign-in credential in HP SIM. This is
because the Privilege Elevation feature is not used for identification of servers and running dmidecode
requires the root privilege. In addition, to identify the VMware ESX server as the VMware ESX Host subtype,
the WBEM cimserver on the ESX host must be up and working correctly. There are many ways to set these
credentials:
• Global sign-in credentials (Options→Security→Credentials→Global Credentials)
• System Sign-in credentials (Options→Security→Credentials→System Credentials)
• Discovery task Sign-in credentials (Options→Discovery→Edit→Credentials)
-------------------------------------------------------------
Management processors for complexes can be identified using SNMP or XML data. SNMP must be enabled
for management processors that are identified through SNMP.
-------------------------------------------------------------
To discover and properly identify SNMP-based HP Network-attached Storage (NAS) systems, you must add
the
cpqPublic
community string on the Global Protocol Settings page. To access the Global Protocol
Settings page, select Options→Protocol Settings→Global Protocol Settings.
-------------------------------------------------------------
Depending on the information provider, inconsistent operating system version information is returned. For
instance, Microsoft's WMI always returns the operating system type for all of Windows NT, Windows 2000,
Windows XP, and Windows 2003 as Windows NT, even though code values for the other variants are
defined. In addition, data from the SNMP providers is also inconsistent for some Windows versions.
For example, Windows XP systems appear under Microsoft Windows XP systemlist itself. Also, the System
Page Identity tab for a Windows XP system displays both Windows XP and Windows NT.
-------------------------------------------------------------
If a system uses an Emulex Host Bus Adapter (HBA) and you are missing some Logical Unit Numbers (LUNs)
on the System Page of that system, the workaround is to rerun data collection against the system.
1. Select Options→Data Collection. The Data Collection page appears.
2. Select the target system.
3. Click Next.
28 Known Issues and Workarounds