Table Of Contents
Implementing the CISCO-CLASS-BASED-QOS-MIB
QoS MIB Policy Action Support Matrix
QoS MIB Implementation
This appendix provides information about QoS-based features that are implemented on the Cisco Carrier Routing System line cards and what tables and objects in the QoS MIB support these QoS features. The Cisco Carrier Routing System line card families each have a different QoS implementation. Do not assume that the QoS features across line card families are equivalent. Some of the QOS configuration is done at the PFC2 (policy feature card) level and others at the parallel express forwarding (PXF) processor level in each line card.
This appendix contain the following topics:
•
Implementing the CISCO-CLASS-BASED-QOS-MIB
•
QoS MIB Policy Action Support Matrix
Implementing the CISCO-CLASS-BASED-QOS-MIB
This section describes which objects from the CISCO-CLASS-BASED-QOS-MIB are implemented, which objects are relevant to the features available for the Cisco Carrier Routing System line cards, and which QoS features are supported by each Cisco Carrier Routing System line card.
Table B-1 defines the expected values for Policy Actions.
Table B-1 QoS Policy Action Parameters
Policy Action Definition NotesBandwidth
A rate limiting function. The difference between the highest and lowest frequencies available for network signals. Bandwidth divides the link bandwidth among different traffic streams into multiple queues.
Must be set before you enable WRED. Aggregate bandwidth rate limits match all of the packets on an interface or subinterface. Granular bandwidth rate limits match a particular type of traffic based on precedence, MAC address, or other parameters.
Priority
Priority queuing allows you to assign a guaranteed minimum bandwidth to one queue to minimize the packet delay variance for delay-sensitive traffic.
A routing feature in which frames in an output queue are prioritized based on various characteristics, such as packet size and interface type.
Shape
A shaper typically delays excess traffic using a buffer or queueing mechanism to hold packets and shape the flow when the data rate of the source is higher than expected. (for example, GTS1 uses a weighted fair queue to delay packets to shape the flow, and FRTS2 uses either a PQ3 , a CQ4 , or a FIFO5 queue for the same, depending on how you configure it.)
Shapers identify traffic descriptor violations.
Police
A policer typically drops traffic. (For example, CAR6 rate-limiting policer either drops the packet or rewrites its IP precedence, resetting the packet header type of service bits.)
Policing is the process by which the OSR limits the bandwidth consumed by a flow of traffic. Policing can mark or drop traffic.
Queue limit
Parameter specifies the number of packets held by the queue. It operates on the default packet drop method of congestion management.
A Cisco queuing technique. A flow-based queuing algorithm that creates bit-wise fairness by allowing each queue to be serviced fairly in terms of byte count. For example, if queue 1 has 100-byte packets and queue 2 has 50-byte packets, the WFQ algorithm takes two packets from queue 2 for each one packet from queue 1. This makes service fair for each queue: 100 bytes each time the queue is serviced.
WFQ ensures that queues do not starve for bandwidth and that traffic gets predictable service. Low-volume traffic streams-which comprise the majority of traffic-receive increased service, transmitting the same number of bytes as high-volume streams. This behavior results in what appears to be preferential treatment for low-volume traffic, when in actuality it is creating fairness.
Fair queue
Traffic shaping smooths traffic by storing traffic above the configured rate in a queue. When a packet arrives at the interface for transmission, the following happens:
•
If the queue is empty, the arriving packet is processed by the traffic shaper.
•
If possible, the traffic shaper sends the packet. Otherwise, the packet is placed in the queue.
•
If the queue is not empty, the packet is placed in the queue.
When there are packets in the queue, the traffic shaper removes the number of packets it can transmit from the queue at each time interval.
A Cisco queuing technique. A flow-based queuing algorithm that creates bit-wise fairness by allowing each queue to be serviced fairly in terms of byte count. For example, if queue 1 has 100-byte packets and queue 2 has 50-byte packets, the WFQ algorithm takes two packets from queue 2 for each one packet from queue 1. This makes service fair for each queue: 100 bytes each time the queue is serviced.
WRED7
Action that randomly discards packets during IP precedence settings congestion.
Precedence is a value of 0 to 7 where zero is low priority traffic and 7 represents high priority traffic.
Set (precedence)
The IP precedence (QoS) bits in the packet header are rewritten. The packet is then transmitted. You can use this action to either color (set precedence) or recolor (modify existing packet precedence) the packet.
—
1 GTS = Generic Traffic Shaping
2 FRTS = Frame Relay Traffic Shaping
3 PQ = Priority Queue
4 CQ = Custom Queue
5 FIFO = first in, first out
6 CAR = Commited Access Rate
7 WRED = Weighted Random Early Detection
Notes About QoS:
•
Congestion-management tools include priority queuing (PQ), custom queuing (CQ), weighted fair queuing (WFQ), and class-based weighted fair queuing (CBWFQ).
•
Police and shape are traffic regulation mechanisms:
–
Shaping is used to create a traffic flow that limits the full bandwidth potential of the flows. This is used many times to prevent the overflow problem. For instance, many network topologies use Frame Relay in a hub-and-spoke design. In this case, the central site normally has a high-bandwidth link (such as T1), while remote sites have a low-bandwidth link in comparison (such as 384 Kbps). In this case, it is possible for traffic from the central site to overflow the low bandwidth link at the other end. Shaping is a good way to pace traffic closer to 384 Kbps to avoid the overflow of the remote link. Traffic above the configured rate is buffered for transmission later to maintain the rate configured.
–
Policing is similar to shaping, but it differs in one important way; traffic that exceeds the configured rate is not buffered (and normally is discarded).
QoS MIB Policy Action Support Matrix
The tables in this section describe which objects from the CISCO-CLASS-BASED-QOS-MIB are implemented and which ones are relevant to the different features available for the Cisco Carrier Routing System line cards. The tables are divided into objects on the Cisco Carrier Routing System platform that are:
•
Supported, implemented, and instrumented (works as defined in the MIB)—Table B-3
•
Not supported or support is limited—Table B-4
![]()
Note
The following tables are to be considered examples only as they relate to the ASR 9K.
Table B-2 lists the definitions of the values that are returned by objects listed in Table B-3 and Table B-4. Policy actions are dependent on return values.
Table B-3 lists QoS MIB table objects that are supported and implemented on the Cisco ASR 9000 Series router platform and the QoS policy actions that these objects support.
Table B-4 lists QoS MIB table objects that are unsupported or have limited support on the Cisco ASR 9000 Series router platform and the QoS policy actions that these objects support.