Web Management Guide-R04

Table Of Contents
Chapter 13
| Basic Administration Protocols
OAM Configuration
– 510 –
Mode – Sets the OAM operation mode. (Default: Active)
ActiveAll OAM functions are enabled.
Passive – All OAM functions are enabled, except for OAM discovery,
sending variable request OAMPDUs, and sending loopback control
OAMPDUs.
Critical Link Event – Controls reporting of critical link events to its OAM peer.
Dying Gasp - 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.
Critical Event – 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.
Errored Frame – 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.
Active Send Local 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.
Send Local And Remote The local OAM entity has discovered the peer but has not yet
accepted or rejected the configuration of the peer.
Send Local And Remote
OK
OAM peering is allowed by the local device.
OAM Peering Locally
Rejected
The local OAM entity rejects the peering.
OAM Peering Remotely
Rejected
The remote OAM entity rejects the peering.
Operational When the local OAM entity learns that both it and the remote OAM
entity have accepted the peering, the state moves to this state.
Non Oper Half Duplex This state is returned whenever Ethernet OAM is enabled but the
interface is in half-duplex operation.
Table 35: OAM Operation State (Continued)
State Description