OID reference

rcDot1agCfmMaMepListTable

1.3.6.1.4.1.8886.6.1.32.1.6.3

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 tab…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.8886.6.1.32.1.6 (rcDot1agCfmMa)
Node code
3
Node name
rcDot1agCfmMaMepListTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.8886.6.1.32.1.6.3
URN notation
urn:oid:1.3.6.1.4.1.8886.6.1.32.1.6.3
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 8886 6 1 32 1 6 3}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMa(6) rcDot1agCfmMaMepListTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMa(6) rcDot1agCfmMaMepListTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMa(6) rcDot1agCfmMaMepListTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMa(6) rcDot1agCfmMaMepListTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMa(6) rcDot1agCfmMaMepListTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMa(6) rcDot1agCfmMaMepListTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMa(6) rcDot1agCfmMaMepListTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMa(6) rcDot1agCfmMaMepListTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMa(6) rcDot1agCfmMaMepListTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMa(6) rcDot1agCfmMaMepListTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMa(6) rcDot1agCfmMaMepListTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMa(6) rcDot1agCfmMaMepListTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMa(6) rcDot1agCfmMaMepListTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMa(6) rcDot1agCfmMaMepListTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMa(6) rcDot1agCfmMaMepListTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcDot1ag(32) rcDot1agMIBObjects(1) rcDot1agCfmMa(6) rcDot1agCfmMaMepListTable(3)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/8886/6/1/32/1/6/3
  • /ISO/Identified-Organization/6/1/4/1/8886/6/1/32/1/6/3
  • /ISO/3/6/1/4/1/8886/6/1/32/1/6/3
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/8886/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMa/rcDot1agCfmMaMepListTable
  • /iso/identified-organization/dod/internet/private/enterprise/raisecom/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMa/rcDot1agCfmMaMepListTable
  • /iso/identified-organization/dod/internet/private/enterprise/raiseCom/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMa/rcDot1agCfmMaMepListTable
  • /iso/identified-organization/dod/internet/private/enterprises/8886/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMa/rcDot1agCfmMaMepListTable
  • /iso/identified-organization/dod/internet/private/enterprises/raisecom/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMa/rcDot1agCfmMaMepListTable
  • /iso/identified-organization/dod/internet/private/enterprises/raiseCom/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMa/rcDot1agCfmMaMepListTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/8886/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMa/rcDot1agCfmMaMepListTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/raisecom/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMa/rcDot1agCfmMaMepListTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/raiseCom/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMa/rcDot1agCfmMaMepListTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/8886/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMa/rcDot1agCfmMaMepListTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/raisecom/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMa/rcDot1agCfmMaMepListTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/raiseCom/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMa/rcDot1agCfmMaMepListTable
  • /iso/org/dod/internet/private/enterprise/8886/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMa/rcDot1agCfmMaMepListTable
  • /iso/org/dod/internet/private/enterprise/raisecom/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMa/rcDot1agCfmMaMepListTable
  • /iso/org/dod/internet/private/enterprise/raiseCom/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMa/rcDot1agCfmMaMepListTable
  • /iso/org/dod/internet/private/enterprises/8886/iscomSeries/iscomSwitch/rcDot1ag/rcDot1agMIBObjects/rcDot1agCfmMa/rcDot1agCfmMaMepListTable
  • Additional combinations skipped.

SNMP properties

Value type
SEQUENCE OF RcDot1agCfmMaMepListEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

