Configuring Priority Flow Control on an Ethernet Interface
Configuring Priority Flow Control in Auto Mode
Configuring Priority Flow Control in Auto Mode
POST http://<mgmt0_IP>/api/mo/sys/intf.json
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
},
"children": [
{
"ipqosPriorFlowCtrl": {
"attributes": {
"mode": "auto",
"send_tlv": "no"
}}}]}}]}}
{
imdata:[]
}
<System>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/2</id>
<priorflowctrl-items>
<mode>0</mode>
<send_tlv>false</send_tlv>
</priorflowctrl-items>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
Note: This example was added in Release 9.3(5).
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.
interface eth1/2
priority-flow-control mode auto
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.
| MO | DN |
|---|---|
| interfaceEntity | sys/intf |
| l1PhysIf | sys/intf/phys-[eth1/2] |
| ipqosPriorFlowCtrl | sys/intf/phys-[eth1/2]/priorflowctrl |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 Name | Data Type | Description | Values |
|---|---|---|---|
| id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
ipqosPriorFlowCtrl Properties
The following table contains information about the ipqosPriorFlowCtrl 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 Name | Data Type | Description | Values |
|---|---|---|---|
| mode | ipqos:PriorFlowCtrlMode (scalar:UByte) | priority-flow-control mode on/off/auto | SELECTION: 0 - auto 1 - on 2 - off DEFAULT: 0 |
| send_tlv | scalar:Bool | send\_tlv used for sending dcbx pfc tlv when pfc mode is on | SELECTION: true or false DEFAULT: false |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Forcing Priority Flow Control Off
Forcing Priority Flow Control Off
POST http://<mgmt0_IP>/api/mo/sys/intf.json
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
},
"children": [
{
"ipqosPriorFlowCtrl": {
"attributes": {
"mode": "off",
"send_tlv": "no"
}}}]}}]}}
{
imdata:[]
}
<System>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/2</id>
<priorflowctrl-items>
<mode>2</mode>
<send_tlv>false</send_tlv>
</priorflowctrl-items>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
Note: This example was added in Release 9.3(5).
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.
interface eth1/2
priority-flow-control mode off
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.
| MO | DN |
|---|---|
| interfaceEntity | sys/intf |
| l1PhysIf | sys/intf/phys-[eth1/2] |
| ipqosPriorFlowCtrl | sys/intf/phys-[eth1/2]/priorflowctrl |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 Name | Data Type | Description | Values |
|---|---|---|---|
| id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
ipqosPriorFlowCtrl Properties
The following table contains information about the ipqosPriorFlowCtrl 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 Name | Data Type | Description | Values |
|---|---|---|---|
| mode | ipqos:PriorFlowCtrlMode (scalar:UByte) | priority-flow-control mode on/off/auto | SELECTION: 0 - auto 1 - on 2 - off DEFAULT: 0 |
| send_tlv | scalar:Bool | send\_tlv used for sending dcbx pfc tlv when pfc mode is on | SELECTION: true or false DEFAULT: false |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring DCBX TLV for PFC
Configuring DCBX TLV for PFC
POST http://<mgmt0_IP>/api/mo/sys/intf.json
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
},
"children": [
{
"ipqosPriorFlowCtrl": {
"attributes": {
"mode": "on",
"send_tlv": "yes"
}}}]}}]}}
{
imdata:[]
}
<System>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/2</id>
<priorflowctrl-items>
<mode>1</mode>
<send_tlv>true</send_tlv>
</priorflowctrl-items>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
Note: This example was added in Release 9.3(5).
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.
interface eth1/2
priority-flow-control mode on send-tlv
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.
| MO | DN |
|---|---|
| interfaceEntity | sys/intf |
| l1PhysIf | sys/intf/phys-[eth1/2] |
| ipqosPriorFlowCtrl | sys/intf/phys-[eth1/2]/priorflowctrl |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 Name | Data Type | Description | Values |
|---|---|---|---|
| id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
ipqosPriorFlowCtrl Properties
The following table contains information about the ipqosPriorFlowCtrl 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 Name | Data Type | Description | Values |
|---|---|---|---|
| mode | ipqos:PriorFlowCtrlMode (scalar:UByte) | priority-flow-control mode on/off/auto | SELECTION: 0 - auto 1 - on 2 - off DEFAULT: 0 |
| send_tlv | scalar:Bool | send\_tlv used for sending dcbx pfc tlv when pfc mode is on | SELECTION: true or false DEFAULT: false |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring PFC Watch-Dog Interval to On
Configuring PFC Watch-Dog Interval to On
POST http://<mgmt0_IP>/api/mo/sys/intf.json
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
},
"children": [
{
"ipqosPriorFlowCtrlWd": {
"attributes": {
"disableAction": "no",
"interfaceMutiplier": "11",
"watchDogInterval": "on"
}}}]}}]}}
{
imdata:[]
}
<System>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/2</id>
<priorflowctrlwd-items>
<disableAction>false</disableAction>
<interfaceMutiplier>11</interfaceMutiplier>
<watchDogInterval>1</watchDogInterval>
</priorflowctrlwd-items>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
Note: This example was added in Release 9.3(5).
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.
interface eth1/2
priority-flow-control watch-dog-interval on
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.
| MO | DN |
|---|---|
| interfaceEntity | sys/intf |
| l1PhysIf | sys/intf/phys-[eth1/2] |
| ipqosPriorFlowCtrlWd | sys/intf/phys-[eth1/2]/priorflowctrlwd |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 Name | Data Type | Description | Values |
|---|---|---|---|
| id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
ipqosPriorFlowCtrlWd Properties
The following table contains information about the ipqosPriorFlowCtrlWd 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 Name | Data Type | Description | Values |
|---|---|---|---|
| disableAction | scalar:Bool | only generate syslog for stuck queue, no action | SELECTION: true or false DEFAULT: false |
| interfaceMutiplier | ipqos:PriorFlowCtrlWdIntfMulti (scalar:UByte) | shutdown mutlipler value | RANGE: [1 , 11] DEFAULT: 11 |
| watchDogInterval | ipqos:PriorFlowCtrlWdIntvl (scalar:UByte) | watch dog internal on/off | SELECTION: 1 - on 2 - off (Default) |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring PFC Watch-Dog Interval to Off
Configuring PFC Watch-Dog Interval to Off
POST http://<mgmt0_IP>/api/mo/sys/intf.json
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
},
"children": [
{
"ipqosPriorFlowCtrlWd": {
"attributes": {
"disableAction": "no",
"interfaceMutiplier": "11",
"watchDogInterval": "off"
}}}]}}]}}
{
imdata:[]
}
<System>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/2</id>
<priorflowctrlwd-items>
<disableAction>false</disableAction>
<interfaceMutiplier>11</interfaceMutiplier>
<watchDogInterval>2</watchDogInterval>
</priorflowctrlwd-items>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
Note: This example was added in Release 9.3(5).
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.
interface eth1/2
priority-flow-control watch-dog-interval off
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.
| MO | DN |
|---|---|
| interfaceEntity | sys/intf |
| l1PhysIf | sys/intf/phys-[eth1/2] |
| ipqosPriorFlowCtrlWd | sys/intf/phys-[eth1/2]/priorflowctrlwd |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 Name | Data Type | Description | Values |
|---|---|---|---|
| id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
ipqosPriorFlowCtrlWd Properties
The following table contains information about the ipqosPriorFlowCtrlWd 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 Name | Data Type | Description | Values |
|---|---|---|---|
| disableAction | scalar:Bool | only generate syslog for stuck queue, no action | SELECTION: true or false DEFAULT: false |
| interfaceMutiplier | ipqos:PriorFlowCtrlWdIntfMulti (scalar:UByte) | shutdown mutlipler value | RANGE: [1 , 11] DEFAULT: 11 |
| watchDogInterval | ipqos:PriorFlowCtrlWdIntvl (scalar:UByte) | watch dog internal on/off | SELECTION: 1 - on 2 - off (Default) |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting PFC Watch-Dog Interval
Deleting PFC Watch-Dog Interval
POST http://<mgmt0_IP>/api/mo/sys/intf.json
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
},
"children": [
{
"ipqosPriorFlowCtrlWd": {
"attributes": {
"status": "deleted"
}}}]}}]}}
{
imdata:[]
}
<System>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/2</id>
<priorflowctrlwd-items nc:operation="delete">
</priorflowctrlwd-items>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
Note: This example was added in Release 9.3(5).
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.
interface eth1/2
no priority-flow-control watch-dog-interval on
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.
| MO | DN |
|---|---|
| interfaceEntity | sys/intf |
| l1PhysIf | sys/intf/phys-[eth1/2] |
| ipqosPriorFlowCtrlWd | sys/intf/phys-[eth1/2]/priorflowctrlwd |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 Name | Data Type | Description | Values |
|---|---|---|---|
| id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
ipqosPriorFlowCtrlWd Properties
The following table contains information about the ipqosPriorFlowCtrlWd 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 Name | Data Type | Description | Values |
|---|---|---|---|
| status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring Priorty Flow Control, Disable Action, and Shutdown Multiplier
Configuring Priorty Flow Control, Disable Action, and Shutdown Multiplier
POST http://<mgmt0_IP>/api/mo/sys/intf.json
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
},
"children": [
{
"ipqosPriorFlowCtrlWd": {
"attributes": {
"disableAction": "yes",
"interfaceMutiplier": "7",
"watchDogInterval": "on"
}}}]}}]}}
{
imdata:[]
}
<System>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/2</id>
<priorflowctrlwd-items>
<disableAction>true</disableAction>
<interfaceMutiplier>7</interfaceMutiplier>
<watchDogInterval>1</watchDogInterval>
</priorflowctrlwd-items>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
Note: This example was added in Release 9.3(5).
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.
interface eth1/2
priority-flow-control watch-dog-interval on disable-action interface-multiplier 7
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.
| MO | DN |
|---|---|
| interfaceEntity | sys/intf |
| l1PhysIf | sys/intf/phys-[eth1/2] |
| ipqosPriorFlowCtrlWd | sys/intf/phys-[eth1/2]/priorflowctrlwd |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 Name | Data Type | Description | Values |
|---|---|---|---|
| id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
ipqosPriorFlowCtrlWd Properties
The following table contains information about the ipqosPriorFlowCtrlWd 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 Name | Data Type | Description | Values |
|---|---|---|---|
| disableAction | scalar:Bool | only generate syslog for stuck queue, no action | SELECTION: true or false DEFAULT: false |
| interfaceMutiplier | ipqos:PriorFlowCtrlWdIntfMulti (scalar:UByte) | shutdown mutlipler value | RANGE: [1 , 11] DEFAULT: 11 |
| watchDogInterval | ipqos:PriorFlowCtrlWdIntvl (scalar:UByte) | watch dog internal on/off | SELECTION: 1 - on 2 - off (Default) |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting Priorty Flow Control, Disable Action, and Shutdown Multiplier
Deleting Priorty Flow Control, Disable Action, and Shutdown Multiplier
POST http://<mgmt0_IP>/api/mo/sys/intf.json
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
},
"children": [
{
"ipqosPriorFlowCtrlWd": {
"attributes": {
"status": "deleted"
}}}]}}]}}
{
imdata:[]
}
<System>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/2</id>
<priorflowctrlwd-items nc:operation="delete">
</priorflowctrlwd-items>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
Note: This example was added in Release 9.3(5).
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.
interface eth1/2
no priority-flow-control watch-dog-interval on disable-action interface-multiplier 7
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.
| MO | DN |
|---|---|
| interfaceEntity | sys/intf |
| l1PhysIf | sys/intf/phys-[eth1/2] |
| ipqosPriorFlowCtrlWd | sys/intf/phys-[eth1/2]/priorflowctrlwd |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 Name | Data Type | Description | Values |
|---|---|---|---|
| id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
ipqosPriorFlowCtrlWd Properties
The following table contains information about the ipqosPriorFlowCtrlWd 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 Name | Data Type | Description | Values |
|---|---|---|---|
| status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Disabling Statistics for a Policy
Disabling Statistics for a Policy
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ipqosEntity": {
"children": [
{
"ipqosDefaultQoS": {
"children": [
{
"ipqosServPol": {
"children": [
{
"ipqosEgress": {
"children": [
{
"ipqosIf": {
"attributes": {
"name": "eth1/2"
},
"children": [
{
"ipqosInst": {
"attributes": {
"name": "pmap_name",
"stats": "false"
}
}
}
]
}
}
]
}
}
]
}
}
]
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ipqos-items>
<dflt-items>
<policy-items>
<out-items>
<intf-items>
<If-list>
<name>eth1/2</name>
<pmap-items>
<name>pmap_name</name>
<stats>false</stats>
</pmap-items>
</If-list>
</intf-items>
</out-items>
</policy-items>
</dflt-items>
</ipqos-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/2</id>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
Note: This example was added in Release 9.3(5).
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.
interface eth1/2
service-policy type qos output pmap_name no-stats
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.
| MO | DN |
|---|---|
| topSystem | sys |
| ipqosEntity | sys/ipqos |
| ipqosDefaultQoS | sys/ipqos/dflt |
| ipqosServPol | sys/ipqos/dflt/policy |
| ipqosEgress | sys/ipqos/dflt/policy/out |
| ipqosIf | sys/ipqos/dflt/policy/out/intf-[eth1/2] |
| ipqosInst | sys/ipqos/dflt/policy/out/intf-[eth1/2]/pmap |
| interfaceEntity | sys/intf |
| l1PhysIf | sys/intf/phys-[eth1/2] |
ipqosIf Properties
The following table contains information about the ipqosIf 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 Name | Data Type | Description | Values |
|---|---|---|---|
| name | nw:IfId (base:IfIndex) | Interface name in a short form. eth1/1 or pc1 | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
ipqosInst Properties
The following table contains information about the ipqosInst 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 Name | Data Type | Description | Values |
|---|---|---|---|
| name | ipqos:PMapName (string:Basic) | Policy-map Name | MAX SIZE: 39 |
| stats | scalar:Bool | turn on/off statistics | SELECTION: true or false DEFAULT: true |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 Name | Data Type | Description | Values |
|---|---|---|---|
| id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Enabling Statistics
Enabling Statistics
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ipqosEntity": {
"children": [
{
"ipqosDefaultQoS": {
"children": [
{
"ipqosServPol": {
"children": [
{
"ipqosEgress": {
"children": [
{
"ipqosIf": {
"attributes": {
"name": "eth1/2"
},
"children": [
{
"ipqosInst": {
"attributes": {
"name": "pmap_name",
"stats": "true"
}
}
}
]
}
}
]
}
}
]
}
}
]
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ipqos-items>
<dflt-items>
<policy-items>
<out-items>
<intf-items>
<If-list>
<name>eth1/2</name>
<pmap-items>
<name>pmap_name</name>
<stats>true</stats>
</pmap-items>
</If-list>
</intf-items>
</out-items>
</policy-items>
</dflt-items>
</ipqos-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/2</id>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
Note: This example was added in Release 9.3(5).
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.
interface eth1/2
no service-policy type qos output pmap_name
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.
| MO | DN |
|---|---|
| topSystem | sys |
| interfaceEntity | sys/intf |
| l1PhysIf | sys/intf/phys-[eth1/2] |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 Name | Data Type | Description | Values |
|---|---|---|---|
| id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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: