To configure an 802.3ah EFM OAM diagnostic test from an NE Properties form

CAUTION

Service Disruption

Performing an 802.3ah EFM diagnostic is service-affecting.

Ensure that you consider the implications of performing this test before you proceed.

Steps

Note: For the 802.3ah EFM diagnostic to be successful, the local and peer ports must support the 802.3ah protocol, and be operationally and administratively up.

When a port is in loopback mode, service mirroring does not work if the port is a mirror source or a mirror destination.

Satellite ports support virtually all OAM functionality. The only exception is that no EFM-OAM link monitoring is available for such ports.

Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view.

Right-click on the device where you want to configure an 802.3ah EFM OAM diagnostic and select Properties. The Network Element (Edit) form opens.

On the Network Element (Edit) form navigation tree, expand the Shelf icon.

Expand to the port level and click on a port object. The Physical Port (Edit) form opens.

Click on the Ethernet tab. The Ethernet port configuration form opens.

Click on the EFM-OAM tab. The EFM-OAM form opens.

Configure the required parameters.

Click Apply. A dialog box appears.

Click Yes.

Click Resync.

The EFM-OAM form is updated with the results of the 802.3ah EFM diagnostic. The values that are displayed on the form depend on the configuration of the local and peer ports.

Table 90-3, 802.3ah EFM OAM results, Table 90-4, 802.3ah EFM OAM Statistics and Table 90-5, 802.3ah EFM OAM peer information describe the displayed information.

Table 90-3: 802.3ah EFM OAM results

Parameter	Value	Description
Operational Status (dot3OamOperStatus)	Disabled	The Administrative State parameter on the local port is set to Disabled.
	Active Send Local	The Mode parameter is set to Active and the local port is discovering the peer port EFM OAM capabilities.
	Passive Wait	The Mode parameter is set to Passive and the local port is waiting to receive OAMPDUs from the peer device.
	Send Local and Remote	The local port discovered the peer but has not yet accepted or rejected the configuration of the peer. The local port may determine that the peer port is not compatible and decline OAM peering.
	OAM Peering Locally Rejected	The local port declined OAM peering.
	Send Local and Remote Ok	The local port accepted OAM peering.
	OAM Peering Remotely Rejected	The remote port declined OAM peering.
	Operational	The local and remote ports accepted the OAM peering.
	Non-operational Half Duplex	The Administrative State parameter is set to Enabled but the local port is in half-duplex mode.
	Link Fault	The link detected a fault and is transmitting OAMPDUs with a link fault indication.
Max. PDU Size (dot3OamMaxOamPduSize)	PDU size	The largest OAMPDU size, in bytes, that is supported by the local port: Minimum is 64 Maximum is 1518 Default is 1514
Configuration Revision (dot3OamConfigRevision)	0 to 65 535	The configuration revision of the OAM entity obtained from the latest OAMPDU sent by the OAM entity. The value is used by OAM entities to indicate that configuration changes occurred that may require the peer OAM entity to re-evaluate whether OAM peering is allowed.
Functions Supported (dot3OamFunctionsSupported)	Event Support	The port can send and receive event notification OAMPDUs.
	Loopback Support	The port can initiate and respond to loopback commands.
	Unidirectional Support	The port supports the transmission of OAMPDUs on links that operate in unidirectional mode.
	Variable Support	The port can send and receive variable request and response OAMPDUs.
Loopback Status (dot3OamLoopbackStatus)	No Loopback	The port is not in a loopback condition.
	Initiating Loopback	The local device initiated a loopback, sent a loopback OAMPDU and is waiting for a response from the peer port.
	Remote Loopback	The peer port is in loopback mode.
	Terminating Loopback	The local port is in the process of terminating a loopback on the peer port.
	Local Loopback	The peer port has put the local port into loopback mode.
	Unknown	An OAMPDU that contains an unexpected message was received by the local port.

Table 90-4: 802.3ah EFM OAM Statistics

Statistics	Displayed Value	Description
Frames Lost Due to OAM(dot3OamFramesLostDueToOam)	Number of frames	The number of frames that were dropped by the OAM multiplexer. Discontinuities of this counter can occur under some conditions.
Information Rx (dot3OamInformationRx)	Number of OAMPDUs	The number of information OAMPDUs received on this interface
Information Tx (dot3OamInformation Tx)	Number of OAMPDUs	The number of information OAMPDUs transmitted on this interface. Discontinuities of this counter can occur can occur under some conditions.
Loopback Control Rx (dot3OamLoopbackControlRx)	Number of OAMPDUs	The number of loopback control OAMPDUs received on this interface
Loopback Control Tx (dot3OamLoopbackConrolTx)	Number of OAMPDUs	The number of loopback control OAMPDUs transmitted on this interface
Unsupported Codes Rx (dot3OamUnsupportedCodesRx)	Number of OAMPDUs	The number of OAMPDUs received on this interface with an unsupported opcode
Unsupported Codes Tx (dot3OamUnsupportedCodesTx)	Number of OAMPDUs	The number of OAMPDUs transmitted on this interface with an unsupported opcode

Table 90-5: 802.3ah EFM OAM peer information

Peer Information	Displayed Value	Description
Peer MAC Address (dot3OamPeerMacAddress)	MAC address	The MAC address of the peer port. The MAC address is contained in the received OAMPDU.
Peer Vendor OUI (dot3OamPeerVendorOui)	OUI	The OUI of the OAM peer. The OUI is part of the peer MAC address contained in the received OAMPDU. The OUI can be used to identify the vendor of the remote OAM device.
Peer Vendor Info (dot3OamPeerVendorInfo)	Vendor information text	The vendor information field is in the local information TLV, and can be used to determine additional information about the peer device.
Peer Mode (dot3OamPeerMode)	Active or Passive	See Mode
Peer Max PDU Size (dot3OamPeerMaxOamPduSize)	PDU size	The largest OAMPDU value, in bytes, that is supported by the peer port. Minimum is 64 Maximum is 1518 Default is 1514
Peer Configuration Revision (dot3OamPeerConfigRevision)	0 to 65 535	The configuration revision of the OAM device as identified in the latest OAMPDU sent by the OAM peer. The configuration revision is used by OAM devices to indicate that configuration changes have occurred which might require the peer OAM device to re-evaluate whether OAM peering is allowed.
Peer Functions Supported (dot3OamPeerFunctSupported)	Event Support	The peer port can send and receive Event Notification OAMPDUs.
	Loopback Support	The peer port can initiate and respond to loopback commands.
	Unidirectional Support	The peer port supports the transmission of OAMPDUs on links that are operating in unidirectional mode.
	Variable Support	The peer port can send and receive Variable Request and Response OAMPDUs.

Close the EFM-OAM form when you have completed the EFM OAM diagnostic.

End of steps