This blog series covers some of the new API released as part of the APIC-EM 1.3 release of code.
This particular blog covers a the EasyQoS application. EasyQoS is a policy based approach to deploying Quality of Server (QoS) across Cisco switches, routers and Wireless LAN controllers.
This particular blog show how to update an existing QoS policy, create a new application and add a new policy containing the new application.
A bit about EasyQoS application
There are two key concepts with EasyQoS.
1) Scope: defines the devices that will have a policy applied to them. A device can only be assigned to one policy scope.
2) Policy: a mapping between applications and "relevance". The relevance has one of three values:
"Default": the application will be treated as default (no QoS marking, default queuing)
"Relevant": the application will have appropriate QoS markings and queuing defined as per the Cisco Validated Design (CVD)
"Irrelevant": the application will marked as not important and restricted to a small amount of network bandwidth (scavenger, for those familiar with QoS)
Defining the initial policy via User Interface
In this example, a simple policy ("adam-branch") has been defined. It is applied to the scope "branchQoS". The "sap" application has been defined as business relevant. Note there are no applications defined as "Default" or "Business Irrelevant" in this example.
Click on the "branchQoS" scope, shows the policy has been successfully defined on a single device.
Using the API to modify a policy
Taking a look at the current policies defined on the scope "branchQoS", a single policy has been defined. The name of the policy is "adam-branch-BR". The reason for the "-BR" suffix is that these are applications that are Business-Relevant. In this example the list contains a single application ("sap"), but could contain multiple applications.
In later examples "-BI" (Business Irrelevant) and "-D" (default) policies will be shown.
In this example, the "oracle-bi" application is also business relevant, so the policy needs to be updated. First need to get "id" of the pre-defined oracle-bi application using the following request. The application has an id of "8d04df43-56c2-4572-802d-b743dc50b836" and is using TCP ports "9703,9704"
The next step is to modify the existing policy to add the "oracle-bi" application. NOTE: This will be a PUT (modify) rather than POST (create a new policy). I will show you how to create an application from scratch in the next example.
Remember the id of the oracle-bi application is "8d04df43-56c2-4572-802d-b743dc50b836".
The policy change will be reflected in the user interface.
Using the API to create a custom application
Although there are 1300 applications defined in EasyQoS application, there is also an API to create new application definitions.
In this example, I am creating an application "adam-new" which is a TCP application with an IP address of "10.200.20.0" and TCP Port of 2320. The QoS Class for this application is "BULK_DATA". The other attributes are for IWAN path selection.
As usual, there will be a task created, which needs to be polled. The response will show the status of the task and the id of the newly created application will returned in the "progress" attribute 2297ba33-42da-494c-9875-4d7551060b18.
Using the id of the newly created application "adam-new" a "Business Irrelevant" policy will be created for the same scope. The name of the policy will be the same as before, except it will have a "-BI" and the "relevanceLevel" also needs to reflect the policy is Business-Irelevant applications. The application id is the same one created in the earlier step (adam-new).
This blog covered some basic API for the EasyQoS application on APIC-EM.
In the meantime, if you would like to learn more about this, you could come hang out with us in The Cisco Devnet DNA Community. We’ll have a continuous stream of blogs like this and you can ask questions and we’ll get you answers. In addition, we have a Github repository where you can get examples related to EasyQoS.