Cisco EasyQoS Application for APIC-EM Release Notes
This document describes the Cisco EasyQoS features, limitations, and bugs for release 1.6.1.x.
Along with Cisco EasyQoS, Cisco APIC-EM supports the following additional applications:
-
Cisco Network Visibility
-
Cisco Path Trace
-
Cisco Active Advisor
-
Cisco Integrity Verification
-
Cisco Remote Troubleshooter
-
Cisco Wide Area Bonjour
-
Cisco IWAN
-
Cisco Network PnP
For information about the Cisco APIC-EM controller infrastructure (system requirements, security, licensing, supported multi-host configurations, and so on) and the other Cisco APIC-EM applications, see their corresponding release notes at the following URL:
What’s New in Cisco EasyQoS for APIC-EM, Release 1.6.1.x
There are no new features for this release.
Cisco EasyQoS Supported Platforms and Software Requirements
For information about the network devices and software versions supported for this release by the EasyQoS app, see http://www.cisco.com/c/en/us/support/cloud-systems-management/one-enterprise-network-controller/products-device-support-tables-list.html
Installing or Upgrading EasyQoS
The EasyQoS image is built into the APIC-EM controller image. When you install or upgrade Cisco APIC-EM, the Cisco EasyQoS application is installed or upgraded as well.
After installing or upgrading the APIC-EM software, you can begin to use EasyQoS by enabling the application. For information about how to enable applications, see the Cisco Application Policy Infrastructure Controller Enterprise Module Administration Guide. For any of the following information, see these sources:
|
Information |
Source |
|---|---|
|
Installing APIC-EM or EasyQoS |
Cisco Application Policy Infrastructure Controller Enterprise Module Installation Guide |
|
Upgrading APIC-EM or EasyQoS |
Cisco Application Policy Infrastructure Controller Enterprise Module Upgrade Guide |
|
Obtaining bug information about APIC-EM |
Cisco Application Policy Infrastructure Controller Enterprise Module Release Notes |
Caveats
Open Caveats
The following table lists the open caveats for this release.
|
Caveat ID Number |
Headline |
|---|---|
|
The DSCP customization is not applied for queuing policy on MLS and Nexus 7000 QoS platforms. Workaround: There is no workaround at this time. |
|
|
Incorrect configuration sent to Cisco Catalyst 6000 switch ACCESS role with port-channel. Workaround: There is no workaround at this time. |
|
|
The QoS statistics output "queueBandwidthbps" shows NA when configured with several commands. On an ISR router, configure the policy-map with the bandwidth and priority commands. Start a flow analysis with QoS statistics collection request with the ISR router in the path. This happens when configured with following commands:
Workaround: There is no workaround at this time. |
|
|
Traffic will be disrupted when applying an EasyQoS policy on a Cisco Catalyst 4500 series switch that is using port channels. Workaround: When configuring EasyQoS on a Cisco Catalyst 4500 series switch using port channels, we recommend that you apply the EasyQoS policy during a maintenance window or by changing the routing metrics (either EIGRP or OSPF) to remove traffic off of the member links during the application of the policy. |
|
|
When a Cisco 2500 Series Wireless Controller (WLC) is upgraded from version 7.4.100.0 or lower to any version that EasyQos supports, EasyQos can push a policy to the WLC, but it cannot attach the WLAN. In this scenario, EasyQos should not push the policy to the WLC. Instead, it should display a message on the EasyQos GUI similar to the following: "AVC is not supported with the current bootloader version (1.0.16). Please upgrade the bootloader to version 1.0.18 or Field Upgradable software version 1.8.0.0 or higher. See Cisco documentation for information about Field Upgradable software.” This issue is specific to the Cisco 2500 Series Wireless Controller (WLC). Workaround: Upgrade the wireless controller bootloader to version 1.0.18 or higher, perform an inventory synchronization, and reapply the policy. |
|
|
An application may be omitted from the ACL due to limited TCAM resources, while higher rank applications are included in the ACL. When editing advanced settings for such NBAR applications in EasyQoS Policies window (e.g. change to bi-directional or add consumer application), it will still be omitted from the ACL in case of limited TCAM resources. Workaround: Mark the edited application as "Favorite" in the EasyQoS Application Registry screen. This will cause the application to be highly ranked and included in the ACL. |
|
|
In the EasyQoS application page, the unassigned count includes all devices that a user has access to; although, only devices for which the user is an admin are actually displayed. Workaround: There is no workaround at this time. |
|
|
When the destination port and IP address are not provided in an input flow, EasyQoS looks up this information in the custom application profile and should display it in the Dynamic QoS tab. However, EasyQoS does not display it. Workaround: There is no workaround at this time. |
|
|
EasyQoS reports an error message that the QoS configuration failed due to an invalid command for Cisco Nexus devices. If a Cisco Nexus device has virtual device contexts (VDCs) configured, and you try to apply a QoS policy configuration with the non-default/non-admin VDC, EasyQoS fails to configure the device and reports an error. Workaround To avoid this issue, discover and perform EasyQoS operations through the default/admin VDC. |
|
|
When the configuration for a custom application is removed from a device, EasyQoS fails to remove all of the configuration. The remarks and ACL commands are not being removed. Workaround: There is no workaround at this time. |
Resolved Caveats
The following table lists the resolved caveats for this release.
 Note |
