Configuring Hardware Profile Settings

Configuring the Buffer Monitor (Unicast Sampling Interval in Nano-Seconds and Histogram Threshold)

Configuring the Buffer Monitor (Unicast Sampling Interval in Nano-Seconds and Histogram Threshold)

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "children": [
            {
              "platformBufferMonitor": {
                "attributes": {
                  "bufferMonitorMode": "Unicast",
                  "bufferMonitorState": "Enable",
                  "bufferMonitorThreshhold": "456",
                  "sampling": "123"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <pltfm-items>
    <buffermonitor-items>
      <bufferMonitorMode>Unicast</bufferMonitorMode>
      <bufferMonitorState>Enable</bufferMonitorState>
      <bufferMonitorThreshhold>456</bufferMonitorThreshhold>
      <sampling>123</sampling>
    </buffermonitor-items>
  </pltfm-items>
</System>


CLI Commands

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

hardware profile buffer monitor unicast sampling 123 threshold 456

Note: The property information for this example was added in Release 9.3(3).


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
platformBufferMonitor sys/pltfm/buffermonitor


platformBufferMonitor Properties

The following table contains information about the platformBufferMonitor 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
bufferMonitorModeplatform:bufferMonitorMd
(scalar:Enum8)		Buffer monitor modeSELECTION:
0 - None
2 - Unicast
3 - Multicast
DEFAULT: None
bufferMonitorStateplatform:bufferMonitorSt
(scalar:Enum8)		Buffer monitor stateSELECTION:
0 - Disable
1 - Enable
DEFAULT: Enable
bufferMonitorThreshholdplatform:bufferMonitorThreshhold
(scalar:Uint32)		Buffer monitor threshold
RANGE: [0 , 6144]
DEFAULT: 0
samplingplatform:bufferMonitorSampling
(scalar:Uint32)		Buffer Monitor Sampling
RANGE: [0 , 20000000]
DEFAULT: 4000000


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 Maximum Limit of LPM (Non-Host) Entries

Configuring the Maximum Limit of LPM (Non-Host) Entries

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "attributes": {
            "ipv6LpmMaxEntries": "1"
}}}]}}

{
    imdata:[]
}

<System>
  <pltfm-items>
    <ipv6LpmMaxEntries>1</ipv6LpmMaxEntries>
  </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 profile ipv6 lpm-entries maximum 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
topSystem sys


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
ipv6LpmMaxEntriesplatform:IPv6LpmRange
(scalar:Uint32)		Maximum limit for IPv6 LPM routes
RANGE: [0 , 6144]


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 the Maximum Limit of LPM (Non-Host) Entries

Deleting the Maximum Limit of LPM (Non-Host) Entries

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "platformEntity": {
          "attributes": {
            "ipv6LpmMaxEntries": "1024"
}}}]}}

{
    imdata:[]
}

<System>
  <pltfm-items>
    <ipv6LpmMaxEntries>1024</ipv6LpmMaxEntries>
  </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 profile ipv6 lpm-entries maximum 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
topSystem sys


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
ipv6LpmMaxEntriesplatform:IPv6LpmRange
(scalar:Uint32)		Maximum limit for IPv6 LPM routes
RANGE: [0 , 6144]


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