Reference record for OID 1.3.6.1.4.1.259.6.10.95.1.10.9.1.10

Parent
1.3.6.1.4.1.259.6.10.95.1.10.9.1 (ipv6netConfigEntry)
Node code
10
Node name
ipv6netConfigStatus
Numeric OID
1.3.6.1.4.1.259.6.10.95.1.10.9.1.10
URN notation
urn:oid:1.3.6.1.4.1.259.6.10.95.1.10.9.1.10
ASN.1 notation

{1 3 6 1 4 1 259 6 10 95 1 10 9 1 10}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) accton(259) snmpMgt(6) cheetahSwitchMgt(10) es4524dMIB(95) es4524dMIBObjects(1) ipMgt(10) ipv6netConfigTable(9) ipv6netConfigEntry(1) ipv6netConfigStatus(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) accton(259) snmpMgt(6) cheetahSwitchMgt(10) es4524dMIB(95) es4524dMIBObjects(1) ipMgt(10) ipv6netConfigTable(9) ipv6netConfigEntry(1) ipv6netConfigStatus(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) accton(259) snmpMgt(6) cheetahSwitchMgt(10) es4524dMIB(95) es4524dMIBObjects(1) ipMgt(10) ipv6netConfigTable(9) ipv6netConfigEntry(1) ipv6netConfigStatus(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) accton(259) snmpMgt(6) cheetahSwitchMgt(10) es4524dMIB(95) es4524dMIBObjects(1) ipMgt(10) ipv6netConfigTable(9) ipv6netConfigEntry(1) ipv6netConfigStatus(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) accton(259) snmpMgt(6) cheetahSwitchMgt(10) es4524dMIB(95) es4524dMIBObjects(1) ipMgt(10) ipv6netConfigTable(9) ipv6netConfigEntry(1) ipv6netConfigStatus(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) accton(259) snmpMgt(6) cheetahSwitchMgt(10) es4524dMIB(95) es4524dMIBObjects(1) ipMgt(10) ipv6netConfigTable(9) ipv6netConfigEntry(1) ipv6netConfigStatus(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) accton(259) snmpMgt(6) cheetahSwitchMgt(10) es4524dMIB(95) es4524dMIBObjects(1) ipMgt(10) ipv6netConfigTable(9) ipv6netConfigEntry(1) ipv6netConfigStatus(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) accton(259) snmpMgt(6) cheetahSwitchMgt(10) es4524dMIB(95) es4524dMIBObjects(1) ipMgt(10) ipv6netConfigTable(9) ipv6netConfigEntry(1) ipv6netConfigStatus(10)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) accton(259) snmpMgt(6) cheetahSwitchMgt(10) es4524dMIB(95) es4524dMIBObjects(1) ipMgt(10) ipv6netConfigTable(9) ipv6netConfigEntry(1) ipv6netConfigStatus(10)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) accton(259) snmpMgt(6) cheetahSwitchMgt(10) es4524dMIB(95) es4524dMIBObjects(1) ipMgt(10) ipv6netConfigTable(9) ipv6netConfigEntry(1) ipv6netConfigStatus(10)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) accton(259) snmpMgt(6) cheetahSwitchMgt(10) es4524dMIB(95) es4524dMIBObjects(1) ipMgt(10) ipv6netConfigTable(9) ipv6netConfigEntry(1) ipv6netConfigStatus(10)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) accton(259) snmpMgt(6) cheetahSwitchMgt(10) es4524dMIB(95) es4524dMIBObjects(1) ipMgt(10) ipv6netConfigTable(9) ipv6netConfigEntry(1) ipv6netConfigStatus(10)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) accton(259) snmpMgt(6) cheetahSwitchMgt(10) es4524dMIB(95) es4524dMIBObjects(1) ipMgt(10) ipv6netConfigTable(9) ipv6netConfigEntry(1) ipv6netConfigStatus(10)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) accton(259) snmpMgt(6) cheetahSwitchMgt(10) es4524dMIB(95) es4524dMIBObjects(1) ipMgt(10) ipv6netConfigTable(9) ipv6netConfigEntry(1) ipv6netConfigStatus(10)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) accton(259) snmpMgt(6) cheetahSwitchMgt(10) es4524dMIB(95) es4524dMIBObjects(1) ipMgt(10) ipv6netConfigTable(9) ipv6netConfigEntry(1) ipv6netConfigStatus(10)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) accton(259) snmpMgt(6) cheetahSwitchMgt(10) es4524dMIB(95) es4524dMIBObjects(1) ipMgt(10) ipv6netConfigTable(9) ipv6netConfigEntry(1) ipv6netConfigStatus(10)}
OID-IRI notation
  • /1/3/6/1/4/1/259/6/10/95/1/10/9/1/10
  • /ISO/Identified-Organization/6/1/4/1/259/6/10/95/1/10/9/1/10
  • /ISO/3/6/1/4/1/259/6/10/95/1/10/9/1/10
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/259/snmpMgt/cheetahSwitchMgt/es4524dMIB/es4524dMIBObjects/ipMgt/ipv6netConfigTable/ipv6netConfigEntry/ipv6netConfigStatus
  • /iso/identified-organization/dod/internet/private/enterprise/accton/snmpMgt/cheetahSwitchMgt/es4524dMIB/es4524dMIBObjects/ipMgt/ipv6netConfigTable/ipv6netConfigEntry/ipv6netConfigStatus
  • /iso/identified-organization/dod/internet/private/enterprise/EdgeCore/snmpMgt/cheetahSwitchMgt/es4524dMIB/es4524dMIBObjects/ipMgt/ipv6netConfigTable/ipv6netConfigEntry/ipv6netConfigStatus
  • /iso/identified-organization/dod/internet/private/enterprises/259/snmpMgt/cheetahSwitchMgt/es4524dMIB/es4524dMIBObjects/ipMgt/ipv6netConfigTable/ipv6netConfigEntry/ipv6netConfigStatus
  • /iso/identified-organization/dod/internet/private/enterprises/accton/snmpMgt/cheetahSwitchMgt/es4524dMIB/es4524dMIBObjects/ipMgt/ipv6netConfigTable/ipv6netConfigEntry/ipv6netConfigStatus
  • /iso/identified-organization/dod/internet/private/enterprises/EdgeCore/snmpMgt/cheetahSwitchMgt/es4524dMIB/es4524dMIBObjects/ipMgt/ipv6netConfigTable/ipv6netConfigEntry/ipv6netConfigStatus
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/259/snmpMgt/cheetahSwitchMgt/es4524dMIB/es4524dMIBObjects/ipMgt/ipv6netConfigTable/ipv6netConfigEntry/ipv6netConfigStatus
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/accton/snmpMgt/cheetahSwitchMgt/es4524dMIB/es4524dMIBObjects/ipMgt/ipv6netConfigTable/ipv6netConfigEntry/ipv6netConfigStatus
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/EdgeCore/snmpMgt/cheetahSwitchMgt/es4524dMIB/es4524dMIBObjects/ipMgt/ipv6netConfigTable/ipv6netConfigEntry/ipv6netConfigStatus
  • /iso/identified-organization/dod/internet/private/vendor-objects/259/snmpMgt/cheetahSwitchMgt/es4524dMIB/es4524dMIBObjects/ipMgt/ipv6netConfigTable/ipv6netConfigEntry/ipv6netConfigStatus
  • /iso/identified-organization/dod/internet/private/vendor-objects/accton/snmpMgt/cheetahSwitchMgt/es4524dMIB/es4524dMIBObjects/ipMgt/ipv6netConfigTable/ipv6netConfigEntry/ipv6netConfigStatus
  • /iso/identified-organization/dod/internet/private/vendor-objects/EdgeCore/snmpMgt/cheetahSwitchMgt/es4524dMIB/es4524dMIBObjects/ipMgt/ipv6netConfigTable/ipv6netConfigEntry/ipv6netConfigStatus
  • /iso/org/dod/internet/private/enterprise/259/snmpMgt/cheetahSwitchMgt/es4524dMIB/es4524dMIBObjects/ipMgt/ipv6netConfigTable/ipv6netConfigEntry/ipv6netConfigStatus
  • /iso/org/dod/internet/private/enterprise/accton/snmpMgt/cheetahSwitchMgt/es4524dMIB/es4524dMIBObjects/ipMgt/ipv6netConfigTable/ipv6netConfigEntry/ipv6netConfigStatus
  • /iso/org/dod/internet/private/enterprise/EdgeCore/snmpMgt/cheetahSwitchMgt/es4524dMIB/es4524dMIBObjects/ipMgt/ipv6netConfigTable/ipv6netConfigEntry/ipv6netConfigStatus
  • /iso/org/dod/internet/private/enterprises/259/snmpMgt/cheetahSwitchMgt/es4524dMIB/es4524dMIBObjects/ipMgt/ipv6netConfigTable/ipv6netConfigEntry/ipv6netConfigStatus
  • Additional combinations skipped.

