Hi Andrew,
I've done that, but it still a separate object. Investigating a little bit with your perception that alternative boot bank is not right, I found this thread: http://community.hpe.com/t5/ITRC-Systems-Insight-Manager/Alternate-Boot-Bank-discovered-ESX5-1/td-p/6014859
Restarted CIM server and re-run the discovery, but it still not able to associate it with its management processor:
********* Significant issues and overall target discovery/identification
status:
Minor: The discovered server cannot be associated with its management
processor. For Windows and Linux, verify that the supported HP
Insight Management Agents or WBEM provider is installed on the
server. For HP-UX, verify that the WBEM Services version has the
Management Processor provider. Also, verify that the management
processor has been discovered in HP SIM.
Minor: The discovered blade is not in an enclosure. For c-Class
enclosures, verify that the supported OA firmware version is
installed and verify that the OA has been discovered in HP SIM. For
p-Class enclosures, verify that the iLO firmware and the HP Insight
Management Agents on the server are installed and verify that the
iLO has been discovered in HP SIM.
Normal: The system has valid hardware data (model, serial number, and
unique identifier) and has been identified properly for SIM to
manage.
Minor: HP SIM can access the ESX Host and VM information on the embedded
ESX host, but cannot get ProLiant hardware data from the HP WBEM
provider. Either the provider is not installed, or the WBEM CIMOM
service needs to be restarted on the system.
Also tried enabling snmp in a host and configuring it. Still no luck.
Any suggestion is more than welcome.
Thank you