Configuring Broadcast-Based Ntp Associates - Cisco NCS 5000 Series Manual

Implementing NTP
Command or Action
Example:
RP/0/RP0/CPU0:router(config-ntp)# peer
192.168.22.33
minpoll 8 maxpoll 12 source tengige
0/0/0/1
Step 5
Use one of the following commands:
• end
• commit
Example:
RP/0/RP0/CPU0:router(config-ntp)# end
or
RP/0/RP0/CPU0:router(config-ntp)# commit

Configuring Broadcast-Based NTP Associates

In a broadcast-based NTP association, an NTP server propagates NTP broadcast packets throughout a network.
Broadcast clients listen for the NTP broadcast packets propagated by the NTP server and do not engage in
any polling.
Broadcast-based NTP associations should be used when time accuracy and reliability requirements are modest
and if your network is localized and has a large number of clients (more than 20). Broadcast-based NTP
associations also are recommended for use on networks that have limited bandwidth, system memory, or CPU
resources. Time accuracy is marginally reduced in broadcast-based NTP associations because information
flows only one way.
Use the broadcast client command to set your networking device to listen for NTP broadcast packets
propagated through a network. For broadcast client mode to work, the broadcast server and its clients must
be located on the same subnet. The time server that is transmitting NTP broadcast packets must be enabled
on the interface of the given device using the broadcast command.
Purpose
Note
Saves configuration changes.
System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x
Configuring Broadcast-Based NTP Associates
To complete the configuration of a peer-to-peer association
between the router and the remote device, the router must
also be configured as a peer on the remote device.
• When you issue the end command, the system prompts you to
commit changes:
Uncommitted changes found, commit them before
exiting(yes/no/cancel)?
[cancel]:
◦ Entering yes saves configuration changes to the running
configuration file, exits the configuration session, and
returns the router to EXEC mode.
◦ Entering no exits the configuration session and returns the
router to EXEC mode without committing the configuration
changes.
◦ Entering cancel leaves the router in the current
configuration session without exiting or committing the
configuration changes.
• Use the commit command to save the configuration changes
to the running configuration file and remain within the
configuration session.
149