SUPERMICRO-ECFM-Y1731-MI-MIB Table View

Contains ECFM information specific to interface.

List of per virtual context ECFM-Y1731 Module Parameters.

The Maintenance Entity Group table. Each row in the table
represents a different Maintenance Entity Group.
          
A Maintenance Entity Group is described in ITU-T Recommendation 
Y.1731 as the one which includes different MEs that satisfy the 
following conditions:
- MEs in a MEG exist in the same administrative boundary; and
- MEs in a MEG have the same MEG Level; and
- MEs in a MEG belong to the same point-to-point ETH connection or 
  multipoint ETH connectivity.

The Maintenance Entity table.  Each row in the table represents 
an ME.  An ME represents a relationship between two MEPs, each 
configured with a single service instance.
          
Configuring a Maintenance Entity Group End Point (MEP) at each 
of the DSAPs creates a Maintenance Entity (ME) to monitor
that connectionless connectivity. The ITU-Carrier Code (ICC) and 
Unique MEGID Code (UMC) form the Maintenance Entity Group Identifier 
(MEGID) that is carried in CFM Messages to identify incorrect 
connectivity among Service Instances.  A small integer, the 
Maintenance Entity Group End Point Identifier (MEPID), identifies 
each MEP among those configured on a single ME.
          
This table uses two indices, first index is the index of the
Maintenance Entity Group table.
          
The writable objects in this table need to be persistent
upon reboot or restart of a device.

The Maintenance Entity Group End Point (MEP) table.
          
Each row in the table represents a different MEP. A MEP is
an actively managed CFM entity, associated with a specific
DSAP of a Service Instance, which can generate and receive
CFM PDUs and track any responses.  It is an end point of a
single Maintenance Entity.
          
This table uses three indices. The first two indices are the
indices of the Maintenance Entity Group (MEG) and Maintenance 
Entity (ME) tables, the reason being that a MEP is always 
related to an ME and MEG.
          
The MEP table stores all the managed objects for sending
LBM, LTM, AIS and LCK. This table also stores all the managed
objects required for monitoring the performance.
          
The objects which are used to initiate a transaction are to
be set only when the row-status of the table is active.
'fsMIY1731MepTransmit' naming convention is used to isolate 
these objects from the others.

The Error Log table.
Size of this table is defined by the object fsMIY1731ErrorLogSize.
If the addition of an error entry would exceed the 
resources allocated to table, then the oldest entries in the table are 
deleted until sufficient resources are available to hold the new
error entry.
          
Each row in the table represents error or defect
detected by a specific MEP.
This table uses three indices. The first four are the indices of MEP
table the reason being that a error or defect can only
be detected by MEP.
          
SNMP SMI does not allow to state in a MIB that an object in
a table is an array.  The solution is to take the index (or
indices) of the first table and add one or more indices.

This table extends the MEP table and contains a list of
Linktrace replies received by a specific MEP in response to
a linktrace message.
          
SNMP SMI does not allow to state in a MIB that an object in
a table is an array.  The solution is to take the index (or
indices) of the first table and add one or more indices.

This table extends the MEP table and contains information of
Loopback messages sent by a specific MEP.
          
SNMP SMI does not allow to state in a MIB that an object in
a table is an array.  The solution is to take the index (or
indices) of the first table and add one or more indices.

This table extends the MEP table and contains a list of
Loopback replies received by a specific MEP in response to
a loopback message.
          
Size of this table is defined by the object fsMIY1731LbrCacheSize.
If the addition of a loopback reply entry would exceed the 
resources allocated to table, then the oldest entries in the table are 
deleted until sufficient resources are available to hold the new
loopback reply entry.
          
SNMP SMI does not allow to state in a MIB that an object in
a table is an array.  The solution is to take the index (or
indices) of the first table and add one or more indices.

This table extends the MEP table and contains output of loopback 
or ping transaction. 
Output includes number of replies recieved, time taken for a reply to
come.
          
SNMP SMI does not allow to state in a MIB that an object in
a table is an array.  The solution is to take the index (or
indices) of the first table and add one or more indices.

This table extends the MEP table and contains a list of
information about the Frame Delay measured at various times by a 
MEP.
Size of this table is defined by the object
fsMIY1731FrameDelayBufferSize. If the addition of a frame delay entry 
would exceed the resources allocated to table, then the oldest entries 
in the table are deleted until sufficient resources are available to 
hold the new frame delay entry.
          
Delay Measured can be of one-way or two-way.

This table extends the MEP table and contains output of one-way and 
two-way delay measurement transaction.

This table extends the MEP table and contains a information about
the Frame-loss measured at various times by a MEP. 
          
Size of this table is defined by the object
fsMIY1731FrameLossBufferSize. If the addition of a frame loss entry 
would exceed the resources allocated to table, then the oldest entries 
in the table are deleted until sufficient resources are available to 
hold the new frame loss entry.

This table extends the MEP table and contains output of 
frame-loss measurement transaction.

The Remote Maintenance End Point table for the Y.1731 extensions
over MPLS-TP networks. 
Each row in the table realizes an ME for the MPLS-TP networks using
the local and remote MEP identifiers which are indices to the table. 
This table is mainly used to associate a specific LSP/PW to an ME.
          
This table uses five indices, first index provides the virtual context 
identifier in which this entry resides. The second index is the index 
to the MEG table identifying the specific MD/Level. Third index is the 
index to ME table identifying the specific MEG. The fourth index is 
the Local MEP Indentifier. The fifth index is the remote MEP Identifier.
          
The writable objects in this table need to be persistent upon reboot 
or restart of a device.

List of per virtual context ECFM-Y1731 Module Statistics.