Configuring DSCP
You can configure a differentiated services code point (DSCP) for a neighbor. You can specify a DSCP value for locally originated packets for IPv4 or IPv6.
For more information, see the Cisco Nexus 9000 Series NX-OS System Management Configuration Guide.
Configuring DSCP to be Used for Locally Originated Packets for IPv4 and IPv6
Configuring DSCP to be Used for Locally Originated Packets for IPv4 and IPv6
POST http://<mgmt0_IP>/api/mo/sys/tcpudp.json
{
"tcpudpEntity": {
"children": [
{
"tcpudpInst": {
"attributes": {
"dscpLop": "40"
}}}]}}
{
imdata:[]
}
<System>
<tcpudp-items>
<inst-items>
<dscpLop>40</dscpLop>
</inst-items>
</tcpudp-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.
ip dscp-lop 40
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 |
---|---|
tcpudpEntity | sys/tcpudp |
tcpudpInst | sys/tcpudp/inst |
tcpudpInst Properties
The following table contains information about the tcpudpInst 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 |
---|---|---|---|
dscpLop | tcpudp:DscpLop (scalar:Uint16) | DSCP value for Locally Originated Packets | RANGE: [0 , 85] DEFAULT: unconfigured |
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 DSCP to be Used for Locally Originated Packets for IPv4 and IPv6
Deleting DSCP to be Used for Locally Originated Packets for IPv4 and IPv6
POST http://<mgmt0_IP>/api/mo/sys/tcpudp.json
{
"tcpudpEntity": {
"children": [
{
"tcpudpInst": {
"attributes": {
"dscpLop": "unconfigured"
}}}]}}
{
imdata:[]
}
<System>
<tcpudp-items>
<inst-items>
<dscpLop>85</dscpLop>
</inst-items>
</tcpudp-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 ip dscp-lop 40
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 |
---|---|
tcpudpEntity | sys/tcpudp |
tcpudpInst | sys/tcpudp/inst |
tcpudpInst Properties
The following table contains information about the tcpudpInst 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 |
---|---|---|---|
dscpLop | tcpudp:DscpLop (scalar:Uint16) | DSCP value for Locally Originated Packets | RANGE: [0 , 85] DEFAULT: unconfigured |
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 DSCP to be Used for Locally Originated Packets for IPv4 and IPv6 (Precedence 2)
Configuring DSCP to be Used for Locally Originated Packets for IPv4 and IPv6 (Precedence 2)
POST http://<mgmt0_IP>/api/mo/sys/tcpudp.json
{
"tcpudpEntity": {
"children": [
{
"tcpudpInst": {
"attributes": {
"dscpLop": "cs2"
}}}]}}
{
imdata:[]
}
<System>
<tcpudp-items>
<inst-items>
<dscpLop>77</dscpLop>
</inst-items>
</tcpudp-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.
ip dscp-lop cs2
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 |
---|---|
tcpudpEntity | sys/tcpudp |
tcpudpInst | sys/tcpudp/inst |
tcpudpInst Properties
The following table contains information about the tcpudpInst 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 |
---|---|---|---|
dscpLop | tcpudp:DscpLop (scalar:Uint16) | DSCP value for Locally Originated Packets | RANGE: [0 , 85] DEFAULT: unconfigured |
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 DSCP to be Used for Locally Originated Packets for IPv4 and IPv6 (Precedence 2)
Deleting DSCP to be Used for Locally Originated Packets for IPv4 and IPv6 (Precedence 2)
POST http://<mgmt0_IP>/api/mo/sys/tcpudp.json
{
"tcpudpEntity": {
"children": [
{
"tcpudpInst": {
"attributes": {
"dscpLop": "unconfigured"
}
}
}
]
}
}
{
imdata:[]
}
<System>
<tcpudp-items>
<inst-items>
<dscpLop>85</dscpLop>
</inst-items>
</tcpudp-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 ip dscp-lop cs2
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 |
---|---|
tcpudpEntity | sys/tcpudp |
tcpudpInst | sys/tcpudp/inst |
tcpudpInst Properties
The following table contains information about the tcpudpInst 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 |
---|---|---|---|
dscpLop | tcpudp:DscpLop (scalar:Uint16) | DSCP value for Locally Originated Packets | RANGE: [0 , 85] DEFAULT: unconfigured |
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: