the validity of the leap second file needed to perform the conversion from UTC (NTP times-
cale) to TAI (PTP timescale) is detailed in the panel. A detailed explanation of the para-
meters is provided below:
OID Name Value Type Description
3.7120.x gm/info/xxx Specific information about the state of GM
timing source.
.
3.7120.0 Message <String> User friendly message that summarizes the current
state of the GM timing source.
3.7120.2 PPS Detec-
ted
• NONE
• PPS (Only)
• CLK (Only)
• PPS & CLK
Report the detection of external reference input on
the front panel.
3.7120.4 Leap
Second File
Expiration
Date
<String> Expiration date of the leap seconds files. If there is
more than one file, this will show the date that is fur-
ther in the future. The date format is YYYY-MM-DD
HH:MM:SS.
3.7120.5 Leap
Second File
Validity
<Bool>
• No
• Yes
“Yes” if the leap seconds file is valid. “No” if it is
expired or missing. See
"Update Leap Seconds
File" on page81
for updating this file.
5.6 NTP
This section is about the configuration and monitorization related to the NTP protocol.
Note: Periodic pooling of NTP offset: In the current version of WRZ-OS it is
recommended to set the NTP server in every node of the topology, either
GM or BC, to check the coherence of the timing reference.
5.6.1 Configuration
5.6.1.1 NTP Provider
The WRZ-OS allow the device to provide its time through NTP on the management inter-
faces using the following parameters:
OID Name Value Type Description
3.7005.x ntp/cfg/provider/xxx Configuration on how to provides NTP to
3rd party devices.
.
5.6 NTP
CHAPTER 5 • WR-Z16 User Manual Rev. v3.4
75
To Next Page
Loading...