All MIBs › RFC1229-MIB › ifExtnsRcvAddrStatus
ifExtnsRcvAddrStatus
Module: RFC1229-MIB
OID (symbolic): RFC1229-MIB::ifExtnsRcvAddrStatus
OID (numeric): 1.3.6.1.2.1.12.3.1.3
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: This object has the value nonVolatile(4) for those entries in the table which are valid and will not be deleted by the next restart of the managed system. Entries having the value volatile(3) are valid and exist, but have not been saved, so that will not exist after the next restart of the managed system. Entries having the value other(1) are valid and exist but are not classified as to whether they will continue to exist after the next restart. Entries having the value invalid(2) are invalid and do not represent an address for which an interface accepts frames. Setting an object instance to one of the values other(1), volatile(3), or nonVolatile(4) causes the corresponding entry to exist or continue to exist, and to take on the respective status as regards the next restart of the managed system. Setting an object instance to the value invalid(2) causes the corresponding entry to become invalid or cease to exist. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant ifExtnsRcvAddrStatus object instance.
What is ifExtnsRcvAddrStatus?
This object records the persistence status of a receive-address entry: nonVolatile(4) means the entry survives a restart, volatile(3) means it will be lost on the next restart, other(1) means its persistence is unclassified, and invalid(2) marks it as no longer a recognized receive address. An admin can write other, volatile, or nonVolatile to create or keep an entry in that persistence class, or write invalid to remove or invalidate it, and must check this value since agents may leave stale invalid entries in the table rather than deleting them outright. Setting a newly added multicast receive address's status to nonVolatile(4) ensures the device keeps accepting that address after a power cycle.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.12.3.1.3 snmpwalk -v2c -c public <target> RFC1229-MIB::ifExtnsRcvAddrStatus
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.12.3.1.3.1 snmpget -v2c -c public <target> RFC1229-MIB::ifExtnsRcvAddrStatus.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.2.1.12.3.1.3.1 i <value>
Start monitoring vendor-neutral, standards-based MIB, router/bridge/NIC with IEEE 802.5 Token Ring interfaces with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RFC1229-MIB::ifExtnsRcvAddrStatus OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, router/bridge/NIC with IEEE 802.5 Token Ring interfaces from a single console.
OID Breakdown
Upper-level ancestors (9 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.2 | mgmt | AXON-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| 1.3.6.1.2.1.12 | ifExtensions2 | LBHUB-BOOM-MIB |
| 1.3.6.1.2.1.12.3 | ifExtnsRcvAddrTable | LBHUB-MSH4PTBRDG-MIB |
| 1.3.6.1.2.1.12.3.1 | ifExtnsRcvAddrEntry | LBHUB-MSH4PTBRDG-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.12.3.1.3 | ifExtnsRcvAddrStatus | RFC1229-MIB |