02-07-2017 11:20 PM - edited 03-01-2019 01:03 PM
Hi. I have a question because my customer gave me an abnormal question.
In speaking of our infrustructure
1. server farm(blade 22EA) is already in operation, some servers will be added to the existing chassises.
2. The cpu of existing servers is Intel E series v3 and we are going to upgrade firmwares before adding the new servers(11EA) with E series v4.
3. Operation system is ESXi 6.0 u2
4. Firmware upgrade precedure : IOM -> UCS manager -> Fabric interconnect (A) -> Fabric interconnect (B) -> Blade servers (22EA)
5. After upgrading firmwares, eNIC and fNIC drivers will be upgraded in ESXi side
All of them excluding Blade servers has been upgraded properly.
For upgrading blade servers, I pre-configured the maintenance policy as "User Ack" protected against automatically reboot.
and also Host firmware policy (existing policy : 2.2.6e / Added : 2.2.8f).
These policies are already associated into each profile and the profiles associated to each physical server.
I have a plan to upgrade all of blade servers using host firmware policy change.
At this point, when I choose 2.2.8f policy in each profile and then apply, the servers will not be rebooted automatically.
As i pre-configured, when reboot needed the massages will be indicated on "Pending Activities".
My thought is correct?
Solved! Go to Solution.
02-08-2017 04:02 AM
Greetings.
The User ack will perform as you are expecting.
There were some caveats on previous code such as CSCus42584 or CSCuv32417, but this will not impact you at the code level you are already at.
A much requested feature was added at 2.28a UCSM:
Next Boot—The maintenance policy now provides an On Next Boot option. This option is used in combination with either User Ack or Timer Automatic. With the On Next Boot option enabled, one of the following conditions can trigger the associated FSM to apply the changes waiting for the User Ack, or the Timer Automatic maintenance window.
This allows you to apply OS patches or driver updates requiring a reboot, to then trigger the user-ack pending firmware.
Thanks,
Kirk
02-08-2017 04:02 AM
Greetings.
The User ack will perform as you are expecting.
There were some caveats on previous code such as CSCus42584 or CSCuv32417, but this will not impact you at the code level you are already at.
A much requested feature was added at 2.28a UCSM:
Next Boot—The maintenance policy now provides an On Next Boot option. This option is used in combination with either User Ack or Timer Automatic. With the On Next Boot option enabled, one of the following conditions can trigger the associated FSM to apply the changes waiting for the User Ack, or the Timer Automatic maintenance window.
This allows you to apply OS patches or driver updates requiring a reboot, to then trigger the user-ack pending firmware.
Thanks,
Kirk
02-10-2017 11:10 PM
Hi Krik.
Thanks for your advice. It really help me to upgrade firmware correctly..
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide