- Print
- PDF
# Overview
Cisco Provider Connectivity Assurance Sensors support the use of the Network Time Protocol (NTP) to synchronize the unit’s local clock with an external time reference. When all sensors are synchronized to the same time reference, one-way delay measurements can be performed using performance monitoring technologies such as Ethernet OAM (Y.1731), TWAMP, or PAA.
Example 1: Two assurance sensors synchronized with an NTP server
In this example, two assurance sensors are synchronized with an NTP server available in the network.
On both assurance sensors, the NTP Client is enabled and configured to communicate with the NTP server. A logical interface (IP address) must be configured on the port used to connect to the NTP server. Take note that if the assurance sensor has multiple IP interfaces, the configuration of a static route may be required to define which interface will be used to reach the NTP server.
The following figure illustrates this example:
In this example, the existing in-band management interface on each device will be used to support NTP synchronization. If needed, refer to the product documentation for more information on how to configure IP interfaces.
Configure NTP on the assurance sensors
For both the NODE and the NID, if the port connected to the NTP server is a network port or the management port, configure a logical interface on this port so that it becomes part of the NTP server’s network.
Proceed as follows to enable and configure the NTP client on each assurance sensor:
- Access the System ▶ Configuration ▶ Interface page on Assurance Sensor
Click Add to create a new interface.
If using Manual Configuration, configure the IP parameters for this interface.
Complete the required fields, then click Apply.
Configure the NODE and NID for NTP Synchronization
Individually configure both the NODE and then the NID to synchronize with an NTP server.
To configure the NODE and NID for NTP synchronization
Access System ▶ Configuration ▶ Time.
Check the NTP enable option. This will open a subsection below where an NTP server can be defined.
In the NTP Server field, enter the IP address to the NTP server (192.168.50.70) and click the Add button. This will add the NTP server to the NTP Server List above. Optionally, a second NTP server may be added as a backup.
Select (check) the NTP server you just added in the NTP Server List, make sure the High Resolution Sync option is enabled, and click Apply.
Verify the synchronization status message in the page. Eventually, it will indicate that the NTP client is synchronized with the NTP server.
Repeat these steps to configure the NTP client in Assurance Sensor 2.
Example 2: Assurance Sensor 1 configured as an NTP server for Assurance Sensor 2
In this example, the Assurance Sensor 1 is synchronized with the NTP server as we saw in the previous example. However, it is also configured to act as an NTP server for Assurance Sensor 2.
The following figure illustrates this example:
The first part of this example involves synchronizing the NODE with an NTP server, as explained in Example 1: One NID and One NODE Synchronized with an NTP Server.
Note: If the port connected to the NTP server is a network port or the management port, configure a logical interface on this port so that it becomes part of the NTP server’s network.
Once the NODE has been synchronized, it must then be configured as an NTP server. Once again, you may need to add a logical interface so the NID's NTP client becomes part of the network where the NODE's NTP server resides.
Proceed as follows to enable the NTP server option on Assurance Sensor 1 and synchronize Assurance Sensor 2 to it:
- Access the System ▶ Configuration ▶ Time page on Assurance Sensor 1. The NTP Client should be configured as in the previous example.
- Check the NTP server enable option, uncheck the High Resolution Sync option, and click Apply.
- Access the System ▶ Configuration ▶ Time on Assurance Sensor 2 and configure the NTP client as explained in the previous example, but this time, use the IP address of Assurance Sensor 1 (10.10.1.11) to define the NTP server.
© 2024 Cisco and/or its affiliates. All rights reserved.
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms
For legal information about Accedian Skylight products, please visit: Accedian legal terms and tradmarks