New and Changed Information
Cisco APIC Release Version |
Feature |
Description |
What Changed |
---|---|---|---|
Release 4.0(1x) |
|
Support for new QoS levels and L3 out configuration |
QoS for L3Outs Custom QoS Multipod QoS |
Release 4.0(1x) |
|
Support for new QoS settings to enable RoCEv2 technology in Cisco APIC environment. |
QoS for RoCEv2 |
Release 3.1(2m) |
QoS for L3Outs |
In this release, QoS policy enforcement on L3Out ingress traffic is enhanced. |
QoS for L3Outs |
Release 2.2(1n) |
Translating QoS Ingress Markings to Egress Markings |
Added additional information |
Translating QoS CoS Using the REST API |
Release 2.1(1h) | Translating QoS Ingress Markings to Egress Markings | In this release, you can enable the ACI Fabric to classify the traffic for devices that classify the traffic based only on the CoS value. |
Translating QoS Ingress Markings to Egress Markings |
Release 2.0(2f) |
Multipod QoS |
Support for Preserving CoS and DSCP settings was added for multipod topologies. |
Multipod QoS |
QoS for L3Outs
QoS for L3Outs
To configure QoS policies for an L3Out, use the following guidelines:
-
To configure the QoS policy to be enforced on the border leaf where the L3Out is located, the VRF instance must be in egress mode (Policy Control Enforcement Direction must be "Egress").
-
To enable the QoS policy to be enforced, the VRF Policy Control Enforcement Preference must be "Enforced."
-
When configuring the contract governing communication between the L3Out and other EPGs, include the QoS class or target DSCP in the contract or subject.
Note
Only configure a QoS class or target DSCP in the contract, not in the external EPG (
l3extInstP
).
-
When creating a contract subject, you must choose a QoS priority level. You cannot choose Unspecified.
Note
With the exception of Custom QoS Policies as a custom QoS Policy will set the DSCP/CoS value even if the QoS Class is set to Unspecified. When QOS level is unspecified, it by default takes as Level 3 default queue. No unspecified is supported and valid.
-
Starting with release 4.0(1x), QoS supports new levels 4, 5, and 6 configured under Global policies, EPG, L3out, custom QoS, and Contracts. The following limitations apply:
-
Number of classes that can be configured with Strict priority is up to 5.
-
The 3 new classes are not supported with non-EX and non-FX switches.
-
If traffic flows between non-EX or non-FX switches and EX or FX switches, the traffic will use QoS level 3.
-
For communicating with FEX for new classes, the traffic carries a Layer 2 COS value of 0.
-
-
Starting with release 4.0(1x), you can configure QoS Class or create a Custom QoS Policy to apply on an L3Out Interface.
Configuring QoS for L3Outs Using the GUI
QoS for an L3Out is configured as part of the L3Out configuration.
Procedure
Step 1 |
Configure the VRF instance for the tenant consuming the L3Out to support QoS to be enforced on the border leaf switch that is used by the L3Out. |
Step 2 |
When configuring filters for contracts to enable communication between the EPGs consuming the L3Out, include a QoS class or target DSCP to enforce the QoS priority in traffic ingressing through the L3Out.
|
Step 3 |
Add a contract. |
Step 4 |
To configure QoS for a L3Out interface, in the Navigation pane, expand right-click, and choose Create Interface Profile and perform the following steps:
|
Configuring QoS for L3Outs Using the NX-OS Style CLI
QoS for L3Out is configured as part of the L3Out configuration.
Procedure
Step 1 |
When configuring the tenant and VRF, to support QoS priority enforcement on the L3Out, configure the VRF for egress mode and enable policy enforcement, using the following commands: Example:
|
||||
Step 2 |
When creating filters (
Example:
|
||||
Step 3 |
To configure QoS priorities for a L3Out SVI: Example:
|
||||
Step 4 |
To configure QoS priorities for a sub-interface: Example:
|
||||
Step 5 |
To Configure QoS priorities for a routed outside: Example:
|
Configuring QoS for L3Outs Using the REST API
QoS for L3Out is configured as part of the L3Out configuration.
Procedure
Step 1 |
When configuring the tenant, VRF, and bridge domain, configure the VRF for egress mode ( Example:
|
||||
Step 2 |
When creating the filters and contracts to enable the EPGs participating in the L3Out to communicate, configure the QoS priority. The contract in this example includes the QoS priority, The filter also has the matchDscp="EF" criteria, so that traffic with this specific TAG received by the L3out processes through the queue specified in the contract subject.
Example:
|
||||
Step 3 |
To configure QoS priorities for a L3Out SVI: Example:
|
||||
Step 4 |
To configure QoS priorities for a sub-interface: Example:
|
||||
Step 5 |
To Configure QoS priorities for a routed outside: Example:
|
QoS for RoCEv2
RoCEv2 and the Required APIC QoS Settings
Remote Direct Memory Access (RDMA) over Converged Ethernet (RoCE) technology allows data to be transferred between servers or from storage to server without having to pass through the CPU and main memory path of TCP/IP. The network adapters transfers data directly to and from the application memory bypassing the operating system and the CPU. This zero copy and CPU offloading approach ensures greater CPU availability for other tasks while providing low latency and reduced jitter. A single fabric can be used for both, storage and compute. RoCEv2 provides additional functionality by allowing RDMA to be used with both Layer-2 and Layer-3 (UDP/IP) packets, enabling Layer-3 routing over multiple subnets.
Starting with Cisco Application Policy Infrastructure Controller Release 4.0(1), you can enable RoCEv2 functionality in your fabric by configuring specific QoS options for Layer-3 traffic in Cisco APIC, such as Weighted Random Early Detection (WRED) congestion algorithm and Explicit Congestion Notification (ECN).
The following sections describe how to configure the required QoS options using three different methods – the Cisco APIC GUI, the NX-OS style CLI, and the REST API – but regardless of which you choose, you'll have to configure the following:
-
Weighted Random Early Detection (WRED) congestion algorithm, which manages congestion on spine switches using the following configuration options:
-
WRED Min Threshold – if the average queue size is below the minimum threshold value, the arriving packets are queued immediately.
-
WRED Max Threshold – if the average queue size is greater than the maximum threshold value, the arriving packets are dropped.
-
WRED Probability – if the average queue size is between the Min and Max threshold, the Probability value determines whether the packet is dropped or queued.
-
WRED Weight – weight has a range of
0
to7
and is used to calculate average queue length. Lower weight prioritizes current queue length, while higher weight prioritizes older queue lengths.
-
-
Explicit Congestion Notification (ECN), which is used for congestion notification. In case of congestion, ECN gets transmitting device to reduce transmission rate until congestion clears allowing traffic to continue without pause. ECN along with WRED enables end-to-end congestion notification between two endpoints on the network.
-
Priority Flow Control (PFC), which is used to achieve Layer 2 flow control. PFC provides the capability to pause traffic in case of congestion.
ROCEv2 Hardware Support.
The following Cisco hardware is supported for ROCEv2 in this release:
-
Cisco Nexus 9300-EX platform switches
-
Cisco Nexus 9300-FX platform switches
-
Cisco Nexus 9300-FX2 platform switches
-
N9K-X9700-EX line cards
-
N9K-C9504-FM-E fabric modules
Configuring Priority Flow Control (PFC) On Interfaces
Before you can configure the appropriate QoS settings for ROCEv2, you must enable PFC on each interface that is connected
to ROCE devices. PFC setting can be set to one of three values, on
, off
, and auto
. If you set it to auto
, the DCBX protocol negotiates the PFC state on the interface.
You can configure PFC on one or more interfaces using any of the following methods:
-
Using the Cisco APIC GUI, as described in Configuring PFC On Interfaces Using the Cisco APIC GUI
-
Using the NX-OS style CLI, as described in Configuring PFC On Interfaces Using the NX-OS Style CLI
-
Using the REST API, as described in Configuring PFC On Interfaces Using the REST API
Configuring PFC On Interfaces Using the Cisco APIC GUI
You can use the Cisco APIC GUI to configure PFC state on the interfaces connecting to ROCEv2 devices.
Procedure
Step 1 |
Log in to Cisco APIC. |
Step 2 |
From the top navigation bar, choose . |
Step 3 |
In the left-hand sidebar, navigate to . |
Step 4 |
In the main pane, select the Interface tab. |
Step 5 |
In the main pane, from the Mode dropdown menu, select Configuration. |
Step 6 |
Choose an L2 port you want to configure. |
Step 7 |
In the bottom pane, select the FCoE/FC tab. |
Step 8 |
Set the PFC State of the port to |
Configuring PFC On Interfaces Using the NX-OS Style CLI
You can use the NX-OS style CLI to configure PFC state on the interfaces connecting to ROCEv2 devices.
Procedure
Step 1 |
Enter APIC configuration mode. Example:
|
Step 2 |
Enter switch configuration. Example:
|
Step 3 |
Enable PFC for specific interfaces. Example:
|
Configuring PFC On Interfaces Using the REST API
You can use REST API to configure PFC state on the interfaces connecting to ROCEv2 devices.
Procedure
Step 1 |
You can configure PFC state on a group of interfaces using a policy group. Example:
|
Step 2 |
Alternatively, you can configure PFC state on individual interfaces. Example:
|
Configuring QoS for ROCEv2
After you have enabled PFC on each interfaces that is connected to ROCE devices, you can configure the appropriate QoS settings for ROCEv2.
You can configure QoS for ROCE using any of the following methods:
-
Using the Cisco APIC GUI, as described in Configuring QoS for ROCEv2 Using the GUI
-
Using the NX-OS style CLI, as described in Configuring QoS for RoCEv2 Using the NX-OS Style CLI
-
Using the REST API, as described in Configuring QoS for RoCEv2 Using the REST API
Configuring QoS for ROCEv2 Using the GUI
You can use the Cisco APIC GUI to configure the required QoS options to enable support for RoCEv2 in your fabric.
Procedure
Step 1 |
Log in to Cisco APIC. |
Step 2 |
Navigate to |
Step 3 |
Select the QOS Class Level for which you want to configure ROCEv2 |
Step 4 |
For the Congestion Algorithm option, select Weighted random early detection. |
Step 5 |
For the Congestion Notification option, select Enabled. Enabling Congestion Notification causes the packets that would be dropped to be ECN-marked instead. |
Step 6 |
For the Min Threshold (percentage) option, set the minimum queue threshold as a percentage of the maximum queue length. If the average queue size is below the minimum threshold value, the arriving packets are queued immediately. |
Step 7 |
For the Max Threshold (percentage) option, set the maximum queue threshold as a percentage of the maximum queue length. If the average queue size is greater than the maximum threshold value, the arriving packets are dropped or marked if ECN is enabled. |
Step 8 |
For the Probability (percentage) option, set the probability value. The probability determines whether the packet is dropped or queued when the average queue size is between the minimum and the maximum threshold values. |
Step 9 |
For the Weight option, set the weight value. Weight has a range of |
Step 10 |
Check the PFC Admin State checkbox and specify a value for the No-Drop-CoS option to be used by PFC. |
Step 11 |
For the Scope option, select |
Step 12 |
Optionally, you can choose to enable the Forward Non-ECN Traffic option, so that non-ECN traffic is not dropped even when the queue is congested. Congestion Notification must be enabled for this option to be configurable. |
Configuring QoS for RoCEv2 Using the NX-OS Style CLI
You can use the NX-OS style CLI to configure the required QoS options to enable support for RoCEv2 in your fabric.
Procedure
Step 1 |
Enter configuration mode. Example:
|
Step 2 |
Choose the QoS Level you want to configure. In the following command, replace level2 with the QoS Level you want to configure: Example:
|
Step 3 |
Configure the congestion algorithm and its parameters. Example:
|
Step 4 |
(Optional) Configure forwarding of the non-ECN traffic. You can choose to enable forwarding of all non-ECN traffic, even when the queue is congested. Example:
|
Step 5 |
Exit congestion algorithm configuration. Example:
|
Step 6 |
Configure the CoS value for the QoS Level you chose. Example:
If you do not provide the |
Configuring QoS for RoCEv2 Using the REST API
You can use REST API to configure the required QoS options to enable support for RoCEv2 in your fabric.
Procedure
Step 1 |
Configure QoS for RoCEv2. In the following example, replace level2 with the QoS class you want to configure and the WRED parameters with values appropriate for your environment.
Example:
|
Step 2 |
(Optional) Configure forwarding of the non-ECN traffic. You can choose to enable forwarding of all non-ECN traffic, even when the queue is congested. Example:
|
Custom QoS
Configuring a Custom QoS Policy
You can configure a custom QoS policy.
Procedure
Step 1 |
On the menu bar, choose . |
||||||||||||
Step 2 |
In the Navigation pane, expand , right-click Application Profile-name, and choose Create Application EPG. |
||||||||||||
Step 3 |
In the Create Application EPG dialog box, choose Create Custom QOS Policy from the Custom QoS drop-down list. The Create Custom QOS Policy dialog box appears. |
||||||||||||
Step 4 |
Complete the following fields:
|
||||||||||||
Step 5 |
In the DSCP to priority map section, click + to add a differentiated services code point (DSCP) to the prority map. |
||||||||||||
Step 6 |
Complete the following fields:
|
||||||||||||
Step 7 |
In the Dot1P Classifiers section, click + to add a dot1p classifier. |
||||||||||||
Step 8 |
Complete the following fields:
|
||||||||||||
Step 9 |
Click SUBMIT. The Create Custom QOS Policy dialog box closes and the custom QoS policy is created. |
QoS Preservation
Preserving 802.1P Class of Service Settings
APIC enables preserving 802.1P class of service (CoS) settings within the fabric. Enable the fabric global QoS policy dot1p-preserve
option to guarantee that the CoS value in packets which enter and transit the ACI fabric is preserved.
802.1P CoS preservation is supported in single pod and multipod topologies.
In multipod topologies, CoS Preservation can be used where you want to preserve the QoS priority settings of 802.1P traffic entering POD 1 and egressing out of POD 2, but you are not concerned with preserving the CoS/DSCP settings in interpod network (IPN) traffic between the pods. To preserve CoS/DSCP settings when multipod traffic is transitting an IPN, use a dot1p policy. For more information, see Preserving QoS Priority Settings in a Multipod Fabric.
Observe the following 801.1P CoS preservation guidelines and limitations:
-
The current release can only preserve the 802.1P value within a VLAN header. The DEI bit is not preserved.
-
For VXLAN encapsulated packets, the current release will not preserve the 802.1P CoS value contained in the outer header.
-
802.1P is not preserved when the following configuration options are enabled:
-
Contracts are configured that include QoS.
-
The outgoing interface is on a FEX.
-
Preserving QoS CoS priority settings is not supported when traffic is flowing from an EPG with isolation enforced to an EPG without isolation enforced.
-
A DSCP QoS policy is configured on a VLAN EPG and the packet has an IP header. DSCP marking can be set at the filter level on the following with the precedence order from the innermost to the outermost:
-
Contract
-
Subject
-
In Term
-
Out Term
Note
When specifying vzAny for a contract, external EPG DSCP values are not honored because vzAny is a collection of all EPGs in a VRF, and EPG specific configuration cannot be applied. If EPG specific target DSCP values are required, then the external EPG should not use vzAny.
-
-
Preserving QoS CoS Settings Using the GUI
To ensure that QoS priority settings are handled the same for traffic entering and transiting a single-pod fabric, or for traffic entering one pod and egressing another in a multi-pod fabric, you can enable CoS preservation using the GUI.
![]() Note |
Enabling CoS preservation applies a default mapping of the CoS priorities to DSCP levels to the various traffic types. |
Procedure
Step 1 |
From the menu bar, navigate to . |
Step 2 |
In the left-hand navigation pane, select . |
Step 3 |
In the Global - QOS Class main window pane, check the Preserve COS: Dot1p Preserve checkbox. |
Step 4 |
Click Submit. |
Preserving QoS CoS Settings Using the NX-OS Style CLI
To ensure that QoS priority settings are handled the same for traffic entering and transiting a single-pod fabric, or for traffic entering one pod and egressing another in a multi-pod fabric, you can enable CoS preservation using the NS-OS style CLI.
![]() Note |
Enabling CoS preservation applies a default mapping of the CoS priorities to DSCP levels to the various traffic types. |
Procedure
Step 1 |
Enters APIC configuration mode. Example:
|
Step 2 |
Enables CoS preservation. Example:
|
Preserving QoS CoS Settings Using the REST API
To ensure that QoS priority settings are handled the same for traffic entering and transiting a single-pod fabric, or for traffic entering one pod and egressing another in a multi-pod fabric, you can enable CoS preservation using the REST API.
![]() Note |
Enabling CoS preservation applies a default mapping of the CoS priorities to DSCP levels to the various traffic types. |
Procedure
You can use the following example to enable CoS preservation. POST https://<apic-ip>/api/node/mo/uni/infra/qosinst-default.xml Example:
To disable CoS preservation, you can use the same Example:
|
Multipod QoS
Preserving QoS Priority Settings in a Multipod Fabric
This topic describes how to guarantee QoS priority settings in a multipod topology, where devices in the interpod network are not under APIC management, and may modify 802.1p settings in traffic transiting their network.
![]() Note |
You can alternatively use CoS Preservation where you want to preserve the QoS priority settings of 802.1p traffic entering POD 1 and egressing out of POD 2, but you are not concerned with preserving the CoS/DSCP settings in interpod network (IPN) traffic between the pods. For more information, see Preserving 802.1P Class of Service Settings. |

As illustrated in this figure, traffic between pods in a multipod topology passes through an IPN, which may not be under APIC management. When an 802.1p frame is sent from a spine or leaf switch in POD 1, the devices in the IPN may not preserve the CoS setting in 802.1p frames. In this situation, when the frame reaches a POD 2 spine or leaf switch, it has the CoS level assigned by the IPN device, instead of the level assigned at the source in POD 1. Use a DSCP policy to ensure that the QoS priority levels are preserved in this case.
Configure a DSCP policy to preserve the QoS priority settings in a multipod topology, where there is a need to do deterministic mapping from CoS to DSCP levels for different traffic types, and you want to prevent the devices in the IPN from changing the configured levels. With a DSCP policy enabled, APIC converts the CoS level to a DSCP level, according to the mapping you configure. When a frame is sent from POD 1 (with the PCP level mapped to a DSCP level), when it reaches POD 2, the mapped DSCP level is then mapped back to the original PCP CoS level.
DSCP Settings
![]() Note |
For traffic passing through the IPN, do not map any DSCP value to COS6 (except traceroute traffic). |
![]() Note |
Starting with release 4.0(1x), custom DSCP values can be selected for class levels 4 through 6 for Multipod QoS polices. Example:
|
DSCP or TOS Level |
Description |
---|---|
AF11 |
Assured Forwarding Class 1, low probability of dropping |
AF12 |
Assured Forwarding Class 1, medium probability of dropping |
AF13 |
Assured Forwarding Class 1, high probability of dropping |
AF21 |
Assured Forwarding Class 2, low probability of dropping |
AF22 |
Assured Forwarding Class 2, medium probability of dropping |
AF23 |
Assured Forwarding Class 2, high probability of dropping |
AF31 |
Assured Forwarding Class 3, low probability of dropping |
AF32 |
Assured Forwarding Class 3, medium probability of dropping |
AF33 |
Assured Forwarding Class 3, high probability of dropping |
AF41 |
Assured Forwarding Class 4, low probability of dropping |
AF42 |
Assured Forwarding Class 4, medium probability of dropping |
AF43 |
Assured Forwarding Class 4, high probability of dropping |
CS0 |
TOS Class Selector value 0 (the default) |
CS1 |
TOS Class Selector value 1 (typically used for streaming traffic) |
CS2 |
TOS Class Selector value 2 (typically used for OAM traffic such as SNMP, SSH, and Syslog) |
CS3 |
TOS Class Selector value 3 (typically used for signalling traffic) |
CS4 |
TOS Class Selector value 4 (typically used for Policy Plane traffic and to priority queue) |
CS5 |
TOS Class Selector value 5 (typically used for broadcast video traffic) |
CS6 |
TOS Class Selector value 6 (typically used for Network control traffic) |
CS7 |
TOS Class Selector value 7 |
Expedited Forwarding |
EF is dedicated to low-loss, low-latency traffic |
Voice Admit |
Similar to EF, but also admitted through CAC |
Creating a DSCP Policy Using the GUI
Create a DSCP policy to enable guaranteeing QoS priority settings in a multipod topology and configure DSCP mappings for various traffic streams in the fabric. The mappings must be unique within the policy.
Procedure
Step 1 |
On the menubar, click . |
Step 2 |
In the Navigation pane, expand . |
Step 3 |
In the Properties panel, click Enabled to enable the DSCP policy. |
Step 4 |
Map each traffic stream to one of the available levels. They must all be unique. |
Step 5 |
Click Submit. |
Creating a DSCP Policy Using the NX-OS Style CLI
Create a DSCP map (known as a DSCP policy in the APIC GUI) to guarantee QoS priority settings in a multipod topology. The mappings must be unique within the policy.
Configure a DSCP map with custom mappings for traffic streams with the following steps:
Procedure
Step 1 |
Enters global configuration mode. Example:
|
||
Step 2 |
Enters tenant configuration mode for the infra tenant. Example:
|
||
Step 3 |
Configures the DSCP map. Example:
|
||
Step 4 |
Sets the custom DSCP mappings, similar to the following example. The mappings must all be unique within a DSCP map.
Example:
|
||
Step 5 |
Enables the DSCP map. Example:
|
Creating a DSCP Policy Using the REST API
Procedure
Step 1 |
Configure and enable a DSCP policy with a post, such as the following:
Example:
|
Step 2 |
Disable the DSCP policy with a post such as the following:
Example:
|
Translating QoS Ingress Markings to Egress Markings
Translating QoS Ingress Markings to Egress Markings
APIC enables translating the 802.1P CoS field (Class of Service) based on the ingress DSCP value. 802.1P CoS translation is supported only if DSCP is present in the IP packet and dot1P is present in the Ethernet frames.
This functionality enables the ACI Fabric to classify the traffic for devices that classify the traffic based only on the CoS value. It allows mapping the dot1P CoS value based on the ingress dot1P value. It is mainly applicable for Layer 2 packets, which do not have an IP header.
Observe the following 802.1P CoS translation guidelines and limitations:
-
Enable the fabric global QoS policy
dot1p-preserve
option. -
802.1P CoS translation is not supported on external L3 interfaces.
-
802.1P CoS translation is supported only if the egress frame is 802.1Q encapsulated.
802.1P CoS translation is not supported when the following configuration options are enabled:
-
Contracts are configured that include QoS.
-
The outgoing interface is on a FEX.
-
Multipod QoS using a DSCP policy is enabled.
-
Dynamic packet prioritization is enabled.
-
If an EPG is configured with intra-EPG endpoint isolation enforced.
-
If an EPG is configured with allow-microsegmentation enabled.
Translating QoS CoS Settings Using the GUI
Create a custom QoS policy and then associate the policy with an EPG.
Before you begin
Create the tenant, application, and EPGs that will consume the custom QoS policy.
Procedure
Step 1 |
On the menu bar, click . |
Step 2 |
From the Actions drop-down list, choose Create Custom QoS Policy. |
Step 3 |
In the Create Custom QoS Policy window, specify the Target CoS in the DSCP to priority map field. This setting allows you to map ingress DSCP value to egress CoS value. |
Step 4 |
In the Create Custom QoS Policy window, specify the Target CoS in the Dot1P Classifiers field. This setting allows you to translate ingress CoS value to egress CoS value. |
Step 5 |
Click Submit. |
Step 6 |
On the menu bar, click . |
Step 7 |
In the EPG panel, select the custom QoS policy you created in step 3. |
Step 8 |
Click Submit. |
Translating QoS CoS Settings Using the NX-OS CLI
Create a custom QoS policy and then associate the policy with an EPG using the following commands:
Before you begin
Create the tenant, application, and EPGs that will consume the custom QoS policy.
Procedure
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 |
configure Example:
|
Enters global configuration mode.
|
||
Step 2 |
tenant tenant-name Example:
|
Enters tenant configuration mode for the tenant. |
||
Step 3 |
policy-map type qos QoS-policy-name Example:
|
Creates QoS policy. |
||
Step 4 |
match dscp AF23 AF31 set-cos 6 Example:
|
Sets DCSP value and target QoS value. |
||
Step 5 |
exit Example:
|
Returns to the tenant configuration mode. |
||
Step 6 |
application app-name Example:
|
Creates an application profile.
|
||
Step 7 |
epg epg-name Example:
|
Creates an EPG in the application profile. |
||
Step 8 |
service-policy policy-name Example:
|
Associates the EPG to the policy. |
||
Step 9 |
exit Example:
|
Returns to the tenant configuration mode. |
||
Step 10 |
external-l2 epg epg-name Example:
|
Creates an external layer 2 EPG.
|
||
Step 11 |
service-policy policy-name Example:
|
Associates the EPG to the policy. |
||
Step 12 |
exit |
Returns to the tenant configuration mode. |
Translating QoS Ingress Markings to Egress Markings Using the REST API
Create a custom QoS policy and then associate the policy with an EPG.
Before you begin
Create the tenant, application, and EPGs that will consume the custom QoS policy. The example creates the vrfQos001
custom QoS policy and associates it with the ep2
EPG, that will consume it.
Procedure
Step 1 |
Create a custom QoS policy by sending a post with XML such as the following example: Example:
|
Step 2 |
Associate the policy with an EPG that will consume it by sending a post with XML such as the following example: Example:
|
Configuring QoS for Multipod
Use this procedure to configure QoS on a multipod setup.
Before you begin
You must have configured Multipod.
Procedure
Step 1 |
Preserve QoS CoS settings to ensure QoS priority settings are handled the same, in APIC traffic through the fabric. |
||
Step 2 |
Match the QoS Class Policy-Level 1, QoS Class Policy-Level 2, and QoS Class Policy-Level 3 according to the policy determined in the IP network (IPN to IPN).
|
||
Step 3 |
Create a DSCP policy to enable guaranteeing QoS priority settings in a multipod topology and configure DSCP mappings for various traffic streams in the fabric. Example:
|
||
Step 4 |
Create class maps to match the markings configured on the APIC. Example:
|
||
Step 5 |
Create a policy map to label the ingress Control Plane and Policy Plane traffic with a QoS group. Example:
|
||
Step 6 |
Configure priority queue for the QoS group. Example:
|
||
Step 7 |
Apply the policy map to system level QoS. Example:
|
||
Step 8 |
Associate the interfaces connected to the spine switch with the service policy. Example:
|
||
Step 9 |
Verify the ingress interface on IPN. Example:
|
||
Step 10 |
Verify the egress interface on IPN. Example:
|
Troubleshooting Cisco APIC QoS Policies
The following table summarizes common troubleshooting scenarios for the Cisco APIC QoS.
Problem |
Solution |
---|---|
Unable to update a configured QoS policy. |
|
Show QoS interface statistics. |
CLI displays statistics for eth1/1 for only QoS classes – level1, leve2, level3, level4, level5, level6, and policy-plane – if you don’t use “detail” option.
If you want to display statistics for control-plane and span classes for an interface, you need to use CLI with the “detail” option. Example: fabric 107 show queuing interface ethernet 1/1 detail
|