README - HP Systems Insight Manager 5.3

-------------------------------------------------------------
When trying to discover a WBEM protocol supported system (target), you must have a root user credential
entered in the Global Protocol Settings page in HP SIM of the target system before discovery is started.
Otherwise, WBEM subscriptions fail, WBEM identification does not collect proper information from the target
system, and WBEM status icon updates are not set properly because the data has not been discovered and
collected successfully. This does not apply to HP-UX, OpenVMS, and Linux Integrity systems. The following
lists the access level needed for each CIMOM that is supported in HP SIM.
Table 2-2 CIMOM access level
Write CIM objects (e.g. Create
Subscription
Read CIM Objects (e.g. SIM
Identification)
Operating systemCIMOM
Non-super userNon-super userNSKNSK (T0682ABP and later)
Super userSuper userNSKNSK (pre ABP)
Non-rootNon-rootVMWare ESXiSFCB
Root or AdministratorNon-rootX86 Linux, Windows StorageOpenPegasus*
Root**Non-rootHP-UX, OpenVMSHP WBEM Services
Admin***Admin***WindowsWMI (Windows ProLiant
Providers
* If using root to access the OpenPegasus CIMOM you must configure root access in
/etc/Pegasus/access.conf
** Override the default behavior by setting the configuration parameter
enableSubscriptionsForNonprivilegedusers to true in the cimserver using the cimconfig command. See
the cimconfig man page for details.
*** Use Configure or Repair Agents in HP SIM to configure the non-administrator account with sufficient
privileges to access the WMI CIMOM.
WBEM Indications
When HP SIM subscribes to NSK WBEM Indications, the indications are listed in the Events log. Over time
the NSK CIMOM deletes the subscription and HP SIM no longer receives indications.
You must periodically check to see if the subscription is still valid by running the mxwbemsub command for
the NSK managed system. If the mxwbemsub command does not list any subscriptions, you must resubscribe
for WBEM indications on the NSK managed system.
WMI Mapper
If you have created subscriptions on a Windows managed system and then elects to change the WMI
Mapper proxy or install a WMI Mapper on the managed system, you must first unsubscribe for WBEM
events, change the proxy, re-identify the systems, and then resubscribe for WBEM events. If you do not
unsubscribe for the WBEM events, HP SIM will no longer receive indications from the managed system.
WBEM Indications
For ProLiant iLO2's to be properly identified with WS-MAN functionality, the iLO2 credentials must be the
first credentials specified in either the discovery credential list or the global credential list when discovery is
run. Otherwise, system credentials can be set directly for the system after it is discovered.
50 Known Issues and Workarounds