Allied Telesis AlliedWare Plus Overview
Allied Telesis AlliedWare Plus Overview

Allied Telesis AlliedWare Plus Overview

Overview of quality of service features
Hide thumbs Also See for AlliedWare Plus:

Advertisement

AlliedWare Plus
Overview of |

Introduction

This How To Note describes the main features of QoS on switches running the
AlliedWare Plus OS. The main features include:
Prioritisation and marking
Right at the point of ingress into the QoS process, packets classified to particular class
maps can have values written to one or more of their associated "markers". The markers
can be externally visible fields (DSCP value, 802.1p value) and/or internally visible fields
(bandwidth class and queue number). These markers are explained in
page
Policing
Packets belonging to any given class map can be assigned a colour (bandwidth class) based
on whether they are inside or outside the bandwidth limits set for that class map. The
packets are marked with the colour that was applied to them, and at various points in the
QoS process, decisions on the packets' fate can be made on the basis of what colour they
have been marked with.
Remarking
After policing, remarking can update packets' QoS markers depending on how well the
flow conforms to its bandwidth limits. For example, if a flow exceeds its bandwidth
requirements, QoS can update the packets' DSCP values.
Per-port control over egress queue parameters
Queue lengths, scheduling process, relative weights, etc can be set on all queues on a per-
port basis.
Highly configurable default class map
All the parameters that can be set on a normal class map can also be set on the default
class map (the catch-all class map that matches all traffic that does not explicitly match any
other class map).
C613-16120-00 REV A
TM
OS
Quality of Service Features on x900-12,
x900-24, and SwitchBlade x908 Switches
4.
"Packet markers" on
www.alliedtelesis.com

Advertisement

Table of Contents
loading

