This section describes how to configure static 1588v2 functions. You can specify the master and slave clocks manually, without using the BMC algorithm.
To manually determine the master/slave relationship between clock nodes within a network, run the ptp port-state command to set the status of 1588v2 interfaces on the nodes. Static clock source selection and dynamic BMC selection are two independent mechanisms. Static clock source selection has a higher priority than dynamic BMC selection.
The 1588v2 status needs to be specified on OC, BC, and TCandBC interfaces. The 1588v2 status is Premaster on TCs interfaces, including those on TCOC and TCandBC devices.
Typical static 1588v2 network with OC, BC, TC, and TCOC devices
The OC on the 1588v2 network shown in Figure 1 functions as the grandmaster to receive time signals provided by a BITS or GPS and sends 1588v2 packets carrying the time signals over the bearer network. TCs, including the TCOC, are core devices on the bearer network. TCs transparently transmit time information over the bearer network. The TCOC can also implement frequency synchronization. BCs at the edge of the bearer network send highly accurate time information carried in 1588v2 packets to wireless access devices, such as NodeBs and radio network controllers (RNCs).
Typical static 1588v2 network with TCandBC devices
All devices, including the NodeB, run 1588v2 on the network shown in Figure 2. ISP A's network contains the NodeB, OC2, and BC. OC2 is connected to BITS2 on ISP A's network. ISP A's network has no bearer network device. ISP A's network has no bearer network device. ISP A leases the bearer network that ISP B operates, and ISP B devices trace clock signals of BITS1. Time synchronization on ISP A's network is independent of that on ISP B's network. Devices on ISP A's and ISP B's networks support static 1588v2. The deployment is as follows: