Configuring Hardware QoS

Changing Values When Configuring the Minimum/Reserved Buffer Selection for a QoS Group

There are three possible values when configuring the minimum/reserved buffer: all (default value), default, and none. These examples demonstrate how to change the values

Note: This configuration requires saving config and reload of the system to take effect.

Configuring the Minimum/Reserved Buffer Selection for a QoS Group (Default)

Configuring the Minimum/Reserved Buffer Selection for a QoS Group (Default)
POST http://<mgmt-ip>/api/mo/sys/pltfm.json
{
        "platformEntity": {
          "attributes": {
            "qosMinBuffer": "default", 
          }
        }
      }
{
    "imdata": [
        {
            "warning": {
                "attributes": {
                    "text": "Please save config and reload the system for the configuration to take effect\n"
                }
            }
        }
    ]
}
<nc:rpc xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:7b4eca9e-003e-4465-b3a5-b5f657d558b7"><nc:edit-config>
    <nc:target>
      <nc:running/>
    </nc:target>
    <nc:config>
      <System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
        <pltfm-items nc:operation="merge">
          <qosMinBuffer>default</qosMinBuffer>
        </pltfm-items>
      </System>
    </nc:config>
  </nc:edit-config>
</nc:rpc>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

hardware qos min-buffer qos-group default


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntity sys/pltfm


platformEntity Properties

The following table contains information about the platformEntity properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
qosMinBufferplatform:QosMinBuffer
(scalar:Enum8)
qos min-buffer qos-groupSELECTION:
0 - all
1 - none
2 - default
DEFAULT: all


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring the Minimum/Reserved Buffer Selection for a QoS Group (None)

Configuring the Minimum/Reserved Buffer Selection for a QoS Group (None)
POST http://<mgmt-ip>/api/mo/sys/pltfm.json
{
        "platformEntity": {
          "attributes": {
            "qosMinBuffer": “none”,
          }
        }
      }
{
    "imdata": [
        {
            "warning": {
                "attributes": {
                    "text": "Please save config and reload the system for the configuration to take effect\n"
                }
            }
        }
    ]
}
<nc:rpc xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:7b4eca9e-003e-4465-b3a5-b5f657d558b7"><nc:edit-config>
    <nc:target>
      <nc:running/>
    </nc:target>
    <nc:config>
      <System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
        <pltfm-items nc:operation="merge">
          <qosMinBuffer>none</qosMinBuffer>
        </pltfm-items>
      </System>
    </nc:config>
  </nc:edit-config>
</nc:rpc>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

hardware qos min-buffer qos-group none


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntity sys/pltfm


platformEntity Properties

The following table contains information about the platformEntity properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
qosMinBufferplatform:QosMinBuffer
(scalar:Enum8)
qos min-buffer qos-groupSELECTION:
0 - all
1 - none
2 - default
DEFAULT: all


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring the Minimum/Reserved Buffer Selection for a QoS Group (All)

Configuring the Minimum/Reserved Buffer Selection for a QoS Group (All)
POST http://<mgmt-ip>/api/mo/sys/pltfm.json
{
        "platformEntity": {
          "attributes": {
            "qosMinBuffer": “all”,
          }
        }
      }
{
    "imdata": [
        {
            "warning": {
                "attributes": {
                    "text": "Please save config and reload the system for the configuration to take effect\n"
                }
            }
        }
    ]
}
<nc:rpc xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:7b4eca9e-003e-4465-b3a5-b5f657d558b7"><nc:edit-config>
    <nc:target>
      <nc:running/>
    </nc:target>
    <nc:config>
      <System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
        <pltfm-items nc:operation="merge">
          <qosMinBuffer>all</qosMinBuffer>
        </pltfm-items>
      </System>
    </nc:config>
  </nc:edit-config>
</nc:rpc>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

hardware qos min-buffer qos-group all


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntity sys/pltfm


platformEntity Properties

The following table contains information about the platformEntity properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
qosMinBufferplatform:QosMinBuffer
(scalar:Enum8)
qos min-buffer qos-groupSELECTION:
0 - all
1 - none
2 - default
DEFAULT: all


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring PG Headroom Reservation Percent

Configuring PG Headroom Reservation Percent
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "platformEntity": {
    "children": [
      {
        "platformQos": {
          "attributes": {
            "pgHdrmReserve": "25"
}}}]}}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <qos-items>
      <pgHdrmReserve>25</pgHdrmReserve>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

