TIMETRA-IEEE8021-CFM-MIB :: tmnxDot1agCfmMepFaultPropagation

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TIMETRA-IEEE8021-CFM-MIB › tmnxDot1agCfmMepFaultPropagation

tmnxDot1agCfmMepFaultPropagation

Module: TIMETRA-IEEE8021-CFM-MIB

OID (symbolic): TIMETRA-IEEE8021-CFM-MIB::tmnxDot1agCfmMepFaultPropagation

OID (numeric): 1.3.6.1.4.1.6527.3.1.2.52.7.1.1.24

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-create

Description: The value of tmnxDot1agCfmMepFaultPropagation specifies what action should be taken by the MEP if a fault is detected in the service containing the MEP. It also specifies if the MEP should propagate a fault that it has detected into the service.

When this object is set to 'disabled (0)', no additional fault propagation will occur. When this object is set to 'useIfStatusTLV (1)', the MEP will send an interface status TLV in the next CCM indicating fault when fault is detected, even if the MEP itself has not detected a fault. When this object is set to 'suspendCCM (2)', faults will be propagated by stopping the regular CCM transmissions entirely. Once the fault is cleared, the regular CCM transmissions will resume. Additionally, when the value of tmnxDot1agCfmMepFaultPropagation is different than 'disabled (0)', a defect detected by the MEP will be propagated into the service.

What is tmnxDot1agCfmMepFaultPropagation?

This value specifies how a MEP reacts when a fault is detected in the service it's monitoring, and whether it propagates a detected fault into the service: disabled(0) does neither, useIfStatusTLV(1) sends an interface-status TLV in the next CCM to signal fault, and suspendCCM(2) stops regular CCM transmission entirely until the fault clears. An admin chooses suspendCCM(2) when downstream systems are configured to treat a CCM timeout itself as the fault signal, or useIfStatusTLV(1) when a more graceful, explicit status flag is preferred over an outright CCM outage. Setting this to anything other than disabled(0) also means a fault this MEP itself detects will be propagated further into the service, not just faults detected elsewhere.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.6527timetraALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3timetraProductsALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3.1tmnxSRMIBALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3.1.2tmnxSRObjsALCATEL-IND1-TIMETRA-GLOBAL-MIB
Numeric OIDNameModule
1.3.6.1.4.1.6527.3.1.2.52tmnxDot1agMIBObjsTIMETRA-IEEE8021-CFM-MIB
1.3.6.1.4.1.6527.3.1.2.52.7tmnxDot1agCfmMepTIMETRA-IEEE8021-CFM-MIB
1.3.6.1.4.1.6527.3.1.2.52.7.1tmnxDot1agCfmMepTableTIMETRA-IEEE8021-CFM-MIB
1.3.6.1.4.1.6527.3.1.2.52.7.1.1tmnxDot1agCfmMepEntryTIMETRA-IEEE8021-CFM-MIB
1.3.6.1.4.1.6527.3.1.2.52.7.1.1.24tmnxDot1agCfmMepFaultPropagationTIMETRA-IEEE8021-CFM-MIB