Configuring QoS Class Maps
The following examples pertain specifically to QoS class maps.
Configuring or Modifying a Class Map
You can create or modify a class map then reference class maps in policy maps.
Note: You cannot create a queuing class map; you must use one of the system-defined queuing class maps.
CLI Command
The CLI command below is the equivalent to the payload example 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 or the YANG tab to view the XML payload.
class-map type qos class1
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.
MO | DN |
ipqosCMapEntity |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c |
ipqosCMapInst |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name} |
ipqosCMapInst Properties
The following table contains information about the ipqosCMapInst 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 |
matchType | ipqos:QoSMatchType (scalar:Enum8) | Match-any, match-all or match-first | SELECTION: 0 - match-any 1 - match-all 2 - match-first DEFAULT: match-all |
name | ipqos:CMapName (string:Basic) | Name of class-map | MAX SIZE: 39 |
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
Applying Descriptions to MQC Objects
You can use the description command to add a description to a MQC object. The description can be up to 200 alphanumeric characters.
Note: You cannot modify the description of system-defined queuing class maps.
CLI Commands
The CLI commands and options listed below are the 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 or the YANG tab to view the XML payload.
The CLI commands and options 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 or the YANG tab to view the XML payload.
class-map type qos class1
description This is a description of the class-map
policy-map pol1
description This is a description of the policy-map
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.
MO | DN |
ipqosEntity |
sys/bd/vlanconfig-{[accEncap]}/ipqos |
ipqosDefaultQoS |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt |
ipqosCMapEntity |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c |
ipqosCMapInst |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name} |
ipqosDescription |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name}/Description |
ipqosPMapEntity |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/p |
ipqosPMapInst |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/p/name-{name} |
ipqosCMapInst Properties
The following table contains information about the ipqosCMapInst 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 |
matchType | ipqos:QoSMatchType (scalar:Enum8) | Match-any, match-all or match-first | SELECTION: 0 - match-any 1 - match-all 2 - match-first DEFAULT: match-all |
name | ipqos:CMapName (string:Basic) | Name of class-map | MAX SIZE: 39 |
ipqosDescription Properties
The following table contains information about the ipqosDescription 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 |
val | ipqos:DescStr (string:Basic) | Description string | MAX SIZE: 200 |
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 Name | Data Type | Description | Values |
matchType | ipqos:QoSMatchType (scalar:Enum8) | Match-any, match-all or match-first | SELECTION: 0 - match-any 1 - match-all 2 - match-first DEFAULT: match-all |
name | ipqos:PMapName (string:Basic) | Name of policy-map | MAX SIZE: 39 |
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 a Policy Class
This example creates a named object that represents a set of policies that are to be applied to a set of traffic classes and associates a class map with the policy map and enters the configuration mode for the specified system class.
Note: The associated class map must be the same type as the policy map type.
CLI Commands
The CLI commands and options 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 or the YANG tab to view the XML payload.
policy-map type qos p1
class type qos class2
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.
MO | DN |
ipqosPMapInst |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/p/name-{name} |
ipqosMatchCMap |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/p/name-{name}/cmap-{name} |
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 Name | Data Type | Description | Values |
matchType | ipqos:QoSMatchType (scalar:Enum8) | Match-any, match-all or match-first | SELECTION: 0 - match-any 1 - match-all 2 - match-first DEFAULT: match-all |
name | ipqos: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 Name | Data Type | Description | Values |
name | ipqos:CMapName (string:Basic) | Match using class-map | MAX SIZE: 39 |
userSetBit | scalar:Uint64 | NO COMMENTS | SELECTION:
0ull - defaultValue defaultValue: 0ull |
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 ACL Classification
You can classify traffic by matching packets based on existing ACLs. The permit and deny ACL keywords are ignored in the matching. QoS does not use the permit-deny functions of ACLs. You can classify by either IPv4, IPv6, or MAC address.
CLI Commands
The CLI commands and options 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 or the YANG tab to view the XML payload.
class-map type qos class1
match access-group foo
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.
MO | DN |
ipqosCMapInst |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name} |
ipqosAcl |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name}/acl-{name} |
ipqosCMapInst Properties
The following table contains information about the ipqosCMapInst 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 |
matchType | ipqos:QoSMatchType (scalar:Enum8) | Match-any, match-all or match-first | SELECTION: 0 - match-any 1 - match-all 2 - match-first DEFAULT: match-all |
name | ipqos:CMapName (string:Basic) | Name of class-map | MAX SIZE: 39 |
ipqosAcl Properties
The following table contains information about the ipqosAcl 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 | acl:Name (string:Basic) | Match using ACL | MAX SIZE: 63 |
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 CoS Classification
You can classify traffic based on the class of service (CoS) in the IEEE 802.1Q header. This 3-bit field is defined in IEEE 802.1p to support QoS traffic classes. CoS is encoded in the high order 3 bits of the VLAN ID Tag field and is referred to as user_priority.
CLI Commands
The CLI commands and options 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 or the YANG tab to view the XML payload.
class-map class_cos
match cos 4
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.
MO | DN |
ipqosCMapInst |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name} |
ipqosCos |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name}/cos-{val} |
ipqosCMapInst Properties
The following table contains information about the ipqosCMapInst 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 |
matchType | ipqos:QoSMatchType (scalar:Enum8) | Match-any, match-all or match-first | SELECTION: 0 - match-any 1 - match-all 2 - match-first DEFAULT: match-all |
name | ipqos:CMapName (string:Basic) | Name of class-map | MAX SIZE: 39 |
ipqosCos Properties
The following table contains information about the ipqosCos 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 |
val | ipqos:Cos (scalar:UByte) | Cos value | RANGE: [0 , 7] |
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 DSCP Classification
This example configures the traffic class by matching packets based on
dscp-values.
CLI Commands
The CLI commands and options 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 or the YANG tab to view the XML payload.
class-map class_cos
match dscp af21
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.
MO | DN |
ipqosDefaultQoS |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt |
ipqosCMapEntity |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c |
ipqosCMapInst |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name} |
ipqosDscp |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name}/dscp-{val} |
ipqosCMapInst Properties
The following table contains information about the ipqosCMapInst 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 |
matchType | ipqos:QoSMatchType (scalar:Enum8) | Match-any, match-all or match-first | SELECTION: 0 - match-any 1 - match-all 2 - match-first DEFAULT: match-all |
name | ipqos:CMapName (string:Basic) | Name of class-map | MAX SIZE: 39 |
ipqosDscp Properties
The following table contains information about the ipqosDscp 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 |
val | ipqos:Dscp (scalar:UByte) | Dscp value | RANGE: [0 , 63] 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 Vxlan Outer DSCP Classification
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.
class-map type qos cqos
match dscp tunnel af22
Note: The property information for this example was added in release 10.4(1)F.
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 |
sys/ipqos/dflt/c/name-[cqos]/dscptunnel |
sys/ipqos/dflt/c/name-[cqos]/dscptunnel |
ipqosDscpTunnel Properties Properties
The following table contains information about the ipqosDscpTunnel 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 | Values | Description |
Val | Scalar: af22 | Match Outer Dscp Value |
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 IP RTP Classification
The IP Real-time Transport Protocol (RTP) is a transport protocol for real-time applications that transmit data such as audio or video and is defined by RFC 3550. Although RTP does not use a common TCP or UDP port, you typically configure RTP to use ports 16384 to 32767. UDP communications uses an even-numbered port and the next higher odd-numbered port is used for RTP Control Protocol (RTCP) communications.
You can configure classification based on UDP port ranges, which are likely to target applications using RTP.
CLI Commands
The CLI commands and options 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 or the YANG tab to view the XML payload.
class-map class_cos
match IP rtp 3000
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.
MO | DN |
ipqosCMapInst |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name} |
ipqosIpRtp |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name}/ipRtp |
ipqosCMapInst Properties
The following table contains information about the ipqosCMapInst 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 |
matchType | ipqos:QoSMatchType (scalar:Enum8) | Match-any, match-all or match-first | SELECTION: 0 - match-any 1 - match-all 2 - match-first DEFAULT: match-all |
name | ipqos:CMapName (string:Basic) | Name of class-map | MAX SIZE: 39 |
ipqosIpRtp Properties
The following table contains information about the ipqosIpRtp 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 |
range | string:Basic
| range string values | A sequence of characters |
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
Matching an MPLS Experimental Label
The match mpls experimental topmost command classifies traffic on the basis of the EXP value in the topmost label header.
CLI Commands
These CLI commands and options are equivalent to the payload examples displayed in the pane on the right.
class-map class_c1
match mpls experimental topmost 3
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.
MO | DN |
ipqosCMapInst |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name} |
ipqosMPLSExperimental |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name}/mplsExperimental-{val} |
ipqosCMapInst Properties
The following table contains information about the ipqosCMapInst 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 |
matchType | ipqos:QoSMatchType (scalar:Enum8) | Match-any, match-all or match-first | SELECTION: 0 - match-any 1 - match-all 2 - match-first DEFAULT: match-all |
name | ipqos:CMapName (string:Basic) | Name of class-map | MAX SIZE: 39 |
ipqosMPLSExperimental Properties
The following table contains information about the ipqosMPLSExperimental 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 |
val | ipqos:MPLSExperimental (scalar:UByte) | MPLS experimental value | RANGE: [0 , 7] |
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 CoS Matches
This example removes a specified class of service value as a match criteria.
CLI Commands
The CLI commands and options 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 or the YANG tab to view the XML payload.
class-map class_c1
match not cos 4
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.
MO | DN |
ipqosCMapInst |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name} |
ipqosNotCos |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name}/cosNot-{val} |
ipqosCMapInst Properties
The following table contains information about the ipqosCMapInst 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 |
matchType | ipqos:QoSMatchType (scalar:Enum8) | Match-any, match-all or match-first | SELECTION: 0 - match-any 1 - match-all 2 - match-first DEFAULT: match-all |
name | ipqos:CMapName (string:Basic) | Name of class-map | MAX SIZE: 39 |
ipqosNotCos Properties
The following table contains information about the ipqosNotCos 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 |
val | ipqos:Cos (scalar:UByte) | Not cos value | RANGE: [0 , 7] |
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 Packet Length Matches
This example removes a specified Layer 3 packet length in bytes as a match criteria.
CLI Commands
The CLI commands and options 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 or the YANG tab to view the XML payload.
class-map class_c1
match not packet length 100
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.
MO | DN |
ipqosCMapInst |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name} |
ipqosNotPacketLength |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name}/packetLengthNot |
ipqosCMapInst Properties
The following table contains information about the ipqosCMapInst 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 |
matchType | ipqos:QoSMatchType (scalar:Enum8) | Match-any, match-all or match-first | SELECTION: 0 - match-any 1 - match-all 2 - match-first DEFAULT: match-all |
name | ipqos:CMapName (string:Basic) | Name of class-map | MAX SIZE: 39 |
ipqosNotPacketLength Properties
The following table contains information about the ipqosNotPacketLength 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 |
range | string:Basic
| range string values | A sequence of characters |
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 MPLS Experimental Label Matches
This example removes specified MPLS experimental label values as a match criteria.
CLI Commands
The CLI commands and options 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 or the YANG tab to view the XML payload.
class-map class_co1
match not mpls experimental topmost 3
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.
MO | DN |
ipqosCMapInst |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name} |
ipqosNotMPLSExperimental |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name}/mplsExperimentalNot-{val} |
ipqosCMapInst Properties
The following table contains information about the ipqosCMapInst 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 |
matchType | ipqos:QoSMatchType (scalar:Enum8) | Match-any, match-all or match-first | SELECTION: 0 - match-any 1 - match-all 2 - match-first DEFAULT: match-all |
name | ipqos:CMapName (string:Basic) | Name of class-map | MAX SIZE: 39 |
ipqosNotMPLSExperimental Properties
The following table contains information about the ipqosNotMPLSExperimental 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 |
val | ipqos:MPLSExperimental (scalar:UByte) | Not mpls experimental value | RANGE: [0 , 7] |
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 DSCP Matches
This example removes specified DSCP values as a match criteria.
CLI Commands
The CLI commands and options 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 or the YANG tab to view the XML payload.
class-map class_c1
match not dscp af21
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.
MO | DN |
ipqosCMapInst |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name} |
ipqosNotDscp |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name}/dscpNot-{val} |
ipqosCMapInst Properties
The following table contains information about the ipqosCMapInst 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 |
matchType | ipqos:QoSMatchType (scalar:Enum8) | Match-any, match-all or match-first | SELECTION: 0 - match-any 1 - match-all 2 - match-first DEFAULT: match-all |
name | ipqos:CMapName (string:Basic) | Name of class-map | MAX SIZE: 39 |
ipqosNotDscp Properties
The following table contains information about the ipqosNotDscp 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 |
val | ipqos:Dscp (scalar:UByte) | Not dscp value | RANGE: [0 , 63] 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 Precedence Matches
This example removes a specified precedence value as a match criteria.
CLI Commands
The CLI commands and options 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 or the YANG tab to view the XML payload.
class-map class_c1
match not precedence critical
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.
MO | DN |
ipqosCMapInst |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name} |
ipqosNotPrecedence |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name}/precedenceNot-{val} |
ipqosCMapInst Properties
The following table contains information about the ipqosCMapInst 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 |
matchType | ipqos:QoSMatchType (scalar:Enum8) | Match-any, match-all or match-first | SELECTION: 0 - match-any 1 - match-all 2 - match-first DEFAULT: match-all |
name | ipqos:CMapName (string:Basic) | Name of class-map | MAX SIZE: 39 |
ipqosNotPrecedence Properties
The following table contains information about the ipqosNotPrecedence 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 |
val | ipqos:Prec (scalar:Enum8) | Not precedence value | SELECTION: 0 - routine 1 - priority 2 - immediate 3 - flash 4 - flash-override 5 - critical 6 - internet 7 - network |
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 Protocol Matches
This example matches on protocols that do not match the specified protocol.
CLI Commands
The CLI commands and options 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 or the YANG tab to view the XML payload.
class-map class_c1
match not protocol arp
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.
MO | DN |
ipqosCMapInst |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name} |
ipqosNotProtocol |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name}/protocolNot-{val} |
ipqosCMapInst Properties
The following table contains information about the ipqosCMapInst 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 |
matchType | ipqos:QoSMatchType (scalar:Enum8) | Match-any, match-all or match-first | SELECTION: 0 - match-any 1 - match-all 2 - match-first DEFAULT: match-all |
name | ipqos:CMapName (string:Basic) | Name of class-map | MAX SIZE: 39 |
ipqosNotProtocol Properties
The following table contains information about the ipqosNotProtocol 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 |
val | ipqos:Protocol (scalar:Enum8) | Not protocol value | SELECTION: 0 - unspecified 1 - arp 2 - bridging 3 - cdp 7 - dhcp 8 - isis 14 - fcoe |
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 Layer 3 Packet Length Classification
This example configures the traffic class by matching packets based on various packet lengths (bytes). Values can range from 1 to 9198.
CLI Commands
The CLI commands and options 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 or the YANG tab to view the XML payload.
class-map class_c1
match packet length 100
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.
MO | DN |
ipqosCMapInst |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name} |
ipqosPacketLength |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name}/packetLength |
ipqosCMapInst Properties
The following table contains information about the ipqosCMapInst 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 |
matchType | ipqos:QoSMatchType (scalar:Enum8) | Match-any, match-all or match-first | SELECTION: 0 - match-any 1 - match-all 2 - match-first DEFAULT: match-all |
name | ipqos:CMapName (string:Basic) | Name of class-map | MAX SIZE: 39 |
ipqosPacketLength Properties
The following table contains information about the ipqosPacketLength 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 |
range | string:Basic
| range string values | A sequence of characters |
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 IP Precedence Marking
This example configures the traffic class by matching packets based on precedence-values.
CLI Commands
The CLI commands and options 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 or the YANG tab to view the XML payload.
class-map class_c1
match precedence critical
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.
MO | DN |
ipqosCMapInst |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name} |
ipqosPrecedence |
sys/bd/vlanconfig-{[accEncap]}/ipqos/dflt/c/name-{name}/precedence-{val} |
ipqosCMapInst Properties
The following table contains information about the ipqosCMapInst 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 |
matchType | ipqos:QoSMatchType (scalar:Enum8) | Match-any, match-all or match-first | SELECTION: 0 - match-any 1 - match-all 2 - match-first DEFAULT: match-all |
name | ipqos:CMapName (string:Basic) | Name of class-map | MAX SIZE: 39 |
ipqosPrecedence Properties
The following table contains information about the ipqosPrecedence 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 |
val | ipqos:Prec (scalar:Enum8) | Precedence value | SELECTION: 0 - routine 1 - priority 2 - immediate 3 - flash 4 - flash-override 5 - critical 6 - internet 7 - network |
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