OID reference

myExperiment

1.3.6.1.4.1.171.10.97.5

Description

myExperiment provides a root object identifier from which experimental mibs may be temporarily based. mibs are typicially based here if they fall in one of two categories 1) are IETF work-in-process mibs which have not been assigned a permanent object identifier by the IANA. 2) are my work-in-process which has not bee…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.171.10.97 (switchMib)
Node code
5
Node name
myExperiment
Numeric OID
1.3.6.1.4.1.171.10.97.5
URN notation
urn:oid:1.3.6.1.4.1.171.10.97.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 171 10 97 5}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dlink(171) dlink-products(10) switchMib(97) myExperiment(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dlink(171) products(10) switchMib(97) myExperiment(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dlink(171) nmsGponMIB(10) switchMib(97) myExperiment(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) d-link(171) dlink-products(10) switchMib(97) myExperiment(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) d-link(171) products(10) switchMib(97) myExperiment(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) d-link(171) nmsGponMIB(10) switchMib(97) myExperiment(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) company(171) dlink-products(10) switchMib(97) myExperiment(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) company(171) products(10) switchMib(97) myExperiment(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) company(171) nmsGponMIB(10) switchMib(97) myExperiment(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) my(171) dlink-products(10) switchMib(97) myExperiment(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) my(171) products(10) switchMib(97) myExperiment(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) my(171) nmsGponMIB(10) switchMib(97) myExperiment(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(171) dlink-products(10) switchMib(97) myExperiment(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(171) products(10) switchMib(97) myExperiment(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(171) nmsGponMIB(10) switchMib(97) myExperiment(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dlink(171) dlink-products(10) switchMib(97) myExperiment(5)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/171/10/97/5
  • /ISO/Identified-Organization/6/1/4/1/171/10/97/5
  • /ISO/3/6/1/4/1/171/10/97/5
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/dlink/dlink-products/switchMib/myExperiment
  • /iso/identified-organization/dod/internet/private/enterprise/dlink/products/switchMib/myExperiment
  • /iso/identified-organization/dod/internet/private/enterprise/dlink/nmsGponMIB/switchMib/myExperiment
  • /iso/identified-organization/dod/internet/private/enterprise/d-link/dlink-products/switchMib/myExperiment
  • /iso/identified-organization/dod/internet/private/enterprise/d-link/products/switchMib/myExperiment
  • /iso/identified-organization/dod/internet/private/enterprise/d-link/nmsGponMIB/switchMib/myExperiment
  • /iso/identified-organization/dod/internet/private/enterprise/company/dlink-products/switchMib/myExperiment
  • /iso/identified-organization/dod/internet/private/enterprise/company/products/switchMib/myExperiment
  • /iso/identified-organization/dod/internet/private/enterprise/company/nmsGponMIB/switchMib/myExperiment
  • /iso/identified-organization/dod/internet/private/enterprise/my/dlink-products/switchMib/myExperiment
  • /iso/identified-organization/dod/internet/private/enterprise/my/products/switchMib/myExperiment
  • /iso/identified-organization/dod/internet/private/enterprise/my/nmsGponMIB/switchMib/myExperiment
  • /iso/identified-organization/dod/internet/private/enterprise/nms/dlink-products/switchMib/myExperiment
  • /iso/identified-organization/dod/internet/private/enterprise/nms/products/switchMib/myExperiment
  • /iso/identified-organization/dod/internet/private/enterprise/nms/nmsGponMIB/switchMib/myExperiment
  • /iso/identified-organization/dod/internet/private/enterprises/dlink/dlink-products/switchMib/myExperiment
  • Additional combinations skipped.

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

myExperiment OBJECT-IDENTITY
        STATUS  current
        DESCRIPTION
                "myExperiment provides a root object identifier
                from which experimental mibs may be temporarily
                based.  mibs are typicially based here if they
                fall in one of two categories
                1) are IETF work-in-process mibs which have not
                been assigned a permanent object identifier by
                the IANA.
                2) are my work-in-process which has not been
                assigned a permanent object identifier by the
                my assigned number authority, typicially because
                the mib is not ready for deployment.

                NOTE WELL:  support for mibs in the myExperiment
                subtree will be deleted when a permanent object
                identifier assignment is made."
        ::= { switchMib 5 }

Meaning

Descriptions

1 unique

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

myExperiment provides a root object identifier from which experimental mibs may be temporarily based. mibs are typicially based here if they fall in one of two categories 1) are IETF work-in-process mibs which have not been assigned a permanent object identifier by the IANA. 2) are my work-in-process which has not been assigned a permanent object identifier by the my assigned number authority, typicially because the mib is not ready for deployment. NOTE WELL: support for mibs in the myExperiment subtree will be deleted when a permanent object identifier assignment is made.

Sources for this description

D-Link official switch MIBsD-Link 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 1D-Link official switch MIBs, D-Link MIB copies (LibreNMS/Observium Community)1 record · 3 sources

Description 1

myExperiment · currentD-Link official switch MIBs, D-Link MIB copies (LibreNMS/Observium Community)3 sources

Status in source: current.

Names: myExperiment

Technical details
{
  "smi_kind": "OBJECT-IDENTITY",
  "definition": [
    "myExperiment",
    "OBJECT-IDENTITY",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"myExperiment provides a root object identifier from which experimental mibs may be temporarily based. mibs are typicially based here if they fall in one of two categories 1) are IETF work-in-process mibs which have not been assigned a permanent object identifier by the IANA. 2) are my work-in-process which has not been assigned a permanent object identifier by the my assigned number authority, typicially because the mib is not ready for deployment. NOTE WELL: support for mibs in the myExperiment subtree will be deleted when a permanent object identifier assignment is made.\"",
    "::=",
    "{",
    "switchMib",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "myExperiment provides a root object identifier from which experimental mibs may be temporarily based. mibs are typicially based here if they fall in one of two categories 1) are IETF work-in-process mibs which have not been assigned a permanent object identifier by the IANA. 2) are my work-in-process which has not been assigned a permanent object identifier by the my assigned number authority, typicially because the mib is not ready for deployment. NOTE WELL: support for mibs in the myExperiment subtree will be deleted when a permanent object identifier assignment is made."
    ],
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.171)

Henry P. Nagai

Siblings (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.171.10.97.1 mySwitchProducts44
1.3.6.1.4.1.171.10.97.2 myMgmt442107
1.3.6.1.4.1.171.10.97.3 myAgentCapability00
1.3.6.1.4.1.171.10.97.4 myModules11