.svg?sv=2022-11-02&spr=https&st=2024-12-23T09%3A31%3A08Z&se=2024-12-23T09%3A41%3A08Z&sr=c&sp=r&sig=IoiH6Pztj2KemMu0cRf90ZTBpbjfaDqiX%2F5CO%2Bx75z8%3D){kind=logo}
Setting the System Date and Time
- 25 Sep 2024
- 6 Minutes to read
- Contributors
- Print
- PDF
Setting the System Date and Time
- Updated on 25 Sep 2024
- 6 Minutes to read
- Contributors
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Accurate, precise date and time values are important when managing and troubleshooting a network. These values are used for time-stamping alarms and other functions.
The system date and time can be set manually, or you can have it set automatically via an NTP server.
Note: To avoid conflicts, only one NTP server can be used in a network.
Setting Date and Time Manually
▶ To set the date and time manually
Access the page System ▶ Configuration ▶ Time.
Specify the current date and time in the provided fields.
Select the Change to entered date and time if possible when applied box to allow a single manual update to the system date and time.
Note: When you click Apply, this box is reset to the unselected state.Click Apply.
For more information on specific parameters, refer to the table at the end of this section.
Setting Time Zones and Daylight Saving Time
The unit also provides for time zones and daylight saving time. For a list of time zones and rules for daylight saving time, refer to: http://www.worldtimezone.com/.
▶ To set the time zone and/or the daylight saving function
Access the page System ▶ Configuration ▶ Time.
Select Daylight saving time enable.
Complete the required fields, then click Apply.
For more information, refer to the following table.
Date and Time Parameters (System ▶ Configuration ▶ Time ▶ General)
| Parameter | Description |
|---|---|
| TAI offset | The offset to add to UTC time to convert to Temps Atomique International (TAI)—atomic international time. In early 1972, TAI was exactly 10 seconds ahead of UTC. From 1972 until June 30, 2015, 26 leap seconds were added to the difference. Since the last second was added on December 31, 2016, TAI has been exactly 37 seconds ahead of UTC. It is important that the TAI offset value be consistent throughout your network in order to ensure valid measurements and avoid synchronization issues. This is particularly true if Accedian products are being used with equipment from other vendors that support leap seconds. If there is a TAI mismatch between units, the one-way delay measurements will show an offset of one second. In most cases, it is preferable to allow the unit to update its TAI offset value through a firmware upgrade (during a maintenance window to minimize impact) instead of manually changing the value here. |
| Date and Time | If you are not using NTP, the date and time can be set manually by entering values here Select the Change to entered date and time if possible when applied box to allow a single manual update to the system date and time. When you click Apply, this box is reset to the unselected state. If the NTP Server Enable box is selected, and you manually update the system date and time, your changes will be pushed to all client devices immediately. |
| UTC offset | The offset from Coordinated Universal Time to apply to the time zone:
|
| Daylight saving time enable | Select to use daylight saving time (DST). Note: Services such as syslog that timestamp events with the current time and date are affected during DST transitions. As such, you may observe 60-minute gaps or duplicate timestamps around the time when the clock was changed. |
Examples of Setting the System Time
Setting the System Time for Montreal, Canada
| Parameter | Value |
|---|---|
| UTC offset | -5 |
| DST enable | Check |
| DST offset | 1 |
| DST start | Month=March, Week=2, Day=Sunday, Hour=2, Min=0 |
| DST end | Month=November, Week=1, Day=Sunday, Hour=2, Min=0 |
Setting the System Time for Wellington, New Zealand
| Parameter | Value |
|---|---|
| UTC offset | 12 |
| DST enable | Check |
| DST offset | 1 |
| DST start | Month=September, Week=5, Day=Sunday, Hour=2, Min=0 |
| DST end | Month=April, Week=1, Day=Sunday, Hour=3, Min=0 |
Setting Date and Time Using NTP
The Cisco Provider Connectivity Assurance Sensor Control stores a list of NTP servers that can be used to set the system date and time. You can add up to seven servers to the list and enable one or two of them (a primary and a secondary, if the primary is not available).
Note: If ARTS is not disabled the Sensor Control will raise a Time-of-day synchronization.
▶ To set the date and time using NTP
Access the page System ▶ Configuration ▶ Time.
Select a clock then select the NTP Enable option.
Note: Port ETH-2 cannot be used for NTP synchronization.Verify that the NTP server you want to use appears in the NTP Server List.
If not, add a new server by specifying its name or IP address in the NTP Server box then clicking Add.
Select a time server from the list, then click Apply.
▶ To delete an NTP server
Access the page System ▶ Configuration ▶ Time.
Select the NTP server's entry from the NTP Server List by clicking its name or IP address.
Tip: Do not click the check box.
Click Delete.
NTP Settings (System ▶ Configuration ▶ Time ▶ NTP)
| Parameter | Description |
|---|---|
| Client enable | Sets the system time automatically by polling an NTP server. Select a server from the list or add your own. |
| Synchronization status | The status of the synchronization. |
| Diffserv Code Point (DSCP) | When using NTP, the priority can be set in the Differentiated Services Code Point by making a selection in the drop-down list. |
| Priority Code Point | Acceptable values range from 0 to 7. |
| Time interval | When using NTP, the interval of time after which the unit synchronizes with the NTP server. Expressed in seconds. Acceptable values are integers that are factors of two (2) and range from 23 (8) to 28 (256). |
| Number of Messages | When using NTP, the number of synchronization messages exchanged with the NTP server during each time interval. Acceptable values range from 1 to 6. |
| NTP server List | One or two NTP servers can be enabled simultaneously. The Sensor Control will automatically update its date and time from one of the enabled NTP servers. If the NTP server being used is unreachable, the Sensor Control will attempt to contact the other enabled NTP server. |
| Hostname/Address | When using an NTP client instance, the name or the IP address of the NTP server to add. |
Viewing the Clock List
Clocks are automatically created and cannot be deleted.
▶ To view the clock list
Access the page System ▶ Configuration ▶ Time.
A list of all clocks associated with this instance of the Sensor Control is displayed.(Optional) To limit the view to only specific clocks, enter a value on which to filter, then click Search. You can filter by the Clock name or the Remote device.
For more information on specific parameters, refer to the table below.
Clock Parameters (System ▶ Configuration ▶ Time)
| Parameter | Description |
|---|---|
| Clock name | Name of the clock |
| Type | Local or Remote |
| Remote Device | Name of the remote device |
| General | Enabled or Disabled |
| NTP | Enabled or Disabled |
| PTP | Enabled or Disabled |
| ARTS | Enabled or Disabled |
| SYNCE | Enabled or Disabled |
PTP Transparent Clock (TC)
Precision Time Protocol (PTP) Transparent Clock (TC) Layer-2 is supported on Cisco Provider Connectivity Assurance Sensor SFP and Cisco Provider Connectivity Assurance Sensor Modules. PTP is always enabled and the correction field in the PTP message is updated with the device transient time.
© 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
Was this article helpful?