vRtrLdpNgSessInAddrLclLdpIdType
TIMETRA-LDP-NG-MIB ·
.1.3.6.1.4.1.6527.3.1.2.91.10.1.3
Object
The value of vRtrLdpNgSessInAddrLclLdpIdType indicates the local LDP identifier type for the LDP session indicated by vRtrLdpNgSessionInAddrLocalLdpId.
Context
- MIB
- TIMETRA-LDP-NG-MIB
- OID
.1.3.6.1.4.1.6527.3.1.2.91.10.1.3- Type
- column
- Access
- readonly
- Status
- current
- Parent
- vRtrLdpNgSessionInAddrEntry
- Groups
- 1
Net-SNMP examples
How SNMP and these commands workWalk the column to discover its indexed instances, or supply every index to read one instance.
Walk the column
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'TIMETRA-LDP-NG-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-LDP-NG-MIB::vRtrLdpNgSessInAddrLclLdpIdType'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'TIMETRA-LDP-NG-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-LDP-NG-MIB::vRtrLdpNgSessInAddrLclLdpIdType.<vRtrID>.<vRtrLdpNgPeerLdpIdType>.<vRtrLdpNgPeerLdpId>.<vRtrLdpNgSessionInAddrAddrType>.<vRtrLdpNgSessionInAddrAddress>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'TIMETRA-LDP-NG-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-LDP-NG-MIB::vRtrLdpNgSessInAddrLclLdpIdType'
Syntax
- Source
- TIMETRA-TC-MIBTmnxMplsLdpNgIdType
- Base type
Enumeration
Type Description
A value that represents the type of LDP identifier
ipv4(1) An IPv4 identifier type as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 identifier type as defined by the
InetAddressIPv6 textual convention.
Each definition of a concrete TmnxMplsLdpNgIdType value must be
accompanied by a definition of a textual convention for use with that
TmnxMplsLdpNgIdType.
Implementations must ensure that TmnxMplsLdpNgIdType objects
and any dependent objects (e.g., TmnxMplsLdpNgIdentifier objects) are
consistent. An inconsistentValue error must be generated
if an attempt to change an TmnxMplsLdpNgIdType object would,
for example, lead to an undefined TmnxMplsLdpNgIdentifier value. In
particular, TmnxMplsLdpNgIdType/TmnxMplsLdpNgIdentifier pairs must be
changed together if the identifier type changes (e.g., from
ipv6(2) to ipv4(1)).
Values & Constraints
Type Values
1 | ipv4 |
2 | ipv6 |
Conformance
Member of