QoS Configuration
Overview
8-2
Overview
The 8100fl switch was designed with Quality of Service (QoS) in mind. QoS is
performed globally and centrally by a scheduler that sees all the queues and
all the priorities for every port. Therefore, the switch only has to queue traffic
once on ingress to schedule traffic through the system, with the result that
wire speed performance is not compromised.
The switch can guarantee bandwidth on an application by application basis,
thus accommodating high-priority traffic even during peak periods of usage.
QoS policies can be broad enough to encompass all the applications in the
network, or relate specifically to a single host-to-host application flow.
Basic QoS Operation
The basic mechanism of QoS is to classify all traffic (in and out), then create
policies to act on these classifications.The classification process uses what is
known as a class map; and the policy process uses what is known as the policy
map.
In addition to the classifier, there is a bandwidth manager, and a WRED
(Weighted Random Early Detection) engine. Once you create a class map and
a policy map, you attach the policy map to an incoming (ingress) port or
outgoing (egress) port – or interface.
For the 8100fl switch, the QoS classifier processes incoming (ingress) traffic.
The bandwidth manager and the WRED engine process outgoing (egress)
traffic. The 8100fl switch also applies special policies on egress using spolicy
commands.
The classifier engine enforces syntax for the policy map statement (what you
see is what you get) making it very easy to use.
These processes are illustrated in
Figure
8-1.