Configuring Network Synchronization

(1)

(2)

The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

(3)

3.1 Configuring Frequency Synchronization 9 3.1.1 Configuring Interfaces for Frequency Synchronization 9 3.1.1.1 Configuring Synchronous Ethernet 9 3.1.1.2 Enabling 2 MHz Sync Clock Input on NPU 11 3.1.1.3 Disabling 2 MHz Sync Clock Output on NPU 11 3.1.1.4 Configuring PTP for Frequency Synchronization (G.8265.1

Profile) 12

3.1.2 Managing Sync Sources 18

3.1.2.1 Adding a Sync Source 18

3.1.2.2 Deleting a Sync Source 19

3.1.2.3 Modifying the Sync Source 20

3.1.2.4 Switching the Sync Source 21

3.1.2.5 Clearing a Switch Command 22

3.1.3 Configuring Parameters of Network Frequency

Synchronization 23

3.1.4 Enabling Network Frequency Synchronization 23

3.2 Configuring Time Synchronization 24

3.2.1 Prerequisites 24

3.2.1.1 Configuring Frequency Synchronization 24 3.2.1.2 Configuring ETU2 B or ETU3 for 1588 Operation Mode 24 3.2.1.3 Configuring Ethernet Traffic Settings 24 3.2.2 Configuring PTP for Time Synchronization 25 3.2.2.1 Configuring PTP Protocol Settings and PTP Clock Ports 25

3.2.2.2 Configuring PTP Link Delays 32

3.2.2.3 Configuring PTP Interfaces 33

3.2.2.4 Disable 1588 Functionality 35

3.2.2.5 Raw Timestamp Logging 35

(4)

Configuring Network Synchronization Using MINI-LINK Craft

4 Configuration and Operations Tasks 39

4.1 Configuring Frequency Synchronization 39 4.1.1 Configuring Interfaces for Frequency Synchronization 39 4.1.1.1 Configuring Synchronous Ethernet 39 4.1.1.2 Enabling/Disabling 2 MHz Sync Clock Input on NPU 41 4.1.1.3 Enabling/Disabling 2 MHz Sync Clock Output on NPU 42 4.1.1.4 Changing between 2 MHz and 2 Mbps for Sync Clock Input

and Output 42

4.1.1.5 Configuring PTP for Frequency Synchronization 43

4.1.2 Managing Sync Sources 52

4.1.2.1 Adding a Sync Source 52

4.1.2.2 Deleting a Sync Source 57

4.1.2.3 Modifying the Sync Source 58

4.1.2.4 Switching the Sync Source 58

4.1.2.5 Clearing Switch Command 59

4.1.3 Configuring Network Frequency Synchronization 59 4.1.3.1 Enabling/Disabling Squelch on E1 Interface for E1 Used

as Clock Output 61

4.1.3.2 Enabling/Disabling Squelch on All E1 Interfaces on a Unit 62 4.1.3.3 Enabling/Disabling Squelch on MS/RS Interface 63 4.1.3.4 Configuring PDH-IME for Network Frequency

Synchronization 64

4.2 Configuring Time Synchronization 65

4.2.1 Prerequisites 65

4.2.1.1 Configuring Frequency Synchronization 65 4.2.1.2 Configuring ETU2 B or ETU3 for 1588 Operation Mode 65 4.2.1.3 Configuring Ethernet Traffic Settings 66 4.2.2 Configuring PTP for Time Synchronization 66 4.2.2.1 Configuring PTP Protocol Settings 66

4.2.2.2 Configuring PTP Clock Ports 68

4.2.2.3 Configuring PTP Link Delays 70

4.2.2.4 Configuring PTP Interfaces 71

4.2.2.5 Configuring Unicast and Unicast Master for PTP Clock Port 72 4.2.2.6 Configuring Multicast for PTP Clock Port 73

(5)

1 Introduction

This instruction describes how to configure network synchronization in MINI-LINK TN, using either CLI commands or MINI-LINK Craft.

Figure 1 shows the configuration workflow for the Network Frequency Synchronization function.

(6)

(7)

Figure 2 shows the configuration workflow for the Network Time Synchronization function.

(8)

(9)

1.1 Description

Network synchronization is a generic concept that depicts how to distribute a common time, frequency, or both, to all elements in a network. Network synchronization provides a synchronized network where all the NEs in a network are synchronized to the same source.

There are two main methods for frequency synchronization: • Layer 1 based frequency synchronization

Synchronization over Radio Link, PDH, SDH, 2 MHz, or Synchronous Ethernet.

• Packet based synchronization for frequency in G.8265.1 profile

Time synchronization can be provided with packet based synchronization in G.8275.1 or in Default PTP profile.

The IEEE 1588-2008 standard defines the Precision Time Protocol (PTP), which is the basis for packet based synchronization.

For more information, see Technical Description, Reference [15] and Network

Synchronization Guidelines, Reference [10].

1.2 Planning Advice

To ensure proper node and network function, all configuration activities must be planned in advance by skilled personnel.

Before configuring network synchronization, consider the following planning advice:

• Read through the appropriate section for network planning in Network

• Read through all applicable sections and make sure referenced documents are available. All pages in MINI-LINK Craft are described in detail in

MINI-LINK Craft User Interface Descriptions, Reference [9].

• Make sure you have access to the NE using MINI-LINK Craft. For more information, see Accessing a Network Element, Reference [1].

1.3 Limitations

(10)

2 Prerequisites

This section includes information about required preparation before configuring network synchronization.

2.1 Safety Information

Make sure that the information in the following documents has been understood by the persons performing the procedures:

• Personal Health and Safety Information, Reference [11]

• System Safety Information, Reference [14]

• Supplementary Safety Information for MINI-LINK, Reference [13]

2.2 Required Hardware

For the required hardware, see Technical Description, Reference [15].

2.3 Required Licenses and Software

Layer 1 based frequency synchronization is a basic feature in MINI-LINK TN and does not require a specific license. See the compatibility documents in the Planning folder of the MINI-LINK TN library.

Note: To access an NE remotely through MINI-LINK Craft, a MINI-LINK Craft license is required on that specific NE.

Packet based synchronization for frequency and phase/time requires a license according to Table 1.

Table 1 Required Licenses

Profile PTP device type Required license

G.8265.1 Packet Master Basic Sync or Enh Sync G.8265.1 Packet Slave Basic Sync or Enh Sync

and Sync Distr IEEE 1588v2 Default OC, BC, or TC Enh Sync

G.8275.1 OC or BC Enh Sync

For information about how to install a license, see Installing and Managing

(11)

2.4 Required Documentation

Read through this document. Make sure that referenced documentation is available during the configuration process by having the electronic CPI library available on your PC. See Library Description, Reference [7] for information about how to make the CPI library available.

(12)

(13)

Configuring Network Synchronizati

on Using CLI

3 Configuration and Operations Tasks

To configure Network Synchronization parameters using CLI commands, perform the tasks described in the following sections.

Note: The configuration can be prepared offline and transferred to the node in the form of a CLI script, either remotely (when modifying the configuration for an installed node) or on site (when installing a new node).

