dot3OamLoopbackStatus

ZXEPON-SERVICE-OAM-MIB · .1.3.6.1.4.1.3902.1015.1010.1.6.3.1.1

Object

column r/w Enumeration
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). The values initiatingLooopback(2) and 
terminatingLoopback(4) can be read or written. The other values can only 
be read - they can never be written. Writing initiatingLoopback causes the 
local OAM entity to start the loopback process with its peer. This value 
can only be written when the status is noLoopback(1). Writing the value 
initiatingLoopback(2) in any other state has no effect. When in remoteLoopback(3), 
writing terminatingLoopback(4) causes the local OAM entity to initiate the 
termination of the loopback state. Writing terminatingLoopack(4) in any other 
state has no effect. If the OAM client initiates a looopback and 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.

Context

MIB
ZXEPON-SERVICE-OAM-MIB
OID
.1.3.6.1.4.1.3902.1015.1010.1.6.3.1.1
Type
column
Access
readwrite
Status
current
Parent
dot3OamLoopbackEntry
Table
dot3OamLoopbackTable
Siblings
1

Syntax

Enumeration

Values & Constraints

Enumerated Values
1noLoopback
2initiatingLoopback
3remoteLoopback
4terminatingLoopback
5localLoopback
6unknown

Related Objects

Sibling Objects