"FD 100/320Gbps NT and FX NT IHub System
Basics, Management and OAM Guide"
Ethernet Connection Fault Management
Issue: 10 3HH-11982-AAAA-TQZZA 169
8.2 ETH-CFM Building Blocks
The IEEE and the ITU-T use their own nomenclature when describing administrative
contexts and functions. This introduces a level of complexity to configuration,
discussion and different vendors naming conventions. CLI has chosen to
standardize on the IEEE 802.1ag naming where overlap exists. ITU-T naming is
used, thus, no equivalent is available in the IEEE standard. In the following
definitions, both the IEEE name and ITU-T names are provided for completeness,
using the format IEEE Name/ITU-T Name.
Maintenance Domain (MD)/Maintenance Entity (ME) is the administrative container
that defines the scope, reach and boundary for faults. It is typically the area of
ownership and management responsibility. The IEEE allows for various formats to
name the domain, allowing up to 45 characters, depending on the format selected.
ITU-T supports only a format of “none” and does not accept the IEEE naming
conventions.
• 0 - Undefined and reserved by the IEEE.
• 1 - No domain name. It is the only format supported by Y.1731 as the ITU-T
specification does not use the domain name. This is supported in the IEEE
802.1ag standard but not in currently implemented for 802.1ag defined contexts.
• 2,3,4 - Provides the ability to input various different textual formats, up to 45
characters.The string format (2) is the default and therefore the keyword is not
shown when looking at the configuration.
Maintenance Association (MA)/Maintenance Entity Group (MEG) is the construct
where the different management entities will be contained. Each MA is uniquely
identified by its MA-ID.The MA-ID is comprised of the by the MD level and MA name
and associated format. This is another administrative context where the linkage is
made between the domain and the service using the bridging-identifier configuration
option. The IEEE and the ITU-T use their own specific formats. The MA short name
formats (0-255) have been divided between the IEEE (0-31,64-255) and the ITU-T
(32-63), with five currently defined (1-4, 32). Even though the different standards
bodies do not have specific support for the others formats a Y.1731 context can be
configured using the IEEE format options.
• 1 (Primary VID) - Values 0 - 4094
• 2 (String) - Raw ASCII, excluding 0-31 decimal/0-1F hex (which are control
characters) form the ASCII table
• 3 (2-octet integer) - 0 - 65535
RDI Remote Defect Indication
SLM Synthetic Loss Message
SLR Synthetic Loss Reply
TST Ethernet Test (Y.1731)
Acronym Callout
(2 of 2)
To Next Page
Loading...
