Hp insight control power management, Identification, Hp insight control power management identification – HP Systems Insight Manager User Manual
Page 131
HP Insight Control power management
After discovering new servers and their iLO 2 management processors using Reports
→Insight Power
Manager
, the task wizard indicates the server is not compatible with Insight Power Manager.
Solution: Insight Power Manager requires an association to exist between the iLO management processor
and the server before compatibility can be determined. If you attempt to use the Insight Power Manager tool
before this has been determined, you encounter this issue.
•
Select the iLO 2 from the system list and execute Tools
→Identify Systems to re-execute the Insight
Power Manager compatibility check.
or
•
Wait for 15 minutes for Insight Power Manager's periodic system management to re-determine
compatibility. After compatibility has been verified, this problem should not reoccur.
-------------------------------------------------------------
After applying an iLO Select or Advanced license to the iLO 2 using its user interface, Refresh Data is
clicked in Insight Power Manager to collect new power history data and a message appears indicating the
iLO 2 has no license.
Solution: Systems Insight Manager must re-identify the iLO 2 to detect the presence of the new license. Select
Tools
→Identify Systems to re-identify the iLO 2 or wait for Systems Insight Manager's periodic identification
cycle to complete. You can check the status of Systems Insight Manager's awareness of iLO 2 license
assignment selecting Deploy
→License Manager.
Identification
Unable to identify ESX 3.x classic servers to have the appropriate system types and subtypes, or no virtual
machines can be discovered from the ESX 3.x hosts.
Symptoms:
•
The host is not identified correctly in Systems Insight Manager with the type Server and subtype as
VMware ESX Host, Virtual Machine Host
•
The host is discovered correctly in Systems Insight Manager with the appropriate types and subtypes.
However, no guests are discovered. The Vman page shows the host, but no guests. The virtual machine
management property page is the one place on the CMS that does show the guests.
•
On the ESX host, when attempting to start the WBEM server, the following error is given:
# service pegasus start
Processing /var/pegasus/vmware/install_queue/1 [FAILED]
ERROR: See log - /var/pegasus/vmware/install_queue/1.log
•
When running Systems Insight Manager discovery, the following information appears:
Running WBEM rules based identification.
Cannot get ComputerSystem WBEM/WMI data from the system
[WBEM] System identified as WBEM instrumented but no usable WBEM credentials
available. Check configuration and rerun Identification.
Root Cause: Identification failed to generate relevant WBEM credentials
for target system.
Corrective Action: Check network and configuration of target system. Check
the following pages to ensure appropriate WBEM credentials and port number
data are provided: Global Protocol Settings, System Protocol Settings.
Rerun Identification and Data Collection..
Solution: Go to
. Note that the fix above
references /var/pegasus/vmware/install_queue/1 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.
HP Insight Control power management
131