- Device Manager Help
- Configuring Cisco DCNM-SAN Server
- Configuring Authentication in Cisco DCNM-SAN
- Configuring Cisco DCNM-SAN Client
- Device Manager
- Configuring Performance Manager
- Configuring High Availability
- Configuring Trunking
- Configuring PortChannels
- Configuring N Port Virtualization
- Configuring Interfaces
- Configuration of Fibre Channel Interfaces
- Using the CFS Infrastructure
- Configuring SNMP
- Configuring Domain Parameters
- Configuring and Managing Zones
- Configuring FCoE
- Configuring Dense Wavelength Division Multiplexing
- Configuring and Managing VSANs
- Discovering SCSI Targets
- Configuring SAN Device Virtualization
- Configuring Fibre Channel Routing Services and Protocols
- Managing FLOGI, Name Server, FDMI, and RSCN Databases
- Configuring FICON
- Creating Dynamic VSANs
- Distributing Device Alias Services
- Configuring Advanced Fabric Features
- Configuring Users and Common Role
- Configuring Security Features on an External AAA Server
- Configuring Certificate Authorities and Digital Certificates
- Configuring FC-SP and DHCHAP
- Configuring Cisco TrustSec Fibre Channel Link Encryption
- Configuring FIPS
- Configuring IPv4 and IPv6 Access Control Lists
- Configuring IPsec Network Security
- Configuring Port Security
- Configuring Fabric Binding
- Configuring FCIP
- Configuring the SAN Extension Tuner
- Configuring iSCSI
- Configuring IP Services
- Configuring IP Storage
- Configuring IPv4 for Gigabit Ethernet Interfaces
- Configuring IPv6 for Gigabit Ethernet Interfaces
- Configuring SCSI Flow Services
- Configuring SCSI Flow Statistics
- Configuring Fibre Channel Write Acceleration
- Monitoring the Network
- Monitoring Performance
- Configuring Call Home
- Configuring System Message Logging
- Scheduling Maintenance Jobs
- Configuring RMON
- Configuring Fabric Configuration Server
- Monitoring Network Traffic Using SPAN
- Monitoring System Processes and Logs
- Configuring QoS
- Configuring Port Tracking
- Configuring FlexAttach Virtual pWWN
- Configuring Interface Buffers
- Verifying Ethernet Interfaces
- Information About the Command Scheduler
- Licensing Requirements for Command Scheduler
- Guidelines and Limitations
- Default Settings
- Configuring the Command Scheduler
Scheduling Maintenance Jobs
The Cisco MDS command scheduler feature helps you schedule configuration and maintenance jobs in any switch in the Cisco MDS 9000 Family. You can use this feature to schedule jobs on a one-time basis or periodically.
Information About the Command Scheduler
The Cisco NX-OS command scheduler provides a facility to schedule a job (set of CLI commands) or multiple jobs at a specified time in the future. The job(s) can be executed once at a specified time in the future or at periodic intervals.
You can use this feature to schedule zone set changes, make QoS policy changes, back up data, save the configuration and do other similar jobs.
Scheduler Terminology
The following terms are used in this chapter:
- Job—A job is a set of NX-OS CLI commands (EXEC and config mode) that are executed as defined in the schedule.
- Schedule—A schedule determines the time when the assigned jobs must be executed. Multiple jobs can be assigned to a schedule. A schedule executes in one of two modes: one-time or periodic.
- Periodic mode—A job is executed at the user-specified periodic intervals, until it is deleted by the administrator. The following types of periodic intervals are supported:
– Daily—The job is executed once a day.
– Weekly—The job is executed once a week.
– Monthly—The job is executed once a month.
– Delta—The job is executed beginning at the specified start time and thereafter at user-specified intervals (days:hours:minutes).
Licensing Requirements for Command Scheduler
To use the command scheduler, you do not need to obtain any license.
Guidelines and Limitations
Before scheduling jobs on a Cisco MDS 9000 switch, note the following guidelines:
- Prior to Cisco MDS SAN-OS Release 3.0(3), only users local to the switch could perform scheduler configuration. As of Cisco MDS SAN-OS Release 3.0(3), remote users can perform job scheduling using AAA authentication.
- Be aware that the scheduled job can fail if it encounters one of the following situations when executing the job:
– If the license has expired for a feature at the time when a job containing commands pertaining to that feature is scheduled.
– If a feature is disabled at the time when a job containing commands pertaining to that feature is scheduled.
– If you have removed a module from a slot and the job has commands pertaining to the interfaces for that module or slot.
- Verify that you have configured the time. The scheduler does not have any default time configured. If you create a schedule and assign job(s) and do not configure the time, that schedule is not launched.
- While defining a job, verify that no interactive or disruptive commands (for example, copy bootflash: file ftp: URI , write erase , and other similar commands) are specified as part of a job because the job is executed noninteractively at the scheduled time.
Default Settings
Table 52-1 lists the default settings for command scheduling parameters.
Configuring the Command Scheduler
The Cisco NX-OS command scheduler provides a facility to schedule a job (set of CLI commands) or multiple jobs at a specified time in the future.
This section includes the following tasks:
- Task Flow for Configuring the Command Scheduler
- Enabling the Command Scheduler
- Configuring Remote User Authentication
- Defining a Job
- Specifying a Schedule
- Configuring Execution Logs
Task Flow for Configuring the Command Scheduler
Follow these steps to configure the Command Scheduler:
Step 2 Authorize remote user access (optional).
Step 4 Specify the schedule and assign jobs to the schedule.
Step 5 Specify the time for the schedule(s).
Step 6 Verify the scheduled configuration.
Enabling the Command Scheduler
To use the scheduling feature, you must explicitly enable this feature on the required switches in the fabric. By default, this feature is disabled in all switches in the Cisco MDS 9000 Family.
The configuration and verification commands for the command scheduler feature are only available when this feature is enabled on a switch. When you disable this feature, all related configurations are automatically discarded.
To enable the command scheduling feature, follow these steps:
Configuring Remote User Authentication
Prior to Cisco MDS SAN-OS Release 3.0(3), only users local to the switch could perform scheduler configuration. As of Cisco MDS SAN-OS Release 3.0(3), remote users can perform job scheduling using AAA authentication.
Prerequisites <Optional>
- AAA authentication requires the clear text password of the remote user before creating and configuring command scheduler jobs.
To configure remote user authentication, follow these steps:
Defining a Job
To define a job, you must specify the job name. This action places you in the job definition (config-job
)
submode. In this submode, you can define the sequence of CLI commands that the job has to perform. Be sure to exit the config-job submode to complete the job definition.
Restrictions
- Job configuration files created using MDS NX-OS or SAN-OS releases before Cisco MDS NX-OS Release 4.1(1b) are not supported. However, you can edit the job configuration file and combine the commands within a job into a single line using a semicolon (;).
- You must exit the config-job submode for the job definition to be complete.
- You cannot modify or remove a command after exiting the config-job submode. To make changes, you must explicitly delete the defined job name and then reconfigure the job with new commands.
To define a job for the command scheduler, follow these steps:
Specifying a Schedule
After defining jobs, you can create schedules and assign jobs to the schedule. Subsequently, you can configure the time of execution. The execution can be one-time or periodic depending on your requirements. If the time for the schedule is not configured, then it will never be executed.
You can specify a periodic job execution at the specified (daily, weekly, monthly, or delta) intervals.
To specify a periodic job for the command scheduler, follow these steps:
Examples
The following examples are for reference:
The most significant fields in the time parameter are optional. If you omit the most significant fields, the values are assumed to be the same as the current time. For example, if the current time is September 24, 2004, 22:00 hours, then the commands are executed as follows:
- The time start 23:00 repeat 4:00:00 command implies a start time of September 24, 2004, 23:00 hours.
- The time daily 55 command implies every day at 22:55 hours.
- The time weekly 23:00 command implies every Friday at 23:00 hours.
- The time monthly 23:00 command implies the 24th of every month at 23:00 hours.
Note If the time interval configured for any schedule is smaller than the time taken to execute its assigned job(s), then the subsequent schedule execution occurs only after the configured interval amount of time has elapsed following the completion time of the last iteration of the schedule. For example, a schedule is executed at 1-minute intervals and a job assigned to it takes 2 minutes to complete. If the first schedule is at 22:00 hours, the job finishes at 22:02 after which the 1-minute interval is observed, and the next execution occurs at 22:03 and finishes at 22:05.
Specifying a One-Time Schedule
When you specify a one-time job execution, that job is only executed once.
To specify a one-time job for the command scheduler, follow these steps:
Removing an Assigned Job
Deleting a Schedule Time
Configuring Execution Logs
The command scheduler maintains a log file. While you cannot modify the contents of this file, you can change the file size. This log file is a circular log that contains the output of the job executed. If the output of the job is greater than the log file, then the output stored in this file remains truncated.
You can configure the log file size to be a maximum of 1024 KB. The default size of the execution log file is 16 KB.
To configure the execution log file size, follow these steps:
Verifying Scheduler Configuration
To display the command scheduler configuration information, perform one of the following tasks:
For detailed information about the fields in the output from these commands, refer to the Cisco MDS 9000 Family Command Reference .
This section includes the followinf topics:
- Verifying the Command Scheduler Configuration
- Verifying the Command Scheduler Execution Status
- Verifying the Job Definition
- Displaying Execution Log File Contents
- Clearing the Execution Log File Contents
Verifying the Command Scheduler Configuration
To display the scheduler configuration, use the show scheduler config command.
Verifying the Command Scheduler Execution Status
To verify the command scheduler execution status, use the show scheduler schedule command.
Displaying Execution Log File Contents
To display the execution log for all jobs executed in the system, use the show scheduler logfile command.
To display the scheduler password configuration for remote users, use the show running-config command.
Note The scheduler remote user passwords are always displayed in encrypted form in the show running-config command output. The encrypted option (7) in the command exists to support applying the ASCII configuration to the switch.
To display the execution log file configuration, use the show scheduler config command.