mplsFTNAddrType
MPLS-FTN-STD-MIB ·
.1.3.6.1.2.1.10.166.8.1.3.1.5
Object
This object determines the type of address contained in
the source and destination address objects
(mplsFTNSourceAddrMin, mplsFTNSourceAddrMax,
mplsFTNDestAddrMin and mplsFTNDestAddrMax) of a
conceptual row.
This object MUST NOT be set to unknown(0) when
mplsFTNMask has bit positions sourceAddr(0) or
destAddr(1) set to one.
When both these bit positions of mplsFTNMask are set to
zero the value of mplsFTNAddrType SHOULD be set to
unknown(0) and the corresponding source and destination
address objects SHOULD be set to zero-length strings.
Context
- MIB
- MPLS-FTN-STD-MIB
- OID
.1.3.6.1.2.1.10.166.8.1.3.1.5- Type
- column
- Access
- readwrite
- Status
- current
- Parent
- mplsFTNEntry
- 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 'MPLS-FTN-STD-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'MPLS-FTN-STD-MIB::mplsFTNAddrType'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'MPLS-FTN-STD-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'MPLS-FTN-STD-MIB::mplsFTNAddrType.<mplsFTNIndex>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'MPLS-FTN-STD-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'MPLS-FTN-STD-MIB::mplsFTNAddrType'
Syntax
- Source
- INET-ADDRESS-MIBInetAddressType
- Base type
Enumeration
Values & Constraints
Type Values
0 | unknown |
1 | ipv4 |
2 | ipv6 |
3 | ipv4z |
4 | ipv6z |
16 | dns |
25 | l2vpn |
Conformance
Member of
Compliance refinements
mplsFTNModuleFullCompliance
INET-ADDRESS-MIB::InetAddressType
Values:
ipv4(1), ipv6(2)
An implementation is only required to support IPv4
and/or IPv6 addresses. An implementation is only
required to support the address types that are actually
supported on the LSR.
and/or IPv6 addresses. An implementation is only
required to support the address types that are actually
supported on the LSR.
Values:
ipv4(1), ipv6(2)
Write access is not required. An implementation is only
required to support IPv4 and IPv6 addresses.
required to support IPv4 and IPv6 addresses.