- Introducing the IOS XE REST API
- Installing the Virtual Services Management Container
- Client Authentication
- Global Configuration Requirements
- Domain Name System (DNS) Server
- Network Time Protocol (NTP)
- IP Interface Configuration Requirements
- L2 Interfaces
- Bridge Domains
- Multicast
- VxLAN
- DHCP Server and Relay Agent
- Routing Protocol (OSPF, BGP, EIGRP) Requirements
- ACL Requirements for Subnets or IP Ranges
- Network Address Translation (NAT)
- Firewall Inspection Requirements
- License Requirements
- Memory and CPU Usage Report
- VRF
- Virtual Private Networks (SVTI and EzVPN)
- LISP
- QoS
- HSRP
QoS
Introduction to QoS
Quality of Service (QoS) network tools improve service to selected network traffic by the following methods:
- Supporting dedicated bandwidth
- Improving loss characteristics
- Avoiding and managing network congestion
- Shaping network traffic
- Setting traffic priorities across the network
QOS configuration comprises defining a traffic class, creating a traffic policy, and attaching the traffic policy to an interface.
QoS offers two kinds of traffic regulation mechanisms—policing and shaping. Packet classification tools enable partitioning network traffic into multiple priority levels or classes of service.
- Policing features limit the input or output transmission rate of a class of traffic based on userdefined criteria.
- Shaping features manage traffic and congestion on the network.
A hierarchical policy is a QoS model that enables specifying QoS behavior at multiple levels of hierarchy. Multiple policy maps can be configured to shape multiple queues together. For hierarchical policies, the service-policy command is used to attach:
- Child policies to child policies
- Child policies to parent policies
- Parent policies to interfaces, subinterfaces, and virtual circuits
A parent policy contains only the class-default class. It cannot contain any other classes.
There are numerous restrictions on parent and child policies. For more information, see:
http://www.cisco.com/c/en/us/td/docs/routers/10000/10008/configuration/guides/qos/qoscf.pdf
Resource Summary for QoS
|
|||||
---|---|---|---|---|---|
|
|
|
|
|
|
QoS Class Maps
History
|
|
Properties for class-map
JSON Representation for Class Map
Create a Class Map
Resource URI
|
|
---|---|
Example
Retrieve All Class Maps
Resource URI
|
|
---|---|
Example
Retrieve a Class Map
Resource URI
|
|
---|---|
Example
Modify a Class Map
Resource URI
|
|
---|---|
Example
Delete a Class Map
Resource URI
|
|
---|---|
Example
QoS Policy Map
History
|
|
Properties: Configuring a Policy Map
Properties: Configuring a Class Object under a Policy Map
Properties: Policy Map Policing—Rate/CIR Configuration Properties
Policy-map policing rate can be configured using one of the following (not both):
|
|
|
|
---|---|---|---|
Percent of interface bandwidth for committed information rate |
|||
Properties: Policy Map Policing—Rate Configuration Properties
Policy-map policing rate can be configured using one of the following (not both):
Properties: Policy Map Policing—Action Configuration
JSON Representation: Policy Map Policing
Expansion of POLICE_OBJECT Above
Create a Policy Map
Resource URI
|
|
---|---|
Example
Retrieve All Policy Maps
Resource URI
|
|
---|---|
Example
Retrieve a Policy Map
Resource URI
|
|
---|---|
Example
Modify a Policy Map
A policy map can be applied to a list of interfaces while creating the policy map. Alternatively, the policy map can be applied to an interface after creating the policy map by specifying only the policy map name and interface name(s) (see Example 2: Applying Policy map to an Existing Configuration).
Resource URI
|
|
---|---|
Example 1
Example 2: Applying Policy map to an Existing Configuration
The following example updates a policy map by applying the "OUTBAND-CLASSIFY" policy map to the interface "gigabitethernet2". Doing so does not delete the existing configuration; it only adds the policy to the interface.
Delete a Policy Map
Resource URI
|
|
---|---|