Descriptions

ipv6netConfigStatus — Edgecore MIB copies (Observium Community)

The status of this conceptual row entry. This object isused to manage the creation and deletion of conceptual rows. The status column has six defined values: - 'active', which indicates that the conceptual row is available for use by the managed device; - 'notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); - 'notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device; - 'createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - 'createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - 'destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except 'notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: 'notReady', 'notInService' or 'active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value 'active'); it is not available for use by the managed device, though the agent has sufficient information to make it so (the status column has value 'notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value 'notReady'). For a detailed description of this object, please refer to SNMPv2-TC MIB.

Source records

ipv6netConfigStatus

Status in source: current.

Names: ipv6netConfigStatus

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "ipv6netConfigStatus",
    "OBJECT-TYPE",
    "SYNTAX",
    "RowStatus",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The status of this conceptual row entry. This object isused to manage the creation and deletion of conceptual rows. The status column has six defined values: - 'active', which indicates that the conceptual row is available for use by the managed device; - 'notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); - 'notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device; - 'createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - 'createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - 'destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except 'notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: 'notReady', 'notInService' or 'active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value 'active'); it is not available for use by the managed device, though the agent has sufficient information to make it so (the status column has value 'notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value 'notReady'). For a detailed description of this object, please refer to SNMPv2-TC MIB.\"",
    "::=",
    "{",
    "ipv6netConfigEntry",
    "10",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "RowStatus"
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The status of this conceptual row entry. This object isused to manage the creation and deletion of conceptual rows. The status column has six defined values: - 'active', which indicates that the conceptual row is available for use by the managed device; - 'notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); - 'notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device; - 'createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - 'createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - 'destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except 'notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: 'notReady', 'notInService' or 'active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value 'active'); it is not available for use by the managed device, though the agent has sufficient information to make it so (the status column has value 'notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value 'notReady'). For a detailed description of this object, please refer to SNMPv2-TC MIB."
    ],
    null,
    null,
    null,
    null
  ]
}
  • Edgecore MIB copies (Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz

    Vendor MIB copy from the Observium Community archive. Edgecore support.

    Module: ES4524D-MIB

    Published definition
    ipv6netConfigStatus OBJECT-TYPE
         SYNTAX  RowStatus
         MAX-ACCESS  read-create
         STATUS      current
         DESCRIPTION 	"The status of this conceptual row entry. This object isused to manage the
    			creation and deletion of conceptual rows.
    
    			The status column has six defined values:
    
    			     - 'active', which indicates that the conceptual row is
    			     available for use by the managed device;
    
    			     - 'notInService', which indicates that the conceptual
    			     row exists in the agent, but is unavailable for use by
    			     the managed device (see NOTE below);
    
    			     - 'notReady', which indicates that the conceptual row
    			     exists in the agent, but is missing information
    			     necessary in order to be available for use by the
    			     managed device;
    
    			     - 'createAndGo', which is supplied by a management
    			     station wishing to create a new instance of a
    			     conceptual row and to have its status automatically set
    			     to active, making it available for use by the managed
    			     device;
    
    			     - 'createAndWait', which is supplied by a management
    			     station wishing to create a new instance of a
    			     conceptual row (but not make it available for use by
    			     the managed device); and,
    
    			     - 'destroy', which is supplied by a management station
    			     wishing to delete all of the instances associated with
    			     an existing conceptual row.
    
    			Whereas five of the six values (all except 'notReady') may
    			be specified in a management protocol set operation, only
    			three values will be returned in response to a management
    			protocol retrieval operation:  'notReady', 'notInService' or
    			'active'.  That is, when queried, an existing conceptual row
    			has only three states:  it is either available for use by
    			the managed device (the status column has value 'active');
    			it is not available for use by the managed device, though
    			the agent has sufficient information to make it so (the
    			status column has value 'notInService'); or, it is not
    			available for use by the managed device, and an attempt to
    			make it so would fail because the agent has insufficient
    			information (the state column has value 'notReady').
    
                For a detailed description of this object, please refer to
                SNMPv2-TC MIB."
         ::= { ipv6netConfigEntry 10 }
    Module imports
    {'IF-MIB': ['InterfaceIndex', 'ifIndex'], 'SNMPv2-TC': ['DisplayString', 'RowStatus', 'TruthValue', 'RowPointer'], 'BRIDGE-MIB': ['BridgeId', 'Timeout', 'dot1dStpPort', 'dot1dStpPortEntry'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'Integer32', 'Counter32', 'IpAddress', 'NOTIFICATION-TYPE', 'enterprises', 'TimeTicks'], 'DIFFSERV-MIB': ['diffServClfrEntry', 'diffServMultiFieldClfrEntry', 'IndexIntegerNextFree', 'IndexInteger'], 'P-BRIDGE-MIB': ['EnabledStatus'], 'Q-BRIDGE-MIB': ['PortList', 'VlanIndex', 'dot1qVlanStaticEntry'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetAddressPrefixLength', 'InetPortNumber'], 'TOKEN-RING-RMON-MIB': ['MacAddress']}

    Related source files and packages:


    Source location: ES4524D-MIB::ipv6netConfigStatus.
    Source version and references

    Downloaded: 2026-10-23T19:26:18.268243+00:00.

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.259)

Rooney Don

Siblings (9)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.259.6.10.95.1.10.9.1.1 ipv6netConfigIfIndex00
1.3.6.1.4.1.259.6.10.95.1.10.9.1.2 ipv6netConfigIpAddressType00
1.3.6.1.4.1.259.6.10.95.1.10.9.1.3 ipv6netConfigIpAddress00
1.3.6.1.4.1.259.6.10.95.1.10.9.1.4 ipv6netConfigPrefixLength00
1.3.6.1.4.1.259.6.10.95.1.10.9.1.5 ipv6netConfigAddrType00
1.3.6.1.4.1.259.6.10.95.1.10.9.1.6 ipv6netConfigAddrAnycastFlag00
1.3.6.1.4.1.259.6.10.95.1.10.9.1.7 ipv6netConfigAddrStatus00
1.3.6.1.4.1.259.6.10.95.1.10.9.1.8 ipv6netConfigAddrFlag00
1.3.6.1.4.1.259.6.10.95.1.10.9.1.9 ipv6netConfigGeneralPrefixBased00