Service OAM Fault Management YANG Modules



MEF 38 is a specification document developed by the Technical Committee of the MEF.


"This document specifies the Fault Management (FM) YANG Modules necessary to implement the Service Operations, Administration, and Maintenance (OAM) that satisfies the Service OAM requirements and framework specified by MEF 17, the Service OAM Fault Management requirements as specified by SOAM-FM, and the Service OAM management objects as specified by MEF 7.1 which are applicable to Fault Management functions. One MEF document, the SOAM TC/FM MIB and two non-MEF documents serve as the baseline documents for this work: ITU-T Y.1731 and IEEE 802.1Q. YANG is the data modeling language used to model configuration and state data manipulated by the NETCONF protocol, and NETCONF notifications on the Network Element (NE)."




Related and Further Reading
Specifications | Management | Modelling |


TC (MEF members only) |

1 Comment

  1. Hi,

    Can you please let me know why InnerValId and OuterVlanId is not present under "container alarm-indication-signal {"?

    Regarding configurable vlan field in AIS msg, following is the extract from MEF 30.1 (Section 8.5, Page 35)

    Having determined the set of client MEGs, there are two ways that a MEP can inject AIS into each client MEG:

    If the client MEG does not have a MEP on the same interface as the injecting MEP, i.e., it has a MIP or has no MP at all, then injecting an AIS involves transmitting an AIS PDU at the client MEG Level, with the appropriate VLAN tags for the client MEG, in the opposite direction to that in which the MEP normally sends CFM frames (that is, an Up MEP would send AIS PDUs out towards the wire, and a Down MEP would send AIS PDUs in towards the bridging function). Note that in this case, the injecting MEP requires knowledge (e.g., by configuration) of the MEG Level and (where the client MEGs have additional VLAN tags) the primary VID for each client MEG.