7210 SAS-MXP, R6, R12, S, SX, T BASIC SYSTEM
CONFIGURATION GUIDE RELEASE 22.9.R1
System management
from NTP servers; it cannot be used to provide time services to other systems. SNTP is a compact, client-
only version of NTP. SNTP does not authenticate traffic.
In the 7210 SAS software, the SNTP client can be configured in both unicast client modes (point-to-point)
and broadcast client modes (point-to-multipoint). SNTP should be used only at the extremities of the
synchronization subnet. SNTP clients should operate only at the highest stratum (leaves) of the subnet and
in configurations where no NTP or SNTP client is dependent on another SNTP client for synchronization.
SNTP time servers should operate only at the root (stratum 1) of the subnet and then only in configurations
where no other source of synchronization other than a reliable radio clock is available.
6.1.2.4 CRON
The CRON feature supports the SAA functions and time-based policy scheduling to meet time of day
requirements. CRON functionality includes the ability to specify the commands to be run, their scheduling,
including one-time only functionality (oneshot), interval and calendar functions, and the storage location for
the script output. CRON can also specify the relationship between input, output, and schedule. Scheduled
reboots, peer turn ups, service assurance agent tests, and OAM events, such as connectivity checks or
troubleshooting runs, can also be scheduled.
CRON features are saved to the configuration file.
CRON features run serially with at least 255 separate schedules and scripts. Each instance can support a
schedule where the event is repeatedly executed.
The following CRON elements are supported:
• action
This configures 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 that contains information about 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.
3HE 18197 AAAB TQZZA
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com/terms/.
247
SPACER TEXT
To Next Page
Loading...