scope:

This Recommendation addresses management aspects of the multi-protocol label switching (MPLS) transport profile (MPLS-TP) capable network element containing transport functions of one or more of the layer networks of the MPLS-TP network. The management of the MPLS-TP layer networks is separable from that of its client layer networks so that the same means of management can be used regardless of the client. In this version of the Recommendation, fault management, configuration management, performance management and security management are specified.

The generic requirements for managing transport network elements (NEs) are specified in [ITU-T G.7710] and the requirements for the management of equipment used in networks supporting an MPLS-TP are specified in [b-IETF RFC 5951]. This Recommendation specifies the requirements for managing the following MPLS-TP specific equipment functional blocks, which are defined in [ITU-T G.8121]:

− MPLS-TP layer connection function;

− MPLS-TP layer trail termination functions;

− MPLS-TP server to MPLS-TP client adaptation functions;

− MPLS-TP server to Ethernet client adaptation functions;

− synchronous digital hierarchy (SDH) server to MPLS-TP client adaptation functions;

− plesiochronous digital hierarchy (PDH) server to MPLS-TP client adaptation functions;

− optical transport network (OTN) sever to MPLS-TP client adaptation functions;

− Ethernet MAC layer (ETH) sever to MPLS-TP client adaptation functions.

This Recommendation also describes the management network organizational model for communication between an element management layer (EML) operations system and the MPLS-TP equipment management function within an MPLS-TP network element.

The architecture described in this Recommendation for the management of MPLS-TP transport networks is based on the following considerations:

− the management view of network element functional elements should be uniform whether those elements form part of an inter-domain interface or part of an intra-domain interface. Those properties necessary to form such a uniform management view are to be included in this Recommendation;

− MPLS-TP layer network entities (MTLNEs) refer to trail termination, adaptation and connection functions as described in [ITU-T G.8110.1];

− a network element may only contain MPLS-TP layer network entities;

− a network element may contain both MTLNEs and client layer network entities (CLNEs);

− client layer entities are managed as part of their own logical domain (e.g., Ethernet management network);

− CLNE and MTLNE may or may not share a common message communication function (MCF) and management application function (MAF) depending on the application;

- CLNE and MTLNE may or may not share the same agent;

- server layer network entities (SLNEs) and MTLNEs may or may not share the same agent.

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).