OID reference

fsMIY1731MepAvailabilityTable

1.3.6.1.4.1.29601.2.7.1.2.16

Description

This object specifies the Maintenance Entity Group End Point (MEP) Availability table. Each row in the table is associated with a different MEP. 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 …

Full description and source information

Identification

Identifier and names

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

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

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

SNMP properties

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

fsMIY1731MepAvailabilityTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF FsMIY1731MepAvailabilityEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
       "This object specifies the Maintenance Entity Group End Point (MEP) Availability 
        table.

        Each row in the table is associated with a different MEP. 

        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 availability
        measurement.

        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 16 }

Meaning

Descriptions

1 unique

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

This object specifies the Maintenance Entity Group End Point (MEP) Availability table. Each row in the table is associated with a different MEP. 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 availability measurement. 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

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

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

Status in source: current.

Names: fsMIY1731MepAvailabilityTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsMIY1731MepAvailabilityTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "FsMIY1731MepAvailabilityEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object specifies the Maintenance Entity Group End Point (MEP) Availability table. Each row in the table is associated with a different MEP. 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 availability measurement. 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",
    "16",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "FsMIY1731MepAvailabilityEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object specifies the Maintenance Entity Group End Point (MEP) Availability table. Each row in the table is associated with a different MEP. 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 availability measurement. 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.16.1 fsMIY1731MepAvailabilityEntry1818

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.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.17 fsMIY1731LoopbackTable13