Scheduling Options

Deployment Scheduling Options

Creating a Schedule

Procedure

  Command or Action Purpose

Step 1

UCS-A# scope system

Enters system mode.

Step 2

UCS-A /system # create scheduler sched-name

Creates a scheduler and enters scheduler mode.

Step 3

UCS-A /system/scheduler # commit-buffer

Commits the transaction to the system configuration.

Example

The following example creates a scheduler named maintenancesched and commits the transaction: 

UCS-A# scope system
UCS-A /system # create scheduler maintenancesched
UCS-A /system/scheduler* # commit-buffer
UCS-A /system/scheduler #

What to do next

Create a one time occurrence or recurring occurrence for the schedule.

Creating a One Time Occurrence for a Schedule

Procedure

  Command or Action Purpose

Step 1

UCS-A# scope system

Enters system mode.

Step 2

UCS-A /system # scope schedule sched-name

Enters scheduler system mode.

Step 3

UCS-A /system/scheduler # create occurrence one-time occurrence-name

Creates a one-time occurrence.

Step 4

UCS-A /system/scheduler/one-time # set date month day-of-month year hour minute

Sets the date and time this occurrence should run.

Step 5

(Optional) UCS-A /system/scheduler/one-time # set concur-tasks {unlimited | max-num-concur-tasks

(Optional)

Sets the maximum number of tasks that can run concurrently during this occurrence.

If the maximum number of tasks is reached, the scheduler waits for the amount of time set in the minimum interval property before scheduling new tasks.

Step 6

(Optional) UCS-A /system/scheduler/one-time # set max-duration {none | num-of-days num-of-hours num-of-minutes num-of-seconds}

(Optional)

Sets the maximum length of time that this schedule occurrence can run. Cisco UCS completes as many scheduled tasks as possible within the specified time.

Step 7

(Optional) UCS-A /system/scheduler/one-time # set min-interval {none | num-of-days num-of-hours num-of-minutes num-of-seconds}

(Optional)

Sets the minimum length of time that the system should wait before starting a new task.

Step 8

(Optional) UCS-A /system/scheduler/one-time # set proc-cap {unlimited | max-num-of-tasks}

(Optional)

Sets the maximum number of scheduled tasks that can be run during this occurrence.

Step 9

UCS-A /system/scheduler/one-time # commit-buffer

Commits the transaction to the system configuration.

Example

The following example creates a one time occurrence named onetimemaint for a scheduler named maintsched, sets the maximum number of concurrent tasks to 5, sets the start date to April 1, 2011 at 11:00, and commits the transaction: 
UCS-A# scope system
UCS-A /system # scope scheduler maintsched
UCS-A /system/scheduler # create occurrence one-time onetimemaint
UCS-A /system/scheduler/one-time* # set date apr 1 2011 11 00
UCS-A /system/scheduler/one-time* # set concur-tasks 5
UCS-A /system/scheduler/one-time* # commit-buffer
UCS-A /system/scheduler/one-time #

Creating a Recurring Occurrence for a Schedule

Procedure

  Command or Action Purpose

Step 1

UCS-A# scope system

Enters system mode.

Step 2

UCS-A /system # scope schedule sched-name

Enters scheduler system mode.

Step 3

UCS-A /system/scheduler # create occurrence recurring occurrence-name

Creates a recurring occurrence.

Step 4

(Optional) UCS-A /system/scheduler/recurring # set day {even-day | every-day | friday | monday | never | odd-day | saturday | sunday | thursday | tuesday | wednesday}

(Optional)

Specifies the day on which Cisco UCS runs an occurrence of this schedule.

By default, this property is set to never.

Step 5

(Optional) UCS-A /system/scheduler/recurring # set hour hour

(Optional)

Specifies the hour at which this occurrence starts.

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.

Step 6

(Optional) UCS-A /system/scheduler/recurring # set minute minute

(Optional)

Specifies the minute at which this occurrence starts.

