Table of Contents
Advertisement
System Management Parameters
CRON
The CRON feature supports the Service Assurance Agent (SAA) functions as well as the ability to
schedule turning on and off policies to meet "Time of Day" requirements. CRON functionality
includes the ability to specify the commands that need to be run, when they will be scheduled,
including one-time only functionality (oneshot), interval and calendar functions, as well as where
to store the output of the results. In addition, CRON can specify the relationship between input,
output and schedule. Scheduled reboots, peer turn ups, service assurance agent tests and more can
all be scheduled with Cron, as well as OAM events, such as connectivity checks, or
troubleshooting runs.
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.
CRON features run serially with at least 255 separate schedules and scripts. Each instance can
support a schedule where the event is executed any number of times.
The following CRON elements are supported:
•
•
•
•
•
Page 182
Action — Parameters for a script including the maximum amount of time to keep the
results from a script run, the maximum amount of time a script may run, the maximum
number of script runs to store and the location to store the results.
Schedule — The schedule function 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).
Script — The script command opens a new nodal context which contains information on a
script.
Time Range — ACLs and QoS policy configurations may be enhanced to support time
based matching. CRON configuration includes time matching with the 'schedule' sub-
command. Schedules are based on events; time-range defines an end-time used as a match
criteria.
Time of Day — Time of Day (TOD) suites are useful when configuring many types of
time-based policies or when a large number of subscribers or SAPs require the same type
of TOD changes. The TOD suite may be configured while using specific ingress or egress
ACLs or QoS policies, and is an enhancement of the ingress and egress CLI trees.
7710 SR OS Basic System Configuration Guide
Advertisement
Table of Contents