The following additional information is applicable when using CLI commands: • How to start a CLI session and navigate between different command

modes, see CLI User Guide, Reference [3].

• How to prepare a CLI script, see Preparing a CLI Script File Offline, Reference [12].

• How to transfer a CLI script on site, see Transferring a CLI Script File on

Site, Reference [16].

• For a detailed description of each CLI command, see CLI Descriptions, Reference [2].

3.1 Configuring Frequency Synchronization

3.1.1 Configuring Interfaces for Frequency Synchronization

3.1.1.1 Configuring Synchronous Ethernet

This example script configures the LAN interface for Synchronous Ethernet: Note: Enabling Flow Control on a Synchronous Ethernet port may disturb

the sync function since PAUSE frames may cause SSM frames to be discarded. The sync function will recover automatically when SSM frame transmission is restored.

(14)

! on selected interface:

! (config)#interface ethernet-eps <R/S/P> {lan | wan | lan-dcn} ! This example switches to LAN 1/2/3:

interface ethernet-eps 1/2/3 lan ! Connect the interface to a port:

! (config-eth)#[no] usage {bridge-port <PORT>|layer1} ! This example connects the interface to port 1: usage bridge-port 1

! Switch to the submode (config-lan): ! (config-eth)#lan

lan

! Enable the interface: ! (config-lan)#[no] shutdown no shutdown

! Enable or disable sync unsupported or Ethernet down alarms:

! (config-lan)#[no] alarm-enable [sync-unsupported | ethernet-down] ! This example enables sync unsupported alarms:

alarm-enable sync-unsupported

! Activate or deactivate flow control on the port: ! (config-lan)#[no] flowcontrol [autoneg]

! This example deactivates flow control on the port: no flowcontrol

! Set the Ethernet speed:

! (config-lan)#speed {auto-detect|half-duplex10|half-duplex100|// ! half-duplex1000|full-duplex10|full-duplex100|full-duplex1000|// ! full-duplexSlave100|full-duplexMaster100|//

! full-duplexSlave1000|full-duplexMaster1000}

! This example sets the speed to 1000 Mbps Full Duplex Master: speed full-duplexMaster1000

! Enable or disable synchronous Ethernet: ! (config-lan)#[no] sync-enable [noESMC] ! This example enables synchronous Ethernet: sync-enable

! Display the current mode settings: ! (config-lan)#show current

! This example displays the changes made above: show current

! Exit the (config-lan) submode: ! (config-lan)#exit

exit

(15)

! (config-eth)#exit exit

3.1.1.2 Enabling 2 MHz Sync Clock Input on NPU

This example script enables the 2 MHz Sync clock input on an NPU: ! In Global Configuration mode, enable or disable the 2 MHz Sync ! clock input:

! (config)#[no] network-synch node-clock ! This example enables the clock input: network-synch node-clock

! Exit the Global Configuration mode: ! (config)#exit

exit

! Display the currently running configuration file: ! (config)#show running-config <MAP ENTRY>

! The output from this command can be very long.

