Advertisement
Quick Links
AlliedWare Plus
How To |
Configure QoS on x900-24, x900-12, and
SwitchBlade x908 Series Switches
Introduction
This document describes some generic configuration examples for Quality of Service (QoS)
on the AlliedWare Plus OS.
What information will you find in this document?
This document provides information in the following sections:
•
1. Setting the egress rate‚ on page 2
•
2. Setting the priority on a packet‚ on page 7
•
3. Setting the egress queues‚ on page 10
•
Full QoS scenario - tiered services for a single customer‚ on page 13
Which product and software version does this information apply to?
This How To Note applies to the following Allied Telesis switches, running the
AlliedWare Plus OS software version 5.2.1 or later:
•
SwitchBlade x908
•
x900 series
C613-16112-00 REV A
TM
OS
www.alliedtelesis.com
Advertisement
Related Manuals for Allied Telesis Switchblade AT-x900-12
Summary of Contents for Allied Telesis Switchblade AT-x900-12
- Page 1 Full QoS scenario - tiered services for a single customer‚ on page 13 Which product and software version does this information apply to? This How To Note applies to the following Allied Telesis switches, running the AlliedWare Plus OS software version 5.2.1 or later: •...
- Page 2 1. Setting the egress rate Example 1-1: Setting the egress limit of a switch port Commands: interface port1.0.24 egress-rate-limit 25m These commands will set the egress limit of port 24 to 25Mbps. The granularity is 651kbps. Page 2 | AlliedWare Plus™ OS How To Note: QoS 1.
- Page 3 Example 1-2: setting the maximum bandwidth limit per ingress port Ingress rate limiting cannot be configured on the port per se, but is achieved by creating a QoS policy with a bandwidth limited traffic class, and applying that policy to each port. mls qos enable class-map cmap1 policy-map pmap1...
- Page 4 Example 1-3: Setting the maximum bandwidth limit for each user In example 1-1, we configured an egress rate on ports. But the granularity of that bandwidth limiting was multiples of 651kbps. It is possible to achieve finer-grained limiting using the devices advanced QoS capability.
- Page 5 Example 1-4: Setting the maximum bandwidth limit for each IP subnet This example is very similar to example 1-3, except that it is assumed that a whole subnet is attached to each port, not just a single device on each port. Users connected to the switch downloading files from the Internet (192.168.1.0/24 - 192.168.23.0/24) mls qos enable...
- Page 6 Example 1-5: Setting the maximum bandwidth limit of VLANs Ingress ports 1-20 (these ports are carrying a mixture of VLAN2, VLAN3 and VLAN4 packets, either with or without VLAN tags) mls qos enable class-map cmap2 match vlan 2 class-map cmap3 match vlan 3 class-map cmap4 match vlan 4...
- Page 7 2. Setting the priority on a packet Example 2-1: Setting the Layer 2 (VLAN/802.1p) priority per ingress port Here we assign different 802.1p values to packets arriving on different ports. These values are also known as the Layer 2 (L2) or VLAN priority. Ingress ports 1-20 (these ports MAY be carrying a mixture of packets from different VLANs, either with or without VLAN tags) mls qos enable...
- Page 8 Example 2-2: Setting the Layer 2 (VLAN/802.1p) priority per VLAN Ingress ports 1-20 (these ports MAY be carrying a mixture of VLAN2, VLAN3, and VLAN4 packets either with or without VLAN tags) mls qos enable class-map cmap2 match vlan 2 class-map cmap3 match vlan 3 class-map cmap4...
- Page 9 Example 2-3: Setting the Layer 3 (TOS/DCSP) priority per ingress port Use the same configuration provided in Example 2-1 on set cos <cos-value> set dscp <dscp-value> Example 2-4: Setting the Layer 3 (TOS/DSCP) priority per VLAN Use the same configuration provided in Example 2-2 on set cos <cos-value>...
- Page 10 3. Setting the egress queues In this section we look at methods for directing certain packets into certain queues on the egress port. Example 3-1: Setting the egress queue according to the L2 priority of the incoming packet The priority-to-queue map is a straightforward method for assigning packets to egress queues on the basis of the packets’...
- Page 11 Example 3-2: Setting the egress queue according to the ingress port Ingress ports 1-20 (these ports MAY be carrying a mixture of packets from different VLAN packets either with or without VLAN tags) mls qos enable class-map cmap1 policy-map pmap1 class cmap1 set queue 6 policy-map pmap2...
- Page 12 Example 3-3: Configuring WRR for egress queues This example is used for configuring WRR on egress queues according to the ingress port of the traffic. Ingress ports 1-3 (these ports MAY be carrying a mixture of packets from different VLAN packets either with or without VLAN tags) class-map cmap1 policy-map pmap1 class cmap1...
- Page 13 Full QoS scenario - tiered services for a single customer In this section, we will build up a relatively complex QoS configuration to support a scenario requiring quite precise control over the traffic passing through the switch. The scenario is an ISP providing connectivity for a customer, and offering different levels of service for different types of traffic.
- Page 14 Identify the types of traffic The different categories of traffic will be identified by the DSCP values in the packets' headers. It is up to the customer to mark the packets with the appropriate DSCP values. The DSCP values belonging to the different traffic categories are: Gold Silver Bronze...
- Page 15 Set the required properties on the egress queues What is required is that: • Gold traffic ALWAYS has precedence over Silver or Bronze traffic. So, when a Gold packet arrives at the egress port, it is transmitted immediately, irrespective of how many Silver or Bronze packets might be queued up.
- Page 16 534182 T: +65 6383 3832 F: +65 6383 3830 Allied Telesis is a trademark or registered trademark of Allied Telesis, Inc. in the United States and other countries. T: +1 800 424 4284 F: +1 425 481 3895 F: +41 91 69769.11...