IBM 12.1(22)EA6 User Manual
23-3
Cisco Systems Intelligent Gigabit Ethernet Switch Modules for the IBM BladeCenter, Software Configuration Guide
24R9746
Chapter 23 Configuring QoS
Understanding QoS
Figure 23-1
QoS Classification Layers in Frames and Packets
All switches and routers that access the Internet rely on the class information to give the same
forwarding treatment to packets with the same class information and different treatment to packets with
different class information. The class information in the packet can be assigned by end hosts or by
switches or routers along the way, based on a configured policy, detailed examination of the packet, or
both. Detailed examination of the packet is expected to happen closer to the edge of the network so that
the core switches and routers are not overloaded.
forwarding treatment to packets with the same class information and different treatment to packets with
different class information. The class information in the packet can be assigned by end hosts or by
switches or routers along the way, based on a configured policy, detailed examination of the packet, or
both. Detailed examination of the packet is expected to happen closer to the edge of the network so that
the core switches and routers are not overloaded.
Switches and routers along the path can use the class information to limit the amount of resources
allocated per traffic class. The behavior of an individual device when handling traffic in the DiffServ
architecture is called per-hop behavior. If all devices along a path have a consistent per-hop behavior,
you can construct an end-to-end QoS solution.
allocated per traffic class. The behavior of an individual device when handling traffic in the DiffServ
architecture is called per-hop behavior. If all devices along a path have a consistent per-hop behavior,
you can construct an end-to-end QoS solution.
Implementing QoS in your network can be a simple or complex task and depends on the QoS features
offered by your internetworking devices, the traffic types and patterns in your network, and the
granularity of control that you need over incoming and outgoing traffic.
offered by your internetworking devices, the traffic types and patterns in your network, and the
granularity of control that you need over incoming and outgoing traffic.
Basic QoS Model
shows the basic QoS model. Actions at the ingress interface include classifying traffic,
policing, and marking:
•
Classifying distinguishes one kind of traffic from another. For more information, see the
•
Policing determines whether a packet is in or out of profile according to the configured policer, and
the policer limits the bandwidth consumed by a flow of traffic. The result of this determination is
passed to the marker. For more information, see the
the policer limits the bandwidth consumed by a flow of traffic. The result of this determination is
passed to the marker. For more information, see the
•
Marking evaluates the policer and configuration information for the action to be taken when a packet
is out of profile and decides what to do with the packet (pass through a packet without modification,
mark down the DSCP value in the packet, or drop the packet). For more information, see the
is out of profile and decides what to do with the packet (pass through a packet without modification,
mark down the DSCP value in the packet, or drop the packet). For more information, see the
111386
Encapsulated Packet
Layer 2
header
IP header
Data
Layer 2 802.1Q and 802.1p Frame
Preamble
Start frame
delimiter
DA
Len
SA
Tag
PT
Data
FCS
Layer 3 IPv4 Packet
Version
length
ToS
(1 byte)
ID
Offset TTL
Proto FCS IP-SA IP-DA Data
3 bits used for CoS (user priority)
DSCP