moving one blade to another chassis - failure with disassociation of profile

[vijayscsa]

Folks,

After shutting down the host OS, properly i did disassociate the server profile of the blade.  But with 10% it started giving error and FSM status got stuck at 10% and status shows "in progress"

error is "adapter:unconfig Nic failed"

Now what to do?  still i can go ahead move the blade to other chassis.

what's the work around ?  please

[Wes Austin]

In order to move a blade from chassis to chassis, there is not a requirement to disassociate the service profile, as this is done during the decommission of the blade.

You can attempt to reset the slot:

UCS#reset slot x/y......x=Chassis ID y= Server ID

Are you able to recommission the server? There should be no impact if you just move the blade physically, but you should decommission it to avoid duplicating SN.

If the discovery fails in the new slot, you may have a faulty adapter.

[vijayscsa]

actually i'm moving chassis 3, Slot 3 to Chassis 7, slot 7

during the disassocation of slot3, still i get FSM status as In progress.  But it looks like no profile associated.  Still Shall i go ahead take the blade out and moving to new chassis ?

[vijayscsa]

Folks,

power state shows "On" even though i have shut down the ESXi OS.    How to remotely power off the blade from UCS manager?