OID reference

ieee8021CnCpTable

1.0.8802.1.1.18.1.5

Description

Each row in this table supplies values for one Congestion Point (CP). This table is indexed by component, port (interface), and an arbitrary CP index. This arbitrary CP index is not necessarily the Congestion Point Identifier (CPID) carried in Congestion Notification Messages (CNMs). Creating an entry in ieee8021CnCom…

Full description and source information

Identification

Identifier and names

Parent
1.0.8802.1.1.18.1 (ieee8021CnMIBObjects)
Node code
5
Node name
ieee8021CnCpTable
Category
SNMP management object
Numeric OID
1.0.8802.1.1.18.1.5
URN notation
urn:oid:1.0.8802.1.1.18.1.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 0 8802 1 1 18 1 5}

  • {iso(1) standard(0) iso8802(8802) ieee802dot1(1) ieee802dot1mibs(1) ieee8021CnMib(18) ieee8021CnMIBObjects(1) ieee8021CnCpTable(5)}
  • {iso(1) std(0) iso8802(8802) ieee802dot1(1) ieee802dot1mibs(1) ieee8021CnMib(18) ieee8021CnMIBObjects(1) ieee8021CnCpTable(5)}
  • {iso(1) iso-standard(0) iso8802(8802) ieee802dot1(1) ieee802dot1mibs(1) ieee8021CnMib(18) ieee8021CnMIBObjects(1) ieee8021CnCpTable(5)}
  • {iso(1) oidISO(0) iso8802(8802) ieee802dot1(1) ieee802dot1mibs(1) ieee8021CnMib(18) ieee8021CnMIBObjects(1) ieee8021CnCpTable(5)}
OID-IRI notation
  • /1/0/8802/1/1/18/1/5
  • /ISO/Standard/8802/1/1/18/1/5
  • /ISO/0/8802/1/1/18/1/5
Named path variants
  • /iso/standard/iso8802/ieee802dot1/ieee802dot1mibs/ieee8021CnMib/ieee8021CnMIBObjects/ieee8021CnCpTable
  • /iso/std/iso8802/ieee802dot1/ieee802dot1mibs/ieee8021CnMib/ieee8021CnMIBObjects/ieee8021CnCpTable
  • /iso/iso-standard/iso8802/ieee802dot1/ieee802dot1mibs/ieee8021CnMib/ieee8021CnMIBObjects/ieee8021CnCpTable
  • /iso/oidISO/iso8802/ieee802dot1/ieee802dot1mibs/ieee8021CnMib/ieee8021CnMIBObjects/ieee8021CnCpTable

SNMP properties

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

ieee8021CnCpTable OBJECT-TYPE 
         SYNTAX SEQUENCE OF Ieee8021CnCpEntry 
         MAX-ACCESS not-accessible 
         STATUS current 
         DESCRIPTION 
         "Each row in this table supplies values for one 
         Congestion Point (CP).

         This table is indexed by component, port (interface), and 
         an arbitrary CP index. This arbitrary CP index is not 
         necessarily the Congestion Point Identifier (CPID) carried in 
         Congestion Notification Messages (CNMs).

         Creating an entry in ieee8021CnCompntPriTable can create an 
         entry in this table, with the default values, on all ports in 
         the bridge component or end station. Because more than one 
         Congestion Notification Priority Value (CNPV) can flow 
         through a single CP, the creation of an entry in 
         ieee8021CnCompntPriTable does not necessarily create a new 
         entry in this table. An end station can have more than one 
         CP for the same CNPV, so creating an entry in 
         ieee8021CnCompntPriTable can create multiple entries in thistable.

         Because each port in a bridge component or end station can have 
         a different relationship between CNPVs and CPs, the entries 
         created or deleted on each port can be different.

         Deleting the last entry in ieee8021CnCompntPriTable for a 
         CNPV passing through the CP controlled by this entry deletes 
         the entry on some or all of the ports in the bridge componentor end station.

         Because each port in a bridge component or end station can have 
         a different relationship between CNPVs and CPs, the entries 
         created or deleted on each port can be different.

         The relationship between ieee8021CnCpIndex 
         values and CPs is an implementation dependent matter.

         The contents of this table SHALL be maintained across a restart 
         of the system, except as noted in the description of 
         ieee8021CnCpIfIndex.

         "

         REFERENCE
         "802.1Qau clause 12.17.4"


         ::= { ieee8021CnMIBObjects 5 }

Meaning

Descriptions

1 unique

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

