The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the Cisco NX-OS quality of service (QoS) commands that begin with C.
To specify a control plane class map for a control plane policy map, use the class command. To delete a control plane class map from a control plane policy map, use the no form of this command.
Name of the class map. The name is alphanumeric, case sensitive, and has a maximum of 64 characters. |
Control plane policy map configuration
|
|
---|---|
You must create the control plane class maps before you reference them in this command.
This example shows how to configure a class map for a control plane policy map:
To add a reference to an existing qos class map in a policy map and enter the class mode, use the class command. To remove a class from the policy map, use the no form of this command.
class [ type qos ] class-map-name
Policy map type qos configuration
|
|
---|---|
Policy actions in the first class that matches the traffic type are performed.
By default, the class-default class of type qos is created under every policy map of type qos in the system and it is mapped to the QoS group 0. You cannot change this mapping.
You cannot remove the class-default of type qos. If you attempt to delete the class-default class, the switch returns an error message.
This example shows how to add a reference to a qos class map at the end of a policy map:
switch(
config)#
policy-map my_policy1
This example shows how to remove a class map reference in a policy map:
switch(
config)#
policy-map my_policy1
|
|
---|---|
To add a reference to the system default class that does not match any traffic class, use the class class-default command.
QoS policy map configuration mode
Control-plane policy map configuration mode
QoS policy map in switch profile configuration mode
|
|
---|---|
Traffic that fails to match any class is assigned to a default class of traffic called class-default. You cannot delete this class.
This example shows how to add a reference to the system default class at the end of a policy map in a switch profile:
|
|
---|---|
Displays information about the switch profile and the configuration revision. |
|
To add a reference to an existing network QoS class map in a policy map and enter the class mode, use the class type network-qos command. To remove a class from the policy map, use the no form of this command.
class type network-qos class-map-name
no class type network-qos class-map-name
Reference to a network QoS class map. The class map name can be a maximum of 40 characters. The name is case sensitive and can only contain alphabetic characters, numbers, hyphens, and underscores. |
Policy map type network-qos configuration
|
|
---|---|
Policy actions in the first class that matches the traffic type are performed.
This example shows how to add a reference to a class map in a type network-qos policy map:
This example shows how to remove a class map reference in a type network-qos policy map:
|
|
---|---|
Enables Class-based Flow Control (CBFC) pause characteristics on a traffic class. |
|
To add a reference to an existing queuing class map in a policy map and enter the class mode, use the class type queuing command. To remove a class from the policy map, use the no form of this command.
class type queuing class-map-name
no class type queuing class-map-name
Reference to a queuing class map. The class map name can be a maximum of 40 characters. The name is case sensitive and can only contain alphabetic characters, numbers, hyphens, and underscores. |
Policy map type queuing configuration
|
|
---|---|
Policy actions in the first class that matches the traffic type are performed.
This example shows how to add a reference to a class map in a type queuing policy map:
switch(
config)#
policy-map type queuing my_policy1
This example shows how to remove a class map reference in a type queuing policy map:
switch(
config)#
policy-map type queuing my_policy1
|
|
---|---|
To create or modify a class map and enter the class-map configuration mode, use the class-map command. To remove a class map, use the no form of this command.
class-map [ type qos ] [ match-all | match-any ] class-map-name
no class-map [ type qos ] [ match-all | match-any ] class-map-name
|
|
---|---|
You can define a class map for each class of traffic to be used in QoS policies.
If the packet matches any of the criteria configured for this class map with the match command, then this class map is applied to the packet. If no execution strategy is specified (match-any or match-all), then the default value of match-any is applied to the traffic class.
This example shows how to create or modify a qos class map:
switch(
config)#
class-map my_class1
This example shows how to create a qos class map to match all traffic packets:
switch(
config)#
class-map type qos match-all my_class2
This example shows how to remove a qos class map:
switch(
config)#
no class-map my_class1
This example shows the error message that appears when you attempt to remove a class-fcoe class map:
|
|
---|---|
To create or specify a control plane class map and enter class map configuration mode, use the class-map type control-plane command. To delete a control plane class map, use the no form of this command.
class-map type control-plane [ match-any ] class-map-name
no class-map type control-plane [ match-any ] class-map-name
(Optional) Specifies to match any match conditions in the class map. |
|
Name of the class map. The name is alphanumeric and case-sensitive. The maximum length is 64 characters. |
|
|
---|---|
You cannot use match-any or class-default as names for control plane class maps.
You can delete only dynamic class-maps of type control-plane. You cannot delete static class-maps of type control-plane.
This example shows how to specify a control plane class map and enter class map configuration mode:
This example shows how to delete a control plane class map:
|
|
---|---|
Matches traffic with a specified access control list (ACL) group. |
|
Displays control plane policy map configuration information. |
To create or modify a class map that defines a network QoS class of traffic and enter the class-map configuration mode, use the class-map type network-qos command. To remove a class map, use the no form of this command.
class-map type network-qos class_map_name
no class-map type network-qos class_map_name
|
|
---|---|
Class maps of type network qos support only the match qos-group command. If a traffic packet matches any of the criteria configured for this class map with the match command, then this class map is applied to the packet. By default, traffic is filtered using the implicit match-any option.
This example shows how to create or modify a network qos class map named my_class1:
switch(
config)#
class-map type network-qos my_class1
This example shows how to remove a network qos class map:
switch(
config)#
no class-map my_class1
|
|
---|---|
To create or modify a class map that defines a queuing class of traffic and enter the class-map configuration mode, use the class-map type queuing command. To remove the queuing class map, use the no form of this command.
class-map type queuing class_map_name
no class-map type queuing class_map_name
|
|
---|---|
If you modify the queuing type class maps, the configuration for all ports of the specified port type also changes.
You cannot delete the system-defined queuing class map names.
Class maps of type queuing support only the match qos-group command. If a traffic packet matches any of the criteria configured for this class map with the match command, then this class map is applied to the packet. By default, traffic is filtered using the implicit match-any option.
This example shows how to create or modify a queuing class map:
switch(
config)#
class-map type queuing my_class1
This example shows how to modify a system-defined queuing class map named class-default:
switch(
config)#
class-map type queuing match-any class-default
This example shows how to remove a queuing class map:
switch(
config)#
no class-map type queuing my_class1
|
|
---|---|
Configures a traffic class that matches the QoS group values. |
|
To clear the micro-burst counters, use the clear burst counters command.
clear burst-counters [interface {all | ethernet interface }] {both | egrees | ingress }
|
|
---|---|
When the burst threshold command is used to enable micro-burst detection on a port, any activity that occurs on the port and that meets the specified criteria, is identified as a micro-burst and the appropriate burst counters are incremented. To clear the burst counters, you use the clear burst counters command.
This example shows how to clear all burst counters for an ethernet interface:
|
|
---|---|
Configures the maximum number of bursts allowed within a time interval before generating an interrupt. |
|
To clear Control Plane Policing (CoPP) statistics, use the clear copp statistics command.
|
|
---|---|
This example shows how to clear the CoPP statistics:
|
|
---|---|
To clear switch latency monitoring statistics for egress and ingress port pairs, use the clear hardware profile latency monitor command.
clear hardware profile latency monitor {all | interface ethernet egress-interface-slot/port interface ethernet ingress-interface-slot/port }
|
|
---|---|
This command does not require a license.
If you reload the card or a module is powered on, you must use the clear hardware profile latency monitor all command to clear the switch latency monitoring statistics.
The following example shows how to clear all switch latency monitoring statistics:
The following example shows how to clear switch latency monitoring configuration and statistics information for the specified egress and ingress port pairs:
|
|
---|---|
Specifies the histogram base value to construct switch latency monitoring histograms. |
|
Displays switch latency statistics for egress and ingress port pairs. |
To clear QoS packet drop history, use the clear hardware internal bigsur port interface qos-drop-history command in EXEC mode.
clear hardware internal bigsur port ethernet [slot/port] qos-drop-history {all | multicast | unicast}
Specifies Ethernet interface with its slot number and port number |
|
|
|
---|---|
This example shows how to clear all QoS packet drop for QoS-drop-history for port ethernet 1/1:
This example shows how to clear multicast QoS packet drop for QoS-drop-history for port ethernet 1/1:
This example shows how to clear unicast QoS packet drop for QoS-drop-history for port ethernet 1/1:
|
|
---|---|
show hardware internal bigsur port interface qos-drop-history detail. |
To display the number of Ingress packet Drops for qos-drop history of type ‘detail’. |
To clear QoS packet drop history for all-ports, use the clear hardware internal bigsur all-ports qos-drop-history command in EXEC mode.
clear hardware internal bigsur all-ports qos-drop-history {all | multicast | unicast}
|
|
---|---|
This example shows how to clear all QoS packet drop for QoS-drop-history for all ports:
This example shows how to clear multicast QoS packet drop for QoS-drop-history for all ports:
This example shows how to clear unicast QoS packet drop for QoS-drop-history for all ports:
|
|
---|---|
show hardware internal bigsur port interface qos-drop-history detail. |
To display the number of Ingress packet Drops for qos-drop history of type ‘detail’. |
To enter control-plane configuration mode, which allows users to associate attributes that are associated with the control plane of the device, use the control-plane command.
|
|
---|---|
After you use the control-plane command, you can associate a service policy to police all traffic that is destined to the control plane.
This example shows how to enter the control plane configuration mode:
|
|
---|---|
Attaches a policy map to a control plane for aggregate control plane services. |
|
Displays the configuration of a class or all classes for the policy map of a control plane. |