mplsTunnelExtNodeConfigEntry
MPLS-TE-EXT-STD-MIB ·
.1.3.6.1.2.1.10.166.20.0.2.1
Object
row
An entry in this table represents a mapping
identification for the operator or service provider
to a node or an LSR.
As per RFC 6370, IP-compatible mapping is represented
as Global_ID::Node_ID.
As per RFC 6923, the CC and the ICC form the ICC_Operator_ID
as CC::ICC, and ICC-compatible mapping is represented
as ICC_Operator_ID::Node_ID.
Note: Each entry in this table should have a unique
[Global_ID and Node_ID] or [CC::ICC and Node_ID] combination.
Context
- MIB
- MPLS-TE-EXT-STD-MIB
- OID
.1.3.6.1.2.1.10.166.20.0.2.1- Type
- row
- Status
- current
- Parent
- mplsTunnelExtNodeConfigTable
- Table
- mplsTunnelExtNodeConfigTable
- Children
- 8
Net-SNMP examples
How SNMP and these commands workUse a bulk walk to inspect objects and instances beneath this OID.
Walk the subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'MPLS-TE-EXT-STD-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeConfigEntry'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'MPLS-TE-EXT-STD-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeConfigEntry'
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.