
User Guide for FibeAir® IP-20 All-Outdoor Products, CeraOS 10.5
Page 678 of 825
Ceragon Proprietary and Confidential
number of configured clock-interfaces = 14
|=============================================================|
| Slot | Port | Type | Trail Radio | Source-Type | SSM-Admin |
|=============================================================|
| 1 | 1 | Ethernet | | System Clock | Off |
| 1 | 2 | Ethernet | | System Clock | Off |
| 1 | 3 | Ethernet | | System Clock | Off |
| 2 | 1 | Radio | | System Clock | On |
| 2 | 2 | Radio | | System Clock | On |
|=============================================================|
To display the current system clock status, enter the following command in root
view:
root> platform sync clu-state show
The following is a sample system clock status display output:
CLU is in Free-running mode
20.8
Configuring 1588 Transparent Clock (CLI)
IP-20 uses 1588v2-compliant Transparent Clock to counter the effects of delay
variation. Transparent Clock measures and adjusts for delay variation, enabling
the IP-20 to guarantee ultra-low PDV.
A Transparent Clock node resides between a master and a slave node, and
updates the timestamps of PTP packets passing from the master to the slave to
compensate for delay, enabling the terminating clock in the slave node to remove
the delay accrued in the Transparent Clock node. The Transparent Clock node is
itself neither a master nor a slave node, but rather, serves as a bridge between
master and slave nodes.
Note that in release G10.5:
•
1588 TC is not supported when Master-Slave communication is using the IPv6
transport layer.
•
1588 TC cannot be used on 1+1 HSB links.
•
1588 TC is not supported with Frame Cut-Through.
Note:
Make sure to enable Transparent Clock on the remote side of the link
before enabling it on the local side.
To configure Transparent Clock:
1 Add the port receiving synchronization from the customer side as a Sync
source, with Sync Interface Priority 1. See
Configuring an Ethernet Interface as
a Synchronization Source (CLI)
2 Add a radio interface as a Sync source, with lower priority than the port
receiving synchronization from the customer side. See
Interface as a Synchronization Source (CLI)
3 On the remote side of the radio link, add the radio interface facing the local
device as a Sync source, with Sync Interface Priority 1. See