List of MEPIDs that belong to this 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.
For all bridges in which the same MAID {dot1agCfmMdFormat,
dot1agCfmMdName, dot1agCfmMaNetFormat, and dot1agCfmMaNetName}
is configured, the same set of dot1agCfmMaMepListIdentifiers
MUST be configured in the bridges' dot1agCfmMaMepListTables.
This allows each MEP to determine whether or not it is
receiving CCMs from all of the other MEPs in the MA.
For example, if one were creating a new MA whose MAID were
{charString, 'Dom1', charString, 'MA1'}, that had 2 MEPs, whose
MEPIDs were 1 and 3, one could, in Bridge A:
1. Get a new MD index d from dot1agCfmMdTableNextIndex.
2. Create the Maintenance Domain {charString, 'Dom1'}.
3. Get a new MA index a from dot1agCfmMdMaNextIndex [d].
4. Create the Maintenance Association {charString, 'MA1'}.
5. Create a new dot1agCfmMaMepListEntry for each of the MEPs
in the MA: [d, a, 1] and [d, a, 3].
6. Create one of the new MEPs, say [d, a, 1].
Then, in Bridge B:
7. Do all of these steps 1-6, except for using the other MEPID
for the new MEP in Step 6, in this example, MEPID 3.
Note that, when creating the MA, MEP List Table, and MEP
entries in the second bridge, the indices 'd' and 'a'
identifying the MAID {charString, 'Dom1', charString, 'MA1'}
may have different values than those in the first Bridge.
List of MEPIDs that belong to this 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.
For all bridges in which the same MAID {dot1agCfmMdFormat,
dot1agCfmMdName, dot1agCfmMaNetFormat, and dot1agCfmMaNetName}
is configured, the same set of dot1agCfmMaMepListIdentifiers
MUST be configured in the bridges' dot1agCfmMaMepListTables.
This allows each MEP to determine whether or not it is
receiving CCMs from all of the other MEPs in the MA.
For example, if one were creating a new MA whose MAID were
{charString, 'Dom1', charString, 'MA1'}, that had 2 MEPs, whose
MEPIDs were 1 and 3, one could, in Bridge A:
1. Get a new MD index d from dot1agCfmMdTableNextIndex.
2. Create the Maintenance Domain {charString, 'Dom1'}.
3. Get a new MA index a from dot1agCfmMdMaNextIndex [d].
4. Create the Maintenance Association {charString, 'MA1'}.
5. Create a new dot1agCfmMaMepListEntry for each of the MEPs
in the MA: [d, a, 1] and [d, a, 3].
6. Create one of the new MEPs, say [d, a, 1].
Then, in Bridge B:
7. Do all of these steps 1-6, except for using the other MEPID
for the new MEP in Step 6, in this example, MEPID 3.
Note that, when creating the MA, MEP List Table, and MEP
entries in the second bridge, the indices 'd' and 'a'
identifying the MAID {charString, 'Dom1', charString, 'MA1'}
may have different values than those in the first Bridge.
List of MEPIDs that belong to this 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.
For all bridges in which the same MAID {dot1agCfmMdFormat,
dot1agCfmMdName, dot1agCfmMaNetFormat, and dot1agCfmMaNetName}
is configured, the same set of dot1agCfmMaMepListIdentifiers
MUST be configured in the bridges' dot1agCfmMaMepListTables.
This allows each MEP to determine whether or not it is
receiving CCMs from all of the other MEPs in the MA.
For example, if one were creating a new MA whose MAID were
{charString, 'Dom1', charString, 'MA1'}, that had 2 MEPs, whose
MEPIDs were 1 and 3, one could, in Bridge A:
1. Get a new MD index d from dot1agCfmMdTableNextIndex.
2. Create the Maintenance Domain {charString, 'Dom1'}.
3. Get a new MA index a from dot1agCfmMdMaNextIndex [d].
4. Create the Maintenance Association {charString, 'MA1'}.
5. Create a new dot1agCfmMaMepListEntry for each of the MEPs
in the MA: [d, a, 1] and [d, a, 3].
6. Create one of the new MEPs, say [d, a, 1].
Then, in Bridge B:
7. Do all of these steps 1-6, except for using the other MEPID
for the new MEP in Step 6, in this example, MEPID 3.
Note that, when creating the MA, MEP List Table, and MEP
entries in the second bridge, the indices 'd' and 'a'
identifying the MAID {charString, 'Dom1', charString, 'MA1'}
may have different values than those in the first Bridge.
List of MEPIDs that belong to this 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.
For all bridges in which the same MAID {dot1agCfmMdFormat,
dot1agCfmMdName, dot1agCfmMaNetFormat, and dot1agCfmMaNetName}
is configured, the same set of dot1agCfmMaMepListIdentifiers
MUST be configured in the bridges' dot1agCfmMaMepListTables.
This allows each MEP to determine whether or not it is
receiving CCMs from all of the other MEPs in the MA.
For example, if one were creating a new MA whose MAID were
{charString, 'Dom1', charString, 'MA1'}, that had 2 MEPs, whose
MEPIDs were 1 and 3, one could, in Bridge A:
1. Get a new MD index d from dot1agCfmMdTableNextIndex.
2. Create the Maintenance Domain {charString, 'Dom1'}.
3. Get a new MA index a from dot1agCfmMdMaNextIndex [d].
4. Create the Maintenance Association {charString, 'MA1'}.
5. Create a new dot1agCfmMaMepListEntry for each of the MEPs
in the MA: [d, a, 1] and [d, a, 3].
6. Create one of the new MEPs, say [d, a, 1].
Then, in Bridge B:
7. Do all of these steps 1-6, except for using the other MEPID
for the new MEP in Step 6, in this example, MEPID 3.
Note that, when creating the MA, MEP List Table, and MEP
entries in the second bridge, the indices 'd' and 'a'
identifying the MAID {charString, 'Dom1', charString, 'MA1'}
may have different values than those in the first Bridge.
Parsed from file IEEE8021-CFM-MIB.my.txt
Company: None
Module: IEEE8021-CFM-MIB
List of MEPIDs that belong to this 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.
For all bridges in which the same MAID {dot1agCfmMdFormat,
dot1agCfmMdName, dot1agCfmMaNetFormat, and dot1agCfmMaNetName}
is configured, the same set of dot1agCfmMaMepListIdentifiers
MUST be configured in the bridges' dot1agCfmMaMepListTables.
This allows each MEP to determine whether or not it is
receiving CCMs from all of the other MEPs in the MA.
For example, if one were creating a new MA whose MAID were
{charString, 'Dom1', charString, 'MA1'}, that had 2 MEPs, whose
MEPIDs were 1 and 3, one could, in Bridge A:
1. Get a new MD index d from dot1agCfmMdTableNextIndex.
2. Create the Maintenance Domain {charString, 'Dom1'}.
3. Get a new MA index a from dot1agCfmMdMaNextIndex [d].
4. Create the Maintenance Association {charString, 'MA1'}.
5. Create a new dot1agCfmMaMepListEntry for each of the MEPs
in the MA: [d, a, 1] and [d, a, 3].
6. Create one of the new MEPs, say [d, a, 1].
Then, in Bridge B:
7. Do all of these steps 1-6, except for using the other MEPID
for the new MEP in Step 6, in this example, MEPID 3.
Note that, when creating the MA, MEP List Table, and MEP
entries in the second bridge, the indices 'd' and 'a'
identifying the MAID {charString, 'Dom1', charString, 'MA1'}
may have different values than those in the first Bridge.
Parsed from file IEEE8021-CFM-MIB.mib
Module: IEEE8021-CFM-MIB
dot1agCfmMaMepListTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1agCfmMaMepListEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "List of MEPIDs that belong to this 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. For all bridges in which the same MAID {dot1agCfmMdFormat, dot1agCfmMdName, dot1agCfmMaNetFormat, and dot1agCfmMaNetName} is configured, the same set of dot1agCfmMaMepListIdentifiers MUST be configured in the bridges' dot1agCfmMaMepListTables. This allows each MEP to determine whether or not it is receiving CCMs from all of the other MEPs in the MA. For example, if one were creating a new MA whose MAID were {charString, 'Dom1', charString, 'MA1'}, that had 2 MEPs, whose MEPIDs were 1 and 3, one could, in Bridge A: 1. Get a new MD index d from dot1agCfmMdTableNextIndex. 2. Create the Maintenance Domain {charString, 'Dom1'}. 3. Get a new MA index a from dot1agCfmMdMaNextIndex [d]. 4. Create the Maintenance Association {charString, 'MA1'}. 5. Create a new dot1agCfmMaMepListEntry for each of the MEPs in the MA: [d, a, 1] and [d, a, 3]. 6. Create one of the new MEPs, say [d, a, 1]. Then, in Bridge B: 7. Do all of these steps 1-6, except for using the other MEPID for the new MEP in Step 6, in this example, MEPID 3. Note that, when creating the MA, MEP List Table, and MEP entries in the second bridge, the indices 'd' and 'a' identifying the MAID {charString, 'Dom1', charString, 'MA1'} may have different values than those in the first Bridge." REFERENCE "12.14.6.1.3:g" ::= { dot1agCfmMa 3 }
Vendor: Cisco Systems
Module: IEEE8021-CFM-MIB (IEEE8021-CFM-MIB-V1SMI.my)
Type: TABLE
Access: not-accessible
Syntax: SEQUENCE OF
Automatically extracted from www.mibdepot.com
dot1agCfmMaMepListTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1agCfmMaMepListEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "List of MEPIDs that belong to this 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. For all bridges in which the same MAID {dot1agCfmMdFormat, dot1agCfmMdName, dot1agCfmMaNetFormat, and dot1agCfmMaNetName} is configured, the same set of dot1agCfmMaMepListIdentifiers MUST be configured in the bridges' dot1agCfmMaMepListTables. This allows each MEP to determine whether or not it is receiving CCMs from all of the other MEPs in the MA. For example, if one were creating a new MA whose MAID were {charString, 'Dom1', charString, 'MA1'}, that had 2 MEPs, whose MEPIDs were 1 and 3, one could, in Bridge A: 1. Get a new MD index d from dot1agCfmMdTableNextIndex. 2. Create the Maintenance Domain {charString, 'Dom1'}. 3. Get a new MA index a from dot1agCfmMdMaNextIndex [d]. 4. Create the Maintenance Association {charString, 'MA1'}. 5. Create a new dot1agCfmMaMepListEntry for each of the MEPs in the MA: [d, a, 1] and [d, a, 3]. 6. Create one of the new MEPs, say [d, a, 1]. Then, in Bridge B: 7. Do all of these steps 1-6, except for using the other MEPID for the new MEP in Step 6, in this example, MEPID 3. Note that, when creating the MA, MEP List Table, and MEP entries in the second bridge, the indices 'd' and 'a' identifying the MAID {charString, 'Dom1', charString, 'MA1'} may have different values than those in the first Bridge. " REFERENCE "12.14.6.1.3:g" ::= { dot1agCfmMa 3 }
dot1agCfmMaMepListTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1agCfmMaMepListEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "List of MEPIDs that belong to this 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. For all bridges in which the same MAID {dot1agCfmMdFormat, dot1agCfmMdName, dot1agCfmMaNetFormat, and dot1agCfmMaNetName} is configured, the same set of dot1agCfmMaMepListIdentifiers MUST be configured in the bridges' dot1agCfmMaMepListTables. This allows each MEP to determine whether or not it is receiving CCMs from all of the other MEPs in the MA. For example, if one were creating a new MA whose MAID were {charString, 'Dom1', charString, 'MA1'}, that had 2 MEPs, whose MEPIDs were 1 and 3, one could, in Bridge A: 1. Get a new MD index d from dot1agCfmMdTableNextIndex. 2. Create the Maintenance Domain {charString, 'Dom1'}. 3. Get a new MA index a from dot1agCfmMdMaNextIndex [d]. 4. Create the Maintenance Association {charString, 'MA1'}. 5. Create a new dot1agCfmMaMepListEntry for each of the MEPs in the MA: [d, a, 1] and [d, a, 3]. 6. Create one of the new MEPs, say [d, a, 1]. Then, in Bridge B: 7. Do all of these steps 1-6, except for using the other MEPID for the new MEP in Step 6, in this example, MEPID 3. Note that, when creating the MA, MEP List Table, and MEP entries in the second bridge, the indices 'd' and 'a' identifying the MAID {charString, 'Dom1', charString, 'MA1'} may have different values than those in the first Bridge. " REFERENCE "12.14.6.1.3:g" ::= { dot1agCfmMa 3 }
dot1agCfmMaMepListTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1agCfmMaMepListEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "List of MEPIDs that belong to this 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. For all bridges in which the same MAID {dot1agCfmMdFormat, dot1agCfmMdName, dot1agCfmMaNetFormat, and dot1agCfmMaNetName} is configured, the same set of dot1agCfmMaMepListIdentifiers MUST be configured in the bridges' dot1agCfmMaMepListTables. This allows each MEP to determine whether or not it is receiving CCMs from all of the other MEPs in the MA. For example, if one were creating a new MA whose MAID were {charString, 'Dom1', charString, 'MA1'}, that had 2 MEPs, whose MEPIDs were 1 and 3, one could, in Bridge A: 1. Get a new MD index d from dot1agCfmMdTableNextIndex. 2. Create the Maintenance Domain {charString, 'Dom1'}. 3. Get a new MA index a from dot1agCfmMdMaNextIndex [d]. 4. Create the Maintenance Association {charString, 'MA1'}. 5. Create a new dot1agCfmMaMepListEntry for each of the MEPs in the MA: [d, a, 1] and [d, a, 3]. 6. Create one of the new MEPs, say [d, a, 1]. Then, in Bridge B: 7. Do all of these steps 1-6, except for using the other MEPID for the new MEP in Step 6, in this example, MEPID 3. Note that, when creating the MA, MEP List Table, and MEP entries in the second bridge, the indices 'd' and 'a' identifying the MAID {charString, 'Dom1', charString, 'MA1'} may have different values than those in the first Bridge. " REFERENCE "12.14.6.1.3:g" ::= { dot1agCfmMa 3 }
dot1agCfmMaMepListTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1agCfmMaMepListEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "List of MEPIDs that belong to this 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. For all bridges in which the same MAID {dot1agCfmMdFormat, dot1agCfmMdName, dot1agCfmMaNetFormat, and dot1agCfmMaNetName} is configured, the same set of dot1agCfmMaMepListIdentifiers MUST be configured in the bridges' dot1agCfmMaMepListTables. This allows each MEP to determine whether or not it is receiving CCMs from all of the other MEPs in the MA. For example, if one were creating a new MA whose MAID were {charString, 'Dom1', charString, 'MA1'}, that had 2 MEPs, whose MEPIDs were 1 and 3, one could, in Bridge A: 1. Get a new MD index d from dot1agCfmMdTableNextIndex. 2. Create the Maintenance Domain {charString, 'Dom1'}. 3. Get a new MA index a from dot1agCfmMdMaNextIndex [d]. 4. Create the Maintenance Association {charString, 'MA1'}. 5. Create a new dot1agCfmMaMepListEntry for each of the MEPs in the MA: [d, a, 1] and [d, a, 3]. 6. Create one of the new MEPs, say [d, a, 1]. Then, in Bridge B: 7. Do all of these steps 1-6, except for using the other MEPID for the new MEP in Step 6, in this example, MEPID 3. Note that, when creating the MA, MEP List Table, and MEP entries in the second bridge, the indices 'd' and 'a' identifying the MAID {charString, 'Dom1', charString, 'MA1'} may have different values than those in the first Bridge. " REFERENCE "12.14.6.1.3:g" ::= { dot1agCfmMa 3 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.111.2.802.1.1.8.1.6.3.1 | dot1agCfmMaMepListEntry | 2 | 2 | The known MEPS table entry. |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.111.2.802.1.1.8.1.6.1 | dot1agCfmMaNetTable | 1 | 6 | The Maintenance Association table. Each row in the table represents an MA. An MA is a set of MEPs, each configured with a singl… |
| 1.3.111.2.802.1.1.8.1.6.2 | dot1agCfmMaCompTable | 1 | 7 | The Maintenance Association table. Each row in the table represents an MA. An MA is a set of MEPs, each configured with a singl… |
| 1.3.111.2.802.1.1.8.1.6.4 | ieee8021CfmMaCompTable | 1 | 8 | The Maintenance Association table. Each row in the table represents an MA. An MA is a set of MEPs, each configured with a singl… |