System Management
7750 SR OS Basic System Configuration Guide Page 211
performed by either speeding up or slowing down the clock.
• In order to facilitate proper operation once the standby CPM takes over from the active
CPM it is required that the time on the secondary CPM is synchronized with the clock of
the active CPM.
• In order to avoid the generation of too many events/trap the NTP module will rate limit
the generation of events/traps to three per second. At that point a single trap will be
generated that indicates that event/trap squashing is taking place.
SNTP Time Synchronization
For synchronizing the system clock with outside time sources, the 7750 SR OS includes a Simple
Network Time Protocol (SNTP) client. As defined in RFC 2030, SNTP Version 4 is an adaptation
of the Network Time Protocol (NTP). SNTP typically provides time accuracy within 100
milliseconds of the time source. SNTP can only receive the time 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.
SNTP 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.
In the 7750 SR OS, the SNTP client can be configured for either broadcast or unicast client mode.
To Next Page
Loading...
Need help?
General