Summary of Contents for Allied Telesis AlliedWare Plus

  • Page 1: Introduction

    Introduction This How To Note describes the main features of QoS on switches running the AlliedWare Plus OS. The main features include: Prioritisation and marking Right at the point of ingress into the QoS process, packets classified to particular class maps can have values written to one or more of their associated “markers”.
  • Page 2: Table Of Contents

    5: Policing combined traffic types on combined ports ... 37 Fabric QoS ... 38 Mapping the queues in the switching instances to queues in the fabric ... 39 Scheduling the queues within the fabric ... 40 Page 2 | AlliedWare Plus™ OS: Overview of QoS...
  • Page 3: Which Products And Software Version Does This Note Apply To

    Page 3 | AlliedWare Plus™ OS: Overview of QoS...
  • Page 4: Packet Markers

    QoS process and lines up in one of the queues at its eventual egress port. Page 4 | AlliedWare Plus™ OS: Overview of QoS...
  • Page 5: Outline Of The Qos Processing Flow

    The net effect of this process is to set a value on the Egress Queue marker that the packet is carrying. Page 5 | AlliedWare Plus™ OS: Overview of QoS Packet Ingress port Tagged: priority mapped to queue...
  • Page 6: Classification

    DSCP value that QoS will use for look-ups for all packets that match the class map. Whichever of these two criteria is used, the value is used to index the mark-dscp map. Page 6 | AlliedWare Plus™ OS: Overview of QoS "Premarking" on page 13 for a table...
  • Page 7: Policing

    QoS properties for the packet (that is, new values for the DSCP, VLAN tag user priority, bandwidth class, and egress queue can be specified). The new values are taken from the user-configurable policed-dscp map. Page 7 | AlliedWare Plus™ OS: Overview of QoS...
  • Page 8: Queue Shaping

    This is done for each of the three bandwidth classes. Obviously, the queue-length threshold for bandwidth class red should be set at a relatively low value, with the other bandwidth classes having progressively higher values. Page 8 | AlliedWare Plus™ OS: Overview of QoS...
  • Page 9: Scheduling

    When queues 7, 6 & 5 are all completely empty, queues 4, 3 & 2 will be emptied concurrently based on their respective weights. Queues 1 & 0 will be emptied only when there are no packets awaiting transmission in any of the other queues. Page 9 | AlliedWare Plus™ OS: Overview of QoS...
  • Page 10: Details Of The Component Processes, And How To Configure Them

    <name> awplus(config-pmap)#class default Page 10 | AlliedWare Plus™ OS: Overview of QoS Port policy-map class-map...
  • Page 11: Diagram Of The Overall Qos Process Flow

    The following figure summarises the QoS process flow and the commands to configure each stage. The following sections describe the configuration in detail. When using trust dscp and set dscp Page 11 | AlliedWare Plus™ OS: Overview of QoS Tagged packets: set egress queue mls qos map cos-queue...
  • Page 12: Enabling Qos Globally

    Untagged packets are also assigned a CoS value, 0 by default. To change this, first enter interface mode for the desired port and then specify the desired CoS. Use the following commands: Page 12 | AlliedWare Plus™ OS: Overview of QoS 13) or Remarking (page...
  • Page 13: Classification

    Page 13 | AlliedWare Plus™ OS: Overview of QoS What it matches on IP or MAC hardware ACL Class of Service (802.1p value)
  • Page 14 In each cell of the table there are four new marker values that will be applied to packets: 802.1p, DSCP, bandwidth class and egress queue. The following table shows the structure of the mark-dscp map. DSCP Page 14 | AlliedWare Plus™ OS: Overview of QoS New marker values 802.1p = ... new-dscp = ...
  • Page 15 DSCP value that will be marked into all packets that match the class map (as described "Setting new values explicitly" on page Page 15 | AlliedWare Plus™ OS: Overview of QoS 14).
  • Page 16: Policing

    Both ordinary and aggregate policers can be either single-rate or twin-rate. With the AlliedWare Plus OS, you explicitly select whether to use a single-rate or twin-rate policer. The following sections summarise the policing options, and tell you how to configure them.
  • Page 17 To see the settings of aggregate policers, use the command: awplus#show mls qos aggregate-policer Page 17 | AlliedWare Plus™ OS: Overview of QoS...
  • Page 18 <average-bandwidth> <minimum-burstsize> <maximum-burstsize> exceed-action {drop|policed-dscp-transmit} An exceed action of drop means that the switch simply drops red packets. An exceed action of policed-dscp-transmit means that the switch remarks packets after policing. Page 18 | AlliedWare Plus™ OS: Overview of QoS...
  • Page 19 For a more detailed explanation of the algorithm, see the Advanced QoS White Paper in the White Papers library at www.alliedtelesis.com/resources/literature/literature.aspx?id=3. An example of configuring a policer to do twin-rate policing would be: awplus(config-pmap-c)#police twin-rate <minimum-bandwidth> <maximum-bandwidth> <minimum-burstsize> <maximum-burstsize> exceed-action {drop|policed-dscp-transmit} Page 19 | AlliedWare Plus™ OS: Overview of QoS...
  • Page 20 Interface: Class-map: Aggregate Bytes: Green Bytes: Yellow Bytes: Red Bytes: Dropped Bytes: Class-map: Aggregate Bytes: Green Bytes: Yellow Bytes: Red Bytes: Dropped Bytes: Page 20 | AlliedWare Plus™ OS: Overview of QoS port1.0.20 default vlan2 "Applying ordinary policers to class...
  • Page 21 Red Bytes: Dropped Bytes: Aggregate name: Class-map: Aggregate Bytes: Green Bytes: Yellow Bytes: Red Bytes: Dropped Bytes: Page 21 | AlliedWare Plus™ OS: Overview of QoS port1.0.1 default examplePolicer cmap1 cmap2 (port1.0.1) cmap1 cmap2 (port1.0.2) port1.0.2 default examplePolicer cmap1 cmap2 (port1.0.1) cmap1 cmap2 (port1.0.2)
  • Page 22: Remarking

    <maximum-bandwidth> <minimum-burstsize> <maximum-burstsize> exceed-action policed-dscp-transmit Although the keyword is named exceed-action, setting it to policed-dscp-transmit makes QoS remark all matching traffic, not just excessive traffic. Page 22 | AlliedWare Plus™ OS: Overview of QoS Green Yellow 802.1p = ... 802.1p = ...
  • Page 23: Queue Shaping-Queue Sets, Red, And Tail-Drop

    The unused queue sets are empty, so all their values are 0. Port speed Page 23 | AlliedWare Plus™ OS: Overview of QoS Setting Minimum threshold...
  • Page 24 Effectively, the drop probability defines how quickly the rate of dropping packets must increase as the queue length grows from the minimum threshold to the maximum threshold. Page 24 | AlliedWare Plus™ OS: Overview of QoS Setting Minimum threshold...
  • Page 25 You can configure the queue-set parameters for all 8 egress queues, or for any subset of the egress queues. Configuring a subset lets you configure different queue shaping settings for different queues on a port. Page 25 | AlliedWare Plus™ OS: Overview of QoS Class 3 Class 2...
  • Page 26 This may prevent global TCP synchronisation, but will drop more packets. The recommended averaging factor is 9. Page 26 | AlliedWare Plus™ OS: Overview of QoS page 100% 12.5%...
  • Page 27: Scheduling

    The following sections describe how to configure all these aspects of scheduling. To configure scheduling, first enter interface configuration mode for the desired port or ports. Page 27 | AlliedWare Plus™ OS: Overview of QoS 23). If you need to explicitly set a port to tail-drop mode, or if you...
  • Page 28 By default, each queue is limited to 12%, but you can change this by using the following command: wrr-queue queue-limit <1-100> <1-100> <1-100> <1-100> <1-100> <1-100> <1-100> <1-100> Page 28 | AlliedWare Plus™ OS: Overview of QoS "Egress bandwidth limiting" on page...
  • Page 29: Egress Bandwidth Limiting

    Page 29 | AlliedWare Plus™ OS: Overview of QoS...
  • Page 30: Policing Examples

    Policing is the process of counting the number of packets that the switch processes and determining their level of conformance with their bandwidth limits. The AlliedWare Plus OS enables you to police ports and different types of traffic separately (with “ordinary” policers) or in combination (with aggregate policers).
  • Page 31 3000 200 4000 exceed-action drop interface port1.3.1-1.3.3 service-policy input pm1 The restricted traffic types are identified by ACLs (which could match, for example, by address or TCP/UDP port). Page 31 | AlliedWare Plus™ OS: Overview of QoS...
  • Page 32: 2: Policing One Traffic Type On Combined Ports

    The restricted traffic type is identified by an ACL (which could match, for example, by TCP/ UDP port). Page 32 | AlliedWare Plus™ OS: Overview of QoS match access-group class <name> class-map match <parameter>...
  • Page 33: 3: Policing One Traffic Type On Separate Ports, And Another Traffic Type On The Same Ports Combined

    The following figure shows this kind of scenario. match match aggregate policer policer match match Page 33 | AlliedWare Plus™ OS: Overview of QoS match access-group class <map-name> class-map 1 match <parameter> police aggregate <name> police single-rate or police twin-rate class <map-name>...
  • Page 34 The VoIP traffic is identified by having a DSCP value of 35, and the web traffic by matching an ACL (which could match on TCP port). Page 34 | AlliedWare Plus™ OS: Overview of QoS...
  • Page 35: 4: Policing Combined Traffic Types On Separate Ports

    1 match match match match aggregate policer 2 match match Page 35 | AlliedWare Plus™ OS: Overview of QoS match access-group match <parameter> class <map-name> class-map 1 police aggregate <name> class <map-name> class-map 2 class-map 1 class-map 2...
  • Page 36 If you used the same policer on multiple ports, you would have to use different class maps, or else the policer would aggregate the traffic across your ports. Page 36 | AlliedWare Plus™ OS: Overview of QoS...
  • Page 37: 5: Policing Combined Traffic Types On Combined Ports

    The following figure shows this scenario. match match aggregate policer match match Page 37 | AlliedWare Plus™ OS: Overview of QoS match access-group class <map-name> class-map 1 match <parameter> police aggregate <name> class <map-name> class-map 2 port...
  • Page 38: Fabric Qos

    However, in some networks, you need to tweak these settings to achieve a consistent end-to-end QoS processing when packets are passing from one switching instance to another. Let us consider each of these processes in turn. Page 38 | AlliedWare Plus™ OS: Overview of QoS...
  • Page 39: Mapping The Queues In The Switching Instances To Queues In The Fabric

    When the packet reaches the port that it will actually egress, it goes into the egress queue that the standard QoS system had assigned it to. In other words, the fabric queue does not affect the final egress queue. Page 39 | AlliedWare Plus™ OS: Overview of QoS Fabric queue Fabric queue...
  • Page 40: Scheduling The Queues Within The Fabric

    Singapor e 534182 T: +65 6383 3832 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...

Table of Contents