Chapter 10:
Appendix
164
v3.3-a 12/07/2022
V
S
C
-22201
CRITICAL*
Upstream GM in
Free-Running
187
Passive:
WR/PTP @
ifname
The GM is in this network is in Free-Running. This
passive timing source can become active only if no
better time source is available.
V
S
C
-21201
HO CHANGEOVER
Upstream GM in
free-running
187
BC:
Holdover
GM announce itself to be now in FR, if we have an
active HO we should exit through this state and fail
to the HO timing source
V
CS
-20501
CRITICAL
PLL delocked: L1-
Sync (Sync-E) error
248
BC:
WR/PTP @
ifname
For some unexpected reason the MPLL is not able
to follow the received frequency from L1-Sync
(Sync-E) and it has been delocked.
V
CS
-2
1
501
HO
CHANGEOVER
PLL delocked: L1-
Sync (Sync-E) error
187
BC:
Holdover
For some unexpected reason the MPLL is not able
to follow the received frequency from L1-Sync
(Sync-E) and it has been delocked.
If ready, the fast delock trigger launch the Holdover
V
S
C
-20211
*
WARNING
Locked: Upstream
device in holdover
187
BC:
WR/PTP @
ifname
The upstream BC is using its holdover, we have
nothing to do but to inform that our accuracy will
decrease over time and that at some point
(expiration of the HO), the upper BC will be
announced as FR and that we will thus be placed
into a critical state
V
S
C
-20110
WARNING
Locked: Time of
Day not available
on GM
6
BC:
WR/PTP @
ifname
The GM announce a problem that its ToD has not
been properly set since start. Probably due to an
NTP error, the GM will stay there until
restarting/re-evaluation of GM
V
S
C
-20111
WARNING
Locked:
Leap
seconds file on GM
has expired
6
BC:
WR/PTP @
ifname
The GM time is announced has valid but the
utc_offset is not valid. This means that leapsec file
has expired at GM
Содержание WR-Z16
Страница 2: ...Chapter 1 Introduction 2 v3 3 a 12 07 2022 ...
Страница 10: ...Chapter 1 Introduction 10 v3 3 a 12 07 2022 ...
Страница 72: ...Chapter 5 Timing 72 v3 3 a 12 07 2022 ...
Страница 148: ...Chapter 8 Device Maintenance 148 v3 3 a 12 07 2022 ...
Страница 159: ...Chapter 9 Troubleshooting 159 v3 3 a 12 07 2022 Severity info local0 rsyslog server1 IP local0 rsyslog server2 IP ...