ITU-T G.875 PDF

This Recommendation provides a management/control-protocol-neutral information model for managing/controlling network elements in the optical transport network (OTN) [ITU-T G.872], [ITU-T G.709] and [ITU-T G.798]. It identifies the managed entities required for the management/control of OTN network elements. These entities are relevant to information exchanged across standardized interfaces defined in the M.3010 TMN architecture [ITU-T M.3010]. The management/control-protocol-neutral information model should be used as the base for defining management-protocol-specific information models, for examples, XML (Web Service or Netconf/Yang) information model, CORBA IDL model, and SNMP MIB.

The information model defined in this Recommendation is an augmentation to the generic code model specified in [ITU-T G.7711] for managing OTN transport resources. The core information model defined in [ITU-T G.7711] can be used as the base for the extension of OTN-specific information models.

The specific mapping of the management/control-protocol-neutral entities into management/control-protocol-specific managed object classes is the decision of the management/control-protocol-specific solution design. For example, an object class defined in this Recommendation may be mapped into multiple tables in a SNMP MIB. On the other hand, all the monitoring entities may be mapped into a single class in a protocol-specific model. Protocol-specific solution and their mapping from the protocol-neutral model is outside the scope of this Recommendation.

This Recommendation applies to OTN network elements and those systems that manage/control OTN network elements. The management/control system could be an NMS, EMS, SDN controller or hybrid of them. Recommendation [ITU-T G.7701] defines the management-control-continuum (MCC) concept whereby management and control functions are considered to be a continuum. Those systems are thus referred to as a management-control system (MCS) in general in this Recommendation. Functional capabilities of OTN equipment are defined in [ITU-T G.798], and requirements of the management of OTN equipment are provided in [ITU-T G.7710] and [ITU-T G.874]. The information model specified in this Recommendation applies to the management/control interface, as shown in Figure 1-1, specifically for managing/controlling the OTN functional capabilities of the NE.

There are several different perspectives from which information may be defined for management purposes. The network element viewpoint is concerned with the information that is required to manage a network element. This refers to information required to manage the network element function and the physical aspects of the network element. This Recommendation addresses only the network element view of OTN management.

The management/control-protocol-neutral information model specified in this Recommendation consists of a set of transport-technology-specific managed object classes, i.e., OTN-specific managed object classes. These OTN-specific managed object classes are inherited from the generic managed object classes defined in other ITU-T Recommendation such as [ITU-T G.711] and [ITU-T M.3160], including Managed Element, Termination Point and its subclasses, Subnetwork, and Subnetwork Connection ¹ . Because of object class inheritance, the OTN management information model also inherits the generic object management capabilities, such as object creation/deletion, notification of object creation/deletion, attribute value retrieval/modification, notification of attribute/state value change, scoped and filtered retrieval of object instances, and abortion of outstanding operations. The description of these generic object management capabilities is provided in other ITU-T Recommendations, such as the ITU-T M.3700 series, and therefore is outside the scope of this Recommendation.

The object entities defined in this Recommendation apply to fault management and configuration management.

¹ The linkage of the OTN-specific object classes to the generic object classes is specified in details in Appendix III.