ESXi

Hello,

we have the following problem with one of your HP BL 680 G7 Blades. We recently upgraded from ESX 4.0 to ESXi 4.1 with a reinstall of the plattform. We included the HP CIM Modules and the drivers into the VMware Update Manager as Upgrade repsoitories and all went fine so far. We can successfully monitor all systems via HP SIM. For this one particular blade the MGMT Board lost communication to the enclosure and we are not able to connect to console any more or do any hardware related tasks through the HP Enclosure. In the past with ESX 4.0 we were able to restart the board via the system homepage that was installed with the tools. In ESXi there is no homepage just wbem. How can this task be performed, without powering off the system and pulling the blade out of the chassis ? I already tried by enabling the remote support console and did a service restart which restarted all the system related services, but not the managment board. Thanks for your help.

Hi,

we are facing correct same issue on HP hardware. Is there any solution or workaround in place?

regards MuxXx79

Hallo,

for all who are looking for a solution, there was a workaroud in place for HP blades within HP C7000 enclosures.

1. Login vCenter Server via vCenter client

2. Set host in maintenance mode

3, Power off host after entering MM

4. Connect via SSH client to HP Onboard Administrator

5. Run command : "show server list"

6. Identify host and device bay by iLO Name and power state

7. Run command: "RESET Server <BayNo>"

WARNING: Resetting the server trips its E-Fuse. This causes all power to be momentarily removed from the server. This command should only be used when physical access to the server is unavailable, and the server must be removed and

reinserted.

Any disk operations on direct attached storage devices will be affected. I/O

will be interrupted on any direct attached I/O devices.

Entering anything other than 'YES' will result in the command not executing.

Do you want to continue ? YES

Successfully reset the E-Fuse for device bay XX.

Kind regards MuxXx79