sapL3LoopbackEntry
TIMETRA-SAP-MIB ·
.1.3.6.1.4.1.6527.3.1.2.4.3.172.1
Object
row
Each entry represents an active interface loopback. The interface is
placed in loopback by row creation and is removed by row destruction.
Rows in table sapL3LoopbackTable are created and destroyed by SNMP set
operations on the object sapL3LoopbackRowStatus. Rows in table
sapL3LoopbackTable may be destroyed by the system when the associated
SAP has been deleted. A maximum of 64 rows may be created. Rows are
kept in volatile storage and lost upon a system reboot.
Context
- MIB
- TIMETRA-SAP-MIB
- OID
.1.3.6.1.4.1.6527.3.1.2.4.3.172.1- Type
- row
- Status
- current
- Parent
- sapL3LoopbackTable
- Table
- sapL3LoopbackTable
- Children
- 2
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 'TIMETRA-SAP-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-SAP-MIB::sapL3LoopbackEntry'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'TIMETRA-SAP-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-SAP-MIB::sapL3LoopbackEntry'
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.