Each row in this table supplies values for one Congestion Point (CP). This table is indexed by component, port (interface), and an arbitrary CP index. This arbitrary CP index is not necessarily the Congestion Point Identifier (CPID) carried in Congestion Notification Messages (CNMs). Creating an entry in ieee8021CnCompntPriTable can create an entry in this table, with the default values, on all ports in the bridge component or end station. Because more than one Congestion Notification Priority Value (CNPV) can flow through a single CP, the creation of an entry in ieee8021CnCompntPriTable does not necessarily create a new entry in this table. An end station can have more than one CP for the same CNPV, so creating an entry in ieee8021CnCompntPriTable can create multiple entries in thistable. Because each port in a bridge component or end station can have a different relationship between CNPVs and CPs, the entries created or deleted on each port can be different. Deleting the last entry in ieee8021CnCompntPriTable for a CNPV passing through the CP controlled by this entry deletes the entry on some or all of the ports in the bridge componentor end station. Because each port in a bridge component or end station can have a different relationship between CNPVs and CPs, the entries created or deleted on each port can be different. The relationship between ieee8021CnCpIndex values and CPs is an implementation dependent matter. The contents of this table SHALL be maintained across a restart of the system, except as noted in the description of ieee8021CnCpIfIndex.

Sources for this description

Belden, GarrettCom and Hirschmann IT official standalone MIBs

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 1Belden, GarrettCom and Hirschmann IT official standalone MIBs1 record · 1 source

Description 1

ieee8021CnCpTable · currentBelden, GarrettCom and Hirschmann IT official standalone MIBs1 source

Status in source: current.

Names: ieee8021CnCpTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "ieee8021CnCpTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "Ieee8021CnCpEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Each row in this table supplies values for one Congestion Point (CP). This table is indexed by component, port (interface), and an arbitrary CP index. This arbitrary CP index is not necessarily the Congestion Point Identifier (CPID) carried in Congestion Notification Messages (CNMs). Creating an entry in ieee8021CnCompntPriTable can create an entry in this table, with the default values, on all ports in the bridge component or end station. Because more than one Congestion Notification Priority Value (CNPV) can flow through a single CP, the creation of an entry in ieee8021CnCompntPriTable does not necessarily create a new entry in this table. An end station can have more than one CP for the same CNPV, so creating an entry in ieee8021CnCompntPriTable can create multiple entries in thistable. Because each port in a bridge component or end station can have a different relationship between CNPVs and CPs, the entries created or deleted on each port can be different. Deleting the last entry in ieee8021CnCompntPriTable for a CNPV passing through the CP controlled by this entry deletes the entry on some or all of the ports in the bridge componentor end station. Because each port in a bridge component or end station can have a different relationship between CNPVs and CPs, the entries created or deleted on each port can be different. The relationship between ieee8021CnCpIndex values and CPs is an implementation dependent matter. The contents of this table SHALL be maintained across a restart of the system, except as noted in the description of ieee8021CnCpIfIndex. \"",
    "REFERENCE",
    "\"802.1Qau clause 12.17.4\"",
    "::=",
    "{",
    "ieee8021CnMIBObjects",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "Ieee8021CnCpEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Each row in this table supplies values for one Congestion Point (CP). This table is indexed by component, port (interface), and an arbitrary CP index. This arbitrary CP index is not necessarily the Congestion Point Identifier (CPID) carried in Congestion Notification Messages (CNMs). Creating an entry in ieee8021CnCompntPriTable can create an entry in this table, with the default values, on all ports in the bridge component or end station. Because more than one Congestion Notification Priority Value (CNPV) can flow through a single CP, the creation of an entry in ieee8021CnCompntPriTable does not necessarily create a new entry in this table. An end station can have more than one CP for the same CNPV, so creating an entry in ieee8021CnCompntPriTable can create multiple entries in thistable. Because each port in a bridge component or end station can have a different relationship between CNPVs and CPs, the entries created or deleted on each port can be different. Deleting the last entry in ieee8021CnCompntPriTable for a CNPV passing through the CP controlled by this entry deletes the entry on some or all of the ports in the bridge componentor end station. Because each port in a bridge component or end station can have a different relationship between CNPVs and CPs, the entries created or deleted on each port can be different. The relationship between ieee8021CnCpIndex values and CPs is an implementation dependent matter. The contents of this table SHALL be maintained across a restart of the system, except as noted in the description of ieee8021CnCpIfIndex."
    ],
    [
      "REFERENCE",
      "802.1Qau clause 12.17.4"
    ],
    null,
    null,
    null
  ]
}

Registration

Registration authorities

Current Registration Authority (inferred from ancestor 1.0)

ISO and IEC

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.0.8802.1.1.18.1.5.1 ieee8021CnCpEntry1313

Siblings (7)

OIDNameDirect childrenDescendantsDescription
1.0.8802.1.1.18.1.1 ieee8021CnGlobalTable15
1.0.8802.1.1.18.1.2 ieee8021CnErroredPortTable14
1.0.8802.1.1.18.1.3 ieee8021CnCompntPriTable111
1.0.8802.1.1.18.1.4 ieee8021CnPortPriTable110
1.0.8802.1.1.18.1.6 ieee8021CnCpidToInterfaceTable15
1.0.8802.1.1.18.1.7 ieee8021CnRpPortPriTable17
1.0.8802.1.1.18.1.8 ieee8021CnRpGroupTable115