During Blade Firmware upgrade OS has Hard reboot

[SrikanthV]

Hi,
during the blade firmware upgrade on Windows OS, the server gets rebooted after the user acknoledgement, the OS has a hard reboot. the error in the event id is 41. the server was rebooted unexpectedly. is there any way that the OS can have soft reboot instead of hard reboot during blade firmware upgrade.

[Kirk J]

So most 'reset/reboot' type actions taken by the UCSM needing to power cycle a blade/rack server involve acpi commands sent to the server OS, and then after a period (i think 120 seconds) if the UCSM doesn't detect any movement by the OS, it will do hard power reset.

There is an option in the user ACK/Maintenance Policies 

for 'pending next reboot', which means the actual ucsm tasks, won't actually trigger the power cycle, but will wait for you to do the actually reboot via the OS.

Sounds like if the UCSM is having a hard time getting the OS to gracefully reboot, that the 'on next boot' option is your best option for a graceful acknowledgement.

Kirk...

[SrikanthV]

can we shutdown the server manually, change the firmware policy and acknowledge reboot.

will this work?

[Kirk J]

It's probably more scalable to get comfortable with the 'on next reboot' methodology, as you can line up/apply multiple servers sharing the same host firmware policy, and then just reboot individually  from the  OS.

Kirk...