hardware qos ing-pg-hdrm-reserve percent 25


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntitysys/pltfm
platformQossys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
pgHdrmReservescalar:UByte
Percent of Hdrm to reserve
RANGE: [20 , 100]
DEFAULT: 100


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting PG Headroom Reservation Percent

Deleting PG Headroom Reservation Percent
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "platformEntity": {
    "children": [
      {
        "platformQos": {
          "attributes": {
            "pgHdrmReserve": "100"
}}}]}}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <qos-items>
      <pgHdrmReserve>100</pgHdrmReserve>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no hardware qos ing-pg-hdrm-reserve percent 25


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntitysys/pltfm
platformQossys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
pgHdrmReservescalar:UByte
Percent of Hdrm to reserve
RANGE: [20 , 100]
DEFAULT: 100


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring PG Min

Configuring PG Min 
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "platformEntity": {
    "children": [
      {
        "platformQos": {
          "attributes": {
            "pgMinValue": "0",
            "pgNoMin": "yes"
}}}]}}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <qos-items>
      <pgMinValue>0</pgMinValue>
      <pgNoMin>true</pgNoMin>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

hardware qos ing-pg-no-min


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntitysys/pltfm
platformQossys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
pgMinValuescalar:UByte
PG Min Value
RANGE: [0 , 32]
DEFAULT: 0
pgNoMinscalar:Bool
PG no-minSELECTION: true or false
DEFAULT: false


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting PG Min

Deleting PG Min 
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "platformEntity": {
    "children": [
      {
        "platformQos": {
          "attributes": {
            "pgMinValue": "0",
            "pgNoMin": "no"
}}}]}}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <qos-items>
      <pgMinValue>0</pgMinValue>
      <pgNoMin>false</pgNoMin>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no hardware qos ing-pg-no-min


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntitysys/pltfm
platformQossys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
pgMinValuescalar:UByte
PG Min Value
RANGE: [0 , 32]
DEFAULT: 0
pgNoMinscalar:Bool
PG no-minSELECTION: true or false
DEFAULT: false


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring PGMIN Value

Configuring PGMIN Value
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "platformEntity": {
    "children": [
      {
        "platformQos": {
          "attributes": {
            "pgMinValue": "1",
            "pgNoMin": "no"
}}}]}}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <qos-items>
      <pgMinValue>1</pgMinValue>
      <pgNoMin>false</pgNoMin>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

hardware qos ing-pg-no-min pgmin 1


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntitysys/pltfm
platformQossys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
pgMinValuescalar:UByte
PG Min Value
RANGE: [0 , 32]
DEFAULT: 0
pgNoMinscalar:Bool
PG no-minSELECTION: true or false
DEFAULT: false


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting PGMIN Value

Deleting PGMIN Value 
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "platformEntity": {
    "children": [
      {
        "platformQos": {
          "attributes": {
            "pgMinValue": "0",
            "pgNoMin": "no"
}}}]}}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <qos-items>
      <pgMinValue>0</pgMinValue>
      <pgNoMin>false</pgNoMin>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no hardware qos ing-pg-no-min pgmin 1


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntitysys/pltfm
platformQossys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
pgMinValuescalar:UByte
PG Min Value
RANGE: [0 , 32]
DEFAULT: 0
pgNoMinscalar:Bool
PG no-minSELECTION: true or false
DEFAULT: false


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Ingress PG Shared Buffer Usage

Configuring Ingress PG Shared Buffer Usage 
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "platformEntity": {
    "children": [
      {
        "platformQos": {
          "attributes": {
            "pgShare": "Enabled"
}}}]}}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <qos-items>
      <pgShare>Enabled</pgShare>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

hardware qos ing-pg-share


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntitysys/pltfm
platformQossys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
pgShareplatform:ConfigState
(scalar:Enum8)
PG Shared Buffer UsageSELECTION:
0 - Disabled
1 - Enabled
DEFAULT: Enabled


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Ingress PG Shared Buffer Usage

Deleting Ingress PG Shared Buffer Usage
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "platformEntity": {
    "children": [
      {
        "platformQos": {
          "attributes": {
            "pgShare": "Disabled"
}}}]}}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <qos-items>
      <pgShare>Disabled</pgShare>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no hardware qos ing-pg-share


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntitysys/pltfm
platformQossys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
pgShareplatform:ConfigState
(scalar:Enum8)
PG Shared Buffer UsageSELECTION:
0 - Disabled
1 - Enabled
DEFAULT: Enabled


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring QoS Classification on NS Only in Hardware

Configuring QoS Classification on NS Only in Hardware
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "platformEntity": {
    "children": [
      {
        "platformQos": {
          "attributes": {
            "classify": "Enabled"
}}}]}}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <qos-items>
      <classify>Enabled</classify>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

