OID reference

fsMIY1731MeTable

1.3.6.1.4.1.29601.2.7.1.2.3

Description

This object specifies the Maintenance Entity table. Each row in the table represents an ME. An ME represents a relationship between two MEPs, each configured with a single service instance. Configuring a Maintenance Entity Group End Point (MEP) at each of the DSAPs creates a Maintenance Entity (ME) to monitor that con…

Full description and source information

Identification

Identifier and names

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

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

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

SNMP properties

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

fsMIY1731MeTable · current

fsMIY1731MeTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF FsMIY1731MeEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
       "This object specifies the Maintenance Entity table.  Each row in the table represents 
        an ME.  An ME represents a relationship between two MEPs, each 
        configured with a single service instance.

        Configuring a Maintenance Entity Group End Point (MEP) at each 
        of the DSAPs creates a Maintenance Entity (ME) to monitor
        that connectionless connectivity. The ITU-Carrier Code (ICC) and 
        Unique MEGID Code (UMC) form the Maintenance Entity Group Identifier 
        (MEGID) that is carried in CFM Messages to identify incorrect 
        connectivity among Service Instances.  A small integer, the 
        Maintenance Entity Group End Point Identifier (MEPID), identifies 
        each MEP among those configured on a single ME.

        This table uses two indices, first index is the index of the
        Maintenance Entity Group table.

        The writable objects in this table need to be persistent
        upon reboot or restart of a device.
       "
    ::= { fsMIY1731Context 3 }

fsMIY1731MeTable · current

fsMIY1731MeTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF FsMIY1731MeEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
       "The Maintenance Entity table.  Each row in the table represents 
        an ME.  An ME represents a relationship between two MEPs, each 
        configured with a single service instance.

        Configuring a Maintenance Entity Group End Point (MEP) at each 
        of the DSAPs creates a Maintenance Entity (ME) to monitor
        that connectionless connectivity. The ITU-Carrier Code (ICC) and 
        Unique MEGID Code (UMC) form the Maintenance Entity Group Identifier 
        (MEGID) that is carried in CFM Messages to identify incorrect 
        connectivity among Service Instances.  A small integer, the 
        Maintenance Entity Group End Point Identifier (MEPID), identifies 
        each MEP among those configured on a single ME.

        This table uses two indices, first index is the index of the
        Maintenance Entity Group table.

        The writable objects in this table need to be persistent
        upon reboot or restart of a device.
       "
    ::= { fsMIY1731Context 3 }

Meaning

Descriptions

2 unique

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

Description 1

This object specifies the Maintenance Entity table. Each row in the table represents an ME. An ME represents a relationship between two MEPs, each configured with a single service instance. Configuring a Maintenance Entity Group End Point (MEP) at each of the DSAPs creates a Maintenance Entity (ME) to monitor that connectionless connectivity. The ITU-Carrier Code (ICC) and Unique MEGID Code (UMC) form the Maintenance Entity Group Identifier (MEGID) that is carried in CFM Messages to identify incorrect connectivity among Service Instances. A small integer, the Maintenance Entity Group End Point Identifier (MEPID), identifies each MEP among those configured on a single ME. This table uses two indices, first index is the index of the Maintenance Entity Group table. The writable objects in this table need to be persistent upon reboot or restart of a device.

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 table. Each row in the table represents an ME. An ME represents a relationship between two MEPs, each configured with a single service instance. Configuring a Maintenance Entity Group End Point (MEP) at each of the DSAPs creates a Maintenance Entity (ME) to monitor that connectionless connectivity. The ITU-Carrier Code (ICC) and Unique MEGID Code (UMC) form the Maintenance Entity Group Identifier (MEGID) that is carried in CFM Messages to identify incorrect connectivity among Service Instances. A small integer, the Maintenance Entity Group End Point Identifier (MEPID), identifies each MEP among those configured on a single ME. This table uses two indices, first index is the index of the Maintenance Entity Group table. The writable objects in this table need to be persistent upon reboot or restart of a device.

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

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

Status in source: current.

Names: fsMIY1731MeTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsMIY1731MeTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "FsMIY1731MeEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object specifies the Maintenance Entity table. Each row in the table represents an ME. An ME represents a relationship between two MEPs, each configured with a single service instance. Configuring a Maintenance Entity Group End Point (MEP) at each of the DSAPs creates a Maintenance Entity (ME) to monitor that connectionless connectivity. The ITU-Carrier Code (ICC) and Unique MEGID Code (UMC) form the Maintenance Entity Group Identifier (MEGID) that is carried in CFM Messages to identify incorrect connectivity among Service Instances. A small integer, the Maintenance Entity Group End Point Identifier (MEPID), identifies each MEP among those configured on a single ME. This table uses two indices, first index is the index of the Maintenance Entity Group table. The writable objects in this table need to be persistent upon reboot or restart of a device. \"",
    "::=",
    "{",
    "fsMIY1731Context",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "FsMIY1731MeEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object specifies the Maintenance Entity table. Each row in the table represents an ME. An ME represents a relationship between two MEPs, each configured with a single service instance. Configuring a Maintenance Entity Group End Point (MEP) at each of the DSAPs creates a Maintenance Entity (ME) to monitor that connectionless connectivity. The ITU-Carrier Code (ICC) and Unique MEGID Code (UMC) form the Maintenance Entity Group Identifier (MEGID) that is carried in CFM Messages to identify incorrect connectivity among Service Instances. A small integer, the Maintenance Entity Group End Point Identifier (MEPID), identifies each MEP among those configured on a single ME. This table uses two indices, first index is the index of the Maintenance Entity Group table. The writable objects in this table need to be persistent upon reboot or restart of a device."
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2Belden, GarrettCom and Hirschmann IT official standalone MIBs1 record · 1 source

Description 2

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

Status in source: current.

Names: fsMIY1731MeTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsMIY1731MeTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "FsMIY1731MeEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The Maintenance Entity table. Each row in the table represents an ME. An ME represents a relationship between two MEPs, each configured with a single service instance. Configuring a Maintenance Entity Group End Point (MEP) at each of the DSAPs creates a Maintenance Entity (ME) to monitor that connectionless connectivity. The ITU-Carrier Code (ICC) and Unique MEGID Code (UMC) form the Maintenance Entity Group Identifier (MEGID) that is carried in CFM Messages to identify incorrect connectivity among Service Instances. A small integer, the Maintenance Entity Group End Point Identifier (MEPID), identifies each MEP among those configured on a single ME. This table uses two indices, first index is the index of the Maintenance Entity Group table. The writable objects in this table need to be persistent upon reboot or restart of a device. \"",
    "::=",
    "{",
    "fsMIY1731Context",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "FsMIY1731MeEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The Maintenance Entity table. Each row in the table represents an ME. An ME represents a relationship between two MEPs, each configured with a single service instance. Configuring a Maintenance Entity Group End Point (MEP) at each of the DSAPs creates a Maintenance Entity (ME) to monitor that connectionless connectivity. The ITU-Carrier Code (ICC) and Unique MEGID Code (UMC) form the Maintenance Entity Group Identifier (MEGID) that is carried in CFM Messages to identify incorrect connectivity among Service Instances. A small integer, the Maintenance Entity Group End Point Identifier (MEPID), identifies each MEP among those configured on a single ME. This table uses two indices, first index is the index of the Maintenance Entity Group table. The writable objects in this table need to be persistent upon reboot or restart of a device."
    ],
    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.3.1 fsMIY1731MeEntry66

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.4 fsMIY1731MepTable1138
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