- play_arrow Overview
- play_arrow Precision Time Protocol
- play_arrow Precision Time Protocol Overview
- play_arrow Precision Time Protocol Clocks
- PTP Boundary Clock Overview
- Example: Configure PTP Boundary Clock
- Example: Configure PTP Boundary Clock With Unicast Negotiation
- Configure PTP TimeTransmitter Clock
- Configure PTP TimeReceiver Clock
- Example: Configure Ordinary TimeReceiver Clock With Unicast-Negotiation
- Example: Configure Ordinary TimeReceiver Clock Without Unicast-Negotiation
- PTP Transparent Clocks
- Configure PTP Transparent Clock
- play_arrow Precision Time Protocol Profiles
- play_arrow PHY Timestamping
- play_arrow Precision Time Protocol over Ethernet
- PTP over Ethernet Overview
- Guidelines to Configure PTP over Ethernet
- Configure PTP Dynamic Ports for Ethernet Encapsulation
- Configure PTP Multicast TimeTransmitter and TimeReceiver Ports for Ethernet Encapsulation
- Example: Configure PTP over Ethernet for Multicast TimeTransmitter, TimeReceiver, and Dynamic Ports
- play_arrow Precision Time Protocol Additional Features
- Precision Time Protocol (PTP) over Link Aggregation Group (LAG)
- Precision Time Protocol (PTP) Trace Overview
- Line Card Redundancy for PTP
- Timing Defects and Event Management on Routing Platforms
- SNMP MIB for Timing on Routing Platforms
- PTP Passive Port Performance Monitoring on PTX10004 and PTX10008 Devices
-
- play_arrow Global Navigation Satellite System (GNSS)
- play_arrow GPS Systems on Routing Platforms
- play_arrow Integrated GNSS on Routing Platforms
- play_arrow GNSS Configuration for Routers Using External GNSS Receiver
- play_arrow Assisted Partial Timing Support (APTS) on Routing Platforms
-
- play_arrow Synchronous Ethernet
- play_arrow Synchronous Ethernet Overview
- play_arrow Synchronous Ethernet on 10-Gigabit Ethernet MIC
-
- play_arrow Clock Synchronization
- play_arrow Clock Synchronization Concepts
- play_arrow Clock Synchronization for ACX Series Routers
- play_arrow Clock Synchronization for MX Series Routers
- play_arrow Clock Synchronization for PTX Series Routers
- play_arrow Centralized Clocking
-
- play_arrow Hybrid Mode
- play_arrow Hybrid Mode Overview
- play_arrow Hybrid Mode and ESMC Quality-Level Mapping
- Configure Hybrid Mode and ESMC Quality-Level Mapping Overview
- Configure Hybrid Mode with Mapping of the PTP Clock Class to the ESMC Quality-Level
- Configure Hybrid Mode with a User-Defined Mapping of the PTP Clock Class to the ESMC Quality-Level
- Example: Configure Hybrid Mode and ESMC Quality-Level Mapping on ACX Series Router
- Example: Configure Hybrid Mode and ESMC Quality-Level Mapping on MX240 Router
-
- play_arrow Configuration Statements and Operational Commands
- play_arrow Appendix
NTP Time Servers
The IETF defined the Network Time Protocol (NTP) to synchronize the clocks of computer systems connected to each other over a network. Most large networks have an NTP server that ensures that time on all devices is synchronized, regardless of the device location. If you use one or more NTP servers on your network, ensure you include the NTS server addresses in your Junos OS configuration.
When configuring the NTP, you can specify which system on the network is the authoritative time source, or time server, and how time is synchronized between systems on the network. To do this, you configure the router, switch, or security device to operate in one of the following modes:
Client mode—In this mode, the local router or switch can be synchronized with the remote system, but the remote system can never be synchronized with the local router or switch.
Symmetric active mode—In this mode, the local router or switch and the remote system can synchronize with each other. You use this mode in a network in which either the local router or switch or the remote system might be a better source of time.
Symmetric active mode can be initiated by either the local or the remote system. Only one system needs to be configured to do so. This means that the local system can synchronize with any system that offers symmetric active mode without any configuration whatsoever. However, we strongly encourage you to configure authentication to ensure that the local system synchronizes only with known time servers.
Broadcast mode—In this mode, the local router or switch sends periodic broadcast messages to a client population at the specified broadcast or multicast address. Normally, you include this statement only when the local router or switch is operating as a transmitter.
Server mode—In this mode, the local router or switch operates as an NTP server.
In NTP server mode, the Junos OS supports authentication as follows:
If the NTP request from the client comes with an authentication key (such as a key ID and message digest sent with the packet), the request is processed and answered based on the authentication key match.
If the NTP request from the client comes without any authentication key, the request is processed and answered without authentication.
Configure NTP Time Server and Time Services
When you use NTP, configure the router or switch to operate in one of the following modes:
Client mode
Symmetric active mode
Broadcast mode
Server mode
- Configure the Router or Switch to Operate in Client Mode
- Configure the Router or Switch to Operate in Symmetric Active Mode
- Configure the Router or Switch to Operate in Broadcast Mode
- Configure the Router or Switch to Operate in Server Mode
Configure the Router or Switch to Operate in Client Mode
To configure the local router or switch to operate in client mode, include the
server
statement and other optional statements at the [edit
system ntp]
hierarchy level:
[edit system ntp] server address <key key-number> <version value> <prefer>; authentication-key key-number type type value password; trusted-key[key-numbers];
Specify the address of the system acting as the time server. You must specify an address, not a hostname.
To include an authentication key in all messages sent to the time server, include the
key option. The key corresponds to the key number you specify in
the authentication-key
statement, as described in .
By default, the router or switch sends NTP version 4 packets to the time server. To set the NTP version level to 1, 2, or 3, include the version option.
If you configure more than one time server, you can mark one server preferred by including the prefer option.
The following example shows how to configure the router or switch to operate in client mode:
[edit system ntp] authentication-key 1 type md5 value "$ABC123"; server 10.1.1.1 key 1 prefer; trusted-key 1;
Configure the Router or Switch to Operate in Symmetric Active Mode
To configure the local router or switch to operate in symmetric active mode, include the
peer
statement at the [edit system ntp]
hierarchy
level:
[edit system ntp] peer address <key key-number> <version value> <prefer>;
Specify the address of the remote system. You must specify an address, not a hostname.
To include an authentication key in all messages sent to the remote system, include the
key option. The key corresponds to the key number you specify in
the authentication-key
statement.
By default, the router or switch sends NTP version 4 packets to the remote system. To set the NTP version level to 1, 2 or 3, include the version option.
If you configure more than one remote system, you can mark one system preferred by including the prefer option:
peer address <key key-number> <version value> prefer;
Configure the Router or Switch to Operate in Broadcast Mode
To configure the local router or switch to operate in broadcast mode, include the
broadcast
statement at the [edit system ntp]
hierarchy
level:
[edit system ntp] broadcast address <key key-number> <version value> <ttl value>;
Specify the broadcast address on one of the local networks or a multicast address assigned to NTP. You must specify an address, not a hostname. If the multicast address is used, it must be 224.0.1.1. Multicast protocols PIM and IGMP should be enabled on the NTP client facing interfaces in order to facilitate the device to transmit NTP packets over multicast address 224.0.1.1. Run the following commands to do so:
set protocols igmp interface <interface_name> static group 224.0.1.1 set protocols pim rp local address <interface_ip> set protocols pim interface <interface_name> mode sparse-dense
NTP over multicast is not supported within the routing instance on the device.
To include an authentication key in all messages sent to the remote system, include the
key option. The key corresponds to the key number you specify in the
authentication-key
statement.
By default, the router or switch sends NTP version 4 packets to the remote system. To set the NTP version level to 1, 2, or 3, include the version option.
Configure the Router or Switch to Operate in Server Mode
In server mode, the router or switch acts as an NTP server for clients when the clients are configured appropriately. The only prerequisite for “ server mode” is that the router or switch must be receiving time from another NTP peer or server. No other configuration is necessary on the router or switch.
When configuring the NTP service in the management VRF (mgmt_junos
), you
must configure at least one IP address on a physical or logical interface within the
default routing instance and ensure that this interface is up in order for the NTP service
to work with the mgmt_junos VRF.
To configure the local router or switch to operate as an NTP server, include the
following statements at the [edit system ntp]
hierarchy level:
[edit system ntp] authentication-key key-number type type value password; server address <key key-number> <version value> <prefer>; trusted-key [key-numbers];
Specify the address of the system acting as the time server. You must specify an address, not a hostname.
To include an authentication key in all messages sent to the time server, include the
key option. The key corresponds to the key number you specify in
the authentication-key
statement.
By default, the router or switch sends NTP version 4 packets to the time server. To set the NTP version level to 1,or 2, or 3, include the version option.
If you configure more than one time server, you can mark one server preferred by including the prefer option.
The following example shows how to configure the router or switch to operate in server mode:
[edit system ntp] authentication-key 1 type md5 value "$ABC123"; server 192.168.27.46 prefer; trusted-key 1;
Starting unos OS Evolved release version 24.2R1, the following options are added to configure the NTS feature:
[edit system ntp] nts { local-certificate <certificate-id of local certificate>; trusted-ca (trusted-ca-group <trusted ca-group name> | trusted-ca-profile <ca-profile name>); } [edit system ntp server <server>] nts remote-identity { hostname <FQDN of server>; distinguished-name (container <container-string> | wildcard <wild-card string>); }