All MIBs › TN-MPLS-TP-MIB › vRtrMplsTpLspPathReasonDownFlags
vRtrMplsTpLspPathReasonDownFlags
Module: TN-MPLS-TP-MIB
OID (symbolic): TN-MPLS-TP-MIB::vRtrMplsTpLspPathReasonDownFlags
OID (numeric): 1.3.6.1.4.1.7483.6.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?
This read-only bitmask reports the specific reason(s) an MPLS-TP LSP Path is operationally down while its administrative state is in service, with bits covering causes like ccFault(1) (BFD Continuity Check failure), ifDn(3) (out-link interface down), or bfdNoRsrc(12) (maximum BFD sessions reached). Admins check this field first when a path shows down unexpectedly, since it pinpoints the specific failure category (interface, BFD, protection template, or admin-down parent) instead of requiring a manual investigation across several subsystems. Multiple bits can be set simultaneously if more than one condition is contributing to the down state.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.7483.6.1.2.83.2.3.2.1.6 snmpwalk -v2c -c public <target> TN-MPLS-TP-MIB::vRtrMplsTpLspPathReasonDownFlags
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.7483.6.1.2.83.2.3.2.1.6.1 snmpget -v2c -c public <target> TN-MPLS-TP-MIB::vRtrMplsTpLspPathReasonDownFlags.1
Start monitoring Nokia SROS-based router, carrier Ethernet/MPLS-TP transport router (MPLS-TP tunnel/OAM admin status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TN-MPLS-TP-MIB::vRtrMplsTpLspPathReasonDownFlags OID value, configure state conditions and alerts, and monitor any Nokia SROS-based router, carrier Ethernet/MPLS-TP transport router (MPLS-TP tunnel/OAM admin status) from a single console.
OID Breakdown
Upper-level ancestors (10 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.7483 | tropic | TROPIC-GLOBAL-REG |
| 1.3.6.1.4.1.7483.6 | tnProducts | TROPIC-GLOBAL-REG |
| 1.3.6.1.4.1.7483.6.1 | tnSRMIB | TROPIC-GLOBAL-REG |
| 1.3.6.1.4.1.7483.6.1.2 | tnSRObjs | TROPIC-GLOBAL-REG |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.7483.6.1.2.83 | vRtrMplsTpObjs | TN-MPLS-TP-MIB |
| 1.3.6.1.4.1.7483.6.1.2.83.2 | vRtrMplsTpConfigurations | TN-MPLS-TP-MIB |
| 1.3.6.1.4.1.7483.6.1.2.83.2.3 | vRtrMplsTpLspObjects | TN-MPLS-TP-MIB |
| 1.3.6.1.4.1.7483.6.1.2.83.2.3.2 | vRtrMplsTpLspPathTable | TN-MPLS-TP-MIB |
| 1.3.6.1.4.1.7483.6.1.2.83.2.3.2.1 | vRtrMplsTpLspPathEntry | TN-MPLS-TP-MIB |
| 1.3.6.1.4.1.7483.6.1.2.83.2.3.2.1.6 | vRtrMplsTpLspPathReasonDownFlags | TN-MPLS-TP-MIB |