This Recommendation¹ provides a management-protocol-neutral information model for managing network elements in the Ethernet transport network as defined in [ITU-T G.8010]. It identifies the telecommunications management network (TMN) managed entities required for the management of Ethernet transport network elements. These entities are relevant to information exchanged across standardized interfaces defined in the [ITU-T M.3010] TMN architecture. The management-protocol-neutral information model should be used as the base for defining management-protocol-specific information models, for example, the 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 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 an SNMP MIB. Protocol-specific solutions and their mapping from the protocol-neutral model will be described in other Recommendations and is out of the scope of this Recommendation.

This Recommendation applies to Ethernet transport network elements and those systems in the TMN that manage such network elements. Functional capabilities of Ethernet transport equipment are defined in [ITU-T G.8021], and requirements of the management of Ethernet transport equipment are provided in [ITU-T G.7710] and [ITU-T G.8051]. The information model specified in this Recommendation applies to the element management system network element (EMS-NE) interface.

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., Ethernet-specific managed object classes. These Ethernet-specific managed object classes are inherited from the generic managed object classes defined in other Recommendations such as [ITU-T M.3160], including managed element, termination point and its subclasses, subnetwork and subnetwork connection². Because of object class inheritance, the Ethernet management information model also inherits 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 of Recommendations, and therefore it 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 includes an electronic attachment containing the UML model file in the HTML format.

² The linkage of the Ethernet-specific object classes to the generic object classes is specified in details in Appendix I of this Recommendation.