Installation and User Manual
EtherHaul
1200™
EH-INST-02, Issue 4.0
Page 111
The configuration for this scenario is:
Local EtherHaul 1200
Default>show ref-clock
ref-clock host prio : 255
ref-clock host status : backup-1
ref-clock host ql-actual : 11
ref-clock host ql-config : 11
ref-clock host ql-mode : disable
ref-clock host ssm-cvid : none
ref-clock eth1 prio : 200
ref-clock eth1 status : active
ref-clock eth1 ql-actual : 2
ref-clock eth1 ql-config : 2
ref-clock eth1 ql-mode : disable
ref-clock eth1 ssm-cvid : none
Remote EtherHaul 1200
Default>show ref-clock
ref-clock host prio : 255
ref-clock host status : active
ref-clock host ql-actual : 11
ref-clock host ql-config : 11
ref-clock host ql-mode : disable
ref-clock host ssm-cvid : none
ref-clock eth0 prio : 100
ref-clock eth0 status : down
ref-clock eth0 ql-actual : 15
ref-clock eth0 ql-config : 14
ref-clock eth0 ql-mode : enable
ref-clock eth0 ssm-cvid : none
Figure
7-19
illustrates a SyncE scenario in which there is a holdover situation due to line
failure:
Because of the line failure, the local EtherHaul 1200 does not receive timing
information from PRC. The local EtherHaul therefore switches to holdover
mode, maintains the timing information it received previously over Eth1,
and distributes this information with its own ql (ql 11).
The remote EtherHaul 1200 receives and is locked on its Eth0 source and
distributes timing information from this source to its interfaces.
