Filter
Top Products
CHAPTER 31
Deferring Deployment of Service Profile Updates
This chapter includes the following sections:
• Deferred Deployment of Service Profiles, page 469
• Configuring Schedules, page 472
• Configuring Maintenance Policies, page 482
• Managing Pending Activities, page 484
Deferred Deployment of Service Profiles
Some modifications to a service profile or to an updating service profile template can be disruptive and require
a reboot of the server. You can, however, configure deferred deployment to control when those disruptive
configuration changes are implemented. For example, you can choose to deploy the service profile changes
immediately or have them deployed during a specified maintenance window. You can also choose whether
or not a service profile deployment requires explicit user acknowledgement.
Deferred deployment is available for all configuration changes that occur through the association of a service
profile with a server. These configuration changes can be prompted by a change to a service profile, to a policy
that is included in a service profile, or to an updating service profile template. For example, you can defer the
upgrade and activation of firmware through host firmware packages and management firmware packages,
such as server BIOS, RAID controller, host HBA, and network adapters. However, you cannot defer the direct
deployment of firmware images for components that do not use either of the firmware packages, such as Cisco
UCS Manager, fabric interconnects, and I/O modules.
Deferred deployment is not available for the following actions which require the reboot of a server:
• Initial association of a service profile with a server
• Final disassociation of a service profile from a server, without associating the service profile with a
different server
• Decommissioning a server
• Reacknowledging a server
• Resetting a server
Cisco UCS Manager GUI Configuration Guide, Release 2.0
OL-25712-04 469