ZXEPON-SERVICE-OAM-MIB Table View

This table contains the primary controls and status for the OAM 
capabilities of an Ethernet like interface. There will be one row 
in this table for each Ethernet like interface in the system that 
supports the OAM functions defined in [802.3ah].

This table contains information about the OAM peer for a particular Ethernet 
like interface. OAM entities communicate with a single OAM peer entity on 
Ethernet links on which OAM is enabled and operating properly. There is one 
entry in this table for each entry in the OamTable for which information 
on the peer OAM entity is available.

This table contains controls for the loopback state of the local link as well 
as indicating the status of the loopback function. There is one entry in this 
table for each entry in OamTable that supports loopback functionality 
(where OamFunctionsSupported includes the loopbackSupport bit set). 
Loopback can be used to place the remote OAM entity in a state where every 
received frame (except OAMPDUs) are echoed back over the same interface 
on which they were received. In this state, at the remote entity, 'normal' 
traffic is disabled as only the looped back frames are transmitted on 
the interface. Loopback is thus an intrusive operation that prohibits normal 
data flow and should be used accordingly.

This table contains statistics for the OAM function on a particular Ethernet 
like interface. There is an entry in the table for every entry in the OamTable. 
The counters in this table are defined as 32-bit entries to match the counter size 
as defined in [802.3ah]. Given the OAM protocol is a slow protocol, the counters 
increment at a slow rate.

Ethernet OAM includes the ability to generate and receive Event Notification OAMPDUs 
to indicate various link problems. This table contains the mechanisms to enable 
Event Notifications and configure the thresholds to generate the standard Ethernet 
OAM events. There is one entry in the table for every entry in OamTable that 
supports OAM events (where OamFunctionsSupported includes the eventSupport bit set). 
The values in the table are maintained across changes to OamOperStatus. There 
are other events (dying gasp, critical events) that are not threshold crossing 
events but which can be enabled/disabled via this table.

This table records a history of the events that have occurred at the Ethernet 
OAM level. These events can include locally detected events, which may result 
in locally generated OAMPDUs, and remotely detected events, which are detected 
by the OAM peer entity and signaled to the local entity via Ethernet OAM. 
Ethernet OAM events can be signaled by Event Notification OAMPDUs or by the 
flags field in any OAMPDU. This table contains both threshold crossing events 
and non-threshold crossing events. The parameters for the threshold window, 
threshold value, and actual value (OamEventLogWindowXX, OamEventLogThresholdXX, 
OamEventLogValue) are only applicable to threshold crossing events, and 
are returned as all F's (2^32 - 1) for non-threshold crossing events. Entries 
in the table are automatically created when such events are detected. The size 
of the table is implementation dependent. When the table reaches its maximum 
size, older entries are automatically deleted to make room for newer entries.