NFM-P synchronization manager

Overview

The NFM-P synchronization manager provides a centralized view of timing synchronization across the network. The centralized view provides a common list of master and slave synchronization peers in a synchronization domain. The view includes a correlated list of alarms against synchronization objects in the domain, such as PTP clocks, ports, and peers.

You can use the synchronization manager to assign IP path monitors to peers between NEs configured with IEEE 1588 PTP clocks. The synchronization manager provides navigation to related NFM-P objects, such as NEs that are configured with IEEE 1588 PTP clocks, and to related CPAM objects, such as IP path monitors.

Note: The synchronization manager can be used to view and monitor IEEE 1588 PTP clocks. You can configure timing synchronization and IEEE 1588 PTP clocks through the NFM-P NE properties forms or through the device CLI.

Synchronization domains

Synchronization domains allow you to view and manage the PTP peers or SyncE sites in a domain. You can use synchronization domains to assign IP path monitors to PTP peers. You can also filter unmonitored peers and navigate to associated IP path monitors.

When the NFM-P discovers a PTP peer or SyncE site, it is assigned to a synchronization domain based on the domain ID. When the NFM-P discovers a PTP peer or SyncE site with a domain ID that is not shared with an existing synchronization domain, a synchronization domain with that domain ID is automatically created. The domain ID is configured on the IEEE 1588 PTP clock.

The following events can result in the creation of a synchronization domain.

You cannot create synchronization domains manually, and you can delete a synchronization domain only when the domain does not contain peers or SyncE sites. Alarms generated for a PTP clock, port, or peer are propagated to the appropriate synchronization domain.

Synchronization groups

You can create synchronization groups to view a subset of PTP peers separately from the rest of the synchronization domain. A synchronization domain can contain up to 500 synchronization groups. When you create the group, you choose NEs configured with IEEE 1588 PTP clocks and the NFM-P generates a list of constituent peers from the NEs. All of the path monitoring functionality that is available at the synchronization domain level is also available at the synchronization group level.

Peer remote site ID

When the NFM-P discovers a PTP peer, the peer IP address is used to determine the system IP address of the far-end NE. The IP address is displayed in the synchronization manager as the peer remote site ID. If the NFM-P discovers a system or network IP address that matches the peer IP address of a discovered PTP peer, the peer remote site ID is recalculated. The peer remote site ID is set to 0.0.0.0 if it cannot be mapped to a managed NE in the network or if it maps to more than one managed NE.

Timing synchronous links

The synchronization manager lists all timing synchronous links in the network related to a selected PTP peer or SyncE site. The list includes links that are not currently in use. You can click the Find Sync Time Sources button on the PTP peer or SyncE site properties form to view a list of timing synchronous links in the network that are currently being used by the selected site.

From the physical topology map, you can right-click an NE and select Highlight Sync Time Sources to view a graphical representation of the timing synchronous links currently being used by the selected NE.

IP path monitors

You can use the synchronization manager to assign unidirectional and bidirectional IP path monitors to PTP peers. The PTP Peers tabs on the synchronization domain and synchronization group forms include an Unmonitored tab that displays peers that are not assigned an IP path monitor. You can navigate to the IP path monitor object from the synchronization manager.

Alarms that are generated for IP path monitor objects, such as reachability, OAM and path change alarms, are propagated to the respective PTP peers. See the NSP NFM-P Control Plane Assurance Manager User Guide for more information about IP path monitors.

SyncE

The synchronization manager supports SyncE. The NFM-P automatically assigns NEs with Sync-E enabled to the default Sync-E synchronization domain. You can view SyncE sites and associated daughter cards, including correlated alarms. Both the far end and near end NEs must be managed by the NFM-P for SyncE to work.

The properties forms for SyncE sites includes a check box that indicates if the site is also enabled with PTP. The properties forms for PTP peers includes a check box that indicates if the peer is also enabled with SyncE. This flag is processed only if there is a valid peer remote site ID.