rcDot1agCfmMaMepListTable
OBJECT-TYPE
    SYNTAX      SEQUENCE OF RcDot1agCfmMaMepListEntry
    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 {rcDot1agCfmMdFormat,
        rcDot1agCfmMdName, rcDot1agCfmMaNetFormat, and rcDot1agCfmMaNetName}
        is configured, the same set of rcDot1agCfmMaMepListIdentifiers
        must be configured in the bridges' rcDot1agCfmMaMepListTables.
        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 rcDot1agCfmMdTableNextIndex.
         2. Create the Maintenance Domain {charString, 'Dom1'}.
         3. Get a new MA index a from rcDot1agCfmMdMaNextIndex [d].
         4. Create the Maintenance Association {charString, 'MA1'}.
         5. Create a new rcDot1agCfmMaMepListEntry 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
       "802.1ag clause 12.14.6.1.3:g"
    ::= { rcDot1agCfmMa 3 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

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 {rcDot1agCfmMdFormat, rcDot1agCfmMdName, rcDot1agCfmMaNetFormat, and rcDot1agCfmMaNetName} is configured, the same set of rcDot1agCfmMaMepListIdentifiers must be configured in the bridges' rcDot1agCfmMaMepListTables. 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 rcDot1agCfmMdTableNextIndex. 2. Create the Maintenance Domain {charString, 'Dom1'}. 3. Get a new MA index a from rcDot1agCfmMdMaNextIndex [d]. 4. Create the Maintenance Association {charString, 'MA1'}. 5. Create a new rcDot1agCfmMaMepListEntry 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.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

rcDot1agCfmMaMepListTable · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: rcDot1agCfmMaMepListTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "rcDot1agCfmMaMepListTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "RcDot1agCfmMaMepListEntry",
    "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 {rcDot1agCfmMdFormat, rcDot1agCfmMdName, rcDot1agCfmMaNetFormat, and rcDot1agCfmMaNetName} is configured, the same set of rcDot1agCfmMaMepListIdentifiers must be configured in the bridges' rcDot1agCfmMaMepListTables. 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 rcDot1agCfmMdTableNextIndex. 2. Create the Maintenance Domain {charString, 'Dom1'}. 3. Get a new MA index a from rcDot1agCfmMdMaNextIndex [d]. 4. Create the Maintenance Association {charString, 'MA1'}. 5. Create a new rcDot1agCfmMaMepListEntry 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",
    "\"802.1ag clause 12.14.6.1.3:g\"",
    "::=",
    "{",
    "rcDot1agCfmMa",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "RcDot1agCfmMaMepListEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "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 {rcDot1agCfmMdFormat, rcDot1agCfmMdName, rcDot1agCfmMaNetFormat, and rcDot1agCfmMaNetName} is configured, the same set of rcDot1agCfmMaMepListIdentifiers must be configured in the bridges' rcDot1agCfmMaMepListTables. 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 rcDot1agCfmMdTableNextIndex. 2. Create the Maintenance Domain {charString, 'Dom1'}. 3. Get a new MA index a from rcDot1agCfmMdMaNextIndex [d]. 4. Create the Maintenance Association {charString, 'MA1'}. 5. Create a new rcDot1agCfmMaMepListEntry 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",
      "802.1ag clause 12.14.6.1.3:g"
    ],
    null,
    null,
    null
  ]
}
  • Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz

    Vendor MIB copy from the Observium Community archive.

    Module: RAISECOM-DOT1AG-MIB

    See published definition above

    Module imports
    {'IF-MIB': ['InterfaceIndex', 'InterfaceIndexOrZero'], 'LLDP-MIB': ['LldpChassisId', 'LldpChassisIdSubtype', 'LldpPortId', 'LldpPortIdSubtype'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TimeInterval', 'TimeStamp', 'RowStatus', 'TruthValue', 'MacAddress', 'TDomain', 'TAddress'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32', 'Counter32', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'Q-BRIDGE-MIB': ['VlanIdOrNone', 'VlanId'], 'IEEE8021-CFM-MIB': ['Dot1agCfmMaintDomainNameType', 'Dot1agCfmMaintDomainName', 'Dot1agCfmIngressActionFieldValue', 'Dot1agCfmMaintAssocNameType', 'Dot1agCfmMaintAssocName', 'Dot1agCfmMDLevel', 'Dot1agCfmMDLevelOrNone', 'Dot1agCfmMpDirection', 'Dot1agCfmPortStatus', 'Dot1agCfmInterfaceStatus', 'Dot1agCfmHighestDefectPri', 'Dot1agCfmLowestAlarmPri', 'Dot1agCfmMepId', 'Dot1agCfmMepIdOrZero', 'Dot1agCfmMhfCreation', 'Dot1agCfmIdPermission', 'Dot1agCfmCcmInterval', 'Dot1agCfmFngState', 'Dot1agCfmRelayActionFieldValue', 'Dot1agCfmEgressActionFieldValue', 'Dot1agCfmRemoteMepState', 'Dot1afCfmIndexIntegerNextFree', 'Dot1agCfmMepDefects', 'dot1agCfmMepHighestPrDefect', 'Dot1agCfmConfigErrors', 'Dot1agCfmPbbComponentIdentifier'], 'RAISECOM-BASE-MIB': ['iscomSwitch']}
    · Download RAISECOM-DOT1AG-MIB

    Related source files and packages:

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.8886)

Gao Lei

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.8886.6.1.32.1.6.3.1 rcDot1agCfmMaMepListEntry22

Siblings (2)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.8886.6.1.32.1.6.1 rcDot1agCfmMaNetTable16
1.3.6.1.4.1.8886.6.1.32.1.6.2 rcDot1agCfmMaCompTable17