OID reference

prioAclToCosMappingStatus

1.3.6.1.4.1.52.4.12.30.1.16.3.1.1.4

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 …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.52.4.12.30.1.16.3.1.1 (prioAclToCosMappingEntry)
Node code
4
Node name
prioAclToCosMappingStatus
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.52.4.12.30.1.16.3.1.1.4
URN notation
urn:oid:1.3.6.1.4.1.52.4.12.30.1.16.3.1.1.4
Type
OBJECT-TYPE
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 52 4 12 30 1 16 3 1 1 4}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cabletron(52) mibs(4) ctronV2H(12) v2h124-24MIB(30) v2h124-24MIBObjects(1) qosMgt(16) cosMgt(3) prioAclToCosMappingTable(1) prioAclToCosMappingEntry(1) prioAclToCosMappingStatus(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cabletron(52) mibs(4) ctronV2H(12) v2h124-24MIB(30) v2h124-24MIBObjects(1) qosMgt(16) cosMgt(3) prioAclToCosMappingTable(1) prioAclToCosMappingEntry(1) prioAclToCosMappingStatus(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cabletron(52) mibs(4) ctronV2H(12) v2h124-24MIB(30) v2h124-24MIBObjects(1) qosMgt(16) cosMgt(3) prioAclToCosMappingTable(1) prioAclToCosMappingEntry(1) prioAclToCosMappingStatus(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cabletron(52) mibs(4) ctronV2H(12) v2h124-24MIB(30) v2h124-24MIBObjects(1) qosMgt(16) cosMgt(3) prioAclToCosMappingTable(1) prioAclToCosMappingEntry(1) prioAclToCosMappingStatus(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cabletron(52) mibs(4) ctronV2H(12) v2h124-24MIB(30) v2h124-24MIBObjects(1) qosMgt(16) cosMgt(3) prioAclToCosMappingTable(1) prioAclToCosMappingEntry(1) prioAclToCosMappingStatus(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cabletron(52) mibs(4) ctronV2H(12) v2h124-24MIB(30) v2h124-24MIBObjects(1) qosMgt(16) cosMgt(3) prioAclToCosMappingTable(1) prioAclToCosMappingEntry(1) prioAclToCosMappingStatus(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) cabletron(52) mibs(4) ctronV2H(12) v2h124-24MIB(30) v2h124-24MIBObjects(1) qosMgt(16) cosMgt(3) prioAclToCosMappingTable(1) prioAclToCosMappingEntry(1) prioAclToCosMappingStatus(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) cabletron(52) mibs(4) ctronV2H(12) v2h124-24MIB(30) v2h124-24MIBObjects(1) qosMgt(16) cosMgt(3) prioAclToCosMappingTable(1) prioAclToCosMappingEntry(1) prioAclToCosMappingStatus(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cabletron(52) mibs(4) ctronV2H(12) v2h124-24MIB(30) v2h124-24MIBObjects(1) qosMgt(16) cosMgt(3) prioAclToCosMappingTable(1) prioAclToCosMappingEntry(1) prioAclToCosMappingStatus(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cabletron(52) mibs(4) ctronV2H(12) v2h124-24MIB(30) v2h124-24MIBObjects(1) qosMgt(16) cosMgt(3) prioAclToCosMappingTable(1) prioAclToCosMappingEntry(1) prioAclToCosMappingStatus(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cabletron(52) mibs(4) ctronV2H(12) v2h124-24MIB(30) v2h124-24MIBObjects(1) qosMgt(16) cosMgt(3) prioAclToCosMappingTable(1) prioAclToCosMappingEntry(1) prioAclToCosMappingStatus(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cabletron(52) mibs(4) ctronV2H(12) v2h124-24MIB(30) v2h124-24MIBObjects(1) qosMgt(16) cosMgt(3) prioAclToCosMappingTable(1) prioAclToCosMappingEntry(1) prioAclToCosMappingStatus(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) cabletron(52) mibs(4) ctronV2H(12) v2h124-24MIB(30) v2h124-24MIBObjects(1) qosMgt(16) cosMgt(3) prioAclToCosMappingTable(1) prioAclToCosMappingEntry(1) prioAclToCosMappingStatus(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) cabletron(52) mibs(4) ctronV2H(12) v2h124-24MIB(30) v2h124-24MIBObjects(1) qosMgt(16) cosMgt(3) prioAclToCosMappingTable(1) prioAclToCosMappingEntry(1) prioAclToCosMappingStatus(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cabletron(52) mibs(4) ctronV2H(12) v2h124-24MIB(30) v2h124-24MIBObjects(1) qosMgt(16) cosMgt(3) prioAclToCosMappingTable(1) prioAclToCosMappingEntry(1) prioAclToCosMappingStatus(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cabletron(52) mibs(4) ctronV2H(12) v2h124-24MIB(30) v2h124-24MIBObjects(1) qosMgt(16) cosMgt(3) prioAclToCosMappingTable(1) prioAclToCosMappingEntry(1) prioAclToCosMappingStatus(4)}
OID-IRI notation
  • /1/3/6/1/4/1/52/4/12/30/1/16/3/1/1/4
  • /ISO/Identified-Organization/6/1/4/1/52/4/12/30/1/16/3/1/1/4
  • /ISO/3/6/1/4/1/52/4/12/30/1/16/3/1/1/4
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/cabletron/mibs/ctronV2H/v2h124-24MIB/v2h124-24MIBObjects/qosMgt/cosMgt/prioAclToCosMappingTable/prioAclToCosMappingEntry/prioAclToCosMappingStatus
  • /iso/identified-organization/dod/internet/private/enterprise/IMPORTS/mibs/ctronV2H/v2h124-24MIB/v2h124-24MIBObjects/qosMgt/cosMgt/prioAclToCosMappingTable/prioAclToCosMappingEntry/prioAclToCosMappingStatus
  • /iso/identified-organization/dod/internet/private/enterprises/cabletron/mibs/ctronV2H/v2h124-24MIB/v2h124-24MIBObjects/qosMgt/cosMgt/prioAclToCosMappingTable/prioAclToCosMappingEntry/prioAclToCosMappingStatus
  • /iso/identified-organization/dod/internet/private/enterprises/IMPORTS/mibs/ctronV2H/v2h124-24MIB/v2h124-24MIBObjects/qosMgt/cosMgt/prioAclToCosMappingTable/prioAclToCosMappingEntry/prioAclToCosMappingStatus
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/cabletron/mibs/ctronV2H/v2h124-24MIB/v2h124-24MIBObjects/qosMgt/cosMgt/prioAclToCosMappingTable/prioAclToCosMappingEntry/prioAclToCosMappingStatus
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/IMPORTS/mibs/ctronV2H/v2h124-24MIB/v2h124-24MIBObjects/qosMgt/cosMgt/prioAclToCosMappingTable/prioAclToCosMappingEntry/prioAclToCosMappingStatus
  • /iso/identified-organization/dod/internet/private/vendor-objects/cabletron/mibs/ctronV2H/v2h124-24MIB/v2h124-24MIBObjects/qosMgt/cosMgt/prioAclToCosMappingTable/prioAclToCosMappingEntry/prioAclToCosMappingStatus
  • /iso/identified-organization/dod/internet/private/vendor-objects/IMPORTS/mibs/ctronV2H/v2h124-24MIB/v2h124-24MIBObjects/qosMgt/cosMgt/prioAclToCosMappingTable/prioAclToCosMappingEntry/prioAclToCosMappingStatus
  • /iso/org/dod/internet/private/enterprise/cabletron/mibs/ctronV2H/v2h124-24MIB/v2h124-24MIBObjects/qosMgt/cosMgt/prioAclToCosMappingTable/prioAclToCosMappingEntry/prioAclToCosMappingStatus
  • /iso/org/dod/internet/private/enterprise/IMPORTS/mibs/ctronV2H/v2h124-24MIB/v2h124-24MIBObjects/qosMgt/cosMgt/prioAclToCosMappingTable/prioAclToCosMappingEntry/prioAclToCosMappingStatus
  • /iso/org/dod/internet/private/enterprises/cabletron/mibs/ctronV2H/v2h124-24MIB/v2h124-24MIBObjects/qosMgt/cosMgt/prioAclToCosMappingTable/prioAclToCosMappingEntry/prioAclToCosMappingStatus
  • /iso/org/dod/internet/private/enterprises/IMPORTS/mibs/ctronV2H/v2h124-24MIB/v2h124-24MIBObjects/qosMgt/cosMgt/prioAclToCosMappingTable/prioAclToCosMappingEntry/prioAclToCosMappingStatus
  • /iso/org/dod/internet/private/ldap-enterprise/cabletron/mibs/ctronV2H/v2h124-24MIB/v2h124-24MIBObjects/qosMgt/cosMgt/prioAclToCosMappingTable/prioAclToCosMappingEntry/prioAclToCosMappingStatus
  • /iso/org/dod/internet/private/ldap-enterprise/IMPORTS/mibs/ctronV2H/v2h124-24MIB/v2h124-24MIBObjects/qosMgt/cosMgt/prioAclToCosMappingTable/prioAclToCosMappingEntry/prioAclToCosMappingStatus
  • /iso/org/dod/internet/private/vendor-objects/cabletron/mibs/ctronV2H/v2h124-24MIB/v2h124-24MIBObjects/qosMgt/cosMgt/prioAclToCosMappingTable/prioAclToCosMappingEntry/prioAclToCosMappingStatus
  • /iso/org/dod/internet/private/vendor-objects/IMPORTS/mibs/ctronV2H/v2h124-24MIB/v2h124-24MIBObjects/qosMgt/cosMgt/prioAclToCosMappingTable/prioAclToCosMappingEntry/prioAclToCosMappingStatus
  • Additional combinations skipped.

SNMP properties

Value type
RowStatus
Maximum access defined by MIB
read-create
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.

Meaning

Descriptions

2 unique

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

Description 1

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 detail description of this object, please ref to SNMPv2-TC MIB.
Original text from OID Repository
prioAclToCosMappingStatus 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 detail description of this object, please ref to
SNMPv2-TC MIB."
Sources for this description

OID Repository

View at oid-base.com

Description 2

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 detail description of this object, please ref to
SNMPv2-TC MIB.
Sources for this description

Circitor

Parsed from V2H124-24-MIB.mib · V2H124-24-MIB

Source file: Download v2h124-24-mib.txt · Publisher's file

Vendor MIB copy from the Netdisco archive.

Source file: Download V2H124-24-MIB · Publisher's file

Vendor MIB copy from the Observium Community archive.

Related source files and packages:

Source file: Download V2H124-24-MIB.mib

Browse all files from Circitor

Historical records

Additional source information

Information from Circitor
prioAclToCosMappingStatus 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 detail description of this object, please ref to 
            SNMPv2-TC MIB." 
        ::= { prioAclToCosMappingEntry 4 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.52)

McTague Charles N.

Siblings (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.52.4.12.30.1.16.3.1.1.1 prioAclToCosMappingIfIndex00 The port interface of the prioAclToCosMappingEntry. The interface
identified by a particular value of this index is the
same inte…
1.3.6.1.4.1.52.4.12.30.1.16.3.1.1.2 prioAclToCosMappingAclName00 The name of an IP ACL. Within a feature the
name is unique used to identifies
the list to which the entry belongs in the device.
1.3.6.1.4.1.52.4.12.30.1.16.3.1.1.3 prioAclToCosMappingCosValue00 Cos value of the prioAclToCosMappingTable.