ITU-T G.8152 PDF

This Recommendation provides a management-protocol-neutral information model for managing network elements in the MPLS-TP transport network as defined in [ITU-T G.8110.1]. It identifies the telecommunications management network (TMN) managed entities required for the management of MPLS-TP transport network elements. These entities are relevant to information exchanged across standardized interfaces defined in the [ITU-T M.3010] TMN architecture. The management protocolneutral information model should be used as the base for defining management protocol-specific information models, for example XML (web service or Netconf/Yang) information model, common object request broker architecture (CORBA) interface definition language (IDL) model, and simple network management protocol (SNMP) management information base (MIB).

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

The specific mapping of the management protocol-neutral model into management-protocol-specific model is the decision of the management-protocol-specific solution design. For example, an object class defined in this Recommendation may be mapped into multiple tables in a SNMP MIB. Protocol-specific solutions and their mapping from the protocol-neutral model may be described in other Recommendations and is out of the scope of this Recommendation.

This Recommendation applies to MPLS-TP transport network elements and those systems in the TMN that manage such network elements. Functional capabilities of MPLS-TP transport equipment are defined in [ITU-T G.8121], [ITU-T G.8121.1], [ITU-T G.8121.2] and requirements of the management of MPLS-TP transport equipment are provided in [ITU-T G.7710] and [ITU-T G.8151]. The information model specified in this Recommendation applies to the element management system network element (EMS-NE interface, as shown in Figure 1-1, specifically for managing the MPLS-TP functional capabilities of the NE.

The object classes defined in this Recommendation cover the areas of fault management, configuration management, and performance management.

There are several different perspectives from which management 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 Ethernet transport network management.

The management-protocol-neutral information model specified in this Recommendation consists of a set of transport-technology-specific managed object classes, i.e., MPLS-TP-specific managed object classes. These MPLS-TP-specific managed object classes are inherited from the generic managed object classes defined in other ITU-T Recommendation such as [ITU-T M.3160], including managed element, termination point and its subclasses, subnetwork, and subnetwork connection. Because of object class inheritance, the MPLS-TP 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 M.3700 series, and therefore is outside the scope of this Recommendation.

The object classes defined in this Recommendation cover the areas of fault management, configuration management, and performance management.

This Recommendation provides a representation of the MPLS-TP technology using the methodologies that have been used for other transport technologies (e.g., SDH, OTN and Ethernet).