Scheduling Options

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:

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

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

  • GlobalCisco 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.

    • otherCisco 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:

    • UnlimitedCisco 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.

    • otherCisco 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:

    • UnlimitedCisco UCS runs as many concurrent tasks as the system can handle.

    • otherCisco 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:

    • NoneCisco UCS runs the next task as soon as possible.

    • otherCisco 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.

    • otherCisco 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:

    • UnlimitedCisco 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.

    • otherCisco 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:

    • UnlimitedCisco UCS runs as many concurrent tasks as the system can handle.

    • otherCisco 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:

    • NoneCisco UCS runs the next task as soon as possible.

    • otherCisco 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.

  • otherCisco 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:

  • UnlimitedCisco 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.

  • otherCisco 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:

  • UnlimitedCisco UCS runs as many concurrent tasks as the system can handle.

  • otherCisco 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:

  • NoneCisco UCS runs the next task as soon as possible.

  • otherCisco 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.

  • otherCisco 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:

  • UnlimitedCisco 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.

  • otherCisco 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:

  • UnlimitedCisco UCS runs as many concurrent tasks as the system can handle.

  • otherCisco 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:

  • NoneCisco UCS runs the next task as soon as possible.

  • otherCisco 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.