Lantronix S3220 Series User Guide Rev J PDF 34.75 MB - Page 155

Transition Networks ION x222x / x32xx User Guide Disabled ‐ This value is always Disabled(1) if LOAM is disabled on this interface via the 'Admin Status'. LinkFault ‐ If the link has detected a fault and is transmitting OAMPDUs with a link fault indication, the value is LinkFault(2). Also, if the interface is not operational ('Link Status' is not Up(1)), LinkFault(2) is returned. Note that the object 'Link Status' may not be Up(1) as a result of link failure or administrative action (ifAdminState being Down(2) or Testing(3)). PassiveWait ‐ The PassiveWait(3) state is returned only by LOAM entities in passive mode ('LOAM Mode') and reflects the state in which the LOAM entity is waiting to see if the peer device is OA capable. Active Send Local ‐ The Active Send Local(4) value is used by active mode devices ('LOAM Mode') and reflects the LOAM entity actively trying to discover whether the peer has LOAM capability but has not yet made that determination. SendLocalAndRemote ‐ The state SendLocalAndRemote(5) 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 LOAM peering. SendLocalAndRemoteOk ‐ If the LOAM peering is allowed by the local device, the state moves to SendLocalAndRemoteOk(6). LoamPeeringLocallyRejected ‐ If the local LOAM entity rejects the peer LOAM entity, the state becomes OamPeeringLocallyRejected(7). Note that both the SendLocalAndRemote(5) and OamPeeringLocallyRejected(7) states fall within the state SEND_LOCAL_REMOTE of the Discovery state diagram [see 802.3ah, Figure 57‐5], with the difference being whether the local LOAM client has actively rejected the peering or has just not indicated any decision yet. Whether a peering decision has been made is indicated via the local flags field in the OAMPDU (reflected in the aOAMLocalFlagsField of 30.3.6.1.10). LamPeeringRemotelyRejected ‐ If the remote LOAM entity rejects the peering, the state becomes LoamPeeringRemotelyRejected(8). Note that both the SendLocalAndRemoteOk(6) and LoamPeeringRemotelyRejected(8) states fall within the state SEND_LOCAL_REMOTE_OK of the Discovery state diagram [802.3ah, Figure 57‐5], with the difference being whether the remote LOAM client has rejected the peering or has just not yet decided. This is indicated via the remote flags field in the OAMPDU (reflected in the aLOAMRemoteFlagsField of 30.3.6.1.11). Operational ‐ When the local LOAM entity learns that both it and the remote LOAM entity have accepted the peering, the state moves to Operational(9) corresponding to the SEND_ANY state of the Discovery state diagram [802.3ah, Figure 57‐5]. NonOperHalfDuplex ‐ Since Ethernet LOAM functions are not designed to work completely over half‐duplex interfaces, the value NonOperHalfDuplex(10) is returned whenever Ethernet LOAM is enabled ('Admin Status' is Enabled(1)), but the interface is in half‐duplex operation. LOAM Peer Information Fields Each port's LOAM > Main tab > LOAM Peer Information section field is described below. MAC Address ‐ in the format 00‐00‐00‐00‐00‐00. Vendor OUI ‐ in the format 00.00.00. The OUI of the entity defining the object type. All IEEE 802.3 defined events (as appearing in [802.3ah] except for the Organizationally Unique Event TLVs) use the IEEE 802.3 OUI of 0x0180C2. Organizations defining their own Event Notification TLVs include their OUI in the Event Notification TLV that gets reflected here. 33472 Rev. J https://www.transition.com Page 155 of 700