Relationships between OTM components

This is a brief overview of OTM relationships. A more detailed discussion of the relationships and the OTM model definitions is described in the Optical Transport Manager User Guide.

• There are different types of relationships between the various physical and logical components that are needed for event correlation and root cause analysis.

• Once a bidirectional relationship is created in one direction, the reverse relationship is automatically created.

• Some relationships are known beforehand and are created by the API at the time of creating the components. These are indicated in relationship tables given for each physical and logical component.

• Some relationships are not known at the time the component is created and need to be created later.

• Physical and logical component relationships are detailed in the relationship tables indicating the Objects/Classes involved in the relationship, class to which it is related, reverse relation, cardinality of relation, cardinality of the reverse relation, and whether the relation is optional or mandatory.

• The component name is the same as the class name and is also the type of object instantiated by the API make functions and returned by the find function for the component.

• A relationship is optional when the objects involved in the relationship are not always present for each other. However, the relationship must be created when the related objects are available and present.