System Management Parameters
Page 230
7950 SR OS Basic System Configuration Guide
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 (one-shot), 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:
•
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 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.
Содержание 7950 XRS Series
Страница 8: ...Page 8 7950 SR OS Basic System Configuration Guide List of Tables...
Страница 10: ...Page 10 7950 SR OS Basic System Configuration Guide List of Figures...
Страница 14: ...Preface Page 14 7950 SR OS Basic System Configuration Guide...
Страница 46: ...VI Editor Page 46 7950 SR OS Basic System Configuration Guide...
Страница 76: ...File Management Tasks Page 76 7950 SR OS Basic System Configuration Guide...
Страница 78: ...File Command Reference Page 78 7950 SR OS Basic System Configuration Guide...
Страница 92: ...Basic Command Reference Page 92 7950 SR OS Basic System Configuration Guide show system candidate...
Страница 172: ...Basic CLI Commands Page 172 7950 SR OS Basic System Configuration Guide...
Страница 184: ...Configuration Notes Page 184 7950 SR OS Basic System Configuration Guide...
Страница 214: ...DNS Configuration Commands Page 214 7950 SR OS Basic System Configuration Guide...
Страница 220: ...Show Commands Page 220 7950 SR OS Basic System Configuration Guide...
Страница 494: ...System Commands Page 494 7950 SR OS Basic System Configuration Guide...
Страница 500: ...Standards and Protocols Page 500 Standards and Protocols...
Страница 502: ...Index Page 502 7950 SR OS Basic System Configuration Guide system parameters 252 system time elements 256 timing 294...