Deferring Deployment of Service Profile Updates

This chapter includes the following sections:

Service Profile Deferred Deployments

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 acknowledgment.

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

  • Re-acknowledging a server

  • Resetting a server

If you want to defer the deployment of service profile changes, you must configure one or more maintenance policies and configure each service profile with a maintenance policy. If you want to define the time period when the deployment should occur, you also need to create at least one schedule with one or more recurring occurrences or one time occurrences, and include that schedule in a maintenance policy.

Schedules for Deferred Deployments

A schedule contains a set of occurrences. These occurrences can be one time only or can recur at a specified time and day each week. The options defined in the occurrence, such as the duration of the occurrence or the maximum number of tasks to be run, determine whether a service profile change is deployed. For example, if a change cannot be deployed during a given maintenance window because the maximum duration or number of tasks was reached, that deployment is carried over to the next maintenance window.

Each schedule checks periodically to see whether the Cisco UCS domain entered one or more maintenance windows. If so, the schedule executes the deployments that are eligible according to the constraints specified in the maintenance policy.

A schedule contains one or more occurrences, which determine the maintenance windows associated with that schedule. An occurrence can be one of the following:

One Time Occurrence

One time occurrences define a single maintenance window. These windows continue until the maximum duration of the window or the maximum number of tasks that can be run in the window is reached.

Recurring Occurrence

Recurring occurrences define a series of maintenance windows. These windows continue until the maximum number of tasks or the end of the day specified in the occurrence was reached.

Maintenance Policy

The maintenance policy specifies how deploys the service profile changes. The deployment can occur in one of the following ways:

  • Immediately

  • When acknowledged by a user with administrator privileges

  • Automatically at the time specified in a schedule

  • On the next reboot or shutdown without waiting for the user acknowledgment or the timer scheduling option

A UCSM and CIMC version on blade or rack server must be running firmware from 3.1.x bundle, for On Next Boot to work.

If the On Next Boot option is enabled in a maintenance policy, and you downgrade from Cisco UCS Manager Release 3.1(1) or later releases to any release earlier than Cisco UCS Manager Release 2.2(8), firmware downgrade will fail. Disable On Next Boot from the maintenance policy to continue with the downgrade.

You can use the soft shutdown timer in the maintenance policy to configure the wait time for performing a hard shutdown. The soft shutdown timer is applicable when you reboot the server for the following:

  • Reset the server using the Gracefully Restart OS option.

  • Shut down the server with the In case of graceful shutdown failure, a hard shutdown will be issued after X seconds option.

  • Modify a service profile that requires a server reboot.

If the maintenance policy is configured to deploy the change during a scheduled maintenance window, the policy must include a valid schedule. The schedule deploys the changes in the first available maintenance window.


Note

A maintenance policy only prevents an immediate server reboot when a configuration change is made to an associated service profile. However, a maintenance policy does not prevent the following actions from taking place right away:

  • Deleting an associated service profile from the system

  • Disassociating a server profile from a server

  • Directly installing a firmware upgrade without using a service policy

  • Resetting the server

Pending Activities for Deferred Deployments

If you configure a deferred deployment in a Cisco UCS domain, Cisco UCS Manager enables you to view all pending activities. You can see activities that are waiting for user acknowledgement and those that are scheduled.

If a Cisco UCS domain has pending activities, Cisco UCS Manager GUI notifies users with admin privileges when they log in.

Cisco UCS Manager displays information about all pending activities, including the following:

  • Name of the service profile to deploy and associate with a server

  • Server affected by the deployment

  • Disruption caused by the deployment

  • Change performed by the deployment


Note

You cannot specify the maintenance window in which a specific pending activity is applied to the server. The maintenance window depends upon how many activities are pending and which maintenance policy is assigned to the service profile. However, any user with admin privileges can manually initiate a pending activity and reboot the server immediately, whether it is waiting for user acknowledgment or for a maintenance window.

Guidelines and Limitations for Deferred Deployments

Cannot Undo All Changes to Service Profiles or Service Profile Templates

If you cancel a pending change, Cisco UCS Manager attempts to roll back the change without rebooting the server. However, for complex changes, Cisco UCS Manager may have to reboot the server a second time to roll back the change. For example, if you delete a vNIC, Cisco UCS Manager reboots the server according to the maintenance policy included in the service profile. You cannot cancel this reboot and change, even if you restore the original vNIC in the service profile. Instead, Cisco UCS Manager schedules a second deployment and reboot of the server.

