OID reference

mpExperiment

1.3.6.1.4.1.5651.4

Description

maipuExperiment 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) IETF work-in-process mibs which have not been assigned a permanent object identifier by the IANA. 2) Maipu work-in-process which has not been…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.5651 (5651, maipu)
Node code
4
Node name
mpExperiment
Numeric OID
1.3.6.1.4.1.5651.4
URN notation
urn:oid:1.3.6.1.4.1.5651.4
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 5651 4}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) maipu(5651) mpExperiment(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) maipu(5651) mpExperiment(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) maipu(5651) mpExperiment(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) maipu(5651) mpExperiment(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) maipu(5651) mpExperiment(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) maipu(5651) mpExperiment(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) maipu(5651) mpExperiment(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) maipu(5651) mpExperiment(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) maipu(5651) mpExperiment(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) maipu(5651) mpExperiment(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) maipu(5651) mpExperiment(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) maipu(5651) mpExperiment(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) maipu(5651) mpExperiment(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) maipu(5651) mpExperiment(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) maipu(5651) mpExperiment(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) maipu(5651) mpExperiment(4)}
OID-IRI notation
  • /1/3/6/1/4/1/5651/4
  • /ISO/Identified-Organization/6/1/4/1/5651/4
  • /ISO/3/6/1/4/1/5651/4
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/5651/mpExperiment
  • /iso/identified-organization/dod/internet/private/enterprise/maipu/mpExperiment
  • /iso/identified-organization/dod/internet/private/enterprises/5651/mpExperiment
  • /iso/identified-organization/dod/internet/private/enterprises/maipu/mpExperiment
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/5651/mpExperiment
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/maipu/mpExperiment
  • /iso/identified-organization/dod/internet/private/vendor-objects/5651/mpExperiment
  • /iso/identified-organization/dod/internet/private/vendor-objects/maipu/mpExperiment
  • /iso/org/dod/internet/private/enterprise/5651/mpExperiment
  • /iso/org/dod/internet/private/enterprise/maipu/mpExperiment
  • /iso/org/dod/internet/private/enterprises/5651/mpExperiment
  • /iso/org/dod/internet/private/enterprises/maipu/mpExperiment
  • /iso/org/dod/internet/private/ldap-enterprise/5651/mpExperiment
  • /iso/org/dod/internet/private/ldap-enterprise/maipu/mpExperiment
  • /iso/org/dod/internet/private/vendor-objects/5651/mpExperiment
  • /iso/org/dod/internet/private/vendor-objects/maipu/mpExperiment
  • Additional combinations skipped.

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

Show 2 published definitions

mpExperiment · current

mpExperiment OBJECT-IDENTITY
	STATUS	current
	DESCRIPTION
		"maipuExperiment 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) IETF work-in-process mibs which have not been assigned a
		   permanent object identifier by the IANA.
		2) Maipu work-in-process which has not been assigned a
		   permanent object identifier by the maipu assigned number
		   authority, typicially because the mib is not ready for
		   deployment.

		NOTE:  support for mibs in the maipuExperiment subtree will be
		erased when a permanent object identifier assignment is made."
	::= { maipu 4 }

mpExperiment · current

mpExperiment OBJECT-IDENTITY
	STATUS	current
	DESCRIPTION
		"maipuExperiment 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) IETF work-in-process mibs which have not been assigned a 
		   permanent object identifier by the IANA.
		2) Maipu work-in-process which has not been assigned a 
		   permanent object identifier by the maipu assigned number 
		   authority, typicially because the mib is not ready for 
		   deployment.

		NOTE:  support for mibs in the maipuExperiment subtree will be 
		erased when a permanent object identifier assignment is made."
	::= { maipu 4 }

Meaning

Descriptions

1 unique

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

maipuExperiment 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) IETF work-in-process mibs which have not been assigned a permanent object identifier by the IANA. 2) Maipu work-in-process which has not been assigned a permanent object identifier by the maipu assigned number authority, typicially because the mib is not ready for deployment. NOTE: support for mibs in the maipuExperiment subtree will be erased when a permanent object identifier assignment is made.

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 · 2 sources

Description 1

mpExperiment · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)2 sources

Status in source: current.

Names: mpExperiment

Technical details
{
  "smi_kind": "OBJECT-IDENTITY",
  "definition": [
    "mpExperiment",
    "OBJECT-IDENTITY",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"maipuExperiment 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) IETF work-in-process mibs which have not been assigned a permanent object identifier by the IANA. 2) Maipu work-in-process which has not been assigned a permanent object identifier by the maipu assigned number authority, typicially because the mib is not ready for deployment. NOTE: support for mibs in the maipuExperiment subtree will be erased when a permanent object identifier assignment is made.\"",
    "::=",
    "{",
    "maipu",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "maipuExperiment 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) IETF work-in-process mibs which have not been assigned a permanent object identifier by the IANA. 2) Maipu work-in-process which has not been assigned a permanent object identifier by the maipu assigned number authority, typicially because the mib is not ready for deployment. NOTE: support for mibs in the maipuExperiment subtree will be erased when a permanent object identifier assignment is made."
    ],
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.5651)

Xue Zheng

Siblings (5)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.5651.1 mpProducts67110
1.3.6.1.4.1.5651.2 mpTrapObject27
1.3.6.1.4.1.5651.3 mpMgmt382449
1.3.6.1.4.1.5651.5 mpSecurity1386
1.3.6.1.4.1.5651.6 mpMgmt27780