HP Systems Insight Manager - Manual (Page 198)

VMware
The name of the temperature sensors might be incorrect. This is a known issue in the VMWare
provider and will be addressed in a future release of VMWare providers.
WBEM
WBEM is no longer supported on HP servers. The last servers to support WBEM were the G6
servers. Therefore, HP SIM will not identify the operating system details properly for RHEL 5.7 Xen
and KVM servers.
WBEM indications
Current P9500 embedded SMI-S does not support WBEM indications. WBEM indication will be
supported from V05 firmware version.
-------------------------------------------------------------
For a CVAE 7.2 server to receive WBEM indications from XP arrays in HP SIM 7.1, the below
configuration changes need to be performed on CVAE 7.2 server.
Procedure 54 Configuration for a CVAE 7.2 server to receive WBEM indications from XP arrays
1. Create the .ind.keystore file be executing:
keytool.exe -genkey -keystore .ind.keystore -storepass indssl
-validity 365 -keyalg RSA -keysize 2,048
2. After importing HP SIM certificate in CVAE 7.2, the truststore file is creating as
indtruststore
instead of .ind.truststore. You must rename indtruststore file
to .ind.truststore.
-------------------------------------------------------------
HP SIM doesn't support WBEM Indications on ESL G3 tape library with embedded SMI-S(without
CVTL)
WMI Mapper
When WMI Mapper is installed on a Windows 2008 R2 CMS, the WMI Mapper service may
fail to start with the "NT SERVICE\MAPPER" user and the WMI Mapper Indications service might
fail to start with the "NT SERVICE\WbemConsumer" user. This occurs on a Windows 2008 R2
CMS that is part of a domain that's security policy is being controlled by a domain controller, in
which the above two users are not given the log on as service right.
The WMI Mapper and WMI Mapper Indications services fail to start and while trying to start these
services from the services.msc console, the following error appears:
Windows could not start the Pegasus WMI Mapper service on Local Computer.
Error 1069: The service did not start due to a logon failure.
A more detailed error is also listed in the Systems Logs of the Windows Event Viewer.
The problem occurs because in Windows 2008 R2, Mapper and Mapper Indications Services are
started with users having lower privileges. By default a standalone Windows 2008 R2 server will
have these users with the said privileges. However in the case of a server whose security policies
are controlled by a domain controller, these users might be removed from the default set of users
and hence the services will not start.
You can choose to follow any one of the below workarounds based on your requirements:
•
You change the Mapper and Mapper Indications Service to start with a privileged user account
such as the “localSystem” account. This can be made by editing the properties of each of the
service using the “services.msc” console
•
You can choose to give the following two users “NT SERVICE\WMI Mapper” and “NT
SERVICE\WbemConsumer” the “log on as a service” right using the “User Rights Assignment”
option in the Security Policy Editor (secpol.msc).
-------------------------------------------------------------
198 Troubleshooting