Step 7

(Optional) UCS-A /system/scheduler/recurring # set concur-tasks {unlimited | max-num-concur-tasks

(Optional)

Sets the maximum number of tasks that can run concurrently during this occurrence.

If the maximum number of tasks is reached, the scheduler waits for the amount of time set in the minimum interval property before scheduling new tasks.

Step 8

(Optional) UCS-A /system/scheduler/recurring # set max-duration {none | num-of-hours num-of-minutes num-of-seconds}

(Optional)

Sets the maximum length of time that this schedule occurrence can run. Cisco UCS completes as many scheduled tasks as possible within the specified time.

Step 9

(Optional) UCS-A /system/scheduler/recurring # set min-interval {none | num-of-days num-of-hours num-of-minutes num-of-seconds}

(Optional)

Sets the minimum length of time that the system should wait before starting a new task.

Step 10

(Optional) UCS-A /system/scheduler/recurring # set proc-cap {unlimited | max-num-of-tasks}

(Optional)

Sets the maximum number of scheduled tasks that can be run during this occurrence.

Step 11

UCS-A /system/scheduler/recurring # commit-buffer

Commits the transaction to the system configuration.

Example

The following example creates a recurring occurrence called recurringmaint for a scheduler called maintsched, sets the maximum number of concurrent tasks to 5, sets the day this occurrence will run to even days, sets the time it will start to 11:05, and commits the transaction:
UCS-A# scope system
UCS-A /system # scope scheduler maintsched
UCS-A /system/scheduler # create occurrence recurring recurringmaint
UCS-A /system/scheduler/recurring* # set day even-day
UCS-A /system/scheduler/recurring* # set hour 11
UCS-A /system/scheduler/recurring* # set minute 5
UCS-A /system/scheduler/recurring* # set concur-tasks 5
UCS-A /system/scheduler/recurring* # commit-buffer
UCS-A /system/scheduler/recurring #

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

  Command or Action Purpose

Step 1

UCS-A# scope system

Enters system mode.

Step 2

UCS-A /system # scope scheduler sched-name

Enters scheduler system mode.

Step 3

UCS-A /system/scheduler # delete occurrence one-time occurrence-name

Deletes the specified one-time occurrence.

Step 4

UCS-A /system/scheduler # commit-buffer

Commits the transaction to the system configuration.

Example

The following example deletes a one time occurrence called onetimemaint from scheduler maintsched and commits the transaction:
UCS-A# scope system
UCS-A /system # scope scheduler maintsched
UCS-A /system/scheduler # delete occurrence one-time onetimemaint
UCS-A /system/scheduler* # commit-buffer
UCS-A /system/scheduler #

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

  Command or Action Purpose

Step 1

UCS-A# scope system

Enters system mode.

Step 2

UCS-A /system # scope scheduler sched-name

Enters scheduler system mode.

Step 3

UCS-A /system/scheduler # delete occurrence recurring occurrence-name

Deletes the specified recurring occurrence.

Step 4

UCS-A /system/scheduler # commit-buffer

Commits the transaction to the system configuration.

Example

The following example deletes a recurring occurrence named onetimemaint from scheduler maintsched and commits the transaction: 
UCS-A# scope system
UCS-A /system # scope scheduler maintsched
UCS-A /system/scheduler # delete occurrence recurring onetimemaint
UCS-A /system/scheduler* # commit-buffer
UCS-A /system/scheduler #

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

  Command or Action Purpose

Step 1

UCS-A# scope system

Enters system mode.

Step 2

UCS-A /system # delete scheduler sched-name

Deletes a scheduler and enters scheduler mode.

Step 3

UCS-A /system # commit-buffer

Commits the transaction to the system configuration.

Example

The following example deletes a scheduler named maintenancesched and commits the transaction: 

UCS-A# scope system
UCS-A /system # delete scheduler maintenancesched
UCS-A /system* # commit-buffer
UCS-A /system #