cron
config>system
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Commands in this context create scripts, script parameters and schedules that support the Service Assurance Agent (SAA) functions.
CRON features are saved to the configuration file on both primary and backup control modules. If a control module switchover occurs, CRON events are restored when the new configuration is loaded. If a control module switchover occurs during the execution of a CRON script, the failover behavior will be determined by the contents of the script.
schedule schedule-name [owner schedule-owner]
[no] schedule
config>system>cron
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures the type of schedule to run, including one-time only (oneshot), periodic or calendar-based runs. All runs are determined by month, day of month or weekday, hour, minute and interval (seconds).
The no form of this command removes the context from the configuration.
Specifies the name of the schedule.
Specifies the owner name of the schedule.
count number
config>system>cron>sched
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command configures the total number of times a CRON interval schedule is run. For example, if the interval is set to 600 and the count is set to 4, the schedule runs 4 times at 600 second intervals.
Specifies the number of times the schedule is run.
day-of-month {day-number [..day-number] all}
[no] day-of-month
config>system>cron>sched
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command specifies which days of the month that the schedule will occur. Multiple days of the month can be specified. When multiple days are configured, each of them will cause the schedule to trigger. If a day-of-month is configured without configuring the month, weekday, hour and minute commands, the event will not execute.
Using the weekday command as well as the day-of-month command will cause the script to run twice. For example, consider that ‟today” is Monday January 1. If ‟Tuesday January 5” is configured, the script will run on Tuesday (tomorrow) as well as January 5 (Friday).
See the month, weekday, hour, and minute commands for more information.
The no form of this command removes the specified day-of-month from the list.
Specifies the day. The positive integers specify the day of the month counting from the first of the month. The negative integers specify the day of the month counting from the last day of the month. For example, configuring day-of-month -5, 5 in a month that has 31 days will specify the schedule to occur on the 27th and 5th of that month.
Integer values must map to a valid day for the month in question. For example, February 30 is not a valid date.
Specifies all days of the month.
end-time [date | day-name] time
[no] end-time
config>system>cron>sched
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command is used concurrently with type periodic or calendar. Using the type of periodic, end-time determines at which interval the schedule will end. Using the type of calendar, end-time determines on which date the schedule will end.
When no end-time is specified, the schedule runs forever.
Specifies the date to schedule a command.
Specifies the day of the week to schedule a command.
Specifies the time of day to schedule a command.
hour {..hour-number [..hour-number] | all}
[no] hour
config>system>cron>sched
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command specifies which hour to schedule a command. Multiple hours of the day can be specified. When multiple hours are configured, each of them will cause the schedule to trigger. The day-of-month or weekday must also be specified. All days of the month or weekdays can be specified. If an hour is configured without configuring the month, weekday, day-of-month and minute commands, the event will not execute. See the month, weekday, day-of-month, and minute commands for more information.
The no form of this command removes the specified hour from the configuration.
Specifies the hour to schedule a command.
Specifies all hours.
interval seconds
[no] interval
config>system>cron>sched
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command specifies the interval between runs of an event.
Specifies the interval, in seconds, between runs of an event.
minute {minute-number [..minute-number]| all}
[no] minute
config>system>cron>sched
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command specifies the minute to schedule a command. Multiple minutes of the hour can be specified. When multiple minutes are configured, each of them will cause the schedule to occur. If a minute is configured, but no hour or day is configured, the event will not execute. If a minute is configured without configuring the month, weekday, day-of-month and hour commands, the event will not execute.
See the month, weekday, day-of-month, and hour commands for more information.
The no form of this command removes the specified minute from the configuration.
Specifies the minute to schedule a command.
Specifies all minutes.
month {month-number [..month-number] | month-name [..month-name] | all}
no month
config>system>cron>sched
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command specifies the month when the event should be executed. Multiple months can be specified. When multiple months are configured, each of them will cause the schedule to trigger. If a month is configured without configuring the weekday, day-of-month, hour, and minute commands, the event will not execute.
See the weekday, day-of-month, hour and minute commands for more information.
The no form of this command removes the specified month from the configuration.
Specifies a month by number.
Specifies all months.
Specifies a month by name.
type {schedule-type}
config>system>cron>sched
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command specifies how the system should interpret the commands contained within the schedule node.
Specifies the type of schedule for the system to interpret the commands contained within the schedule node.
weekday {weekday-number [..weekday-number]|day-name [..day-name]| all}
no weekday
config>system>cron>sched
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command specifies which days of the week that the schedule will fire on. Multiple days of the week can be specified. When multiple days are configured, each of them will cause the schedule to occur. If a weekday is configured without configuring the month, day-of-month, hour, and minute commands, the event will not execute.
See the month, day-of-month, hour and minute commands for more information.
Using the weekday command as well as the day-of month command will cause the script to run twice. For example, consider that ‟today” is Monday January 1. If ‟Tuesday January 5” is configured, the script will run on Tuesday (tomorrow) as well as January 5 (Friday).
The no form of this command removes the specified weekday from the configuration.
Specifies a weekday by number.
Specifies a day by name.
Specifies all days of the week.