Use the Administration > OAM > Interface page to enable OAM functionality on the selected port. Not all CPEs support operation and maintenance functions, so OAM is therefore disabled by default. If a CPE supports OAM, this functionality must first be enabled on the connected port to gain access to the configuration functions provided under the OAM menu.
Port identifier.
Enables or disables OAM functions. (Default: Disabled)
Shows the operational state between the local and remote OAM devices. This value is always "disabled" if OAM is disabled on the local interface.
OAM is disabled on this interface via the OAM Admin Status.
The link has detected a fault or the interface is not operational.
This value is returned only by OAM entities in passive mode and indicates the OAM entity is waiting to see if the peer device is OAM capable.
This value is used by active mode devices and indicates the OAM entity is actively trying to discover whether the peer has OAM capability but has not yet made that determination.
The local OAM entity has discovered the peer but has not yet accepted or rejected the configuration of the peer.
OAM peering is allowed by the local device.
The local OAM entity rejects the peering.
The remote OAM entity rejects the peering.
When the local OAM entity learns that both it and the remote OAM entity have accepted the peering, the state moves to this state.
This state is returned whenever Ethernet OAM is enabled but the interface is in half-duplex operation.
Sets the OAM operation mode. (Default: Active)
All OAM functions are enabled.
All OAM functions are enabled, except for OAM discovery, sending variable request OAMPDUs, and sending loopback control OAMPDUs.
Controls reporting of critical link events to its OAM peer.
If an unrecoverable condition occurs, the local OAM entity (i.e., this switch) indicates this by immediately sending trap message. (Default: Enabled)
Dying gasp events are caused by an unrecoverable failure, such as a power failure or device reset.
When system power fails, the switch will always send a dying gasp trap message prior to power down.
If a critical event occurs, the local OAM entity indicates this to its peer by setting the appropriate flag in the next OAMPDU to be sent and stores this information in its OAM event log. (Default: Enabled)
Critical events include various failures, such as abnormal voltage fluctuations, out-of-range temperature detected, fan failure, CRC error in flash memory, insufficient memory, or other hardware faults.
Controls reporting of errored frame link events.
An errored frame is a frame in which one or more bits are errored.
An errored frame link event occurs if the threshold is reached or exceeded within the specified period.
If reporting is enabled and an errored frame link event occurs, the local OAM entity (this switch) sends an Event Notification OAMPDU to the remote OAM entity. The Errored Frame Event TLV includes the number of errored frames detected during the specified period.
Enables reporting of errored frame link events. (Default: Enabled)
The period of time in which to check the reporting threshold for errored frame link events. (Range: 10-65535 in units of 10 milliseconds; Default: 10 units of 10 milliseconds, or the equivalent of 1 second)
The threshold for errored frame link events. (Range: 1-65535; Default: 1)