SUPERMICRO-ECFM-MIB Table View

List of Port related Parameters for ecfm module.

The Maintenance Intermediate Point (MIP) table.
          
Each row in the table represents a different MIP. 
A MIP consists two MIP Half Functions (MHFs) on a 
single Bridge Port, an Up MHF and a Down MHF.

It is a list of every distinct {FID, source_address, 
InterfaceIndex} triple from all of the CCMs presented
to all of the Bridge.s MPs. Continuity Check Receivers
since the Bridge was last reset. Entries in the MIP CCM
Database are timed out very slowly, on the order of one day,
so that their information is available for fault isolation long 
after the information is no longer used for frame forwarding.

The Dynamic Maintenance Intermediate Point (MIP) Prevention table.
An entry in this table will restrict the automatic creation of 
MIPs for the corresponding index (IfIndex, MD Level and VLAN Id).

The MEP Database. A database, maintained by every MEP, that
maintains received information about other MEPs in the
Maintenance Domain.

This table contains a list of parameters with which the linktrace
messages were transmitted/initiated by MEP

The Maintenance Association 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 Association, and is an endpoint of a
separate Maintenance Entity for each of the other MEPs in
the same Maintenance Association (802.1ag clause 3.18).
          
This table uses three indices. The first two indices are the
indices of the Maintenance Domain and MA tables, the reason
being that a MEP is always related to an MA and Maintenance
Domain.

The Maintenance Domain table. Each row in the table
represents a different Maintenance Domain. A Maintenance Domain
is described in 802.1ag (3.22) as the network or the part of the
network for which faults in connectivity are to be managed. The
boundary of a Maintenance Domain is defined by a set of DSAPs, 
each of which can become a point of connectivity to a service
instance.

The Maintenance Association table.  Each row in the table
represents an MA.  An MA is a set of MEPs, each configured
with a single service instance.
          
Creation of a Service Instance establishes a connectionless
association among the selected DSAPs.  Configuring a
Maintenance association End Point (MEP) at each of the
DSAPs creates a Maintenance Association (MA) to monitor
that connectionless connectivity.  The MA is identified by a
Short MA Name that is unique within the Maintenance Domain
and chosen to facilitate easy identification of the Service
Instance.  Together, the Maintenance Domain Name and the
Short MA Name form the Maintenance Association Identifier
(MAID) that is carried in CFM Messages to identify
incorrect connectivity among Service Instances.  A small
integer, the Maintenance association End Point Identifier
(MEPID), identifies each MEP among those configured on a
single MA (802.1ag clauses 3.17 and 18.2).
          
This table uses two indices, first index is the index of the
Maintenance Domain table.
          
The writable objects in this table need to be persistent
upon reboot or restart of a device.