OID reference

fsMIY1731MepTable

1.3.6.1.4.1.29601.2.7.1.2.4

Description

This object specifies the Maintenance Entity Group 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 Mai…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.29601.2.7.1.2 (fsMIY1731Context)
Node code
4
Node name
fsMIY1731MepTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.29601.2.7.1.2.4
URN notation
urn:oid:1.3.6.1.4.1.29601.2.7.1.2.4
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 29601 2 7 1 2 4}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsMIY1731MIB(7) fsMIY1731MIBObjects(1) fsMIY1731Context(2) fsMIY1731MepTable(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsMIY1731MIB(7) fsMIY1731MIBObjects(1) fsMIY1731Context(2) fsMIY1731MepTable(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsMIY1731MIB(7) fsMIY1731MIBObjects(1) fsMIY1731Context(2) fsMIY1731MepTable(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsMIY1731MIB(7) fsMIY1731MIBObjects(1) fsMIY1731Context(2) fsMIY1731MepTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsMIY1731MIB(7) fsMIY1731MIBObjects(1) fsMIY1731Context(2) fsMIY1731MepTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsMIY1731MIB(7) fsMIY1731MIBObjects(1) fsMIY1731Context(2) fsMIY1731MepTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsMIY1731MIB(7) fsMIY1731MIBObjects(1) fsMIY1731Context(2) fsMIY1731MepTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsMIY1731MIB(7) fsMIY1731MIBObjects(1) fsMIY1731Context(2) fsMIY1731MepTable(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsMIY1731MIB(7) fsMIY1731MIBObjects(1) fsMIY1731Context(2) fsMIY1731MepTable(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsMIY1731MIB(7) fsMIY1731MIBObjects(1) fsMIY1731Context(2) fsMIY1731MepTable(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsMIY1731MIB(7) fsMIY1731MIBObjects(1) fsMIY1731Context(2) fsMIY1731MepTable(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsMIY1731MIB(7) fsMIY1731MIBObjects(1) fsMIY1731Context(2) fsMIY1731MepTable(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsMIY1731MIB(7) fsMIY1731MIBObjects(1) fsMIY1731Context(2) fsMIY1731MepTable(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsMIY1731MIB(7) fsMIY1731MIBObjects(1) fsMIY1731Context(2) fsMIY1731MepTable(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsMIY1731MIB(7) fsMIY1731MIBObjects(1) fsMIY1731Context(2) fsMIY1731MepTable(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsMIY1731MIB(7) fsMIY1731MIBObjects(1) fsMIY1731Context(2) fsMIY1731MepTable(4)}
OID-IRI notation
  • /1/3/6/1/4/1/29601/2/7/1/2/4
  • /ISO/Identified-Organization/6/1/4/1/29601/2/7/1/2/4
  • /ISO/3/6/1/4/1/29601/2/7/1/2/4
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/29601/2/fsMIY1731MIB/fsMIY1731MIBObjects/fsMIY1731Context/fsMIY1731MepTable
  • /iso/identified-organization/dod/internet/private/enterprises/29601/2/fsMIY1731MIB/fsMIY1731MIBObjects/fsMIY1731Context/fsMIY1731MepTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/29601/2/fsMIY1731MIB/fsMIY1731MIBObjects/fsMIY1731Context/fsMIY1731MepTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/29601/2/fsMIY1731MIB/fsMIY1731MIBObjects/fsMIY1731Context/fsMIY1731MepTable
  • /iso/org/dod/internet/private/enterprise/29601/2/fsMIY1731MIB/fsMIY1731MIBObjects/fsMIY1731Context/fsMIY1731MepTable
  • /iso/org/dod/internet/private/enterprises/29601/2/fsMIY1731MIB/fsMIY1731MIBObjects/fsMIY1731Context/fsMIY1731MepTable
  • /iso/org/dod/internet/private/ldap-enterprise/29601/2/fsMIY1731MIB/fsMIY1731MIBObjects/fsMIY1731Context/fsMIY1731MepTable
  • /iso/org/dod/internet/private/vendor-objects/29601/2/fsMIY1731MIB/fsMIY1731MIBObjects/fsMIY1731Context/fsMIY1731MepTable
  • /iso/iso-identified-organization/dod/internet/private/enterprise/29601/2/fsMIY1731MIB/fsMIY1731MIBObjects/fsMIY1731Context/fsMIY1731MepTable
  • /iso/iso-identified-organization/dod/internet/private/enterprises/29601/2/fsMIY1731MIB/fsMIY1731MIBObjects/fsMIY1731Context/fsMIY1731MepTable
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/29601/2/fsMIY1731MIB/fsMIY1731MIBObjects/fsMIY1731Context/fsMIY1731MepTable
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/29601/2/fsMIY1731MIB/fsMIY1731MIBObjects/fsMIY1731Context/fsMIY1731MepTable
  • /iso/iso-organization/dod/internet/private/enterprise/29601/2/fsMIY1731MIB/fsMIY1731MIBObjects/fsMIY1731Context/fsMIY1731MepTable
  • /iso/iso-organization/dod/internet/private/enterprises/29601/2/fsMIY1731MIB/fsMIY1731MIBObjects/fsMIY1731Context/fsMIY1731MepTable
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/29601/2/fsMIY1731MIB/fsMIY1731MIBObjects/fsMIY1731Context/fsMIY1731MepTable
  • /iso/iso-organization/dod/internet/private/vendor-objects/29601/2/fsMIY1731MIB/fsMIY1731MIBObjects/fsMIY1731Context/fsMIY1731MepTable

SNMP properties

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

fsMIY1731MepTable · current

fsMIY1731MepTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF FsMIY1731MepEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
       "This object specifies the Maintenance Entity Group 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 Entity.

        This table uses three indices. The first two indices are the
        indices of the Maintenance Entity Group (MEG) and Maintenance 
        Entity (ME) tables, the reason being that a MEP is always 
        related to an ME and MEG.

        The MEP table stores all the managed objects for sending
        LBM, LTM, AIS and LCK. This table also stores all the managed
        objects required for monitoring the performance.

        The objects which are used to initiate a transaction are to
        be set only when the row-status of the table is active.
        'fsMIY1731MepTransmit' naming convention is used to isolate 
        these objects from the others.
       "
    ::= { fsMIY1731Context 4 }

fsMIY1731MepTable · current

fsMIY1731MepTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF FsMIY1731MepEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
       "The Maintenance Entity Group 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 Entity.

        This table uses three indices. The first two indices are the
        indices of the Maintenance Entity Group (MEG) and Maintenance 
        Entity (ME) tables, the reason being that a MEP is always 
        related to an ME and MEG.

        The MEP table stores all the managed objects for sending
        LBM, LTM, AIS and LCK. This table also stores all the managed
        objects required for monitoring the performance.

        The objects which are used to initiate a transaction are to
        be set only when the row-status of the table is active.
        'fsMIY1731MepTransmit' naming convention is used to isolate 
        these objects from the others.
       "
    ::= { fsMIY1731Context 4 }

Meaning

Descriptions

2 unique

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

Description 1

This object specifies the Maintenance Entity Group 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 Entity. This table uses three indices. The first two indices are the indices of the Maintenance Entity Group (MEG) and Maintenance Entity (ME) tables, the reason being that a MEP is always related to an ME and MEG. The MEP table stores all the managed objects for sending LBM, LTM, AIS and LCK. This table also stores all the managed objects required for monitoring the performance. The objects which are used to initiate a transaction are to be set only when the row-status of the table is active. 'fsMIY1731MepTransmit' naming convention is used to isolate these objects from the others.

Sources for this description

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

See 1 matching source record

Description 2

The Maintenance Entity Group 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 Entity. This table uses three indices. The first two indices are the indices of the Maintenance Entity Group (MEG) and Maintenance Entity (ME) tables, the reason being that a MEP is always related to an ME and MEG. The MEP table stores all the managed objects for sending LBM, LTM, AIS and LCK. This table also stores all the managed objects required for monitoring the performance. The objects which are used to initiate a transaction are to be set only when the row-status of the table is active. 'fsMIY1731MepTransmit' naming convention is used to isolate these objects from the others.

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

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

Status in source: current.

Names: fsMIY1731MepTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsMIY1731MepTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "FsMIY1731MepEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object specifies the Maintenance Entity Group 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 Entity. This table uses three indices. The first two indices are the indices of the Maintenance Entity Group (MEG) and Maintenance Entity (ME) tables, the reason being that a MEP is always related to an ME and MEG. The MEP table stores all the managed objects for sending LBM, LTM, AIS and LCK. This table also stores all the managed objects required for monitoring the performance. The objects which are used to initiate a transaction are to be set only when the row-status of the table is active. 'fsMIY1731MepTransmit' naming convention is used to isolate these objects from the others. \"",
    "::=",
    "{",
    "fsMIY1731Context",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "FsMIY1731MepEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object specifies the Maintenance Entity Group 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 Entity. This table uses three indices. The first two indices are the indices of the Maintenance Entity Group (MEG) and Maintenance Entity (ME) tables, the reason being that a MEP is always related to an ME and MEG. The MEP table stores all the managed objects for sending LBM, LTM, AIS and LCK. This table also stores all the managed objects required for monitoring the performance. The objects which are used to initiate a transaction are to be set only when the row-status of the table is active. 'fsMIY1731MepTransmit' naming convention is used to isolate these objects from the others."
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2Belden, GarrettCom and Hirschmann IT official standalone MIBs1 record · 1 source

Description 2

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

Status in source: current.

Names: fsMIY1731MepTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsMIY1731MepTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "FsMIY1731MepEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The Maintenance Entity Group 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 Entity. This table uses three indices. The first two indices are the indices of the Maintenance Entity Group (MEG) and Maintenance Entity (ME) tables, the reason being that a MEP is always related to an ME and MEG. The MEP table stores all the managed objects for sending LBM, LTM, AIS and LCK. This table also stores all the managed objects required for monitoring the performance. The objects which are used to initiate a transaction are to be set only when the row-status of the table is active. 'fsMIY1731MepTransmit' naming convention is used to isolate these objects from the others. \"",
    "::=",
    "{",
    "fsMIY1731Context",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "FsMIY1731MepEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The Maintenance Entity Group 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 Entity. This table uses three indices. The first two indices are the indices of the Maintenance Entity Group (MEG) and Maintenance Entity (ME) tables, the reason being that a MEP is always related to an ME and MEG. The MEP table stores all the managed objects for sending LBM, LTM, AIS and LCK. This table also stores all the managed objects required for monitoring the performance. The objects which are used to initiate a transaction are to be set only when the row-status of the table is active. 'fsMIY1731MepTransmit' naming convention is used to isolate these objects from the others."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.29601)

Arpna Gupta

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.29601.2.7.1.2.4.1 fsMIY1731MepEntry137137

Siblings (16)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.29601.2.7.1.2.1 fsMIY1731ContextTable116
1.3.6.1.4.1.29601.2.7.1.2.2 fsMIY1731MegTable16
1.3.6.1.4.1.29601.2.7.1.2.3 fsMIY1731MeTable17
1.3.6.1.4.1.29601.2.7.1.2.5 fsMIY1731ErrorLogTable15
1.3.6.1.4.1.29601.2.7.1.2.6 fsMIY1731LtrTable14
1.3.6.1.4.1.29601.2.7.1.2.7 fsMIY1731LbmTable114
1.3.6.1.4.1.29601.2.7.1.2.8 fsMIY1731LbrTable111
1.3.6.1.4.1.29601.2.7.1.2.9 fsMIY1731LbStatsTable18
1.3.6.1.4.1.29601.2.7.1.2.10 fsMIY1731FdTable111
1.3.6.1.4.1.29601.2.7.1.2.11 fsMIY1731FdStatsTable19
1.3.6.1.4.1.29601.2.7.1.2.12 fsMIY1731FlTable19
1.3.6.1.4.1.29601.2.7.1.2.13 fsMIY1731FlStatsTable111
1.3.6.1.4.1.29601.2.7.1.2.14 fsMIY1731MplstpExtRemoteMepTable14
1.3.6.1.4.1.29601.2.7.1.2.15 fsMIY1731StatsTable130
1.3.6.1.4.1.29601.2.7.1.2.16 fsMIY1731MepAvailabilityTable119
1.3.6.1.4.1.29601.2.7.1.2.17 fsMIY1731LoopbackTable13