I followed this guide:
And it worked, but I have 2 problems.
1) The blade being put into Standby starts back up immediately - almost like a reboot -
and doesn't stay in Standby mode
2) The Blade being put into Standby mode has Faults on all vFabric's etc because it is
Your issue is likely you have Power Management within the DRS settings enabled. If there's limited hosts, vCenter will immeidately re-power up a host put into standby. This is expected behavior for vCenter protecting the cluster.
Test - Disable DRS on your cluster, and then put a host into standby. It should stay down indefinately.
ESXi 5.0.0, 623860 - Nothing in the logs that shows VMware is sending another signal - only the Standby signal. In fact, it thinks it succesfully put it into Standby mode as the blade goes unresponsive for long enough.
Board Controller: B230100A
CIMC Controller: 2.0(1w)
One suspicion is that maybe UCS is interpreting the signal from ESXi as a reboot instead of a Standby.
If this is the case, then a firmware update is likely required.
Hi Rob and Jim,
How did you guys progress with this one? I am having the same issue and be interested to know the solution.
My environment is vSphere 5.0 with B230 M2 and DPM is not yet enabled. UCS Manager and CIMC are running 2.0(1s).
On testing for Standby from the vSphere client, the blade reboots automatically (no power down). A shutdown command gives the same result (which is a reboot) with a host connection failure alert.
Any help is appreciated.