ESXi blade servers not linked to Enclosure.

[Sebastián Graña]

Hi,

ESXi servers are not linked to the Enclosure despite being correctly identified (SN, server type, etc.). I have duplicate servers, one with hostname as id and other with correct hostname. Both of them show correct serial number but HP SIM is no linking them. Other Windows blade servers are correctly linked. Please take a look at the captures.

I had done this in the past but can't find why it is not linking them now. This is a fresh install.

Do you know how to link them?

Thanks

Best Regards

[Andrew_Haak]

That is strange, try to delete both and the ILO, rerun then onboard admin datacollection and see if you get the serialnamed server back. Now run the ESX discovery with a root like account. The discovered os is alternative bootbank. That's not right so perhaps starting from the begining helps

[Sebastián Graña]

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

[Andrew_Haak · Accepted solution]

Did you install the offline bundle? I also see that discovery thinks the blade is not in an enclosure, did you discover the Onboard Admin in the Enclosure?

You should have a WBEM protocol, i believe this is your problem, do you know what software i mean?

[Sebastián Graña]

Yes, enclosure is discovered with OAs correctly.

I was not aware of this offline bundle. The ESX image is the custom HP image. I thought it has all agents already installed. I will give it a try.

Thanks

[Andrew_Haak]

Look at the credentials for this server, exept logon credentials there should be wbem credentials.

In the screen you posted there should be a wbem protocol, also the credentials shoild be roor or root like for the right rights.

[Sebastián Graña]

Andrew, after installing the offline bundle the server was correctly associated with the iLo en the enclosure. The os is also discovered correctly, VMware ESXi 5.1.0 and not alternative boot bank.

Thank you for pointing me in the right direction.

Regards

[Andrew_Haak]

No problem, glad to help!