Sample HO_Trail entry items shows sample entry items for the HO_Trail class.

Table 1. Sample HO_Trail entry items

Item Name

Value

EMS

Cisco Systems/CTM_HA

SubnetworkConnection

SNC1

A-End ManagedElement

Node1

A-End PTP

/rack=1/shelf=1/slot=2/port=3

A-End CTP

/sts1_au3-j=1-k=1

Z-End ManagedElement

Node2

Z-End PTP

/rack=1/shelf=1/slot=2/port=4

Z-End CTP

/sts1_au3-j=1-k=1

In Optical Transport Manager, the information appears as

Node1/1-1-2/3/1->Node2/1-1-2/4/1

where the values are

  • A-End Managed Element Name = Node1

  • A-End Rack = 1

  • A-End Shelf = 1

  • A-End Slot = 2

  • A-End Port = 3

  • A-End CTP = 1

  • Z-End Managed Element Name = Node2

  • Z-End Rack = 1

  • Z-End Shelf = 1

  • Z-End Slot = 2

  • Z-End Port = 4

  • Z-End CTP = 1

    Note:

    In the Ciena EMS TMF814 model, there is no direct relationship between SubnetworkConnection (SNC) and TopologicalLink (TL). Instead, an SNC rides over one or multiple working RoutingLink (RL) objects, and each RL consists of one or multiple TLs. Since the RL is not modeled in the OTM Adapter for TMF814, each HO_Trail (i.e., SNC) will be LayeredOver multiple TLs. During root cause analysis, for each PTP alarm processed, the corresponding TL will be Down and it will impact all the Underlying HO_Trails.