All MIBs › EFM-COMMON-MIB › dot3OamLoopbackStatus
dot3OamLoopbackStatus
Module: EFM-COMMON-MIB
OID (symbolic): EFM-COMMON-MIB::dot3OamLoopbackStatus
OID (numeric): 1.3.6.1.2.1.9908.1.3.1.2
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: The loopback status of the OAM entity. This status is determined by a combination of the local parser and multiplexer states, the remote parser and multiplexer states, as well as by the actions of the local OAM client. When operating in normal mode with no loopback in progress, the status reads noLoopback(1).
If the OAM client has sent an Loopback OAMPDU and is waiting for a response, where the local parser and multiplexer states are DISCARD (see [802.3ah, 57.2.11.1]), the status is 'initiatingLoopback'. In this case, the local OAM entity has yet to receive any acknowledgement that the remote OAM entity has received its loopback command request.
If the local OAM client knows that the remote OAM entity is in loopback mode (via the remote state information as described in [802.3ah, 57.2.11.1, 30.3.6.1.15]), the status is
remoteLoopback(3). If the local OAM client is in the process of terminating the remote loopback [802.3ah, 57.2.11.3, 30.3.6.1.14], with its local multiplexer and parser states in DISCARD, the status is terminatingLoopback(4). If the remote OAM client has put the local OAM entity in loopback mode as indicated by its local parser state, the status is localLoopback(5).
The unknown(6) status indicates the parser and multiplexer combination is unexpected. This status may be returned if the OAM loopback is in a transition state but should not persist.
The values of this attribute correspond to the following values of the local and remote parser and multiplexer states.
value LclPrsr LclMux RmtPrsr RmtMux noLoopback FWD FWD FWD FWD initLoopback DISCARD DISCARD FWD FWD rmtLoopback DISCARD FWD LPBK DISCARD tmtngLoopback DISCARD DISCARD LPBK DISCARD lclLoopback LPBK DISCARD DISCARD FWD unknown *** any other combination ***
What is dot3OamLoopbackStatus?
Reports the actual OAM loopback state of this link: noLoopback(1) in normal operation, initiatingLoopback(2) while waiting for the peer to acknowledge a loopback request you sent, remoteLoopback(3) once the peer is confirmed looping traffic back, terminatingLoopback(4) while ending it, or localLoopback(5) if the peer has put this local device into loopback instead.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.9908.1.3.1.2 snmpwalk -v2c -c public <target> EFM-COMMON-MIB::dot3OamLoopbackStatus
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.9908.1.3.1.2.1 snmpget -v2c -c public <target> EFM-COMMON-MIB::dot3OamLoopbackStatus.1
Start monitoring Ethernet access/carrier equipment supporting 802.3ah EFM OAM (vendor-neutral IETF standard) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the EFM-COMMON-MIB::dot3OamLoopbackStatus OID value, configure state conditions and alerts, and monitor any Ethernet access/carrier equipment supporting 802.3ah EFM OAM (vendor-neutral IETF standard) from a single console.
OID Breakdown
Upper-level ancestors (6 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 | APERTUS-NPG-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.9908 | efmOamMIB | EFM-COMMON-MIB |
| 1.3.6.1.2.1.9908.1 | dot3OamMIB | EFM-COMMON-MIB |
| 1.3.6.1.2.1.9908.1.3 | dot3OamLoopbackTable | EFM-COMMON-MIB |
| 1.3.6.1.2.1.9908.1.3.1 | dot3OamLoopbackEntry | EFM-COMMON-MIB |
| 1.3.6.1.2.1.9908.1.3.1.2 | dot3OamLoopbackStatus | EFM-COMMON-MIB |