SUPERMICRO-ECFM-MI-MIB Table View

List of per virtual context ECFM Module parameters.

This table defines the association of VIDs into VLANs.  There
is an entry in this table for each VID that is:
    a) a VID belonging to a VLAN associated with more than
       one VID; and
    b) not the Primary VLAN of that VID.
The entry in this table contains the Primary VID of the VLAN.
          
By default, this table is empty, meaning that every VID is
the Primary VID of a single-VID VLAN.
          
VLANs that are associated with only one VID SHOULD NOT have
an entry in this table.
          
The writable objects in this table need to be persistent
upon reboot or restart of a device.

The Default MD Level Managed Object controls MHF creation for
VIDs that are not attached to a specific Maintenance
Association Managed Object, and Sender ID TLV transmission by
those MHFs.
          
For each Bridge Port, and for each VLAN ID whose data can
pass through that Bridge Port, an entry in this table is
used by the algorithm in subclause 22.2.3 only if there is no
entry in the Maintenance Association table defining an MA
for the same VLAN ID and MD Level as this table's entry, and
on which MA an Up MEP is defined.  If there exists such an
MA, that MA's objects are used by the algorithm in
subclause 22.2.3 in place of this table entry's objects.  The
agent maintains the value of fsMIEcfmDefaultMdStatus to
indicate whether this entry is overridden by an MA.
          
When first initialized, the agent creates this table
automatically with entries for all VLAN IDs,
with the default values specified for each object.
          
After this initialization, the writable objects in this
table need to be persistent upon reboot or restart of a
device.

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.

List of MEPIDs (in any bridge) that belong to the same MA.
          
Clause 12.14.6.1.3 specifies that a list of MEPIDs in all
bridges in that MA, but since SNMP SMI does not allow to
state in a MIB that an object in a table is an array, the 
information has to be stored in another table with two
indices, being the first index, the index of the table that 
contains the list or array.

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 Transmit Loopback table.  Entries in this table are
created/removed at the same time than entries in the MEP
table are created/removed.
          
The MEP table also stores all the managed objects for sending
LBM and LTM.
          
*LBM Managed objects
          
LBM Managed objects in the MEP table 
enables the management entity to initiate
transmission of Loopback messages.  It will signal the MEP
that it should transmit some number of Loopback messages
and detect the detection (or lack thereof) of the
corresponding Loopback messages.
          
Steps to use entries in this table:
          
1) Wait for fsMIEcfmMepTransmitLbmStatus value to be
   'ready'.  To do this do this sequence:
   a. an SNMP GET for both SnmpSetSerialNo and
      fsMIEcfmMepTransmitLbmStatus objects (in same SNMP
      PDU).
   b. Check if value for fsMIEcfmMepTransmitLbmStatus is
      'ready'
      - if not, wait x seconds, go to step a above.
      - if yes, save the value of SnmpSetSerialNo and go
        to step 2) below
2) Change fsMIEcfmMepTransmitLbmStatus value from 'ready' to
   'notReady' to ensure no other management entity will use
   the service. In order to not disturb a possible other NMS
   do this by sending an SNMP SET for both SnmpSetSerialNo 
   and fsMIEcfmMepTransmitLbmStatus objects (in same SNMP
   PDU,  and make sure SNmpSetSerialNo is the first varBind).
   For the SnmpSetSerialNo varBind, use the value that you
   obtained in step 1)a.. This ensures that two cooperating
   NMSes will not step on each others toes.
3) Setup the different data to be sent (number of messages,
   optional TLVs,...).
4) Record the current values of fsMIEcfmMepLbrIn,
   fsMIEcfmMepLbrInOutOfOrder, and fsMIEcfmMepLbrBadMsdu.
6) Change fsMIEcfmMepTransmitLbmStatus value from 'notReady'
   to 'transmit' to initiate transmission of Loopback
   messages.
7) Check the value of fsMIEcfmMepTransmitLbmResultOK to
   find out if the operation was successfully initiated or
   not.
8) Monitor the value of fsMIEcfmMepTransmitLbmMessages.
   When it reaches 0, the last LBM has been transmitted.
   Wait an additional 5 seconds to ensure that all LBRs have
   been returned.
9) Compare fsMIEcfmMepLbrIn, fsMIEcfmMepLbrInOutOfOrder,
   and fsMIEcfmMepLbrBadMsdu to their old values from step
   4, above, to get the results of the test.
10) Change the fsMIEcfmMepTransmitLbmStatus value back to
   'ready' to allow other management entities to use the
   table.
          
*LTM Managed objects
The LTM Managed objects in the MEP table are used in a manner
similar to that described for LBM transmission, above.  Upon
successfully initiating the transmission, the variables
fsMIEcfmMepTransmitLtmSeqNumber and
fsMIEcfmMepTransmitLtmEgressIdentifier return the information
required to recover the results of the LTM from the
fsMIEcfmLtrTable.

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.

The MEP Database. A database, maintained by every MEP, that
maintains received information about other MEPs in the
Maintenance Domain.
          
The 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.

It is a list of every distinct {FID, source_address, 
IfIndex} 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 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.

List of per virtual context ECFM Module Statistics parameters.

Port Table

There is one CFM Stack table per bridge. It permits
the retrieval of information about the Maintenance Points
configured on any given interface.

The CFM Configuration Error List table provides a list of
Interfaces and VIDs that are incorrectly configured.

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.

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).