In LANconfig, configure Ethernet OAM according to IEEE 802.3ah under .
- Interface
- Specifies the interface where CFM should be enabled. Possible values are LAN interfaces like LAN-1 or WAN interfaces like DSL-1.
- CFM interface enabled
- Enables or disables CFM on the configured interface.
- MD level
- Defines the Maintenance Domain Level for this interface.
- VLANs
- Defines the VLANs on the interface where CFM messages can be sent and received. If left empty, all VLANs are accepted. You can configure either a single VLAN or a comma-separated list of VLANs.
- Endpoint type
-
Defines the CFM endpoint type. Possible values:
- MEP (Maintenance Association End Point)
- The Maintenance Association End Point represents the boundary of a domain and performs fault detection between the domain boundaries. The MEP creates and sends CFM packets.
- MIP (Maintenance Intermediate Point)
- The Maintenance Intermediate Point is located within the domain and performs path and fault detection within the domain boundaries. The MIP responds to CFM packets.
- Maintenance domain
- Specifies the name of the Maintenance Domain (MD).
- Maintenance association
- Specifies the name of the Maintenance Association (MA).
- MEPID
- Defines the Maintenance Endpoint ID of the device for this entry (1-8191). This must be unique on each device.
- Sender ID
- Specifies the optional Sender ID in CFM CCM messages.
- CoS
- Defines the Class of Service with which CFM CCM (Continuity Check Message) packets are marked. Possible values: Best-Effort (0), Background (1), Excellent-Effort (3), Controlled-Latency (4), Video (5), Voice (6), Network-Control (7).
- CCM initiator
- Specifies whether the device should send regular CCM (Continuity Check Message) packets.
- CCM interval
- Defines the interval at which CCM messages are sent by the device. CCM intervals must be consistent between communication partners.
- CCM lowest alert prio
-
Defines the minimum severity level of detected issues required for the MEP to set the RDI (Remote Defect Indication) flag and
propagate it in CCM packets. Levels, in ascending severity, include:
- RDICCM
- A CC frame with the RDI flag set was received from at least one other MEP.
- MACstatus (Default)
- At least one MEP reported an interface status other than 'up' (e.g., hardware issue), or all MEPs report a port status other than 'up' (e.g., network segment isolated).
- RemoteCCM
- No CCM frames are being received from at least one configured MEP.
- ErrorCCM
- Another MEP is using the same MEPID as the local device, or CCM frames are received from an unconfigured MEP (if Matching is not none), or a different CCM interval is being used by another MEP.
- XconCCM
- CC frames were received from another MEP with a lower MD level, or with a different domain or association.
- CCM receiver
- Specifies whether the device should process or receive CCM messages.
- Remote MEP matching
-
Defines how the device handles remote MEP presence. Unconfigured remote MEPs can be dynamically learned or treated as an error
if a configured remote MEP is not found.
- None
- Unconfigured MEPs are included in the status table and considered in RDICCM and MACstatus conditions.
- Yes
- Unconfigured MEPs are included in the status table but not considered in RDICCM and MACstatus conditions. They trigger ErrorCCM.
- Strict
- Unconfigured MEPs are not included in the status table and not considered in RDICCM and MACstatus conditions. They trigger ErrorCCM.
- LBM responder
- Defines whether the device should respond to CFM Loopback Messages (Ethernet Ping). This feature can be used independently of the CCM operating mode.
- LTM responder
- Defines whether the device should respond to CFM Linktrace Messages (Ethernet Traceroute). This feature can be used independently of the CCM operating mode.
