scope:

This Recommendation addresses management aspects of the Ethernet transport (ET) capable network element containing transport functions of one or more of the layer networks of the Ethernet transport network. The management of the Ethernet 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 this Recommendation, fault management, configuration management, performance management (PM) and security management are specified. Furthermore, only the management information (MI) of the following ET equipment functions is addressed:

- Ethernet MAC layer (ETH) flow forwarding, flow termination, connection, diagnostic and traffic conditioning/shaping functions;

- ETH server to ETH client adaptation functions (including ETH/ETH-m, ETHG/ETH, FlexEC/ETH);

- ETH link aggregation functions;

- Flex Ethernet (FlexE) trail termination functions; and

- FlexE to FlexE client adaptation functions.

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

The architecture described in this Recommendation for the management of Ethernet transport networks is based upon 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;

− Ethernet layer network entities (ELNEs) refer to trail termination, adaptation and connection functions as described in [ITU-T G.8010];

− a network element may only contain Ethernet layer network entities (ELNEs);

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

− client layer entities are managed as part of their own logical domain;

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

− CLNEs and ELNEs may or may not share the same agent,

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