OID reference

fsEcfmMepExTable

1.3.6.1.4.1.2076.150.2.3

Description

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, an…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2076.150.2 (fsEcfmExObjects)
Node code
3
Node name
fsEcfmMepExTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2076.150.2.3
URN notation
urn:oid:1.3.6.1.4.1.2076.150.2.3
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2076 150 2 3}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 fsecfm(150) fsEcfmExObjects(2) fsEcfmMepExTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 fsecfm(150) fsEcfmExObjects(2) fsEcfmMepExTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 fsecfm(150) fsEcfmExObjects(2) fsEcfmMepExTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 fsecfm(150) fsEcfmExObjects(2) fsEcfmMepExTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) 2076 fsecfm(150) fsEcfmExObjects(2) fsEcfmMepExTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 2076 fsecfm(150) fsEcfmExObjects(2) fsEcfmMepExTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 fsecfm(150) fsEcfmExObjects(2) fsEcfmMepExTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 fsecfm(150) fsEcfmExObjects(2) fsEcfmMepExTable(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 fsecfm(150) fsEcfmExObjects(2) fsEcfmMepExTable(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 fsecfm(150) fsEcfmExObjects(2) fsEcfmMepExTable(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 fsecfm(150) fsEcfmExObjects(2) fsEcfmMepExTable(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 fsecfm(150) fsEcfmExObjects(2) fsEcfmMepExTable(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 fsecfm(150) fsEcfmExObjects(2) fsEcfmMepExTable(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 fsecfm(150) fsEcfmExObjects(2) fsEcfmMepExTable(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 fsecfm(150) fsEcfmExObjects(2) fsEcfmMepExTable(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 fsecfm(150) fsEcfmExObjects(2) fsEcfmMepExTable(3)}
OID-IRI notation
  • /1/3/6/1/4/1/2076/150/2/3
  • /ISO/Identified-Organization/6/1/4/1/2076/150/2/3
  • /ISO/3/6/1/4/1/2076/150/2/3
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/2076/fsecfm/fsEcfmExObjects/fsEcfmMepExTable
  • /iso/identified-organization/dod/internet/private/enterprises/2076/fsecfm/fsEcfmExObjects/fsEcfmMepExTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/2076/fsecfm/fsEcfmExObjects/fsEcfmMepExTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/2076/fsecfm/fsEcfmExObjects/fsEcfmMepExTable
  • /iso/org/dod/internet/private/enterprise/2076/fsecfm/fsEcfmExObjects/fsEcfmMepExTable
  • /iso/org/dod/internet/private/enterprises/2076/fsecfm/fsEcfmExObjects/fsEcfmMepExTable
  • /iso/org/dod/internet/private/ldap-enterprise/2076/fsecfm/fsEcfmExObjects/fsEcfmMepExTable
  • /iso/org/dod/internet/private/vendor-objects/2076/fsecfm/fsEcfmExObjects/fsEcfmMepExTable
  • /iso/iso-identified-organization/dod/internet/private/enterprise/2076/fsecfm/fsEcfmExObjects/fsEcfmMepExTable
  • /iso/iso-identified-organization/dod/internet/private/enterprises/2076/fsecfm/fsEcfmExObjects/fsEcfmMepExTable
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/2076/fsecfm/fsEcfmExObjects/fsEcfmMepExTable
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/2076/fsecfm/fsEcfmExObjects/fsEcfmMepExTable
  • /iso/iso-organization/dod/internet/private/enterprise/2076/fsecfm/fsEcfmExObjects/fsEcfmMepExTable
  • /iso/iso-organization/dod/internet/private/enterprises/2076/fsecfm/fsEcfmExObjects/fsEcfmMepExTable
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/2076/fsecfm/fsEcfmExObjects/fsEcfmMepExTable
  • /iso/iso-organization/dod/internet/private/vendor-objects/2076/fsecfm/fsEcfmExObjects/fsEcfmMepExTable

SNMP properties

Value type
SEQUENCE OF FsEcfmMepExEntry
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.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

fsEcfmMepExTable · current

fsEcfmMepExTable OBJECT-TYPE
       SYNTAX SEQUENCE OF FsEcfmMepExEntry
       MAX-ACCESS    not-accessible
       STATUS        current
       DESCRIPTION
       
       "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 a	ssociation (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."
        ::= { fsEcfmExObjects 3 }

fsEcfmMepExTable · current

fsEcfmMepExTable OBJECT-TYPE
       SYNTAX SEQUENCE OF FsEcfmMepExEntry
       MAX-ACCESS    not-accessible
       STATUS        current
       DESCRIPTION
       
       "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."
        ::= { fsEcfmExObjects 3 }

Meaning

Descriptions

2 unique

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

Description 1

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 a ssociation (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.

Sources for this description

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

See 1 matching source record

Description 2

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.

Sources for this description

Belden, GarrettCom and Hirschmann IT official standalone MIBs

See 1 matching source record

Evidence

Source records

2 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

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

Status in source: current.

Names: fsEcfmMepExTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsEcfmMepExTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "FsEcfmMepExEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"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 a ssociation (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.\"",
    "::=",
    "{",
    "fsEcfmExObjects",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "FsEcfmMepExEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "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 a ssociation (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."
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2Belden, GarrettCom and Hirschmann IT official standalone MIBs1 record · 1 source

Description 2

fsEcfmMepExTable · currentBelden, GarrettCom and Hirschmann IT official standalone MIBs1 source

Status in source: current.

Names: fsEcfmMepExTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsEcfmMepExTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "FsEcfmMepExEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"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.\"",
    "::=",
    "{",
    "fsEcfmExObjects",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "FsEcfmMepExEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "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."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2076)

Division Products

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2076.150.2.3.1 fsEcfmMepExEntry1515

Siblings (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2076.150.2.1 fsEcfmRemoteMepDbExTable118
1.3.6.1.4.1.2076.150.2.2 fsEcfmLtmTable14
1.3.6.1.4.1.2076.150.2.4 fsEcfmMdExTable12
1.3.6.1.4.1.2076.150.2.5 fsEcfmMaExTable12