For a list of caveats resolved in an earlier software release, see the Cisco APIC-EM release notes for the specific release. |
|
Bug ID Number |
Headline |
|---|---|
|
There is a behavior difference when you disable Fastlane after enabling it using EasyQoS. The following is provided as an example of this issue. After creating a wireless policy using EasyQoS with Fastlane enabled and that wireless policy is pushed to the WLC, the quality of service is 'Platinum' as expected. Later, Fastlane is disabled using the controller's GUI. When you then reapply the policy, log into the WLC, and run the wlan check qos command, the quality of service is 'Silver' and Fastlane is disabled. This is incorrect, with Fastlane disabled the quality of service should still be 'Platinum'. Workaround: There is no workaround at this time. |
|
|
When rollback and re-apply are done simultaneously policy configuration does not complete. Workaround: On a policy re-apply, the policy configuration will be completed. |
|
|
Restore feature does not work for queuing policy with MLS QoS platforms. For MLS QoS platforms, the queuing policy is configured directly on the interface. EasyQoS may change the policy, so there is no previous configuration saved on the switch platform. Therefore, clicking on the Restore button will not restore the pre-EasyQoS queuing policy for these platforms. Note that the ingress classification and marking policy will be restored, because they use service-policy definitions applied to the interfaces. Workaround: There is no workaround at this time. |
|
|
After deleting a policy in an EasyQoS scope and then creating and applying the same policy in that scope, different configurations are generated for the policy on the Cisco Catalyst 6500 switch. Workaround: When QoS policy is deleted from a Cisco Catalyst 6500 switch, the device should be resynchronized before a new QoS policy is applied. This can be accomplished through a manual resync from the Device Inventory screen, or by waiting until after the next polling interval. The resync will ensure that APIC-EM controller and EasyQoS has the current configuration of the device before applying the new QoS policy. |
|
|
Generating a configuration for preview takes more than a minute for Cisco Catalyst 3850 stackable switches that are configured to full scale limits. Workaround: There is no workaround at this time. |
|
|
The Postgres service restarted on a scale setup with 10,000 devices which was idle for 24-36 hours. Workaround: There is no workaround at this time. |
Using the Bug Search Tool
Use the Bug Search tool to search for a specific bug or to search for all bugs in this release.
Procedure
| Step 1 |
Go to http://tools.cisco.com/bugsearch. |
||
| Step 2 |
At the Log In screen, enter your registered Cisco.com username and password; then, click Log In. The Bug Search page opens.
|
||
| Step 3 |
To search for a specific bug, enter the bug ID in the Search For field and press Return. |
||
| Step 4 |
To search for bugs in the current release: |
EasyQoS Limitations and Restrictions
The EasyQoS application has the following limitations and restrictions.
Note |
Refer to the other Cisco APIC-EM application release notes or Cisco APIC-EM controller release notes for information about any other application or infrastructure-specific issues. |
-
The application does not support configuring Quality of Service in a port-channel interface for ISR 4000 routers.
-
The Postgres service for the Cisco APIC-EM controller restarted on a scale setup with 10,000 devices which was idle for 24-36 hours.
-
When entering characters in the EasyQoS GUI for a URL field while adding a custom application, Cisco EasyQoS supports up to 30 characters. The following Cisco IOS versions support only 29 characters in the URL field:
-
15.5(03)S3.16
-
15.5(03)M3.1
-
15.6(3)M1
-
16.3.2
If your device is running one of the above Cisco IOS versions, then only enter up to 29 characters in the URL field.
-
-
Custom apps created using the EasyQoS GUI application require an IP address (mandatory field). Custom apps created using the API do not require an IP address (optional field). Custom apps created without an IP address using the API will fail when applied to a NBAR router. NBAR routers do not support applications without an IP address. To apply the policy on NBAR routers, please remove the custom app from the list.
-
When removing a network device from a scope in EasyQoS, options that permit you to restore to the original policy or delete the policy are not triggered. Additionally, unlike the option in EasyQoS that permits you to reapply a policy, there are no options to restore an original policy or to delete a policy when a policy fails on the network devices.
-
For the EasyQoS application, the maximum number of devices that can be configured for a scope is 2000.
-
Cisco EasyQoS is not supported on the Cisco ASR 1000 series router running Cisco IOS XE 16.3.1.
-
Within the EasyQoS application, Dynamic QoS is a beta functionality for this release.
-
The DSCP-to-UP mappings provisioned by EasyQoS to WLC platforms are not changed, regardless of whether the network administrator has modified the DSCP marking assigned to a given traffic-class. This could result in sub-optimal QoS. This may occur if the traffic-class is assigned a DSCP marking which maps to the wrong IEEE 802.11 user priority (UP). For example, if a network administrator assigns the Multimedia-Streaming video traffic-class a DSCP value that maps to a UP that belongs to the Best Effort 802.11 access category (AC), then Multimedia-Streaming traffic will receive Best Effort service across the wireless medium.
-
When rolling back an APIC-EM 1.5 policy involving WLC platforms, EasyQoS will remove the AVC Profile from the WLAN/SSID, and will change the QoS Profile to Silver (Best Effort). EasyQoS will leave Fastlane enabled for the WLAN/SSID, although there is no AVC Profile associated with Fastlane and the QoS Profile associated with the WLAN/SSID has been changed from Platinum (the default with Fastlane) to Silver.
-
The application does not support multilink interfaces.
-
At present, the EasyQoS application does not support devices with a cellular interface. This functionality may be added in a later release.
-
If the name of the sub-interface exceeds 64 characters, then complete the following steps:
-
Run the following command on the device.
snmp ifmib ifalias long -
Resync the device in APIC-EM. Confirm that the change has been applied.
-
Reapply the QoS policy.
-
Important |
For specific EasyQoS feature support and restrictions by platform and line card, see Supported Platforms for the Cisco Application Policy Infrastructure Controller Enterprise Module. |
Service and Support
Troubleshooting
See the Cisco Application Policy Infrastructure Controller Enterprise Module Troubleshooting Guide, for troubleshooting procedures.
Related Documentation
The following publications are available for the Cisco APIC-EM:
Cisco APIC-EM Controller Documentation
|
For this type of information... |
See this document... |
|---|---|
|
Release information, including new features, system requirements, and open and resolved caveats. |
Cisco Application Policy Infrastructure Controller Enterprise Module Release Notes |
|
Installation and configuration of the controller, including post-installation tasks. |
Cisco Application Policy Infrastructure Controller Enterprise Module Installation Guide |
|
Introduction to the Cisco APIC-EM GUI and its applications. |
Cisco Application Policy Infrastructure Controller Enterprise Module Quick Start Guide 1 |
|
Configuration of user accounts, RBAC scope, security certificates, authentication and password policies, and global discovery settings. Monitoring and managing Cisco APIC-EM services. Backup and restore. Cisco APIC-EM APIs. |
Cisco Application Policy Infrastructure Controller Enterprise Module Administrator Guide |
|
Troubleshooting the controller, including the installation, services, and passwords. Developer console. How to contact the Cisco Technical Assistance Center (TAC). |
Cisco Application Infrastructure Controller Enterprise Module Troubleshooting Guide |
|
Tasks to perform before updating the controller to the latest version. Software update instructions. Tasks to perform after an update. |
Cisco Application Infrastructure Controller Enterprise Module Upgrade Guide |
Cisco Active Advisor Application Documentation
|
For this type of information... |
See this document... |
|---|---|
|
Release information, including open and resolved caveats for the Cisco Active Advisor application. |
Cisco Active Advisor for APIC-EM Release Notes |
Cisco EasyQoS Application Documentation
|
For this type of information... |
See this document... |
|---|---|
|
Release information, including open and resolved caveats for the Cisco EasyQoS application. |
Cisco EasyQoS Application for APIC-EM Release Notes |
|
Supported platforms and software releases. |
Cisco EasyQoS Application for APIC-EM Supported Platforms |
|
Installation of the application. (This application is installed as part of the Cisco APIC-EM controller software.) |
Cisco Application Policy Infrastructure Controller Enterprise Module Installation Guide |
|
Configuration of quality of service policies on the network devices in your network. |
Cisco EasyQoS Application for APIC-EM User Guide |
Cisco Integrity Verification Application Documentation
|
For this type of information... |
See this document... |
|---|---|
|
Release information, including open and resolved caveats for the Cisco Integrity Verification application. |
Cisco Integrity Verification Application (Beta) on APIC-EM Release Notes |
|
Using the Cisco Integrity Verification application. |
Cisco Integrity Verification Application (Beta) on APIC-EM User Guide |
Cisco Network Plug and Play Application Documentation
|
For this type of information... |
See this document... |
|---|---|
|
Release information, including open and resolved caveats for the Cisco Plug and Play application. Supported Cisco devices for Cisco Network Plug and Play. |
Release Notes for Cisco Network Plug and Play |
|
Configuration of devices using Cisco Network Plug and Play. |
Configuration Guide for Cisco Network Plug and Play on Cisco APIC-EM Cisco Network Plug and Play Agent Configuration Guide or Cisco Open Plug-n-Play Agent Configuration Guide (depending on the Cisco IOS XE release) |
|
Cisco Network Plug and Play solution overview. Main workflows used with the Cisco Network Plug and Play solution. Deployment of the Cisco Network Plug and Play solution. Tasks for using proxies with the Cisco Network Plug and Play solution. Configuration of a DHCP server for APIC-EM controller auto-discovery. Troubleshooting procedures for the Cisco Network Plug and Play solution. |
Solution Guide for Cisco Network Plug and Play |
|
Information about using the Cisco Plug and Play Mobile App. |
Mobile Application User Guide for Cisco Network Plug and Play (also accessible in the app through Help) |
Cisco IWAN Application Documentation
|
For this type of information... |
See this document... |
|---|---|
|
Release information, including open and resolved caveats for the Cisco IWAN application. |
Cisco IWAN Application on APIC-EM Release Notes |
|
Using the Cisco IWAN application. |
Cisco IWAN Application on APIC-EM User Guide |
Cisco Network Visibility Application Documentation
|
For this type of information... |
See this document... |
|---|---|
|
Release information, including open and resolved caveats for the Cisco Network Visibility application. |
Cisco Network Visibility Application for APIC-EM Release Notes |
|
Supported platforms and software releases. |
Cisco Network Visibility Application for APIC-EM Supported Platforms |
|
Installation of the application. (This application is installed as part of the Cisco APIC-EM controller software.) |
Cisco Application Policy Infrastructure Controller Enterprise Module Installation Guide |
|
Network discovery, device and host management, topology maps. |
Cisco Network Visibility Application for APIC-EM User Guide |
Cisco Path Trace Application Documentation
|
For this type of information... |
See this document... |
|---|---|
|
Release information, including open and resolved caveats for the Path Trace application. |
Cisco Path Trace Application for APIC-EM Release Notes |
|
Supported platforms and software releases. |
Cisco Path Trace Application for APIC-EM Supported Platforms |
|
Installation of the application. (This application is installed as part of the Cisco APIC-EM controller software.) |
Cisco Application Policy Infrastructure Controller Enterprise Module Installation Guide |
|
Procedures for performing path traces and information about how to understand the path trace results. |
Cisco Path Trace Application for APIC-EM User Guide |
Cisco Remote Troubleshooter Application Documentation
|
For this type of information... |
See this document... |
|---|---|
|
Release information, including open and resolved caveats for the Cisco Remote Troubleshooter application. |
Cisco Remote Troubleshooter Application on APIC-EM Release Notes |
|
Using the Cisco Remote Troubleshooter application. |
Cisco Remote Troubleshooter Application on APIC-EM User Guide |
Cisco Wide Area Bonjour Application Documentation
|
For this type of information... |
See this document... |
|---|---|
|
Release information, including open and resolved caveats for the Cisco Wide Area Bonjour application. |
Cisco Wide Area Bonjour Application for APIC-EM Release Notes |
|
Installation, configuration, troubleshooting, and usage of the application. |
Cisco Wide Area Bonjour Application for APIC-EM User Guide |
Cisco Remote Troubleshooter Application Documentation
|
For this type of information... |
See this document... |
|---|---|
|
Release information, including open and resolved caveats for the Cisco Remote Troubleshooter application. |
Cisco Remote Troubleshooter Application on APIC-EM Release Notes |
|
Using the Cisco Remote Troubleshooter application. |
Cisco Remote Troubleshooter Application on APIC-EM User Guide |
Cisco APIC-EM Developer Documentation
The Cisco APIC-EM developer website is located on the Cisco DevNet website
|
For this type of information... |
See this document... |
|---|---|
|
API functions, parameters, and responses. |
|
|
Tutorial introduction to controller GUI, DevNet sandboxes and APIC-EM NB REST API. |
Getting Started with Cisco Application Policy Infrastructure Controller Enterprise Module (APIC-EM) |
|
Hands-on coding experience calling APIC-EM NB REST API from Python. |
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at:
http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html
Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation as an RSS feed and delivers content directly to your desktop using a reader application. The RSS feeds are a free service.
Feedback