TIMETRA-MPLS-TP-MIB :: vRtrMplsTpLspPathReasonDownFlags

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsTIMETRA-MPLS-TP-MIBvRtrMplsTpLspPathReasonDownFlags

vRtrMplsTpLspPathReasonDownFlags

Module: TIMETRA-MPLS-TP-MIB

OID (symbolic): TIMETRA-MPLS-TP-MIB::vRtrMplsTpLspPathReasonDownFlags

OID (numeric): 1.3.6.1.4.1.6527.3.1.2.83.2.3.2.1.6

Node type: OBJECT-TYPE

Type: Bits

Access: read-only

Description: The value of vRtrMplsTpLspPathReasonDownFlags specifies the reason why the MPLS-TP LSP Path is operationally down when the administrative state is 'inService (2)'.

The recognized BIT values are: unknown (0) - Unspecified (or unknown) ccFault (1) - BFD Continuity Check (CC) failed cvFault (2) - BFD Connectivity Verification (CV) failed ifDn (3) - The path out-link interface is operationally down portDn (4) - The port associated with the out-link interface is operationally down parentAdminDn (5) - The associated mpls-tp Lsp or mpls-tp instance or mpls instance is admin down mepAdminDn (6) - The path MEP is admin down unsupportedPort (7) - MPLS-TP functionality is not supported over the out-link port. ifNhAddrInconsistent (8) - The configured next-hop address is not bound to the configured out-link interface. ptcTmplMsng (9) - The protect-tp-path is missing a protection-template name. ccDnHold (10) - ccFault effect on path-state is on hold due to 'hold-time-down' config in the oam-template ccUpHold (11) - ccFault clear effect on path-state is on hold due to 'hold-time-up' config in the oam-template bfdNoRsrc (12) - bfd-enable failed since maximum number of supported bfd-sessions was reached.

What is vRtrMplsTpLspPathReasonDownFlags?

A bitmap indicating why this MPLS-TP LSP path is operationally down despite being administratively in-service, covering causes like BFD CC/CV failure, the out-link or its port being down, a missing protection template, or exhausted BFD session resources. Admins read this bitmap to go straight to the root cause of a down path instead of guessing from the oper state alone.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.83.2.3.2.1.6
snmpwalk -v2c -c public <target> TIMETRA-MPLS-TP-MIB::vRtrMplsTpLspPathReasonDownFlags

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.83.2.3.2.1.6.1
snmpget -v2c -c public <target> TIMETRA-MPLS-TP-MIB::vRtrMplsTpLspPathReasonDownFlags.1

Start monitoring Nokia/Alcatel-Lucent 7750 SR, 7705 SAR packet-transport router (MPLS-TP admin state/OAM template status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TIMETRA-MPLS-TP-MIB::vRtrMplsTpLspPathReasonDownFlags OID value, configure state conditions and alerts, and monitor any Nokia/Alcatel-Lucent 7750 SR, 7705 SAR packet-transport router (MPLS-TP admin state/OAM template status) from a single console.

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.83vRtrMplsTpObjsTIMETRA-MPLS-TP-MIB
1.3.6.1.4.1.6527.3.1.2.83.2vRtrMplsTpConfigurationsTIMETRA-MPLS-TP-MIB
1.3.6.1.4.1.6527.3.1.2.83.2.3vRtrMplsTpLspObjectsTIMETRA-MPLS-TP-MIB
1.3.6.1.4.1.6527.3.1.2.83.2.3.2vRtrMplsTpLspPathTableTIMETRA-MPLS-TP-MIB
1.3.6.1.4.1.6527.3.1.2.83.2.3.2.1vRtrMplsTpLspPathEntryTIMETRA-MPLS-TP-MIB
1.3.6.1.4.1.6527.3.1.2.83.2.3.2.1.6vRtrMplsTpLspPathReasonDownFlagsTIMETRA-MPLS-TP-MIB