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 P.
To enable Class Based Flow Control (CBFC) pause characteristics on a class referenced in a type network-qos policy map, use the pause command. To disable the CBFC pause characteristics on a class, use the no form of this command.
pause no-drop [ pfc-cos pfc-cos-list ]
no pause no-drop [ pfc-cos pfc-cos-list ]
Policy map type network-qos class configuration
|
|
---|---|
Ethernet interfaces use priority flow control (PFC) to provide lossless service to no-drop system classes. PFC implements pause frames on a per-class basis and uses the IEEE 802.1p CoS value to identify the classes that require lossless service.
You can configure PFC CoS only for traffic classes that match a criteria other than the CoS value (match cos).
This example shows how to enable pause no-drop on a class referenced in a type network-qos policy map:
|
|
---|---|
To enable Class Based Flow Control (CBFC) pause characteristics on a class referenced in a type network-qos policy map and configure the ingress buffer size for the no-drop class, use the pause no drop buffer-size command. To disable the CBFC pause characteristics on a class and reset the buffer, use the no form of this command.
pause no-drop buffer-size buffer-size pause-threshold xoff-size resume-threshold xon-size
no pause no-drop buffer-size buffer-size pause-threshold xoff-size resume-threshold xon-size
Policy map type network-qos class configuration
|
|
---|---|
Use this command to configure the buffer size and threshold values for a no-drop class. You configure the buffer size to support lossless Ethernet over a link distance of 3000 meters (9843 feet). The switch software rejects the policy if enough buffer resources are not available to support the policy.
When you configure the buffer size, ensure the following:
The minimum difference between the pause threshold value and the resume threshold value must be 20480 bytes on a Cisco Nexus 5020 switch and 19840 bytes on a Cisco Nexus 5548 switch. Otherwise, you see the following message on a Cisco Nexus 5020 switch:
You see the following message on a Cisco Nexus 5548 switch:
This example shows how to enable pause no-drop on a class referenced in a type network-qos policy map:
This example shows how to set the no-drop buffer size for 3000 metres on a class referenced in a type network-qos policy map on a Cisco Nexus 5000 Series switch:
This example shows how to set the no-drop buffer size for 3000 metres on a class referenced in a type network-qos policy map on a Cisco Nexus 5548 switch:
|
|
---|---|
To configure traffic policing for a class map in a policy map, use the police command.
police [ cir ] { committed-rate [ data-rate ] | percent cir-link-percent } [ bc ] { committed-burst-rate }] [ conform { transmit } [ violate { drop }]]]
no police [ cir ] { committed-rate [ data-rate ] | percent cir-link-percent } [ bc ] { committed-burst-rate }] [ conform { transmit } [ violate { drop }]]]
Policy map class configuration (config-pmap-c-qos)
|
|
---|---|
You must create the class map before you reference it in this command.
This example shows how to set a committed information rate ( cir) to 80 mbps and bc as 20 mbytes.
This example shows how to set the committed information rate ( cir) as 10-percent of the interface rate and bc as 20 mbytes.
|
|
---|---|
To configure traffic policing for a class map in a control plane policy map, use the police command.
Average rate in packets per second (pps). The range is from 0 to 20480. |
|
Control plane policy map configuration mode
|
|
This example shows how to configure traffic policing in a control plane policy map with the average rate at 200 packets per second:
To enter the control plane policy map configuration mode, use the policy-map type control-plane command.
policy-map type control-plane policy-map-name
Name of the default control plane policy map. The name is alphanumeric, case sensitive, and has a maximum of 64 characters. |
|
|
In Cisco Nexus devices, you cannot create a user-defined Control Plane Policing (CoPP) policy map. The switch software includes a default control plane policy map, copp-system-policy-default, and one customized policy map, copp-system-policy-customized. You cannot add or remove classes from the default control-plane policy map. You can, however, add or remove classes to or from the copp-system-policy-customized control-plane policy map.
If you attempt to create a control plane policy with a name other than the default, you will see the following error message:
This example shows how to enter the control plane policy map configuration mode:
This example shows the error message that appears when you create a control plane policy map other than the default control plane policy map:
|
|
---|---|
Displays configuration information for control plane policy maps. |
To create or modify a policy map and enter the policy map type network-qos configuration mode, use the policy-map type network-qos command. To remove a policy map, use the no form of this command.
policy-map type network-qos policy-map-name
no policy-map type network-qos policy-map-name
Name assigned to a type network-qos policy map. The name can be a maximum of 40 alphanumeric characters. |
|
|
---|---|
Use the service-policy command to assign policy maps to interfaces.
On a Cisco Nexus 5548 switch, the switch software does not automatically attach the class-fcoe class map to a policy map. You can manually add the class-fcoe class to a policy map. On all other Cisco Nexus 5000 Series switches, this class is, by default, included in a policy map. On a Cisco Nexus 5548 switch, you can remove the class-fcoe class from a policy map.
You can configure the qos-group of a class-fcoe class map on a Cisco Nexus 5548 switch using the set qos-group command. The default qos-group value is 1.
This example shows how to create or modify a type network-qos policy map:
This example shows how to remove a type network-qos policy map:
|
|
---|---|
To create or modify a policy map and enter the policy map type qos configuration mode, use the policy-map command. To remove a QoS policy map, use the no form of this command.
policy-map [ type qos ] qos-policy-map-name
no policy-map [ type qos ] qos-policy-map-name
Name assigned to a type qos policy map. The name can be a maximum of 40 alphanumeric characters. |
The software enters the policy map type qos configuration mode if you enter the policy-map command without specifying a type.
|
|
Use the service-policy command to assign policy maps to interfaces.
On a Cisco Nexus 5548 switch, the switch software does not automatically attach the class-fcoe class map to a policy map. You can manually add the class-fcoe class to a policy map. On all other Cisco Nexus 5000 Series switches, this class is, by default, included in a policy map. On a Cisco Nexus 5548 switch, you can remove the class-fcoe class from a policy map.
You can configure the qos-group of a class-fcoe class map on a Cisco Nexus 5548 switch using the set qos-group command. The default qos-group value is 1.
This example shows how to create or modify a type qos policy map:
switch(
config)#
policy-map my_policy1
This example shows how to remove a type qos policy map:
switch(
config)#
no policy-map my_policy1
|
|
---|---|
To create or modify a policy map and enter the policy map type queuing configuration mode, use the policy-map type queuing command. To remove a policy map, use the no form of this command.
policy-map type queuing queuing-policy-map-name
no policy-map type queuing queuing-policy-map-name
Name assigned to a type queuing policy map. The name can be a maximum of 40 alphanumeric characters. |
|
|
Use the service-policy command to assign policy maps to interfaces.
On a Cisco Nexus 5548 switch, the switch software does not automatically attach the class-fcoe class map to a policy map. You can manually add the class-fcoe class to a policy map. On all other Cisco Nexus 5000 Series switches, this class is, by default, included in a policy map. On a Cisco Nexus 5548 switch, you can remove the class-fcoe class from a policy map.
You can configure the following on a class-fcoe class map:
The bandwidth value must be greater than zero (0).
Note On a Cisco Nexus 5548 switch, the default qos-group value is 1.
This example shows how to create or modify a queuing policy map:
switch(
config)#
policy-map type queuing my_policy1
This example shows how to remove a type queuing policy map:
switch(
config)#
no policy-map type queuing my_policy1
|
|
---|---|
To assign a priority to a traffic class in a policy map, use the priority command. To remove the mapping, use the no form of this command.
Policy map type queuing class configuration
|
|
---|---|
When you configure a strict priority queue for a traffic class in a policy map, the priority class receives preference over other class queues. This queue is serviced before all other queues except queue zero (which carries control traffic, not data traffic).
This example shows how to map the traffic class to a strict priority queue:
|
|
---|---|
To set the priority-flow-control (PFC) mode for the selected interface, use the priority-flow-control command.
priority-flow-control mode { auto | on | off }
no priority-flow-control mode { auto | on | off }
|
|
You can use this command on the following interfaces:
Note Use the no switchport command to configure an interface as a Layer 3 interface.
This example shows how to force-enable PFC on an interface:
switch#
configure terminal
switch(config)#
interface ethernet 1/2
switch(config-if)#
priority-flow-control mode on
switch(config-if)#
This example shows how to force-disable PFC on an interface:
|
|
---|---|
Displays the detailed listing of the flow control settings on all interfaces. |
|
Displays the priority flow control details for a specified interface. |