hardware qos classify ns-only


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntitysys/pltfm
platformQossys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
classifyplatform:ConfigState
(scalar:Enum8)
Qos classificationSELECTION:
0 - Disabled
1 - Enabled
DEFAULT: Disabled


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting IPG in Shaping/Policing

Deleting IPG in Shaping/Policing 
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "platformEntity": {
    "children": [
      {
        "platformQos": {
          "attributes": {
            "ipg": "Disabled"
}}}]}}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <qos-items>
      <ipg>Disabled</ipg>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no hardware qos include ipg


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntitysys/pltfm
platformQossys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
ipgplatform:ConfigState
(scalar:Enum8)
Include IPG in shape/policeSELECTION:
0 - Disabled
1 - Enabled
DEFAULT: Disabled


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring IPG in Shaping/Policing

Configuring IPG in Shaping/Policing
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "platformEntity": {
    "children": [
      {
        "platformQos": {
          "attributes": {
            "ipg": "Enabled"
}}}]}}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <qos-items>
      <ipg>Enabled</ipg>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

hardware qos include ipg


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntitysys/pltfm
platformQossys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
ipgplatform:ConfigState
(scalar:Enum8)
Include IPG in shape/policeSELECTION:
0 - Disabled
1 - Enabled
DEFAULT: Disabled


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring OOBST Burst-Detect Thresholds in Bytes

