Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Timing and Synchronization Guide
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Assisted Partial Timing Support on ACX500 Routers

date_range 20-Dec-24

APTS which is a GNSS backed by PTP delivers accurate timing and synchronization in mobile backhaul networks. This topic talks about the APTS support on ACX500 routers.

On the ACX500 router, the APTS feature helps you to configure PTP timeReceiver ports on a GNSS grandmaster clock serving as the PTP timeTransmitter. APTS uses GNSS as the timeTransmitter time reference at cell site locations, or at an aggregation point close to the cell sites. APTS uses network-based timing distribution to assist and maintain the timing during holdover periods when GNSS is unavailable.

To support this feature on ACX500, you need an APTS node with GNSS source configured at the [edit chassis synchronization] hierarchy level and PTP boundary clock configured at the [edit protocols ptp] hierarchy level as shown below:

GNSS configuration

content_copy zoom_out_map
[edit chassis] 
  synchronization {
            network-option <option-1 | option-2>;
            port gnss {
                  client {
                       constellation <constellation-type>;
                      anti-jamming;
                   }
            }
           esmc-transmit {
                 interface <interfaces-name>;
           }
     }

PTPoE Configuration

content_copy zoom_out_map
[edit protocols] 
 ptp {
            clock-mode boundary;
            slave {
                      interface <slave-ptp-ifl> {
                      multicast-mode {
                             transport ieee-802.3 [ link-local ] ;
                      }
                  }
           }
          master {
                interface <master-ptp-ifl> {
                    multicast-mode {
                    transport ieee-802.3 [ link-local ] ;
                  }
               }
        }

PTPoIP Configuration

content_copy zoom_out_map
[edit protocols] 
clock-mode boundary;
    slave {
            interface <logical-interface-name> {
            unicast-mode {
                transport ipv4;
                clock-source <remote-master-ip-address> local-ip-address <local-slave-ip-address>;
            }
        }
    }
    master {
        interface <logical-interface-name>{
            unicast-mode {
                transport ipv4;
                clock-client <remote-slave-ip> local-ip-address  <local-master-ip>;
            }
        }
    }
   }

The priority of clock source would be GNSS first and then PTP.

You can use the show ptp lock-status detail, show chassis synchronization extensive, and show chassis synchronization gnss extensive show commands to monitor and troubleshoot the configurations.

footer-navigation