Your maintenance policy dictates how a service profile reacts to changes requiring a reboot.
Making sure your service profiles or an updating service profile template the service profiles are bound to, is associated with 'user ack' setting, will ensure the blades do not get rebooted at all, until you individually 'acknowledge' the server's pending changes.
= = = = = = = = = = = = = = = =
When a service profile is associated with a server, or when changes are made to a service profile that is already associated with a server, you must reboot the server to complete the process. The Reboot Policy field determines when the reboot occurs for servers associated with any service profiles that include this maintenance policy. This can be one of the following:
-
Immediate—The server reboots automatically as soon as the service profile association is complete or when you save service profile changes.
-
User Ack—You must explicitly acknowledge the pending activities for the changes made to the service profile to be applied to the associated server.
-
Timer Automatic—Cisco UCS defers all service profile associations and changes until the maintenance window defined by the schedule shown in the Schedule field.
-
On Next Boot—This option is used in combination with either User Ack or Timer Automatic. When the On Next Boot option is enabled, the host OS reboot, shutdown, and reset, or server reset and shutdown also triggers the associated FSM to apply the changes waiting for theUser Ack, or the Timer Automatic maintenance window.
|
Note
|
De-selecting the On Next Boot option disables the Maintenance Policy on the BMC.
|
|
Note
|
The reboot policy prevents the server from rebooting only when you make changes to the service profile. The server reboots immediately when you perform actions such as the following:
-
Deleting a service profile.
-
Disassociating a service profile.
-
Updating firmware directly without using a policy.
-
Resetting a server.
|
Kirk...