! This example displays the 26th map entry (Network Frequency Synchronization co ! of the running configuration file:

show running-config 26

! Switch to Global Configuration mode: ! #config

config

3.1.1.3 Disabling 2 MHz Sync Clock Output on NPU

(16)

! In Global Configuration mode, enable or disable the 2 MHz Sync ! clock output:

! (config)#[no] network-synch node-clock ! This example disables the clock output: no network-synch node-clock

exit

! This example displays the 26th map entry (Network Frequency Synchronization conf ! of the running configuration file:

config

3.1.1.4 Configuring PTP for Frequency Synchronization (G.8265.1 Profile) It is recommended to read about packet-based frequency synchronization (G.8265.1 Profile) in Network Synchronization Guidelines before starting a configuration.

Note: Using packet-based frequency synchronization (G8265.1 Profile) excludes the usage of time synchronization.

The two example scripts configure a Packet Master and a Packet Slave node for PTP-based frequency synchronization using the G.8265.1 Telecom profile. In Packet Master mode, the node distributes the clock signal of the Network Frequency Synchronization function. In Packet Slave mode, the node recovers frequency information from the PTP packets and presents the recovered clock as a candidate towards the Frequency Synchronization function.

In G.8265.1 profile, MINI-LINK TN operates as an Ordinary Clock and has one Clock Port configured over a transport VLAN, that is, SVLAN in provider mode, and CVLAN in customer bridge mode). This transport VLAN tag is configured with the vlancommand under the clock-port settings. In provider bridge mode, that is, when the VLAN refers to the SVLAN, an applicable CVLAN can also be specified for a given clock-port. The inner-tag command under the clock-port settings can be used to configure such CVLAN besides the SVLAN. For more details on Provider Bridge mode, see Technical Description, Reference [15]. The PTP messages are sent unicast with UDP/IPv4 over Ethernet encapsulation.

(17)

The interface/bridge port over which PTP packets enter or exit the node is not explicitly configured, but is determined by the VLAN topology and STP if applicable.

Note: Ensure that all member interfaces of the transport VLAN, over which the remote Packet Master or Slave is reachable, are PTP time stamping capable.

3.1.1.4.1 Configuring Packet Master

This example script configures a Packet Master that distributes the frequency of its node clock to one or more Packet Slaves over PTP.

The NE must be configured for synchronizing its frequency to a Layer1 Sync Source. See configuration examples in Section 3.1 on page 9.

! Configure the Master Node: ! (config)#ptp

! Remove all previous clock-ports: no clock-port <NAME>

no clock

! Set the priority values of the local clock: priority1 128

priority2 128

! Configure clock to profile G.8265.1 and as Grand Master (GM): clock g82651 grandmaster

! Configure the PTP domain: domain 4

! Configure Netsync function and add PTP-sync port: sync-port disabled

network-synch-assistance enabled ! Set the link delay:

interface 1/4/2 0

link-delay-compensation 1/4/2 0

! Create new clock port: clock-port pm1

! Set IP address for the clock port:

interface udpipv4 192.168.3.17 255.255.255.0 ! Configure the DSCP field in the IP header: dscp 46

(18)

! Assign VLAN to the clock port: vlan 6

! Configure VLAN priority: vlan-priority 7

! Configure the delay mechanism for the port: delay-mechanism e2e

! Disable inner VLAN tagging: no inner-tag

! Enable PTP on the port: enabled

! Return to Global Configuration mode: exit

exit

Use the following commands to check the connectivity between the Packet Master and the Packet Slave. The output of the commands is given here as an example.

show ptp peers SLAVES:

Local Port Name Peer Address Announce Interval Synch Interval

---pm1 192.168.3.16 0 -4

MASTERS:

Local Port Name Peer Address Grandmaster ClockID Accessible Timestamping Bridgeport

---show ptp clock-port configured ports:

---+---+---+---+---+---+---+ Name |Admin State |Oper State |Port Role |Bridge port |Vlan |Local address | ---+---+---+---+---+---+---+

pm1 |UP |UP |master |0 |7 |192.168.3.17 |

show ptp clock-port <NAME> statistics

RX TX delta_RX delta_TX Announce : 134 0 134 0 Synch : 4237 0 4237 0 Follow up : 0 0 0 0 Delay req : 0 4236 0 4236 Delay resp : 4236 0 4236 0 Pdelay req : 0 0 0 0 Pdelay resp: 0 0 0 0 Signaling : 6 6 6 6

3.1.1.4.2 Configuring Packet Slave

The Packet Slave recovers the frequency of the Packet Master based on the rate of PTP packets. The recovered frequency is offered as a candidate to the Network Frequency Synchronization function through the so called PTP Sync Port.

(19)

! Configure the Slave Node: ! (config)#ptp

! Remove all previous clock-ports no clock-port <NAME>

no clock

priority2 128

! Configure clock to profile G.8265.1 and as slave only: clock g82651 slave-only

! Configure Netsync function and add PTP-sync port: sync-port enabled

network-synch-assistance disabled ! Set the link delay:

interface 1/4/2 0

link-delay-compensation 1/4/2 0

! Create new clock port: clock-port ps1

! Set IP address for the clock port:

interface udpipv4 192.168.3.16 255.255.255.0 ! Configure the DSCP field in the IP header: dscp 46

! Configure VLAN priority: vlan-priority 7

! Configure the delay mechanism for the port: delay-mechanism e2e

! Disable inner VLAN tagging: no inner-tag

! Enable PTP on the port: enabled

(20)

unicast-configuration

! Change default settings if needed: announce-interval 1 announce-timeout 3 delay-resp-interval -3 delay-resp-timeout 3 duration 250 query-interval 0 sync-interval -4 sync-timeout 3 wait-to-restore-time 5 unicast-master m1 address udpipv4 192.168.3.17 local-priority 6 enabled

exit exit exit

(21)

---MASTERS:

Local Port Name Peer Address Grandmaster ClockID Accessible Timestamping Bridgeport ---cp1 192.168.3.17 00:00:00:00:00:00:00:00 Yes Supported 1 show ptp clock Ptp Clock: ---Clock-identity: 04:4E:06:FF:FE:82:8B:46

Clock state: LOCKED

RTC Time: 1444664854 sec, 2015-10-12T15:46:58Z Locked state counter: 1

All time spent in locked state: 1792 sec, 0 days 0 hours 29 min 52 sec Last time spent in locked state: 1792 sec, 0 days 0 hours 29 min 52 sec Master changed counter: 1

Clock-servo state: locked (5)

Clock-servo pdv: forward 4ns, backward 3ns Clock-servo flags: 0x00000000

show ptp clock-port configured ports:

---+---+---+---+---+---+---+---+ Name |Admin State |Oper State |Port Role |Bridge port |Vlan |Dest. address |Interface | ---+---+---+---+---+---+---+---+

cp1 |UP |UP |slave |1 |1 |01-1B-19-00-00-00|1/7/3 |

show ptp clock parent-ds parent-ds: ---parent-port-identity: AA:BB:11:22:33:44:55:66 parent-statistic-validity: false observed-parent-offset-scaled-logvar: 0 observed-parent-phase-change-rate: 0 gm-identity: AA:BB:11:22:33:44:55:66 gm-priority1: 2 gm-priority2: 5 gm-clock-class: 187

gm-clock-accuracy: unknown-accuracy (0xFE) gm-offset-scaled-logvar 0x6400

To synchronize the node to the PTP recovered frequency, add the PTP Sync Port as a Sync Source. See Section 3.1.2.1 on page 18 for more configuration options.

! Add PTP Sync Port as Sync Source.

! The name of the PTP Sync Port is 1/<S>/20, where <S> is ! the slot position of the NPU.

(22)

Note: If Ethernet Switch Protection is turned on, a PTP Sync Port exists for each NPU. At any time, however, only the NPU with the active switch has its PTP Sync Port operational. Therefore, to protect the PTP recovered frequency, configure both PTP Sync Ports as Sync Source.

3.1.2 Managing Sync Sources

3.1.2.1 Adding a Sync Source

This example script adds a sync source:

Note: There can be a maximum of four sync sources added to the NE. When using ETU3 or ETU2 B for Synchronous Ethernet and adding an interface as sync source, only the NS port can be added to the nominee list. For example, if 1/4/4 and 1/4/4 NS are available, only 1/4/4 NS can be added.

! In Global Configuration mode, select an interface as a sync source and enter ! the (config-synch-nominee) submode:

! (config)#[no] network-synch nominee <IFNAME>

! This example selects E1 1/11/2B as a synch source: network-synch nominee 1/11/2B

! This example selects LAN 1/6/3 as a synch source for SyncE: network-synch nominee "1/6/3 NS"

! Set the priority for the synchronization source: ! (config-synch-nominee)#priority <INTEGER>

! This example sets the priority to 2: priority 2

! Assign a quality level to the sync source:

! (config-synch-nominee)#assigned-qlevel <QUALITYLEVEL>

! This example assigns the sync source the quality level PRC: assigned-qlevel 1

! Set the holdoff time in 100 millisecond units:

! (config-synch-nominee)#[no] holdoff-time <TIME-IN-MS> ! This example sets the holdoff time to 500 ms:

holdoff-time 5

! Assure that a synchronization input signal is stable ! before it is used:

! (config-synch-nominee)#wait-to-restore-time <TIME-IN-SECONDS> ! This example waits 10 seconds before using the

! synchronization input signal: wait-to-restore-time 10

! Set whether the sync source should be excluded from the synchronization ! source selection process:

(23)

! This example sets the sync source not to be excluded: no lockout

! Enable or disable the use of signal degrade: ! (config-synch-nominee)#[no] signal-degrade ! This example enables the use of signal degrade: signal-degrade

! Exit the (config-synch-nominee) submode: ! (config-synch-nominee)#exit

exit

config

3.1.2.2 Deleting a Sync Source

(24)

! In Global Configuration mode, select an interface already configured ! as a sync source:

! This example deletes E1 1/11/2B as a synch source: no network-synch nominee 1/11/2B

exit

config

3.1.2.3 Modifying the Sync Source

This example script modifies a sync source:

! In Global Configuration mode, select an interface already configured as ! a sync source and enter the (config-synch-nominee) submode:

! This example selects the E1 1/11/2B as a synch source: network-synch nominee 1/11/2B

! Set the priority for the synchronization source: ! (config-synch-nominee)#priority <INTEGER>

! This example sets the priority to 1: priority 1

! Assign a quality level to the sync source:

! (config-synch-nominee)#assigned-qlevel <QUALITYLEVEL>

! This example assigns the sync source the quality level SSU-B: assigned-qlevel 3

! Set the holdoff time in 100 millisecond units:

! (config-synch-nominee)#[no] holdoff-time <TIME-IN-MS> ! This example sets the holdoff time to 700 ms:

holdoff-time 7

! Assure that a synchronization input signal is stable ! before it is used:

! (config-synch-nominee)#wait-to-restore-time <TIME-IN-SECONDS> ! This example waits 10 seconds before using the

(25)

! synchronization input signal: wait-to-restore-time 10

! Set whether the sync source should be excluded from the synchronization ! source selection process:

! (config-synch-nominee)#[no] lockout

! No example given because we do not want the sync source to be excluded. ! Enable or disable the use of signal degrade:

! (config-synch-nominee)#[no] signal-degrade

! This example disables the use of signal degrade: no signal-degrade

! Exit the (config-synch-nominee) submode: ! (config-synch-nominee)#exit

exit

config

3.1.2.4 Switching the Sync Source

(26)

! In Global Configuration mode, perform a forced switch to the selected ! synchronization source:

! (config)#[no] network-synch forced-switch {<IFNAME> | holdover} ! Note: Select a source other than the active Sync Source.

! This example performs a forced switch to holdover: network-synch forced-switch holdover

exit

config

3.1.2.5 Clearing a Switch Command

This example script clears a switch command:

! In Global Configuration mode, clear the switch to a synchronization ! source:

! (config)#[no] network-synch forced-switch {<IFNAME> | holdover}

! Note: To clear a switch command a Forced switch or Holdover switch must ! be active.

! This example clears the switch to holdover: no network-synch forced-switch

exit

(27)

3.1.3 Configuring Parameters of Network Frequency Synchronization

This example script configures Network Frequency Synchronization and Node Squelching:

! In Global Configuration mode, set the synch selection mode:

! (config)#[no] network-synch selection-mode {ql-enabled | ql-disabled} ! This example sets the synch selection mode to QL-Enabled:

network-synch selection-mode ql-enabled

! Perform a forced switch to the selected synchronization source: ! (config)#[no] network-synch forced-switch {<IFNAME> | holdover} ! No example given since set synch selection mode is set

! in the step above. ! Set node squelching:

! (config)#[no] network-synch squelch ! This example enables node squelching: network-synch squelch

exit

config

3.1.4 Enabling Network Frequency Synchronization

This command enables Network Frequency Synchronization:

! In Global Configuration mode, enable Network Frequency Synchronization: ! (config)#[no] network-synch enable

! This example enables Network Frequency Synchronization: network-synch enable

(28)

3.2 Configuring Time Synchronization

This section describes the configuration steps required to set up packet-based time synchronization with the IEEE 1588-2008 Precision Time Protocol (PTP) either in G.8275.1 or Default PTP profile.

For a detailed overview of packet-based synchronization and PTP, see Network

3.2.1 Prerequisites

3.2.1.1 Configuring Frequency Synchronization

Time Synchronization function relies on a stable frequency signal provided by the Frequency Synchronization function. Therefore, first configure frequency synchronization locked to a PRC-traceable source over a Layer 1 (physical) interface. See Section 3.1 on page 9 for details.

3.2.1.2 Configuring ETU2 B or ETU3 for 1588 Operation Mode

The following command enables PTP time stamping support on the LAN interfaces of an ETU2 B or ETU3 plug-in unit.

Before configuring an ETU2 B or ETU3 to use the 1588 profile, ensure that all PDH-IMEs on the ETU are disconnected from the Ethernet service and have no E1s assigned. For information on how to configure PDH-IME, see Configuring

Ethernet over PDH, Reference [4].

Note:

• The ETU performs a cold restart when its profile is changed, resulting in a short traffic disturbance on its LAN ports.

• PDH-IME and 1588 capability profiles are mutually exclusive for a specific ETU board. However, ETUs in various capability profile (either PDH-IME or 1588) can co-exist in an NE.

! In Global Configuration mode, select the profile for ETU2 B or ETU3: ! (config)#etub profile { 1588 | pdhime } <SLOT>

! This example selects the IEEE 1588v2 profile for an ! ETU2 B or ETU3 in slot 1/4:

etub profile 1588 4

3.2.1.3 Configuring Ethernet Traffic Settings

An existing Ethernet configuration is necessary for packet based synchronization configurations, that is, the Ethernet configuration of the interfaces must be created first (including switch port/Layer1 connections,

(29)

VLAN assignments, and so on), before the packet based synchronization configuration is created.

For information on how to configure Ethernet, see the Ethernet configuration documents.

3.2.2 Configuring PTP for Time Synchronization

It is recommended to read about Time Synchronization Technologies in

Network Synchronization Guidelines before starting a configuration.

3.2.2.1 Configuring PTP Protocol Settings and PTP Clock Ports

Packet based time synchronization is supported in G.8275.1 profile or in Default PTP profile.

3.2.2.1.1 Configuring in G.8275.1 Profile

MINI-LINK TN supports the Telecom Boundary Clock (T-BC) mode for phase/time sync using the G.8275.1 profile. In T-BC (boundary) mode, the NE can have multiple clock ports, each of which is explicitly assigned to a bridge port.

PTP packets can be sent with or without VLAN tag, and with forwardable (01-1B-19-00-00-00) or non-forwardable (01-80-C2-00-00-0E) destination MAC address.

Note:

• For PTP over LAG, the clock ports must be configured on individual LAG member ports. On each member port of a LAG, clock ports must have the same parameters. Best Master Clock (BMC) algorithm selects the link to be used by PTP messages.

• The NE must be configured for synchronizing its frequency to a Layer 1 Sync Source. See configuration examples in Section 3.1 on page 9.

The following example script configures the NE as a T-BC with two clock ports: • cp1: on bridge port 1 connected to LAN 1/4/2

• cp2: on bridge port 2 connected to WAN 1/11/119

Both clock ports use the Ethernet multicast encapsulation for PTP messages and the BMC algorithm determines the role (master, slave, or passive) for the clock ports. See Figure 3.

(30)

17399 Traffic Links PTP Connections L1 Frequency

S

Slave Master

M

MINI-LINK

BC

MINI-LINK

BC

PRC

M

S

M

WAN

1/11/119

1/4/2

LAN

MAC

D9:16

Figure 3 Nodes in Phase/Time Synchronization

The NE must be configured for synchronizing its frequency to a Layer1 Sync Source. See configuration examples in Section 3.1 on page 9.

! Configure the NE for Boundary Clock mode: ! (config)#ptp

no clock

! Set the Priority2 value of the local clock: priority2 128

! Configure clock to profile G.8275.1, T-BC: clock g82751 boundary multicast bmc

network-synch-assistance enabled

! Set the holdover timeout value for the clock: holdover-timeout 3000

! Set the clock level local priority value: clock-local-priority 128

(31)

interface 1/4/2 250 interface 1/11/119 0

! Configure link delay compensation, MMU in slot 6: link-delay-compensation 1/4/2 0

link-delay-compensation 1/6/1 0 telecom

! Configure Clock Port 1: clock-port cp1

! Use forwardable destination MAC: interface ieee8023 forwardable

! Assign bridge port to the clock port: bridge-port 1

! Change default settings if needed: vlan-priority 7 delay-mechanism e2e local-priority 128 not-slave false enabled multicast-configuration announce-interval -3 announce-timeout 3 sync-interval -4 min-delay-req-interval -4 exit exit

! Use non-forwardable destination MAC: interface ieee8023 non-forwardable ! Assign bridge port to the clock port: bridge-port 2

! Send packets without VLAN tag: no vlan

! Change default settings if needed: not-slave false local-priority 200 delay-mechanism e2e enabled multicast-configuration announce-interval -3

(32)

announce-timeout 3 sync-interval -4

min-delay-req-interval -4

exit exit

3.2.2.1.2 Configuring in Default PTP Profile

MINI-LINK TN supports the Boundary Clock (BC) and Transparent Clock (TC) modes for phase/time sync using the IEEE 1588v2 Default profile. In BC mode the NE can have multiple clock ports, each of which is explicitly assigned to a bridge port and a VLAN.

Configuring Boundary Clock Note:

• The NE must be configured for synchronizing its frequency to a Layer 1 Sync Source. See configuration examples in Section 3.1 on page 9.

• For PTP over LAG, the clock ports must be configured on individual LAG member ports. To protect the PTP communication it is recommended to configure a clock port on each member port of a LAG and clock ports must have the same parameters. Best Master Clock (BMC) algorithm selects the link to be used by PTP messages.

The following example script configures the NE as a BC with two clock ports: • cp1: on bridge port 1 connected to LAN 1/4/2

• cp2: on bridge port 2 connected to WAN 1/11/119

Both clock ports use the Ethernet multicast encapsulation for PTP messages and the BMC algorithm determines the role (master or slave) for the clock ports. ! Configure the NE for Boundary Clock mode:

! (config)#ptp

no clock

(33)

! Configure clock to profile IEEE 1588v2, BC, multicast, and BMC: clock ieee1588v2 boundary multicast bmc

! Configure delay asymmetry compensation: interface 1/4/2 250

interface 1/11/119 0

! Configure link delay compensation, MMU in slot 6: link-delay-compensation 1/4/2 0

link-delay-compensation 1/6/1 0 telecom

interface ieee8023

! Change default settings if needed: vlan-priority 7 delay-mechanism e2e enabled multicast-configuration announce-interval 0 announce-timeout 3 sync-interval -4 min-delay-req-interval -4 exit exit

interface ieee8023

! Change default settings if needed: vlan-priority 7

delay-mechanism e2e enabled

(34)

multicast-configuration announce-interval 0 announce-timeout 3 sync-interval -4

min-delay-req-interval -4

exit exit

(35)

---cp1 192.168.3.16 0 -4

MASTERS:

Local Port Name Peer Address Grandmaster ClockID Accessible Timestamping Bridgeport ---show ptp clock

Ptp Clock:

---Clock-identity: 74:D0:DC:FF:FE:58:04:BE

Clock state: LOCKED

RTC Time: 1421243843 sec, 2015-01-14T13:56:48Z Locked state counter: 1

All time spent in locked state: 32 sec, 0 days 0 hours 0 min 32 sec Last time spent in locked state: 32 sec, 0 days 0 hours 0 min 32 sec Master changed counter: 1

Clock-servo state: locked (5)

Clock-servo pdv: forward 279ns, backward 278ns Clock-servo flags: 0x00000000

show ptp clock-port configured ports:

---+---+---+---+---+---+---+ Name |Admin State |Oper State |Port Role |Bridge port |Vlan |Local address | ---+---+---+---+---+---+---+

cp1 |UP |UP |uncalibr. |0 |7 | |

show ptp clock parent-ds parent-ds: ---parent-port-identity: 00:B0:AE:FF:FE:02:D9:16 parent-stats: 1 offset-scaled-logvar: 17408 phase-change-rate: 0 gm-identity: 00:B0:AE:FF:FE:02:D9:16 gm-priority1: 128 gm-priority2: 128 gm-quality-class: 84 gm-quality-accuracy: nanoSecond100 gm-quality-offset: 25600

Configuring Transparent Clock

This example script configures the NE as an end-to-end Transparent Clock. The NE must be configured for synchronizing its frequency to a Layer1 Sync Source. See configuration examples in Section 3.1 on page 9.

(36)

! Configure the NE for Transparent Clock mode: ! (config)#ptp

no clock

! Configure clock to profile IEEE 1588v2, transparent: clock ieee1588v2 transparent

! Configure delay asymmetry compensation value (in nanoseconds): interface 1/4/2 250

interface 1/11/103 0 interface 1/11/119 0

! Configure link delay compensation, MMUs in slot 5 and 6: link-delay-compensation 1/4/2 0

link-delay-compensation 1/5/1 0 telecom link-delay-compensation 1/6/1 0 telecom

exit

3.2.2.2 Configuring PTP Link Delays

3.2.2.2.1 Configuring Manual Link Delay Compensation

The following example script can be used to set the link delay, when multiple links are grouped (LAG or Radio Link Bonding), to provide equal delays on all links within the group. A similar script can be used for radio links.

(37)

! In Global Configuration mode, change to (config-ptp) submode: ptp

! In (config-ptp) submode, set the link delay on the desired interface:

! (config-ptp)#link-delay-compensation <NAME> <LINK_DELAY_COMPENSATION> [basic | ! The following example sets 100 ns link delay on the 1/2/1 interface:

link-delay-compensation 1/2/1 100 ! Exit the (config-ptp) submode: exit

3.2.2.2.2 Configuring Radio Link PTP Operation Mode

The following example script can be used to switch between radio link PTP operation mode. This command is not applicable on LAN interfaces.

For more details on Radio Link PTP operation modes, see Network

! In (config-ptp) submode, set the Radio Link operation mode on the desired inte ! (config-ptp)#link-delay-compensation <NAME> <LINK_DELAY_COMPENSATION> [basic | ! The following example sets automatic link delay compensation on the 1/2/1 inte link-delay-compensation 1/2/1 0 telecom

! Exit the (config-ptp) submode: exit

The configured Radio Link operation mode can be verified using the show ptp configurationcommand, by looking at the link-delay-compensation rows. The actual performance of a radio link can be verified based on the RL performance column in the output of the show ptp interface command. This RL performance column reflects whether a specific radio link interface is above (Appropriate) or below (Not appropriate) the 100 Mbps limit, and therefore whether or not it complies to the Time Error specification described in

Network Synchronization Guidelines, Reference [10].

3.2.2.3 Configuring PTP Interfaces

3.2.2.3.1 Configuring Link Delay Asymmetry Compensation

The following example script can be used to set the link delay asymmetry compensation on an Ethernet LAN port when the delay is different in forward and backward directions because of differences in cable lengths or signal propagation velocity.

(38)

! In (config-ptp) submode, set the link delay asymmetry on the desired interface: ! (config-ptp)#interface <NAME> <LINK_DELAY_ASYMMETRY_COMPENSATION>

! The following example sets 100 ns link delay asymmetry on the 1/2/1 interface: interface 1/2/1 100

! Exit the (config-ptp) submode: exit

3.2.2.3.2 Enabling PTP support on RL-IME (NPU3 C or NPU3 D)

Note: The configuration steps in this section are only required for RL-IME 102, 103, and 104 on NPU3 C and NPU3 D, if connected to an MMU2 D/H/K. On NPU3 C and NPU3 D, for RL-IMEs 100 and 101 the system allocates timestamping capability automatically. For the single-link RL-IMEs 102, 103, and 104, the timestamping capability can be assigned manually as described in this section.

Note: The RL-IME must be assigned to a Packet Link and the corresponding WAN interface connected to a bridge port before PTP support can be enabled on it. For more information, see Configuring Native Ethernet, Reference [5].

Once PTP support is enabled, it is retained until the RL-IME is disconnected from the Packet Link.

Use the following command to verify timestamping capability on a certain RL-IME group. The output of the command is given here as an example.

! In Global Configuration mode, switch to the (config-ptp) submode: ! (config)#ptp

ptp

! The following command displays the PTP time stamping capable interfaces: ! (config)#show ptp interface

show ptp interface

Timestamping capable interfaces:

Interface Bridgeport Clockport Admin state Operational state PTP capable PTP supported RL pe

1/7/3 1 UP UP Yes Yes n/a

1/7/102 10 UP UP Yes No Not a

PTP support can be enabled for RL-IME interfaces that are PTP capable, but not currently have PTP support. In the following example, 1/7/102 is such an interface.

If an interface is not PTP capable (HW limitation), or PTP support is already enabled, the following configuration steps are not needed for that interface.

(39)

! Enable PTP time stamping support on an RL-IME interface of NPU3 C or NPU3 D: ! (config-ptp)#interface <R/S/P> ptp-support [abort]

! This example enables PTP support on RL-IME 102: interface 1/7/102 ptp-support

!

! Commit all outstanding PTP support enable requests: ! (config-ptp)#commit-ptp-interface-cold-restart

! Warning: This command results in a cold start of the NPU and ! traffic disturbance:

commit-ptp-interface-cold-restart

3.2.2.4 Disable 1588 Functionality

This example script disables the PTP clock.

Before executing this script, all clock ports must be removed. ! Disable the 1588 functionality and restore default settings: ! (config)#ptp

no clock exit

3.2.2.5 Raw Timestamp Logging

This section describes raw timestamp logging, which can be used for troubleshooting the packet-based synchronization network performance. To obtain timestamp information from the PTP engine, perform the following steps:

1. Start timestamp logging in CLI using the log-clock-servo command. 2. Retrieve saved timestamps using Bug Reporting Tool in MINI-LINK Craft. The log-clock-servo command records the timestamps of the transmitted and received 1588 packets.

Synopsis

log-clock-servo <FREQUENCY> <SECONDS>

Command Mode

(40)

Operands

FREQUENCY Specifies the frequency of the logging. Every nth sample is saved. The valid range is 1–1000.

SECONDS Specifies the time duration for the logging in seconds. The valid range is 0–100000. The value 0 stops the logging.

The recorded samples are available in the local.log.cslog file generated by the Bug Reporting Tool within the tn_local_logs_*.tgz file. The maximum size of the log is 20000 timestamp pairs. The local.log.cslog file contains the timestamps in a compressed format as follows:

The log is split into sections. Each section starts with a header row that contains absolute PTP time in seconds. Within each section, each row represents a PTP message (either SYNC or DELAY_RESP) and contains the following timestamp information:

• Seconds relative to the absolute time in the header row • Nanoseconds

The format of the sections in the log file is as follows: H x x x x <PTPtimeSec>

x <TxTsDeltaSec> <RxTsDeltaSec> <MsgType> <SeqID> <TxTsNanoSec> <RxTsNanoSec> The following values are possible for <MsgType>:

0 SYNC

9 DELAY_REQ/RESP

Timestamp values can be calculated as follows:

OrigTS: <PTPtimeSec> + <TxTsDeltaSec> + <TxTsNanoSec> RxTS: <PTPtimeSec> + <RxTsDeltaSec> + <RxTsNanoSec> H 0 2 50 1 1194819669

3 2 3 0 1753 784991127 134367512

Example 1 Header row and message row

The calculated timestamps for the example above are as follows: OrigTS: 1194819671.784991127 s

RxTS: 1194819672.134367512 s 3.2.2.6 1PPS Output Configuration

This example script enables the 1PPS (one pulse per second) output interface for PTP synchronization. The 1PPS output interface is available through the Sofix connector B out port.

(41)

This is only applicable for NPU3 D.

! In Global Configuration mode, change to Privileged Exec mode: exit

! Enable the 1PPS output interface:

! #debug ieee1588 one-pps {enabled | disabled}

! The following example enables the 1PPS output interface: debug ieee1588 one-pps enabled

! Change back to Global Configuration mode: config

(42)

(43)

Configuring Network Synchronizatio

n Using MINI-LINK Craft

4 Configuration and Operations Tasks

To configure Network Synchronization parameters using MINI-LINK Craft, perform the tasks described in the following sections.

Note: The configuration can be performed either remotely or on site.

The following additional information is applicable when using MINI-LINK Craft: • How to access the node using MINI-LINK Craft, see Accessing a Network

Element, Reference [1].

• How to navigate in MINI-LINK Craft, see MINI-LINK Craft User Guide, Reference [8].

• For a detailed description of the parameters on each MINI-LINK Craft page, see MINI-LINK Craft User Interface Descriptions, Reference [9].

4.1 Configuring Frequency Synchronization

4.1.1 Configuring Interfaces for Frequency Synchronization

4.1.1.1 Configuring Synchronous Ethernet

This procedure describes how to configure the LAN interface for Synchronous Ethernet.

1. In the Management Tree, under the LAN Interfaces, right-click the LAN Interface that you want to configure.

2. Point to Configure and click General.

(44)

Figure 4 The LAN Configuration Page

3. Under Interface Usage, in the Connect To list, select a port. 4. Under General, modify the following settings: Admin Status,

Notifications, and Ethernet Sync Support Notifications.

5. Under Ethernet Parameters, modify the following settings: Default User Priority (only for variant LAN v.1-3), Auto Negotiation, MDI-MDIX, Flow Control, Sync Mode, and Speed.

(45)

Note:

• If Speed is changed from 1000 Mbit/s Full Duplex Master to 1000 Mbit/s Full Duplex Slave or from 100 Mbit/s Full Duplex Master to 100 Mbit/s Full Duplex Slave, or the other way around, it has to be done in two steps: first, select Disable and click the save icon, then select the new speed and click save. Enabling Flow Control on a Synchronous Ethernet port may disturb the sync function since PAUSE frames may cause SSM frames to be discarded. The sync function will recover automatically when SSM frame transmission is restored. • Speed can be set if you are using electrical interfaces.

Having Link Lost Forwarding activated may cause the PHY to shut down (mute) and consequently stop synchronous Ethernet over that link.

Note: The Ethernet Synchronization Messaging Channel (ESMC) Layer 2 Control Protocol (L2CP) needs to be set to Peer, see MINI-LINK Craft

User Interface Descriptions, Reference [9].

4.1.1.2 Enabling/Disabling 2 MHz Sync Clock Input on NPU

Enable or disable 2 MHz Sync clock input on an NPU interface as follows: 1. In the Management Tree, right click the NPU.

MINI-LINK Craft displays the NPU Configuration page.

Figure 5 The NPU Configuration Page

3. Under Sync, enable the 2 MHz Sync Input/Output by setting the Use Front Port 2MHz Sync Input/Output for the port supporting Clock Input.

(46)

Note: For Clock Input to work, the E1 interface cannot be a part of any other service, like Traffic Routing, SNCP, Loop, BERT, Ethernet Bridge, IMA Link or G.804. If the E1 is part of any of the services, an error message will appear stating the reasons why the E1 cannot be used as Clock Input.

4. Select Save on the Toolbar to apply changes. 4.1.1.3 Enabling/Disabling 2 MHz Sync Clock Output on NPU

Enable or disable 2 MHz Sync clock output on an NPU interface as follows: 1. In the Management Tree, right click the NPU.

MINI-LINK Craft displays the NPU Configuration page.

Figure 6 The NPU Configuration Page

3. Under Sync, enable the 2 MHz Sync Input/Output by setting the Use Front Port 2MHz Sync Input/Output for the port supporting Clock Output. Note: For Clock Output to work, the E1 interface must not be a part

of any other service like: Traffic Routing, SNCP, Loop, BERT, Ethernet Bridge, IMA Link or G.804. If the E1is part of any of the services, an error message will appear stating the reasons why the E1 cannot be used as Clock Output.

4. Select Save on the Toolbar to apply changes.

4.1.1.4 Changing between 2 MHz and 2 Mbps for Sync Clock Input and Output Change between 2 MHz and 2 Mbps for sync clock input and output on an NPU1 D as follows:

1. In the Management Tree, right click the NE.

(47)

MINI-LINK Craft displays the Configure Network Sync page.

Figure 7 The Configure Network Sync Page

3. Under Sync Ports, select 2 MHz or 2 Mbps in the Format list. 4. Click Save on the toolbar to apply changes.

4.1.1.5 Configuring PTP for Frequency Synchronization

This section describes the configuration steps required to set up packet-based frequency synchronization with the IEEE 1588-2008 Precision Time Protocol (PTP).

Note: Using packet-based frequency synchronization (G8265.1 Profile) excludes the usage of time synchronization.

The two examples configure a Packet Master and a Packet Slave node for PTP-based frequency synchronization using the G.8265.1 Telecom profile. In Packet Master mode, the node distributes the clock signal of the Network Frequency Synchronization function. In Packet Slave mode, the node recovers frequency information from the PTP packets and presents the recovered clock as a candidate towards the Frequency Synchronization function.

In G.8265.1 profile, MINI-LINK TN operates as an Ordinary Clock and has one Clock Port configured over a transport VLAN (that is, SVLAN in provider mode, and CVLAN in customer bridge mode). The PTP messages are sent unicast with UDP/IPv4 over Ethernet encapsulation.

The interface/bridge port over which PTP packets enter or exit the node is not explicitly configured, but is determined by the VLAN topology and STP if applicable.

(48)

Note: Ensure that all member interfaces of the transport VLAN, over which the remote Packet Master or Slave is reachable, are PTP time stamping capable.

For a detailed overview of packet-based synchronization and PTP, see Network

4.1.1.5.1 Configuring PTP Protocol Settings for Packet Master Configure PTP Protocol Settings as follows:

1. In the Management Tree, right-click the NE and select Configure > Sync Standard > IEEE 1588 PTP Sync > Protocol Settings.

(49)

Figure 8 The PTP - Configure Protocol Settings Page with Example Settings for a Packet Master

2. Set the General parameters: • PTP Profile

• Device Type

• Message Transport Mode • Clock Role

(50)

• Domain

3. Set the Priority parameters: • Priority1

• Priority2

4. Set the Alarms and Notifications parameters: • Free Running Mode

• Traceability Lost • Hold Over Entered • Clock Protection Lost • Incompatible Hardware • Switch Parent Clock

5. Click Save on the Toolbar to apply the changes. 4.1.1.5.2 Configuring PTP Protocol Settings for Packet Slave

Configure PTP Protocol Settings as follows:

1. In the Management Tree, right-click the NE and select Configure > Sync Standard > IEEE 1588 PTP Sync > Protocol Settings.

(51)

Figure 9 The PTP - Configure Protocol Settings Page with Example Settings for a Packet Slave

2. Set the General parameters: • PTP Profile

• Device Type

• Message Transport Mode • Clock Role

(52)

3. Set the Priority parameters: • Priority1

• Priority2

4. Set the Alarms and Notifications parameters: • Free Running Mode

• Traceability Lost • Hold Over Entered • Clock Protection Lost • Incompatible Hardware • Switch Parent Clock

5. Click Save on the Toolbar to apply the changes. 4.1.1.5.3 Configuring PTP Clock Ports

Configure PTP Clock Ports as follows:

1. In the Management Tree, right-click the NE and select Configure > Sync Standard > IEEE 1588 PTP Sync > Clock Ports.

MINI-LINK Craft displays the PTP - Configure Clock Ports page.

(53)

2. Under Clock Ports, create a clock port or select an existing one to configure and set the following parameters:

• Name • Enable

• Protocol(Encapsulation Type) • Connected Bridge Port • VLAN ID • VLAN Priority • VLAN Tagging • Oper Status • Identity • State • IP Type

3. Set the IP Address parameters of the selected clock port: • IP Address

• Subnet Mask • Default Gateway • DSCP

4. Set the Customer VLAN parameters of the selected clock port: • Tagging

• C-VLAN ID • C-VLAN Priority

5. Click Save on the Toolbar to apply the changes. 4.1.1.5.4 Configuring PTP Interfaces

The configuration steps in this section are only required for RL-IME 102, 103, and 104 on NPU3 C and NPU3 D, if connected to an MMU2 D/H/K.

Configure PTP Interfaces as follows:

1. In the Management Tree, right-click the NE and select Configure > Sync Standard > IEEE 1588 PTP Sync > PTP Interfaces.

(54)

MINI-LINK Craft displays the PTP - Configure PTP Interfaces page.

Figure 11 The PTP - Configure PTP Interfaces Page

2. Set the desired Asymmetry Compensation value for each interface. 3. The timestamping capability for the single-link RL-IMEs 102, 103, and

104 can be assigned by selecting the PTP Supported check-box of the interface.

Note:

• The RL-IME must be assigned to a Packet Link and the corresponding WAN interface connected to a bridge port before PTP support can be enabled on it. For more information, see

Configuring Native Ethernet, Reference [5].

• Once PTP support is enabled, it is retained until the RL-IME is disconnected from the Packet Link.

• For RL-IMEs 100 and 101, on NPU3 C and NPU3 D, the system allocates timestamping capability automatically. 4. Click Set PTP Interfaces Supported.

If PTP support was changed, the NE performs a cold restart. 4.1.1.5.5 Configuring Unicast and Unicast Master for PTP Clock Port

Configure Unicast and Unicast Master for PTP Clock Port as follows:

1. In the Management Tree, right-click the NE and select Configure > Sync Standard > IEEE 1588 PTP Sync > Clock Ports.

MINI-LINK Craft displays the PTP - Configure Clock Ports page. 2. Under Operations, click Configure Unicast/Unicast Master.

(55)

MINI-LINK Craft displays the Clock Port - Configure Unicast/Unicast Master page.

Figure 12 The Clock Port - Configure Unicast/Unicast Master Page

3. Under Unicast Configuration, set the General parameters: • Query Interval

• Duration(sec)

• Wait to Restore(min)

4. Under Unicast Configuration, set the Announce Messages parameters: • Request Interval

• Numbers of Timeout

5. Under Unicast Configuration, set the Synchronized Messages parameters:

• Request Interval • Numbers of Timeout

6. Under Unicast Configuration, set the Delay Response Messages parameters:

• Request Interval • Numbers of Timeout

(56)

7. Under Unicast Masters, create a Unicast Master or select an existing one to configure and set the following parameters:

• Name • Protocol • IP Address • Gateway • Local Priority • Enable • Accessible • Clock ID • TSU Capable • Bridge Port • Address Type

8. Click Save on the Toolbar to apply the changes.

4.1.2 Managing Sync Sources

4.1.2.1 Adding a Sync Source

This section describes how to add a sync source. Different scenarios apply for Synchronous Ethernet, 2 MHz, and E1/STM-1/Sync over Radio Link.

(57)

(58)

(59)

(60)

Figure 16 Adding a PTP Clock as Sync Source

Add a sync source as follows:

2. Select Configure > Sync Standard > Network Sync.

MINI-LINK Craft displays the Configure Network Sync page. 3. Under Sync Sources, click to add a new sync source.

Note: If there are less than four Sync Sources added on the list it is possible to add a new Sync Source.

4. In the new entry, set the new sync source as follows: • Set the Priority.

• Select the unit by choosing it in the Module.

• Select the interface of the unit by selecting it in the Interface. • Select the quality level by selecting it in the Assigned Quality.

(61)

Note: Set Assigned Quality when SSM Support is not available. • Specify Hold Off Time(ms) and Wait To Restore Time(s).

• Set Include Signal Degrade and Locked Out. 5. Select Save on the Toolbar to apply changes. 4.1.2.2 Deleting a Sync Source

Figure 17 shows how to delete a sync source.

Figure 17 Deleting a Sync Source

Delete a sync source as follows:

3. Under Sync Sources, select the Sync Source that you want to removes. 4. Click to delete the sync source.

Note: To undo the deletion, click .

(62)

4.1.2.3 Modifying the Sync Source

Figure 18 shows how to modify a sync source.

Figure 18 Modifying a Sync Source

Modify a sync source as follows:

MINI-LINK Craft displays the Configure Network Sync page, with a list of all previously defined Sync Source interfaces. The interface that currently acts as the active Sync Source is indicated in the list.

3. Under Sync Sources, Select the Sync Source that you want to modify. Note: There must be at least one Sync Source that is not Locked out 4. Click the columns in the selected Sync Source row and enter the new

values.

5. Select Save on the Toolbar to apply changes. 4.1.2.4 Switching the Sync Source

Change the sync source as follows:

(63)

MINI-LINK Craft displays the Configure Network Sync page with a list of all previously defined Sync Source interfaces. The interface that currently acts as the active Sync Source is indicated in the list.

3. Under Sync Sources, select the source that you want to be the sync source.

Note: Select a source other than the active Sync Source.

4. If the Sync Source is not locked out the system offers Forced and Holdover as switch options. If the active Sync Source is selected only the Holdover option is available.

5. Select switch option. For information about parameters see Configure

Network Sync page.

6. Select Save on the Toolbar to apply changes. 4.1.2.5 Clearing Switch Command

Clear a switch command as follows:

MINI-LINK Craft displays the Configure Network Sync page with a list of all previously defined Sync Source interfaces. The interface that currently acts as the active Sync Source is indicated in the list. There are also information that the Forced switch and Holdover switch is enabled. Note: To clear a switch command a Forced switch or Holdover switch

must be active

3. Click Clear to disable the switch command. The page is updated with the new information and displays it accordingly.

4.1.3 Configuring Network Frequency Synchronization

Figure 19 shows the network frequency synchronization configuration flow chart.

(64)

Figure 19 Modifying General Settings

Configure Network Frequency Synchronization as follows: 1. In the Management Tree, right click the NE.

(65)

3. Under general, set Network Sync to enable Network Frequency Synchronization.

4. Select the switch mode by choosing it in the Sync Switch Mode. 5. Select the selection mode by choosing it in the Sync Selection Mode. 6. Set Node Squelching.

Note: Enabling Network Frequency Synchronization on node level overrides any synchronization settings on the LTU155 boards.

4.1.3.1 Enabling/Disabling Squelch on E1 Interface for E1 Used as Clock Output Figure 21 shows how to enable squelch on NPU1 C. The same procedure applies for other plug-in units with E1 interfaces.

Figure 21 Enabling/Disabling Squelch on E1 Interface

Enable or disable squelch on E1 interface for an E1 that is used as clock output as follow:

1. In the Management Tree, right click the E1 interface you want to configure and click Configure.

(66)

MINI-LINK Craft displays the E1 Configuration page.

Figure 22 The E1 Configuration Page

2. Under Squelch, set the enable or disable Squelch.

Note: Check that Enable Node Squelching is enabled, see Section 4.1.3 on page 59.

4.1.3.2 Enabling/Disabling Squelch on All E1 Interfaces on a Unit Enable or disable squelch on all E1 interfaces on a unit as follows:

(67)

1. In the Management Tree, right click the unit you want to configure. 2. Point to Configure and click All E1.

MINI-LINK Craft displays the All E1 Configuration page.

Figure 23 The All E1 Configuration Page

3. Enable/Disable Squelch for the selected E1 interface.

4. Select Save on the Toolbar to apply changes. The system displays that squelching is either enabled or disabled.

4.1.3.3 Enabling/Disabling Squelch on MS/RS Interface Enable or disable squelch on MS/RS interface as follows:

1. In the Management Tree, right click the MS/RS Interface on the LTU 155 or LTU2 155 you want to configure and click Configure.

Configuring Network Synchronization

Contents

1

Introduction

1.1

Description

1.2

Planning Advice

1.3

Limitations

2

Prerequisites

2.1

Safety Information

2.2

Required Hardware

2.3

Required Licenses and Software

2.4

Required Documentation

Configuring Network Synchronizati

on Using CLI

3

Configuration and Operations Tasks

3.1

Configuring Frequency Synchronization

3.2

Configuring Time Synchronization

S

M

BC

BC

M

S

S

M

WAN

1/11/119

1/4/2

LAN

MAC

D9:16

Configuring Network Synchronizatio

n Using MINI-LINK Craft

4

Configuration and Operations Tasks

4.1

Configuring Frequency Synchronization