CANOGA PERKINS 9145E NID Software Version 3.0 - Manual (Page 102)

9145E NID Software User’s Manual 802.3AH OAM
OAM Control
88
9.1 OAM Control
The OAM Control screen (Figure 9-2) is split into two sections. The top of the screen shows
status information. The list below shows the standard status information and the corresponding
MIB objects.
User interface MIB Object
• OAM Operational Status dot3OamOperStatus (dot3oam.my)
• OAM MAX PDU Size dot3OamMaxOamPduSize (dot3oam.my)
• OAM Revision dot3OamConfigRevision (dot3oam.my)
• OAM Functions Supported dot3OamFunctionsSupported (dot3oam.my)
• OAM Loopback Status Dot3OamLoopbackStatus (dot3oam.my)
• OAM Remote Link Fault
10, OAM Operational Status - At initialization and failure conditions, two OAM entities on
the same full-duplex Ethernet link begin a discovery phase to determine what OAM
capabilities may be used on that link. The following is the list of possible values:
11, Disabled: - This value will return “disabled” if OAM is disabled on this interface via the
OAM Admin State.
12, Link Fault: - If the link has detected a fault and is transmitting OAMPDUs with a link fault
indication, the value is link Fault. This value will also be returned if the interface is not
operational.
13, Passive Wait - The passive Wait state is returned only by OAM entities in OAM Mode
passive and reflects the state in which the OAM entity is waiting to see if the peer device
is OA capable.
14, Active Send Local - This value is used by active mode devices and reflects the OAM
entity actively trying to discover whether the peer has OAM capability but has not yet
made that determination.
15, Send Local And Remote - Reflects that the local OA entity has discovered the peer but
has not yet accepted or rejected the configuration of the peer. The local device can, for
whatever reason, decide that the peer device is unacceptable and decline OAM peering.
16, Peering Locally rejected - This message appears when the local OAM entity rejects the
peer OAM entity.
17, Send Local and remote OK - This state shows that the OAM peering is allowed by the
local device.
18, OAM peering Remotely Rejected - This state show that the remote OAM entity rejects
the peering.
19, Operational - Indicate that local and remote OAM entities have accepted the peeing.
And OAM is up and running.
20, Non OperHalf Duplex - This message is indicated when OAM is enable on a half duplex
link as it is not intended to function on half duplex link.