Association of Service Profile Can Exceed Boundaries of Maintenance Window

After Cisco UCS Manager begins the association of the service profile, the scheduler and maintenance policy do not have any control over the procedure. If the service profile association does not complete within the allotted maintenance window, the process continues until it is completed. For example, this can occur if the association does not complete in time because of retried stages or other issues.

Cannot Specify Order of Pending Activities

Scheduled deployments run in parallel and independently. You cannot specify the order in which the deployments occur. You also cannot make the deployment of one service profile change dependent upon the completion of another.

Cannot Perform Partial Deployment of Pending Activity

Cisco UCS Manager applies all changes made to a service profile in the scheduled maintenance window. You cannot make several changes to a service profile at the same time and then have those changes be spread across several maintenance windows. When Cisco UCS Manager deploys the service profile changes, it updates the service profile to match the most recent configuration in the database.

Configuring Schedules

Creating a Schedule

Procedure
    Step 1   In the Navigation pane, click Servers.
    Step 2   On the Servers tab, right-click Schedules and choose Create Schedule.
    Step 3   In the Identify Schedule page of the Create Schedule wizard, complete the following fields:
    Name Description

    Name field

    The name of the schedule.

    This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object is saved.

    Description field

    A description of the schedule. We recommend including information about where and when the schedule should be used.

    Enter up to 256 characters. You can use any characters or spaces except ` (accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign), > (greater than), < (less than), or ' (single quote).

    Owner field

    The owner of the schedule. This can be one of the following:

    • Local—Cisco UCS Manager owns the schedule, which is configured in this Cisco UCS domain.

    • Pending Global—Cisco UCS Manager is in the process of transferring this schedule to Cisco UCS Central.

    • Global—Cisco UCS Central owns the schedule, which is configured on a remote server.
    Step 4   Click Next.
    Step 5   On the One Time Occurrences page, click one of the following:
    Option Description

    Next

    Moves to the next page. Choose this option if you do not want to create a one time occurrence for this schedule.

    If you choose this option, continue with Step 8.

    Add

    Opens the Create a One Time Occurrence dialog box, where you can specify a single time when this schedule should be run.

    If you choose this option, continue with Step 6.
    Step 6   (Optional)  In the Create a One Time Occurrence dialog box, do the following:
    1. Complete the following fields:
      Name Description

      Name field

      The name of the one time occurrence of this schedule.

      This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object is saved.

      Start Time field

      The date and time that the occurrence will run.

      Click the down arrow at the end of the field to select the date from a calendar.
    2. Click the down arrows to expand the Options area.
    3. In the Options area, complete the following fields:
      Name Description

      Max Duration field

      The maximum length of time that the scheduled occurrence can run. This can be one of the following:

      • None—The occurrence runs until all tasks are completed.

      • other—Cisco UCS Manager GUI displays the dd:hh:mm:ss field allowing you to specify the maximum amount of time that the occurrence can run. Cisco UCS completes as many scheduled tasks as possible within the specified time.

      By default, the maximum duration is set to none. If you do not change this setting and you do not set a maximum number of tasks, the maintenance window continues until all pending activities are completed.

      Max Number of Tasks field

      The maximum number of scheduled tasks that can be run during this occurrence. This can be one of the following:

      • Unlimited—Cisco UCS runs all scheduled tasks unless those tasks exceed the maximum time specified in the Max Duration field. If Max Duration is set to none and you select this option, the maintenance window continues until all pending activities are completed.

      • other—Cisco UCS Manager GUI displays a text field allowing you to specify the maximum number of tasks that can be run during this occurrence. Enter an integer between 1 and 65535.

      Note   

      This option does not apply if this schedule is associated with a fault suppression task.

      Max Number of Concurrent Tasks field

      The maximum number of tasks that can run concurrently during this occurrence. This can be one of the following:

      • Unlimited—Cisco UCS runs as many concurrent tasks as the system can handle.

      • other—Cisco UCS Manager GUI displays a text field allowing you to specify the maximum number of concurrent tasks that can be run during this occurrence. Enter an integer between 1 and 65535.

      Note   

      This option does not apply if this schedule is associated with a fault suppression task.

      Minimum Interval Between Tasks field

      The minimum length of time that the system should wait before starting a new task. This setting is meaningful only if the maximum number of concurrent tasks is set to a value other than None. This can be one of the following:

      • None—Cisco UCS runs the next task as soon as possible.

      • other—Cisco UCS Manager GUI displays the dd:hh:mm:ss field allowing you to specify the minimum amount of time that Cisco UCS will wait between tasks.

      Note   

      This option does not apply if this schedule is associated with a fault suppression task.
    4. Click OK.
    Step 7   To add another one time occurrence, click Add and repeat step 6. Otherwise, click Next.
    Step 8   (Optional)  If you want to define a recurring occurrence for this schedule, on the Recurring Occurrences page, click Add.
    1. In the Create a Recurring Occurrence dialog box, complete the following fields:
      Name Description

      Name field

      The name of the recurring occurrence of this schedule.

      This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object is saved.

      Day field

      The day on which Cisco UCS runs an occurrence of this schedule. This can be one of the following:

      • every day

      • Monday

      • Tuesday

      • Wednesday

      • Thursday

      • Friday

      • Saturday

      • Sunday

      • odd days

      • even days

      Hour field

      The hour of the specified day at which this occurrence of the schedule starts. This can be an integer between 0 and 24, where 0 and 24 are both equivalent to midnight.

      Note   

      Cisco UCS ends all recurring occurrences on the same day in which they start, even if the maximum duration has not been reached. For example, if you specify a start time of 11 p.m. and a maximum duration of 3 hours, Cisco UCS starts the occurrence at 11 p.m. but ends it at 11:59 p.m. after only 59 minutes.

      Ensure that the start time you specify is early enough so that the recurring occurrence finishes before 11:59 p.m.

      Minute field

      The minute of the hour at which the schedule occurrence starts. This can be an integer between 0 and 60.
    2. Click the down arrows to expand the Options area.
    3. In the Options area, complete the following fields:
      Name Description

      Max Duration field

      The maximum length of time that each occurrence of this schedule can run. This can be one of the following:

      • None—The occurrence runs until all tasks are completed.

      • other—Cisco UCS Manager GUI displays the dd:hh:mm:ss field allowing you to specify the maximum amount of time that the occurrence can run. Cisco UCS completes as many scheduled tasks as possible within the specified time.

      Max Number of Tasks field

      The maximum number of scheduled tasks that can be run during each occurrence. This can be one of the following:

      • Unlimited—Cisco UCS runs all scheduled tasks unless those tasks exceed the maximum time specified in the Max Duration field. If Max Duration is set to none and you select this option, the maintenance window continues until all pending activities are completed.

      • other—Cisco UCS Manager GUI displays a text field allowing you to specify the maximum number of tasks that can be run during this occurrence. Enter an integer between 1 and 65535.

      Note   

      This option does not apply if this schedule is associated with a fault suppression task.

      Max Number of Concurrent Tasks field

      The maximum number of tasks that can run concurrently during each occurrence. This can be one of the following:

      • Unlimited—Cisco UCS runs as many concurrent tasks as the system can handle.

      • other—Cisco UCS Manager GUI displays a text field allowing you to specify the maximum number of concurrent tasks that can be run during this occurrence. Enter an integer between 1 and 65535.

      Note   

      This option does not apply if this schedule is associated with a fault suppression task.

      Minimum Interval Between Tasks field

      The minimum length of time that the system should wait before starting a new task. This setting is meaningful only if the maximum number of concurrent tasks is set to a value other than None. This can be one of the following:

      • None—Cisco UCS runs the next task as soon as possible.

      • other—Cisco UCS Manager GUI displays the dd:hh:mm:ss field allowing you to specify the minimum amount of time that Cisco UCS will wait between tasks.

      Note   

      This option does not apply if this schedule is associated with a fault suppression task.
    4. Click OK.
    5. To add another recurring occurrence, click Add and repeat this step.
    Step 9   Click Finish.

    Creating a One Time Occurrence for a Schedule


    Note

    By default, the maximum duration and the maximum number of tasks are set to none. If you do not change either of these defaults, Cisco UCS Manager does not impose any limit to the length of time that the maintenance window lasts. All pending activities are applied as soon as the scheduled maintenance window begins, and Cisco UCS Manager continues to reboot the servers impacted by the pending activities until all of those tasks are complete.

    Procedure
      Step 1   In the Navigation pane, click Servers.
      Step 2   Expand Schedules.
      Step 3   Right-click the schedule to which you want to add an occurrence and choose Create a One Time Occurrence.
      Step 4   In the Create a One Time Occurrence dialog box, complete the following fields:
      Name Description

      Name field

      The name of the one time occurrence of this schedule.

      This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object is saved.

      Start Time field

      The date and time that the occurrence will run.

      Click the down arrow at the end of the field to select the date from a calendar.
      Step 5   Click the down arrows to expand the Options area.
      Step 6   In the Options area, complete the following fields:
      Name Description

      Max Duration field

      The maximum length of time that the scheduled occurrence can run. This can be one of the following:

      • None—The occurrence runs until all tasks are completed.

      • other—Cisco UCS Manager GUI displays the dd:hh:mm:ss field allowing you to specify the maximum amount of time that the occurrence can run. Cisco UCS completes as many scheduled tasks as possible within the specified time.

      By default, the maximum duration is set to none. If you do not change this setting and you do not set a maximum number of tasks, the maintenance window continues until all pending activities are completed.

      Max Number of Tasks field

      The maximum number of scheduled tasks that can be run during this occurrence. This can be one of the following:

      • Unlimited—Cisco UCS runs all scheduled tasks unless those tasks exceed the maximum time specified in the Max Duration field. If Max Duration is set to none and you select this option, the maintenance window continues until all pending activities are completed.

      • other—Cisco UCS Manager GUI displays a text field allowing you to specify the maximum number of tasks that can be run during this occurrence. Enter an integer between 1 and 65535.

      Note   

      This option does not apply if this schedule is associated with a fault suppression task.

      Max Number of Concurrent Tasks field

      The maximum number of tasks that can run concurrently during this occurrence. This can be one of the following:

      • Unlimited—Cisco UCS runs as many concurrent tasks as the system can handle.

      • other—Cisco UCS Manager GUI displays a text field allowing you to specify the maximum number of concurrent tasks that can be run during this occurrence. Enter an integer between 1 and 65535.

      Note   

      This option does not apply if this schedule is associated with a fault suppression task.

      Minimum Interval Between Tasks field

      The minimum length of time that the system should wait before starting a new task. This setting is meaningful only if the maximum number of concurrent tasks is set to a value other than None. This can be one of the following:

      • None—Cisco UCS runs the next task as soon as possible.

      • other—Cisco UCS Manager GUI displays the dd:hh:mm:ss field allowing you to specify the minimum amount of time that Cisco UCS will wait between tasks.

      Note   

      This option does not apply if this schedule is associated with a fault suppression task.
      Step 7   Click OK.

      Creating a Recurring Occurrence for a Schedule

      Procedure
        Step 1   In the Navigation pane, click Servers.
        Step 2   Expand Schedules.
        Step 3   Right-click the schedule to which you want to add an occurrence and choose Create a Recurring Occurrence.
        Step 4   In the Create a Recurring Occurrence dialog box, complete the following fields:
        Name Description

        Name field

        The name of the recurring occurrence of this schedule.

        This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object is saved.

        Day field

        The day on which Cisco UCS runs an occurrence of this schedule. This can be one of the following:

        • every day

        • Monday

        • Tuesday

        • Wednesday

        • Thursday

        • Friday

        • Saturday

        • Sunday

        • odd days

        • even days

        Hour field

        The hour of the specified day at which this occurrence of the schedule starts. This can be an integer between 0 and 24, where 0 and 24 are both equivalent to midnight.

        Note   

        Cisco UCS ends all recurring occurrences on the same day in which they start, even if the maximum duration has not been reached. For example, if you specify a start time of 11 p.m. and a maximum duration of 3 hours, Cisco UCS starts the occurrence at 11 p.m. but ends it at 11:59 p.m. after only 59 minutes.

        Ensure that the start time you specify is early enough so that the recurring occurrence finishes before 11:59 p.m.

        Minute field

        The minute of the hour at which the schedule occurrence starts. This can be an integer between 0 and 60.
        Step 5   Click the down arrows to expand the Options area.
        Step 6   In the Options area, complete the following fields:
        Name Description

        Max Duration field

        The maximum length of time that each occurrence of this schedule can run. This can be one of the following:

        • None—The occurrence runs until all tasks are completed.

        • other—Cisco UCS Manager GUI displays the dd:hh:mm:ss field allowing you to specify the maximum amount of time that the occurrence can run. Cisco UCS completes as many scheduled tasks as possible within the specified time.

        Max Number of Tasks field

        The maximum number of scheduled tasks that can be run during each occurrence. This can be one of the following:

        • Unlimited—Cisco UCS runs all scheduled tasks unless those tasks exceed the maximum time specified in the Max Duration field. If Max Duration is set to none and you select this option, the maintenance window continues until all pending activities are completed.

        • other—Cisco UCS Manager GUI displays a text field allowing you to specify the maximum number of tasks that can be run during this occurrence. Enter an integer between 1 and 65535.

        Note   

        This option does not apply if this schedule is associated with a fault suppression task.

        Max Number of Concurrent Tasks field

        The maximum number of tasks that can run concurrently during each occurrence. This can be one of the following:

        • Unlimited—Cisco UCS runs as many concurrent tasks as the system can handle.

        • other—Cisco UCS Manager GUI displays a text field allowing you to specify the maximum number of concurrent tasks that can be run during this occurrence. Enter an integer between 1 and 65535.

        Note   

        This option does not apply if this schedule is associated with a fault suppression task.

        Minimum Interval Between Tasks field

        The minimum length of time that the system should wait before starting a new task. This setting is meaningful only if the maximum number of concurrent tasks is set to a value other than None. This can be one of the following:

        • None—Cisco UCS runs the next task as soon as possible.

        • other—Cisco UCS Manager GUI displays the dd:hh:mm:ss field allowing you to specify the minimum amount of time that Cisco UCS will wait between tasks.

        Note   

        This option does not apply if this schedule is associated with a fault suppression task.
        Step 7   Click OK.

        Deleting a One Time Occurrence from a Schedule

        If this is the only occurrence in a schedule, that schedule is reconfigured with no occurrences. If the schedule is included in a maintenance policy and that policy is assigned to a service profile, any pending activities related to the server associated with the service profile cannot be deployed. You must add a one time occurrence or a recurring occurrence to the schedule to deploy the pending activity.

        Procedure
          Step 1   In the Navigation pane, click Servers.
          Step 2   Expand Schedules > Schedule_Name.
          Step 3   Expand One Time Occurrences.
          Step 4   Right-click the occurrence you want to delete and choose Delete.
          Step 5   If a confirmation dialog box displays, click Yes.

          Deleting a Recurring Occurrence from a Schedule

          If this is the only occurrence in a schedule, that schedule is reconfigured with no occurrences. If the schedule is included in a maintenance policy and that policy is assigned to a service profile, any pending activities related to the server associated with the service profile cannot be deployed. You must add a one time occurrence or a recurring occurrence to the schedule to deploy the pending activity.

          Procedure
            Step 1   In the Navigation pane, click Servers.
            Step 2   Expand Schedules > Schedule_Name.
            Step 3   Expand Recurring Occurrences.
            Step 4   Right-click the occurrence you want to delete and choose Delete.
            Step 5   If a confirmation dialog box displays, click Yes.

            Deleting a Schedule

            If this schedule is included in a maintenance policy, the policy is reconfigured with no schedule. If that policy is assigned to a service profile, any pending activities related to the server associated with the service profile cannot be deployed. You must add a schedule to the maintenance policy to deploy the pending activity.

            Procedure
              Step 1   In the Navigation pane, click Servers.
              Step 2   Expand Schedules.
              Step 3   Right-click the schedule you want to delete and choose Delete.
              Step 4   If a confirmation dialog box displays, click Yes.

              Configuring Maintenance Policies

              Creating a Maintenance Policy

              Before You Begin

              If you plan to configure this maintenance policy for automatic deferred deployment, create a schedule.

              Procedure
                Step 1   In the Navigation pane, click Servers.
                Step 2   Expand Servers > Policies.
                Step 3   Expand the node for the organization where you want to create the policy.

                If the system does not include multitenancy, expand the root node.

                Step 4   Right-click Maintenance Policies and choose Create Maintenance Policy.
                Step 5   In the Create Maintenance Policy dialog box, complete the following fields:
                Name Description

                Name field

                The name of the policy.

                This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object is saved.

                Description field

                A description of the policy. Cisco recommends including information about where and when to use the policy.

                Enter up to 256 characters. You can use any characters or spaces except ` (accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign), > (greater than), < (less than), or ' (single quote).

                Soft Shutdown Timer drop-down list

                This timer allows you to specify the time in seconds when Cisco UCS Manager performs a server shut down and reboot. Cisco UCS Manager waits until the specified time in the maintenance policy before performing a hard shut down. This can be one of the following:

                • 150 Secs—Cisco UCS Manager waits until 150 seconds before performing a hard shut down and reboot of the server.

                • 300 Secs—Cisco UCS Manager waits until 300 seconds before performing a hard shut down and reboot of the server.

                • 600 Secs—Cisco UCS Manager waits for 600 seconds before performing a hard shut down and reboot of the server.

                • Never—Cisco UCS Manager never performs a server shut down.

                Reboot Policy field

                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.

                Schedule drop-down list

                If the Reboot Policy is set to Timer Automatic, the schedule specifies when maintenance operations can be applied to the server. Cisco UCS reboots the server and completes the service profile changes at the scheduled time.

                Create Schedule link

                Creates a new schedule that is available to all objects in this Cisco UCS domain.

                Step 6   Click OK.
                What to Do Next

                Include the policy in a service profile or service profile template.

                Deleting a Maintenance Policy

                Procedure
                  Step 1   In the Navigation pane, click Servers.
                  Step 2   Expand Servers > Policies > Organization_Name.
                  Step 3   Expand Maintenance Policies.
                  Step 4   Right-click the maintenance policy you want to delete and choose Delete.
                  Step 5   If a confirmation dialog box displays, click Yes.

                  Managing Pending Activities

                  Viewing Pending Activities

                  Procedure
                    Step 1   On the toolbar, click Pending Activities.
                    Step 2   Click one of the following tabs:

                    • User Acknowledged Activities—Contains the Service Profiles and Fabric Interconnects tabs that display the tasks requiring user acknowledgment before they can complete.

                    • Scheduled Activities—Displays the tasks that will be performed based on the associated maintenance schedule.

                    Step 3   Click a row in the table to view the details of that pending activity.

                    If you click the link in the Server column, Cisco UCS Manager displays the properties of that server.

                    Deploying a Service Profile Change Waiting for User Acknowledgement

                    Important:

                    You cannot stop Cisco UCS Manager from rebooting the affected server after you acknowledge a pending activity.

                    Procedure
                      Step 1   On the toolbar, click Pending Activities.
                      Step 2   In the Pending Activities dialog box, click the User Acknowledged Activities tab, then the Service Profiles tab.
                      Step 3   Check the check box in the Reboot Now column for each pending activity that you want to deploy immediately.
                      Step 4   Click OK.

                      Cisco UCS Manager immediately reboots the server affected by the pending activity.

                      Deploying All Service Profile Changes Waiting for User Acknowledgement

                      Important:

                      You cannot stop Cisco UCS Manager from rebooting the affected server after you acknowledge a pending activity.

                      Procedure
                        Step 1   On the toolbar, click Pending Activities.
                        Step 2   In the Pending Activities dialog box, click the User Acknowledged Activities tab and then the Service Profiles tab.
                        Step 3   In the toolbar, check the Acknowledge All check box.

                        Cisco UCS Manager GUI checks the Reboot Now check boxes for all pending activities listed in the table.

                        Step 4   Click OK.

                        Cisco UCS Manager immediately reboots all servers affected by the pending activities listed in the table.

                        Deploying a Scheduled Service Profile Change Immediately

                        Important:

                        You cannot stop Cisco UCS Manager from rebooting the affected server after you acknowledge a pending activity.

                        Procedure
                          Step 1   On the toolbar, click Pending Activities.
                          Step 2   In the Pending Activities dialog box, click the Scheduled Activities tab.
                          Step 3   Check the check box in the Reboot Now column for each pending activity you want to deploy immediately.
                          Step 4   Click OK.

                          Cisco UCS Manager immediately reboots the server affected by the pending activity.

                          Deploying All Scheduled Service Profile Changes Immediately

                          Important:

                          You cannot stop Cisco UCS Manager from rebooting the affected server after you acknowledge a pending activity.

                          Procedure
                            Step 1   On the toolbar, click Pending Activities.
                            Step 2   In the Pending Activities dialog box, click the Scheduled Activities tab.
                            Step 3   In the toolbar, check the Acknowledge All check box.

                            Cisco UCS Manager GUI checks the Reboot Now check boxes for all pending activities listed in the table.

                            Step 4   Click OK.

                            Cisco UCS Manager immediately reboots all servers affected by the pending activities listed in the table.