README - HP Systems Insight Manager 5.3
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.
4. Specify how to save data by selecting either:
• Overwrite existing data set (for detailed analysis.) Provides a network snapshot at a certain time
• Append new data set (for historical trend analysis.) Provides trend and usage analysis
5. Click Run Now.
-------------------------------------------------------------
Systems with a dual-port Emulex 1050C HBA card appear in HP SIM as two single-port HBAs. This behavior
is expected because the Emulex 1050DC card is actually two single-port HBAs on one physical card, and
each has its own SCSI controller.
-------------------------------------------------------------
BC1000 blades might appear with an Unknown or Unmanaged status if the CMS is being used as the WMI
Mapper proxy. To correct this problem, enter the WBEM credentials for the CMS in the Global Protocol
Settings page, or edit the system protocol settings for the CMS on the System Protocol Settings page.
Run identification again on the CMS, and then run identification on the blades. See the
HP Systems Insight
Manager Technical Reference Guide
for setting protocol settings and running identification.
-------------------------------------------------------------
HP SIM now supports HP ProLiant Lights-Out 100 Remote Management enabled G3 servers. HP ProLiant
Lights-Out 100 Remote Management enabled G2 servers and earlier are not supported.
Initial ProLiant Support Pack Install
-------------------------------------------------------------
28 Known Issues and Workarounds