Download ExtremeWare Software User Guide

TRAFFIC GROUPINGS
AND
CREATING
A
QOS POLICY
The following example illustrates basic precedence within IPQoS. It configures the
following two IPQoS groupings:
config ipqos add 10.1.2.3/32 qp4
config ipqos add 10.1.2.0/24 qp3
All traffic containing 10.1.2 as the first 24 bits of the destination IP address are assigned
to the QoS profile qp3, except traffic that is destined for the station 10.1.2.3, which is
assigned to the profile qp4.
The following example provides a more detailed illustration of precedence within
IPQoS. The following two groupings are configured:
config ipqos add tcp 10.1.2.3/32 10.2.3.4/32 qp4
config ipqos add tcp 10.1.2.0/24 10.2.3.5/32 qp5
In this example, all TCP traffic from 10.2.3.4 destined for 10.1.2.3 uses the profile qp4.
All TCP traffic from 10.2.3.5 destined for 10.1.2.3 uses the profile qp3.
IPQOS
AND
MULTICAST ADDRESSES
IP multicast addresses can be used as a traffic grouping by specifying the long form of
the IPQoS command. For example, suppose any destination multicast address to
227.x.x.x using UDP packets from a particular server (IP address 10.2.3.4) needs to be
prevented from being routed. The example command is as follows:
config ipqos add udp 227.0.0.0/8 10.2.3.4/32 blackhole
Because this is using an IP multicast destination, it is also possible to define a range of
source IP addresses. Using the previous example, assume, instead, anything from a
subnet starting with 10.x.x.x must be prevented. The example command is as follows:
config ipqos add udp 227.0.0.0/8 10.2.3.4/8 blackhole
The ability to configure a traffic grouping for the 224.0.0.x set of reserved IP
multicast streams is not allowed.
VERIFYING IPQOS
SETTINGS
To verify settings made for IPQoS traffic groupings, use the command:
show ipqos
EXTREMEWARE SOFTWARE USER GUIDE
8-11