Configuring OOBST Burst-Detect Thresholds in Bytes
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "ipqosEntity": {
          "children": [
            {
              "ipqosQueuing": {
                "children": [
                  {
                    "ipqosPMapEntity": {
                      "children": [
                        {
                          "ipqosPMapInst": {
                            "attributes": {
                              "matchType": "match-all",
                              "name": "dme-policy"
                            },
                            "children": [
                              {
                                "ipqosMatchCMap": {
                                  "attributes": {
                                    "name": "c-out-8q-q1"
                                  },
                                  "children": [
                                    {
                                      "ipqosBurstDetectState": {
                                        "attributes": {
                                          "val": "enabled"
                                        }
                                      }
                                    }
                                  ]
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      },
      {
        "platformEntity": {
          "children": [
            {
              "platformQos": {
                "attributes": {
                  "burstDetectFallThreshUnit": "bytes",
                  "burstDetectFallThreshold": "5000",
                  "burstDetectRiseThreshUnit": "bytes",
                  "burstDetectRiseThreshold": "10000"
                }
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <ipqos-items>
    <queuing-items>
      <p-items>
        <name-items>
          <PMapInst-list>
            <name>dme-policy</name>
            <matchType>match-all</matchType>
            <cmap-items>
              <MatchCMap-list>
                <name>c-out-8q-q1</name>
                <burstdetectstate-items>
                  <val>enabled</val>
                </burstdetectstate-items>
              </MatchCMap-list>
            </cmap-items>
          </PMapInst-list>
        </name-items>
      </p-items>
    </queuing-items>
  </ipqos-items>
  <pltfm-items>
    <qos-items>
      <burstDetectFallThreshUnit>bytes</burstDetectFallThreshUnit>
      <burstDetectFallThreshold>5000</burstDetectFallThreshold>
      <burstDetectRiseThreshUnit>bytes</burstDetectRiseThreshUnit>
      <burstDetectRiseThreshold>10000</burstDetectRiseThreshold>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(3).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

hardware qos burst-detect rise-threshold 10000 bytes fall-threshold 5000 bytes
  policy-map type queuing dme-policy
   class type queuing c-out-8q-q1
    burst-detect enable


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
topSystem sys
ipqosEntity sys/ipqos
ipqosQueuing sys/ipqos/queuing
ipqosPMapEntity sys/ipqos/queuing/p
ipqosPMapInst sys/ipqos/queuing/p/name-dme-policy
ipqosMatchCMap sys/ipqos/queuing/p/name-dme-policy/cmap-c-out-8q-q1
ipqosBurstDetectState sys/ipqos/queuing/p/name-dme-policy/cmap-c-out-8q-q1/burstdetectstate
platformEntity sys/pltfm
platformQos sys/pltfm/qos


ipqosPMapInst Properties

The following table contains information about the ipqosPMapInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
matchTypeipqos:QoSMatchType
(scalar:Enum8)
Match-any, match-all or match-firstSELECTION:
0 - match-any
1 - match-all
2 - match-first
DEFAULT: match-all
nameipqos:PMapName
(string:Basic)
Name of policy-map
MAX SIZE: 39


ipqosMatchCMap Properties

The following table contains information about the ipqosMatchCMap properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
nameipqos:CMapName
(string:Basic)
Match using class-map
MAX SIZE: 39


ipqosBurstDetectState Properties

The following table contains information about the ipqosBurstDetectState properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
valipqos:BurstState
(scalar:Enum8)
Burst detect state enabled/disabledSELECTION:
0 - disabled
1 - enabled
DEFAULT: enabled


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
burstDetectFallThreshUnitplatform:ThreshUnit
(scalar:Enum8)
Units for fall-threshold valueSELECTION:
0 - none
1 - bytes
DEFAULT: none
burstDetectFallThresholdplatform:Threshold
(scalar:Uint32)
Threshold bytes to stop monitoring burst
RANGE: [0 , 13319072]
DEFAULT: 0
burstDetectRiseThreshUnitplatform:ThreshUnit
(scalar:Enum8)
Units for rise-threshold valueSELECTION:
0 - none
1 - bytes
DEFAULT: none
burstDetectRiseThresholdplatform:Threshold
(scalar:Uint32)
Threshold bytes to start monitoring burst
RANGE: [0 , 13319072]
DEFAULT: 0


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting OOBST Burst-Detect Thresholds

Deleting OOBST Burst-Detect Thresholds
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "ipqosEntity": {
          "children": [
            {
              "ipqosQueuing": {
                "children": [
                  {
                    "ipqosPMapEntity": {
                      "children": [
                        {
                          "ipqosPMapInst": {
                            "attributes": {
                              "matchType": "match-all",
                              "name": "dme-policy"
                            },
                            "children": [
                              {
                                "ipqosMatchCMap": {
                                  "attributes": {
                                    "name": "c-out-8q-q1"
                                  },
                                  "children": [
                                    {
                                      "ipqosBurstDetectState": {
                                        "attributes": {
                                          "status": "deleted"
                                        }
                                      }
                                    }
                                  ]
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      },
      {
        "platformEntity": {
          "children": [
            {
              "platformQos": {
                "attributes": {
                  "burstDetectFallThreshUnit": "bytes",
                  "burstDetectFallThreshold": "5000",
                  "burstDetectRiseThreshUnit": "bytes",
                  "burstDetectRiseThreshold": "10000"
                }
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <ipqos-items>
    <queuing-items>
      <p-items>
        <name-items>
          <PMapInst-list>
            <name>dme-policy</name>
            <matchType>match-all</matchType>
            <cmap-items>
              <MatchCMap-list>
                <name>c-out-8q-q1</name>
                <burstdetectstate-items nc:operation="delete">
                </burstdetectstate-items>
              </MatchCMap-list>
            </cmap-items>
          </PMapInst-list>
        </name-items>
      </p-items>
    </queuing-items>
  </ipqos-items>
  <pltfm-items>
    <qos-items>
      <burstDetectFallThreshUnit>bytes</burstDetectFallThreshUnit>
      <burstDetectFallThreshold>5000</burstDetectFallThreshold>
      <burstDetectRiseThreshUnit>bytes</burstDetectRiseThreshUnit>
      <burstDetectRiseThreshold>10000</burstDetectRiseThreshold>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(3).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

hardware qos burst-detect rise-threshold 10000 bytes fall-threshold 5000 bytes
  policy-map type queuing dme-policy
   class type queuing c-out-8q-q1
    no burst-detect enable


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
topSystem sys
ipqosEntity sys/ipqos
ipqosQueuing sys/ipqos/queuing
ipqosPMapEntity sys/ipqos/queuing/p
ipqosPMapInst sys/ipqos/queuing/p/name-dme-policy
ipqosMatchCMap sys/ipqos/queuing/p/name-dme-policy/cmap-c-out-8q-q1
ipqosBurstDetectState sys/ipqos/queuing/p/name-dme-policy/cmap-c-out-8q-q1/burstdetectstate
platformEntity sys/pltfm
platformQos sys/pltfm/qos


ipqosPMapInst Properties

The following table contains information about the ipqosPMapInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
matchTypeipqos:QoSMatchType
(scalar:Enum8)
Match-any, match-all or match-firstSELECTION:
0 - match-any
1 - match-all
2 - match-first
DEFAULT: match-all
nameipqos:PMapName
(string:Basic)
Name of policy-map
MAX SIZE: 39


ipqosMatchCMap Properties

The following table contains information about the ipqosMatchCMap properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
nameipqos:CMapName
(string:Basic)
Match using class-map
MAX SIZE: 39


ipqosBurstDetectState Properties

The following table contains information about the ipqosBurstDetectState properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
The upgrade status. This property is for internal use only.SELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
burstDetectFallThreshUnitplatform:ThreshUnit
(scalar:Enum8)
Units for fall-threshold valueSELECTION:
0 - none
1 - bytes
DEFAULT: none
burstDetectFallThresholdplatform:Threshold
(scalar:Uint32)
Threshold bytes to stop monitoring burst
RANGE: [0 , 13319072]
DEFAULT: 0
burstDetectRiseThreshUnitplatform:ThreshUnit
(scalar:Enum8)
Units for rise-threshold valueSELECTION:
0 - none
1 - bytes
DEFAULT: none
burstDetectRiseThresholdplatform:Threshold
(scalar:Uint32)
Threshold bytes to start monitoring burst
RANGE: [0 , 13319072]
DEFAULT: 0


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Dynamic Buffer Sharing

Configuring Dynamic Buffer Sharing
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "ipqosEntity": {
          "attributes": {
            "dynamicBufferShare": "yes"
}}}]}}
{
    imdata:[]
}
<System>
  <ipqos-items>
    <dynamicBufferShare>true</dynamicBufferShare>
  </ipqos-items>
</System>

Note: This example was added in Release 9.3(3).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

hardware qos dynamic-buffer-sharing


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
topSystem sys
ipqosEntity sys/ipqos


ipqosEntity Properties

The following table contains information about the ipqosEntity properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
dynamicBufferSharescalar:Bool
Globally enable/disable dynamic-buffer-sharingSELECTION: true or false


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Dynamic Buffer Sharing

Deleting Dynamic Buffer Sharing
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "ipqosEntity": {
          "attributes": {
            "dynamicBufferShare": "no"
}}}]}}
{
    imdata:[]
}
<System>
  <ipqos-items>
    <dynamicBufferShare>false</dynamicBufferShare>
  </ipqos-items>
</System>

Note: This example was added in Release 9.3(3).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no hardware qos dynamic-buffer-sharing


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
topSystem sys
ipqosEntity sys/ipqos


ipqosEntity Properties

The following table contains information about the ipqosEntity properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
dynamicBufferSharescalar:Bool
Globally enable/disable dynamic-buffer-sharingSELECTION: true or false


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Ability to Drop Multicast Packets for Lossless Queue

Configuring Ability to Drop Multicast Packets for Lossless Queue
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "platformEntity": {
    "children": [
      {
        "platformQos": {
          "attributes": {
            "pfcMcDrop": "Enabled"
}}}]}}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <qos-items>
      <pfcMcDrop>Enabled</pfcMcDrop>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(3).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

hardware qos pfc mc-drop


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntity sys/pltfm
platformQos sys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
pfcMcDropplatform:ConfigState
(scalar:Enum8)
Drop mcast/bcast traffic on no-drop configured classSELECTION:
0 - Disabled
1 - Enabled
DEFAULT: Disabled


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Unconfiguring Ability to Drop Multicast Packets for Lossless Queue

Unconfiguring Ability to Drop Multicast Packets for Lossless Queue
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "platformEntity": {
    "children": [
      {
        "platformQos": {
          "attributes": {
            "pfcMcDrop": "Disabled"
}}}]}}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <qos-items>
      <pfcMcDrop>Disabled</pfcMcDrop>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(3).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no hardware qos pfc mc-drop


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntity sys/pltfm
platformQos sys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
pfcMcDropplatform:ConfigState
(scalar:Enum8)
Drop mcast/bcast traffic on no-drop configured classSELECTION:
0 - Disabled
1 - Enabled
DEFAULT: Disabled


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Class(es) To Monitor

Configuring Class(es) To Monitor 
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "platformEntity": {
    "children": [
      {
        "platformQos": {
          "attributes": {
            "bufPeakMonitorCnt0Class0": "unconfigure",
            "bufPeakMonitorCnt0Class1": "configure",
            "bufPeakMonitorCnt0Class2": "unconfigure",
            "bufPeakMonitorCnt0Class3": "unconfigure",
            "bufPeakMonitorCnt0Class4": "unconfigure",
            "bufPeakMonitorCnt0Class5": "unconfigure",
            "bufPeakMonitorCnt0Class6": "unconfigure",
            "bufPeakMonitorCnt0Class7": "unconfigure"
}}}]}}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <qos-items>
      <bufPeakMonitorCnt0Class0>unconfigure</bufPeakMonitorCnt0Class0>
      <bufPeakMonitorCnt0Class1>configure</bufPeakMonitorCnt0Class1>
      <bufPeakMonitorCnt0Class2>unconfigure</bufPeakMonitorCnt0Class2>
      <bufPeakMonitorCnt0Class3>unconfigure</bufPeakMonitorCnt0Class3>
      <bufPeakMonitorCnt0Class4>unconfigure</bufPeakMonitorCnt0Class4>
      <bufPeakMonitorCnt0Class5>unconfigure</bufPeakMonitorCnt0Class5>
      <bufPeakMonitorCnt0Class6>unconfigure</bufPeakMonitorCnt0Class6>
      <bufPeakMonitorCnt0Class7>unconfigure</bufPeakMonitorCnt0Class7>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(3).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

hardware qos buffer peak monitor counter0 class 1


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntity sys/pltfm
platformQos sys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
bufPeakMonitorCnt0Class0platform:ConfigureSt
(scalar:Enum8)
Used to configure/unconfigure buffer peak monitor for counter 0 class 0SELECTION:
0 - unconfigure
1 - configure
DEFAULT: configure
bufPeakMonitorCnt0Class1platform:ConfigureSt
(scalar:Enum8)
Used to configure/unconfigure buffer peak monitor for counter 0 class 1SELECTION:
0 - unconfigure
1 - configure
DEFAULT: configure
bufPeakMonitorCnt0Class2platform:ConfigureSt
(scalar:Enum8)
Used to configure/unconfigure buffer peak monitor for counter 0 class 2SELECTION:
0 - unconfigure
1 - configure
DEFAULT: configure
bufPeakMonitorCnt0Class3platform:ConfigureSt
(scalar:Enum8)
Used to configure/unconfigure buffer peak monitor for counter 0 class 3SELECTION:
0 - unconfigure
1 - configure
DEFAULT: configure
bufPeakMonitorCnt0Class4platform:ConfigureSt
(scalar:Enum8)
Used to configure/unconfigure buffer peak monitor for counter 0 class 4SELECTION:
0 - unconfigure
1 - configure
DEFAULT: configure
bufPeakMonitorCnt0Class5platform:ConfigureSt
(scalar:Enum8)
Used to configure/unconfigure buffer peak monitor for counter 0 class 5SELECTION:
0 - unconfigure
1 - configure
DEFAULT: configure
bufPeakMonitorCnt0Class6platform:ConfigureSt
(scalar:Enum8)
Used to configure/unconfigure buffer peak monitor for counter 0 class 6SELECTION:
0 - unconfigure
1 - configure
DEFAULT: configure
bufPeakMonitorCnt0Class7platform:ConfigureSt
(scalar:Enum8)
Used to configure/unconfigure buffer peak monitor for counter 0 class 7SELECTION:
0 - unconfigure
1 - configure
DEFAULT: configure


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Class(es) To Monitor

Deleting Class(es) To Monitor 
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "platformEntity": {
    "children": [
      {
        "platformQos": {
          "attributes": {
            "bufPeakMonitorCnt0Class0": "configure",
            "bufPeakMonitorCnt0Class1": "configure",
            "bufPeakMonitorCnt0Class2": "configure",
            "bufPeakMonitorCnt0Class3": "configure",
            "bufPeakMonitorCnt0Class4": "configure",
            "bufPeakMonitorCnt0Class5": "configure",
            "bufPeakMonitorCnt0Class6": "configure",
            "bufPeakMonitorCnt0Class7": "configure"
}}}]}}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <qos-items>
      <bufPeakMonitorCnt0Class0>configure</bufPeakMonitorCnt0Class0>
      <bufPeakMonitorCnt0Class1>configure</bufPeakMonitorCnt0Class1>
      <bufPeakMonitorCnt0Class2>configure</bufPeakMonitorCnt0Class2>
      <bufPeakMonitorCnt0Class3>configure</bufPeakMonitorCnt0Class3>
      <bufPeakMonitorCnt0Class4>configure</bufPeakMonitorCnt0Class4>
      <bufPeakMonitorCnt0Class5>configure</bufPeakMonitorCnt0Class5>
      <bufPeakMonitorCnt0Class6>configure</bufPeakMonitorCnt0Class6>
      <bufPeakMonitorCnt0Class7>configure</bufPeakMonitorCnt0Class7>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(3).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no hardware qos buffer peak monitor counter0 class 1


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntity sys/pltfm
platformQos sys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
bufPeakMonitorCnt0Class0platform:ConfigureSt
(scalar:Enum8)
Used to configure/unconfigure buffer peak monitor for counter 0 class 0SELECTION:
0 - unconfigure
1 - configure
DEFAULT: configure
bufPeakMonitorCnt0Class1platform:ConfigureSt
(scalar:Enum8)
Used to configure/unconfigure buffer peak monitor for counter 0 class 1SELECTION:
0 - unconfigure
1 - configure
DEFAULT: configure
bufPeakMonitorCnt0Class2platform:ConfigureSt
(scalar:Enum8)
Used to configure/unconfigure buffer peak monitor for counter 0 class 2SELECTION:
0 - unconfigure
1 - configure
DEFAULT: configure
bufPeakMonitorCnt0Class3platform:ConfigureSt
(scalar:Enum8)
Used to configure/unconfigure buffer peak monitor for counter 0 class 3SELECTION:
0 - unconfigure
1 - configure
DEFAULT: configure
bufPeakMonitorCnt0Class4platform:ConfigureSt
(scalar:Enum8)
Used to configure/unconfigure buffer peak monitor for counter 0 class 4SELECTION:
0 - unconfigure
1 - configure
DEFAULT: configure
bufPeakMonitorCnt0Class5platform:ConfigureSt
(scalar:Enum8)
Used to configure/unconfigure buffer peak monitor for counter 0 class 5SELECTION:
0 - unconfigure
1 - configure
DEFAULT: configure
bufPeakMonitorCnt0Class6platform:ConfigureSt
(scalar:Enum8)
Used to configure/unconfigure buffer peak monitor for counter 0 class 6SELECTION:
0 - unconfigure
1 - configure
DEFAULT: configure
bufPeakMonitorCnt0Class7platform:ConfigureSt
(scalar:Enum8)
Used to configure/unconfigure buffer peak monitor for counter 0 class 7SELECTION:
0 - unconfigure
1 - configure
DEFAULT: configure


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring SPAN Pool Group Thresholds

Configuring SPAN Pool Group Thresholds 
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "platformEntity": {
    "children": [
      {
        "platformQos": {
          "attributes": {
            "cpuSize": "1443",
            "lCpuSize": "1443",
            "spanSize": "2528"
}}}]}}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <qos-items>
      <cpuSize>1443</cpuSize>
      <lCpuSize>1443</lCpuSize>
      <spanSize>2528</spanSize>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(3).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

hardware qos cpu-pg-size 1443 lcpu-pg-size 1443 span-pg-size 2528


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntity sys/pltfm
platformQos sys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
cpuSizescalar:Uint16
CPU Pool Group threshold
RANGE: [0 , 1500]
DEFAULT: 0
lCpuSizescalar:Uint16
LCPU Pool Group threshold
RANGE: [0 , 1500]
DEFAULT: 0
spanSizescalar:Uint32
Span Pool Group size
RANGE: [0 , 10000]
DEFAULT: 0


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting SPAN Pool Group Thresholds

Deleting SPAN Pool Group Thresholds 
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "platformEntity": {
    "children": [
      {
        "platformQos": {
          "attributes": {
            "cpuSize": "0",
            "lCpuSize": "0",
            "spanSize": "0"
}}}]}}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <qos-items>
      <cpuSize>0</cpuSize>
      <lCpuSize>0</lCpuSize>
      <spanSize>0</spanSize>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(3).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no hardware qos cpu-pg-size 1443 lcpu-pg-size 1443 span-pg-size 2528


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntity sys/pltfm
platformQos sys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
cpuSizescalar:Uint16
CPU Pool Group threshold
RANGE: [0 , 1500]
DEFAULT: 0
lCpuSizescalar:Uint16
LCPU Pool Group threshold
RANGE: [0 , 1500]
DEFAULT: 0
spanSizescalar:Uint32
Span Pool Group size
RANGE: [0 , 10000]
DEFAULT: 0


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring No-drop Pool Group Thresholds for EX Platforms

Configuring No-drop Pool Group Thresholds for EX Platforms 
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "platformEntity": {
    "children": [
      {
        "platformQos": {
          "attributes": {
            "nodropPgGreenThresh": "1",
            "nodropPgRedThresh": "1",
            "nodropPgSize": "1",
            "nodropPgYellowThresh": "1"
}}}]}}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <qos-items>
      <nodropPgGreenThresh>1</nodropPgGreenThresh>
      <nodropPgRedThresh>1</nodropPgRedThresh>
      <nodropPgSize>1</nodropPgSize>
      <nodropPgYellowThresh>1</nodropPgYellowThresh>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(3).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

hardware qos nodrop-PG-thresholds PG-size 1 Red-threshold 1 Yellow-threshold 1 Green-threshold 1


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntity sys/pltfm
platformQos sys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
nodropPgGreenThreshscalar:Uint32
Configure No-drop PG green thresholdRANGE: [0, 4294967295]
DEFAULT: 0
nodropPgRedThreshscalar:Uint32
Configure No-drop PG red thresholdRANGE: [0, 4294967295]
DEFAULT: 0
nodropPgSizescalar:Uint32
Configure No-drop Pool Group sizeRANGE: [0, 4294967295]
DEFAULT: 0
nodropPgYellowThreshscalar:Uint32
Configure No-drop PG yellow thresholdRANGE: [0, 4294967295]
DEFAULT: 0


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting No-drop Pool Group Thresholds for EX Platforms

Deleting No-drop Pool Group Thresholds for EX Platforms
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "platformEntity": {
    "children": [
      {
        "platformQos": {
          "attributes": {
            "nodropPgGreenThresh": "0",
            "nodropPgRedThresh": "0",
            "nodropPgSize": "0",
            "nodropPgYellowThresh": "0"
}}}]}}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <qos-items>
      <nodropPgGreenThresh>0</nodropPgGreenThresh>
      <nodropPgRedThresh>0</nodropPgRedThresh>
      <nodropPgSize>0</nodropPgSize>
      <nodropPgYellowThresh>0</nodropPgYellowThresh>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(3).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no hardware qos nodrop-PG-thresholds PG-size 1 Red-threshold 1 Yellow-threshold 1 Green-threshold 1


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntity sys/pltfm
platformQos sys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
nodropPgGreenThreshscalar:Uint32
Configure No-drop PG green thresholdRANGE: [0, 4294967295]
DEFAULT: 0
nodropPgRedThreshscalar:Uint32
Configure No-drop PG red thresholdRANGE: [0, 4294967295]
DEFAULT: 0
nodropPgSizescalar:Uint32
Configure No-drop Pool Group sizeRANGE: [0, 4294967295]
DEFAULT: 0
nodropPgYellowThreshscalar:Uint32
Configure No-drop PG yellow thresholdRANGE: [0, 4294967295]
DEFAULT: 0


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Noise Thresholds

Configuring Noise Thresholds 
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "platformEntity": {
    "children": [
      {
        "platformQos": {
          "attributes": {
            "qNoisePercent": "52"
}}}]}}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <qos-items>
      <qNoisePercent>52</qNoisePercent>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(3).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

hardware qos q-noise percent 52


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntity sys/pltfm
platformQos sys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
qNoisePercentscalar:Uint16
To configure queue noise threshold in percentage
RANGE: [0 , 100]
DEFAULT: 20


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Noise Thresholds

Deleting Noise Thresholds
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "platformEntity": {
    "children": [
      {
        "platformQos": {
          "attributes": {
            "qNoisePercent": "20"
}}}]}}
{
    imdata:[]
}
<System>
  <pltfm-items>
    <qos-items>
      <qNoisePercent>20</qNoisePercent>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(3).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no hardware qos q-noise percent 52


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
platformEntity sys/pltfm
platformQos sys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
qNoisePercentscalar:Uint16
To configure queue noise threshold in percentage
RANGE: [0 , 100]
DEFAULT: 20


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Burst-Detect

Configuring Burst-Detect
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "children": [
            {
              "platformQos": {
                "attributes": {
                  "burstDetectMaxRecords": "225"
                }
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<pltfm-items>
    <qos-items>
      <burstDetectMaxRecords>225</burstDetectMaxRecords>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(3).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

hardware qos burst-detect max-records 225


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
topSystem sys
platformEntity sys/pltfm
platformQos sys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
burstDetectMaxRecordsscalar:Uint16
Configure the max number of burst records to monitor
RANGE: [200 , 2000]
DEFAULT: 1000


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Burst-Detect

Deleting Burst-Detect
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "children": [
            {
              "platformQos": {
                "attributes": {
                  "burstDetectMaxRecords": "1000"
                }
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<pltfm-items>
    <qos-items>
      <burstDetectMaxRecords>1000</burstDetectMaxRecords>
    </qos-items>
  </pltfm-items>
</System>

Note: This example was added in Release 9.3(3).

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no hardware qos burst-detect max-records 225


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
topSystem sys
platformEntity sys/pltfm
platformQos sys/pltfm/qos


platformQos Properties

The following table contains information about the platformQos properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
burstDetectMaxRecordsscalar:Uint16
Configure the max number of burst records to monitor
RANGE: [200 , 2000]
DEFAULT: 1000


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html