OID reference
1.3.6.1.4.1.8708.2.40.2.6.1.1.9
The entry signifies the priority of the LSP within the tunnel. 1 - Highest priority, working LSP in a revertive protected tunnel with multiple LSPs. 2 - Second highest priority, protecting LSP in a revertive protected tunnel with multiple LSPs. The first LSP created in a tunnel will receive the highest priority and be…
Identification
{1 3 6 1 4 1 8708 2 40 2 6 1 1 9}
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.
Published row index: mplsLspIndex.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.8708.2.40.2.6.1.1.9
Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
The displayed source records contain one distinct definition. Compare its source records.
mplsLspPriority OBJECT-TYPE
SYNTAX Integer32 (1..2)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The entry signifies the priority of the LSP within the tunnel.
1 - Highest priority, working LSP in a revertive
protected tunnel with multiple LSPs.
2 - Second highest priority, protecting LSP in a
revertive protected tunnel with multiple LSPs.
The first LSP created in a tunnel will receive the
highest priority and be regarded a the working LSP.
"
DEFVAL { 1 }
::= { mplsLspEntry 9 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The entry signifies the priority of the LSP within the tunnel. 1 - Highest priority, working LSP in a revertive protected tunnel with multiple LSPs. 2 - Second highest priority, protecting LSP in a revertive protected tunnel with multiple LSPs. The first LSP created in a tunnel will receive the highest priority and be regarded a the working LSP.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: mplsLspPriority
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"mplsLspPriority",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"(",
"1",
".",
".",
"2",
")",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"The entry signifies the priority of the LSP within the tunnel. 1 - Highest priority, working LSP in a revertive protected tunnel with multiple LSPs. 2 - Second highest priority, protecting LSP in a revertive protected tunnel with multiple LSPs. The first LSP created in a tunnel will receive the highest priority and be regarded a the working LSP. \"",
"DEFVAL",
"{",
"1",
"}",
"::=",
"{",
"mplsLspEntry",
"9",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32",
[
"integerSubType",
[
[
1,
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The entry signifies the priority of the LSP within the tunnel. 1 - Highest priority, working LSP in a revertive protected tunnel with multiple LSPs. 2 - Second highest priority, protecting LSP in a revertive protected tunnel with multiple LSPs. The first LSP created in a tunnel will receive the highest priority and be regarded a the working LSP."
],
null,
null,
null,
[
"DEFVAL",
1
]
]
}Vendor MIB copy from the Observium Community archive.
Module: LUM-MPLS-MIB
See published definition above
{'LUM-TC': ['MplsLabel', 'PortNumber', 'MgmtNameString', 'CommandString'], 'LUM-REG': ['lumModules', 'lumMplsMIB'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'DateAndTime', 'MacAddress', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'Integer32', 'Counter64'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'MODULE-COMPLIANCE']}Related source files and packages:
Registration