Speedtouch IPQoS Configuration Manual

Wireless business dsl router

Advertisement

Quick Links

SpeedTouch™
(Wireless) Business DSL Router
IPQoS Configuration Guide
Release R5.3.0
SpeedTouch™608WL and
SpeedTouch™620 only

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the IPQoS and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for Speedtouch IPQoS

  • Page 1 SpeedTouch™ (Wireless) Business DSL Router IPQoS Configuration Guide Release R5.3.0 SpeedTouch™608WL and SpeedTouch™620 only...
  • Page 3 SpeedTouch™ IPQoS Configuration Guide R5.3.0...
  • Page 4 "Wi-Fi Protected Access" are trademarks of the Wi-Fi Alliance. Other products may be trademarks or registered trademarks of their respective manufacturers. Document Information Status: v0.5 (March 2005) Reference: E-NIT-CTC-20041213-0013 Short Title: IPQoS Configuration Guide STBUS R5.3.0...
  • Page 5: Table Of Contents

    Contents Contents About this IPQoS Configuration Guide...... 7 1 Document scope ............9 2 Introduction ..............11 What is Quality of Service? ............12 Relative versus Guaranteed QoS..........14 3 Basic QoS Concepts............ 15 Precedence and TOS ..............16 Differentiated Services ..............18 Classification and conditioning principles........
  • Page 6 Define a relation between chains ..............51 Expressions .................. 52 5.5.1 Expression parameters .................. 53 6 Meters, queues and IPQoS......... 59 Meters and queues ............... 60 The IPQoS command group ............61 EF timers ..................63 Meter command group..............67 6.4.1...
  • Page 7 Configuring labels and rules for Interactive traffic..... 92 IPQoS configuration..............95 8 Scenario 2: Business user with TOS marking..97 Labels ................... 99 Rules..................103 IPQoS per PVC ................112 9 Scenario 3: Metering..........115 E-NIT-CTC-20041213-0013 v0.5...
  • Page 8 Contents E-NIT-CTC-20041213-0013 v0.5...
  • Page 9: About This Ipqos Configuration Guide

    This routing configuration guide explains how routes can/must be used in guide SpeedTouch™ R5.3 products. To explain the use of routes, a distinction is made between standard IP forwarding and packet-based classification. All examples start from a clean SpeedTouch™ configuration.
  • Page 10 About this IPQoS Configuration Guide E-NIT-CTC-20041213-0013 v0.5...
  • Page 11: Document Scope

    1 Document scope Introduction The SpeedTouch™ Release 5.3.0 has a strong Quality of Service (QoS) base that allows classification and forwarding of data to a single or multiple ATM VPI/VCIs with each a set of ATMQoS parameters. IP Quality of Service is an extension to this QoS framework.
  • Page 12 Chapter 1 Document scope E-NIT-CTC-20041213-0013 v0.5...
  • Page 13: Introduction

    Chapter 2 Introduction 2 Introduction Introduction This chapter gives a general description and use of Quality of Service. In this chapter Topic Page 2.1 What is Quality of Service? 2.2 Relative versus Guaranteed QoS E-NIT-CTC-20041213-0013 v0.5...
  • Page 14: What Is Quality Of Service

    Chapter 2 Introduction 2.1 What is Quality of Service? Definition Quality of Service is the ability for an application to obtain the network service it requires for successful operation. Nowadays the total amount of data traffic increases, while new types of data emerge, like: voice data, video data, audio data.
  • Page 15 Chapter 2 Introduction Bandwidth versus QoS Quality of Service is really best noticed when the Best Effort service encounters congestion. So a common question is "why not provide more bandwidth, use Best Effort, and get rid of complicated QoS architectures?" There are four answers: First of all, it is less economic to use more bandwidth than to use QoS.
  • Page 16: Relative Versus Guaranteed Qos

    Chapter 2 Introduction 2.2 Relative versus Guaranteed QoS Types of QoS There are two different approaches to achieve QoS: Guaranteed QoS: Measurable connection parameters are specified for certain data or for a connection, for example a guaranteed amount of bandwidth or delay across the network.
  • Page 17: Basic Qos Concepts

    Chapter 3 Basic QoS Concepts 3 Basic QoS Concepts Introduction This chapter provides a brief explanation about: Basic concepts of Quality of Service in general. Precedence and TOS in general The Differentiated Services architecture in detail In this chapter Topic Page 3.1 Precedence and TOS 3.2 Differentiated Services...
  • Page 18: Precedence And Tos

    Chapter 3 Basic QoS Concepts 3.1 Precedence and TOS Introduction There are two generations of quality of service architectures in the Internet Protocol. The interpretation of the in the Internet Protocol header varies Type of Service Octet between these two generations. The figure below shows the Internet Protocol header.
  • Page 19 Chapter 3 Basic QoS Concepts Precedence values The table below gives the values: precedence Precedence Purpose Routine Priority Immediate Flash Flash Override CRITIC/ECP Internetwork Control Network Control Note that IP Precedence is obsolete and is only implemented to provide backwards compatibility. Second generation is a selector for router's per-hop behaviours.
  • Page 20: Differentiated Services

    Differentiated Services is a framework for scalable service discrimination and allows an approach to modular IPQoS objectives for the needs of various types of applications. The premise to DiffServ networks is that routers within the core of the network are capable to forward the packets of different traffic streams in different Per-Hop Behaviours (PHB).
  • Page 21 The boundary nodes are the access routers and edge routers that directly peer with customers (either individual users or other ISPs). SpeedTouch™ as boundary node Router at ISP as interior node Interior nodes only connect to other interior nodes or boundary nodes within the same DiffServ domain.
  • Page 22: Classification And Conditioning Principles

    Chapter 3 Basic QoS Concepts 3.3 Classification and conditioning principles Introduction Packets go through a number of phases as they transit the network: classification, marking, shaping, policing and queuing. These phases can occur a number of times at each QoS-aware router in the path of the packet. For example, a host might mark outgoing traffic as "best effort", "scavenger", "discard at edge"...
  • Page 23 Chapter 3 Basic QoS Concepts Marking Once classified, a packet is marked to avoid repeated re-classifications. The marking is made to the Differentiated Services Code Point (DSCP). The DSCP is trusted by later routers, so that the high cost of classifying traffic occurs only once. Shaping At the outgoing network edge, traffic is shaped to meet the traffic contract.
  • Page 24: Differentiated Services Code Point (Dscp)

    Chapter 3 Basic QoS Concepts 3.4 Differentiated Services Code Point (DSCP) Introduction A small bit-pattern, called the DS field, in each IP packet is used to mark the packets that should receive a particular forwarding treatment. The DS field uses the space of the former ToS byte in the IPv4 IP header and the traffic class byte in the IPv6 header.
  • Page 25 Chapter 3 Basic QoS Concepts Default PHB The Default PHB is the common, best-effort forwarding behaviour, available in existing routers as standardized in RFC1812. All IP packets which do not belong to any particular BA are considered to belong to this BA. In practice, the traffic in this aggregate is treated as Best Effort traffic.
  • Page 26 Chapter 3 Basic QoS Concepts Assured Forwarding The Assured Forwarding (AF) PHB group allows a provider to offer different levels of forwarding assurances for IP packets. The delivery of IP packets is provided in four (AF) PHB Group: independently forwarded AF classes (AF1x through AF4x). Each AF class is allocated a certain amount of forwarding resources (buffer space and bandwidth) in a DS node.
  • Page 27: Ip Qos Framework Overview

    Chapter 4 IP QoS Framework Overview 4 IP QoS Framework Overview Introduction This chapter presents an overview of the main components of the IP QoS framework within the SpeedTouch™. In this chapter Topic Page 4.1 Main Framework Components 4.2 Resource Management...
  • Page 28: Main Framework Components

    QoS definition. Each label can have an internal QoS class associated with it. Data will experience treatment (queuing and scheduling) according to its QoS class. The SpeedTouch™ Business DSL Router support 16 internal classes which are linked to the 6 queues.
  • Page 29: Resource Management

    Chapter 4 IP QoS Framework Overview 4.2 Resource Management Introduction The RM module reserves memory for four independent traffic classes. Resources are reserved for each RM-class, both in the upstream and in the downstream direction (8 reservations in total). The figure below shows the Resource Management reservations.
  • Page 30 Chapter 4 IP QoS Framework Overview Mapping to internal The RM module maps packets to the an internal class depending on ATM QoS, VLAN priority or DSCP settings. The table below shows the relation between these class settings. Once the mapping to the internal classes has been completed the packet goes through a number of processes like firewall, nat etc.
  • Page 31: Packet Classification And Labelling

    Chapter 5 Packet Classification and Labelling 5 Packet Classification and Labelling Introduction This chapter will explain in detail how packets are classified. This classification is configured via rules in a packet filter mechanism. When a packet hits a rule, it will be marked with the label that is associated with this rule.
  • Page 32: Classification

    Packet Classification and Labelling 5.1 Classification Introduction The basic objective of the Classification module in the SpeedTouch™ is the following: Identifying certain data (on IP or layer 3 level) (called classification) Stating the importance (or priority) of the data, optionally overruling the priority already indicated by the layer 2 network (setting the internal class) The internal class is an internal indication (from 0..15) of the importance/...
  • Page 33: Order Of Classification Rules

    5.1.1 Order of classification rules Introduction The SpeedTouch™ will first check the routing rules and assign a routing-label when a rule is hit. Secondly the packet will go through the QoS rules and a qos-label will be assigned if a rule is hit. So each packet can get two labels assigned.
  • Page 34 Chapter 5 Packet Classification and Labelling Example So, in the example shown in the previous figure, the rules will be applied to incoming packets in the following order: routing labels routing user labels routing default labels qos labels qos user labels qos default labels No rules should be created in the chain _default_labels, because this chain is reserved for automatically created rules that substitute source-routes where...
  • Page 35: Labels

    Chapter 5 Packet Classification and Labelling 5.2 Labels Introduction This section will explain in detail how to configure labels through the CLI. As mentioned before labels are used to assign a user friendly name to a packet for internal usage. The same label can be used in both Routing label rules and QoS label rules.
  • Page 36 Chapter 5 Packet Classification and Labelling Debug command group debug traceconfig stats clear Adding a label Execute the following CLI command to add a label: {Administrator}=>:label add name mylabel The example above will add a label with the name “mylabel” Label parameters Now that we have added a label we can configure its parameters.
  • Page 37: Label Parameters Explained

    16 internal classes. The second part will explain the parameters that need to be set to enable QoS throughout the entire network. Classification The classification parameter determines whether the label classification will set the internal class (used to determine the IPQoS queue). Classification values Description ignore If set to "ignore", the label classification will ignore the...
  • Page 38 Chapter 5 Packet Classification and Labelling Ackclass The ackclass parameter is used to select the DiffServ queue for single ACK segments of a TCP connection. Ackclass values Description 0..15 The internal class number. prioritize If selected the ACK segments will be given a higher priority than the defclass.
  • Page 39 Chapter 5 Packet Classification and Labelling In this case the child connection would be the connection on port 20 of the FTP server. E-NIT-CTC-20041213-0013 v0.5...
  • Page 40: Using Tos, Dscp Or Precedence

    This means that these values are only of significance for outgoing fraffic. The tables below describe the values used when configuring IPQoS by setting the TOS byte, using DSCP or by setting the Precedence bits. type of of IPQoS can be used at the time.
  • Page 41 Chapter 5 Packet Classification and Labelling DSCP When using DSCP the QoS definition is narrowed down to 21 values. This is the most common value used to define QoS. This definition is also backwards compatible with TOS and Precedence. DSCP values Description ef|af11|af12|af13|af2 These are the values that can be used to define the...
  • Page 42: Forwarding Parameters

    Chapter 5 Packet Classification and Labelling 5.2.3 Forwarding parameters. Introduction In this section we will explain the parameters that need to be set to enable packet forwarding throughout the entire network. This means that these values are only of significance for outgoing fraffic. TTLoverwrite The following parameters can be configured for routing purposes.
  • Page 43 Chapter 5 Packet Classification and Labelling Deleting a label Labels can be deleted one by one with the delete command. To delete labels we use the flush command. Execute the following CLI command to delete a specific label: {Administrator}=>:label delete name mylabel force enabled Execute the following CLI command to delete all the labels at once: {Administrator}=>:label flush The flush command offers the possibility to force the deletion of labels that...
  • Page 44: Rules

    This rule applies to data coming from the LAN interface with source address 10.0.0.1 and of the type FTP. Packets matching this rule will be labeled with the label “mylabel” If no index is specified the SpeedTouch™ will automatically use the next available index number . E-NIT-CTC-20041213-0013 v0.5...
  • Page 45: Rules Parameters Explained

    Chapter 5 Packet Classification and Labelling 5.3.1 Rules parameters explained Introduction These are the parameters that can be used to define a rule. We will now have a closer look at these parameters and explain what they are used for. Chain Chain values Description...
  • Page 46 Chapter 5 Packet Classification and Labelling Srcip Srcip values Description private, ssdp_ip, The srcip parameter is used to the source address of mdap_ip, _10.0.0.138, the packet, this can be any ip address. If the source ip _192.168.1.254 parameter is left open any source address is valid. Dstip Dstip values Description...
  • Page 47 Chapter 5 Packet Classification and Labelling Log values Description enable Enables logging when this rule applies. This can be used for debugging. disable Disables logging State State values Description enable Enables this rule. disable Disables this rule. Label Label value Description none If no label needs to be assigned.
  • Page 48 Chapter 5 Packet Classification and Labelling The output of this command will look like this: :label rule add chain=qos_default_labels index=1 serv=sip log=disabled state=enabled label=VoIP :label rule add chain=qos_default_labels index=2 serv=h323 log=disabled state=enabled label=VoIP :label rule add chain=qos_default_labels index=3 serv=telnet log=disabled state=enabled label=Interactive :label rule add chain=qos_default_labels index=4 serv=smtp log=disabled state=enabled label=Interactive...
  • Page 49: Rule Debug Commands

    Chapter 5 Packet Classification and Labelling 5.3.2 Rule debug commands Introduction Under the subgroup rule there is an other subgroup called debug. This subgroup is used to debug the rules. There are only three parameters that can be used here : Traceconfig Traceconfig values Description...
  • Page 50 Chapter 5 Packet Classification and Labelling Stats Execute the following CLI command to show the statistics of all rules. {Administrator}=>:label rule debug stats The output can be refined by adding the chain and index of the rule you want to see the stats from.
  • Page 51: Chains

    Chapter 5 Packet Classification and Labelling 5.4 Chains Introduction A chain or sub-chain can be useful for personal ordering or grouping but is not necessary. You can also place the rules in the _user_labels chain. The following default chains will be configured: Routing_Labels: chain for routing label rules;...
  • Page 52 Chapter 5 Packet Classification and Labelling Delete a chain The chains can be deleted one by one or they can all be deleted with a single command. Execute the following CLI command to delete a single chain: {Administrator}=>:label chain delete chain my_chain Execute the following CLI command to delete all chains at once: {Administrator}=>:label chain flush E-NIT-CTC-20041213-0013 v0.5...
  • Page 53: Define A Relation Between Chains

    Chapter 5 Packet Classification and Labelling 5.4.1 Define a relation between chains Introduction If sub-chains are created manualy they need to be linked to a parent chain, this can be done as follows. Execute the following CLI command to define the relation ship between the chain and the my_chain qos_user_labels...
  • Page 54: Expressions

    Chapter 5 Packet Classification and Labelling 5.5 Expressions Definition Expressions are used in rules for source and destination interface, source and destination IP address (es) (ranges) and services. There are three types of expressions : Interface related expressions. These are expressions related to an interface like: lan, wan,ipoa, pppoe, pppoa etc.
  • Page 55: Expression Parameters

    Chapter 5 Packet Classification and Labelling 5.5.1 Expression parameters Parameters explained In this section we will explain the parameters, used to define an expression, in more detail. Name name value Description string Any given name to identify the expression. Type type value Description intf...
  • Page 56 Chapter 5 Packet Classification and Labelling Bridgeport bridgeport value Description number A bridge port can be selected by using the bridge port number The bridgeport number can be found in the eth subgroup. Under the eth bridge subgroup. Execute the following CLI command to find the bridgeport number: {Administrator}=>:eth bridge iflist The command will give an output like this : : dest : Internal...
  • Page 57 Chapter 5 Packet Classification and Labelling Dscp dscp value Description ef, af11, af12, af13, One of these values can be used to define an af21, af22, af23, af31, expression related to the diffserv code point in the IP af32, af33, af41, af42, packet.
  • Page 58 Chapter 5 Packet Classification and Labelling Srcportend srcportend value Description at-echo, at-nbp, at- One of these or many other ports can be selected to rtmp, at-zis, auth, define an expression related to a source port range. bgp,biff,... number Also a number can be used to define the source port range.
  • Page 59 Chapter 5 Packet Classification and Labelling Icmpcode icmpcode value Description number (0..15) A number can be used to define an expression related to the ICMP code. This value is used to define the start of the ICMP code range. Icmpcodeend icmpcodeend value Description number (0..15)
  • Page 60 Chapter 5 Packet Classification and Labelling List an expression Execute the following CLI command to view a list with all the expressions: {Administrator}=>:expr list The output will look like this : name type flags expression ----------------------------------------------------------------------- DHCP-R_if_0 intf 1. intf=lan1 intf 1.
  • Page 61: Meters, Queues And Ipqos

    Meters, queues and IPQoS 6 Meters, queues and IPQoS Introduction In this chapter we will have a closer look at the IPQoS command group. This command group is used to configure the IPQoS parameters like the meters and queues. In this chapter...
  • Page 62: Meters And Queues

    As seen before in “ Mapping to internal class” the SpeedTouch™ supports up to 6 queues. These queues are used to prioritize data. Each queue handles a range of internal classes. As seen before a packet is associated with an internal class by means of embedded priority indicators as DSCP, VLAN priority or by defining your own specific rules.
  • Page 63: The Ipqos Command Group

    Chapter 6 Meters, queues and IPQoS 6.2 The IPQoS command group Overview The queues,meters and EF timers can be configured through the IPQoS command group. The IPQoS command group contains the following commands and sub groups IPQoS command group ipqos...
  • Page 64 Chapter 6 Meters, queues and IPQoS queue command group queue config list stats clear E-NIT-CTC-20041213-0013 v0.5...
  • Page 65: Ef Timers

    Description intf The IP interface name. state Enable, disable IPQoS EF timer for the interface. timeout The timeout in miliseconds before the MTU goes back to the original value. The MTU of the IP interface in case of EF data.
  • Page 66 Chapter 6 Meters, queues and IPQoS Timeout timeout values Description number (100..10000) The timeout in miliseconds before the MTU goes back to its default value. Each EF packet puts the counter back to 0. mtu values Description number (68..65535) The MTU (Maximum Transmission Unit) to be used for that interface .
  • Page 67 Chapter 6 Meters, queues and IPQoS MTU explained. In this section we will have a closer look at the MTU values and what exactly does it Sometimes it might be usefull to lower the MTU of a link when EF data is to be sent.
  • Page 68 Chapter 6 Meters, queues and IPQoS The table below shows the delay a packet can experience depending on the MTU and link speed. 1024 1500 Bytes Bytes Bytes Bytes Bytes Bytes 18ms 36ms 72ms 144ms 214ms kb/s 16ms 32ms 64ms...
  • Page 69: Meter Command Group

    Adding a meter Execute the following CLI command to add a meter: {Administrator}=>:ipqos meter add name my_meter This command will add a meter with the name “my_meter”. Subsequently we need to configure the meter parameters. The section below shows and explains the different parameters needed to configure a meter.
  • Page 70: Meter Config Command

    In this section we will explian the meter parameters in detail and how to configure a parameters explained meter. Name name value Description string This is the name of the IPQoS meter. Label label value Description BE, DSCP, EF, The label to which the meter applies. Interactive, Management, etc E-NIT-CTC-20041213-0013 v0.5...
  • Page 71 Chapter 6 Meters, queues and IPQoS Intf intf value Description loop, ipoa1, pppoe, The interface to which the meter applies. pppoa, LocalNetwork Droprate droprate value Description number (0..102400) The drop rate in kilobits per second (Kb/s). Packets in excess of this value will be dropped or counted depending on the drop action.
  • Page 72 Chapter 6 Meters, queues and IPQoS If the bucket is already full of tokens, incoming tokens overflow and are not available to future packets. At any time, the largest burst a source can send into the network is roughly proportional to the size of the bucket.
  • Page 73 Chapter 6 Meters, queues and IPQoS Dscp dscp value Description ef, af11, af12, af13, The diffserv code point value to be set. af21, af22, af23, af31, af32, af33, af41, af42, af43, cs0, cs1, cs2, cs3, cs4, cs5, cs6, cs7 or a number...
  • Page 74 The delete command is used to delete a meter from the meters list. For example: the following CLI command will delete the meter with name “test2” from the meter list. {Administrator}=>:ipqos meter delete name my_meter Meter list command The list command will display a list of all meters configured.
  • Page 75 By using the stop command a meter can be deactivated. For example: the command below will stop the meter with name “my_meter” {Administrator}=>:ipqos meter stop name my_meter To check if the meter is stopped or not you can use the list command.
  • Page 76: Packet Flow

    Chapter 6 Meters, queues and IPQoS 6.4.2 Packet flow Illustration The figure below illustrates the packet flow in case label based metering is used. Packet Classification Data Metering Classification Meter Meter Drop Packet is Drop Action dropped Count Mark Mark...
  • Page 77: Queue Command Group

    Queue config command As seen before, the SpeedTouch™ has 6 build-in queues per ATM interface . These queues are pre-defined. The following parameters can be modified by using the config command in the queue subgroup :...
  • Page 78: Queue Config Parameters Explained

    Chapter 6 Meters, queues and IPQoS 6.5.1 Queue config parameters explained In this section we will have a closer look at the different parameters and their values. Dest dest value Description phonebook entry The name of the interface you want to configure.
  • Page 79 Chapter 6 Meters, queues and IPQoS Ackfiltering ackfiltering value Description enabled If the ackfiltering option is enabled duplicate ACK packets in a queue will only be sent once. Meaning that the last duplicate ACK packet will be sent and the...
  • Page 80 The maximum number of packets in the subqueue. As we will see further on there is a parameter in the IPQoS settings maxpackets which sets the max number of packets that can be placed in all queues (0..5) at one time.
  • Page 81 Chapter 6 Meters, queues and IPQoS Resbytes resbytes value Description number (0..64) The reserved subqueue size in kilo bytes (KB). This has the same function as the respackets parameter but uses size in kilo bytes instead of packets. Hold hold value...
  • Page 82 50000 1000 disabled disabled disabled 50000 1000 The example below shows the same command with the use of the dest parameter. {Administrator}=>:ipqos queue list dest atm_pvc_0_35 Name Queue Propagate ECN AckFilter Size Size Reserved Reserved Holdtime Markprob (Packets) (KBytes)
  • Page 83: Ipqos Command Group

    Meters, queues and IPQoS 6.6 IPQoS Command group Introduction The IPQoS command group is used to configure the common parameters for a set of queues instantiaded per interface. ipqos config command The following parameters can be configured in the IPQoS command group:...
  • Page 84: Ipqos Config Parameters Explained

    The name of the interface. Typically, a phonebook entry to which the queues belong. State state value Description enabled This enables IPQoS on the interface disabled This disables IPQoS on the interface The IP QoS policy can only be changed on disconnected (detached) interfaces. Discard...
  • Page 85 Chapter 6 Meters, queues and IPQoS Priority priority value Description strict In case strict is selected as scheduling algorithm, each queue will be served as long as data is present in the queue. This could mean heavy delay. In case WFQ is selected as scheduling algorithm the queues (WFQ4 ..
  • Page 86 25% 25% 25% 25% atm_pvc_8_35 enabled early 25% 25% 25% 25% Now that we have seen all commands to configure IPQoS we will give a few examples on how to use the different commands to get to the desired result. E-NIT-CTC-20041213-0013 v0.5...
  • Page 87: Scenario 1: Residential User

    Chapter 7 Scenario 1: Residential user. 7 Scenario 1: Residential user. Introduction In this chapter describes an example of how IP QoS might be used in a typical residential user scenario. This user uses the following applications: A VoIP device that uses Expedited Forwarding (for example the ST190) A Windows application that uses Assured Forwarding (AF for example Messenger) An interactive Windows application (for example Web surfing)
  • Page 88: Configuring Labels And Rules For Voip

    Via the command line interface (CLI) Via the web interface (GUI) In this chapter we willl use the GUI to configure the SpeedTouch™, at the end of this chapter a CLI command list will be given as well. To enter the GUI open a web browser and surf to the following webpage : http:// 192.168.1.254...
  • Page 89 Chapter 7 Scenario 1: Residential user. Rules Select the IP QoS Rules tab to define one or more rules to get this label assigned to the proper packets. By default only the user defined IP QoS rules are shown. To see the default IP QoS rules click expand In the list that is now shown you will see two rules with label name VoIP.
  • Page 90 TCP (proto=6) with destination port 5060. These two expressions define the protocol and ports used by SIP. Meaning that when UDP traffic on port 5060 is transmitted the SpeedTouch™ knows that this is SIP traffic. This also applies for TCP traffic on port 5060.
  • Page 91 These six expressions define the protocol and ports used by H323. Meaning that when TCP traffic on port 1720 is transmitted the SpeedTouch™ knows that this is H323 traffic. This also applies for UDP traffic on port 1720. By defining these expressions we help the SpeedTouch™...
  • Page 92: Configuring Labels And Rules For Dscp

    Chapter 7 Scenario 1: Residential user. 7.2 Configuring labels and rules for DSCP . Introduction We will now have a closer look at the parameters needed to configure classification for packets with DSCP set. Labels Go to the classification menu and select the Labels tab. Expert mode ->...
  • Page 93 Chapter 7 Scenario 1: Residential user. Expressions We will now have a look at this expression. Therefore go to the expression page and select the Service tab: Expert mode -> IP Router -> Expressions This will show you a list of service expressions defined, if a default configuration is used.
  • Page 94: Configuring Labels And Rules For Interactive Traffic

    Chapter 7 Scenario 1: Residential user. 7.3 Configuring labels and rules for Interactive traffic. Introduction We will now have a closer look at the parameters needed to configure classification for interactive traffic. With interactive traffic we mean traffic like websurfing, e-mail,telnet etc. Labels Go to the classification menu an select the Labels tab: Expert mode ->...
  • Page 95 Chapter 7 Scenario 1: Residential user. Rules Go to the classification menu an select the IP QoS Rules tab: Expert mode -> IP Router -> Classification Here we have to define one or more rules to get this label assigned to the proper packets.
  • Page 96 Chapter 7 Scenario 1: Residential user. Expressions We will now have a look at the http expression. Go to the expression page and select the Service tab. Expert mode -> IP Router -> Expressions This will show you a list of service expressions defined by default. When we click on the + next to the HTTP expression name we can see the definitions used for this expression.
  • Page 97: Ipqos Configuration

    Go to the IP QoS menu and select the Configuration tab. Expert mode -> IP Router -> IP QoS This section on the IPQoS page is used to configure the IPQoS parameters on a per PVC basis. If you click on the arrow on the left side of the PVC name you will see that on the bottom of the page, a list of parameters appears which can be modified.
  • Page 98 Go to the IP QoS menu and select the Queues tab. Expert mode -> IP Router -> IP QoS This section on the IPQoS page is used to configure propagation of the queues, ECN marking and ACK filtering. We do not use propagation, ECN marking or ACK filtering in this scenario.
  • Page 99: Scenario 2: Business User With Tos Marking

    Chapter 8 Scenario 2: Business user with TOS marking. 8 Scenario 2: Business user with TOS marking. Introduction In this chapter we will explain on how IP QoS for a business user can be configured. In our example we will use the following configuration: On the LAN three groups of devices "Gold", "Silver"...
  • Page 100 The “SILVER”segment using IP adresses in the range of 11.0.0.0/24. The “BRONZE” segment using IP adresses in the range of 12.0.0.0/24. We will assume that these three segments are already configured on the SpeedTouch™ (for more information see “SpeedTouch™ user’s guide”. 10.0.0.0/24 GOLD 11.0.0.0/24...
  • Page 101: Labels

    Chapter 8 Scenario 2: Business user with TOS marking. 8.1 Labels Label configuration We will now have a look at the labels that we will need. We have five different classes of traffic, which means that we will need 5 labels: A VoIP label for voice traffic.
  • Page 102 Chapter 8 Scenario 2: Business user with TOS marking. Management label Now we will need to do the same for the Management label. Proceed as followed: Select Management . Set Marking to DSCP. Set the DSCP value to af42. This will enable TOS marking by DSCP, and set the DSCP value to for packets af42 which get this label assigned.
  • Page 103 Chapter 8 Scenario 2: Business user with TOS marking. Silver label To create a label called Silver proceed as followed: On the Label page click new at the bottom. You will now get a configuration screen at the bottom of the page. Set the label name to SILVER.
  • Page 104 Chapter 8 Scenario 2: Business user with TOS marking. Bronze label To create a label called Silver proceed as followed: On the Label page click new at the bottom. You will now get a configuration screen at the bottom of the page. Set Label name to BRONZE.
  • Page 105: Rules

    Chapter 8 Scenario 2: Business user with TOS marking. 8.2 Rules. Rules configuration We will now have a look at the rules that we will need. We will need 8 rules: Two VoIP rules for voice traffic. (SIP and H323). Three Management rules for management traffic.
  • Page 106 Chapter 8 Scenario 2: Business user with TOS marking. VoIP rules We will now add the two VoIP rules to the QoS_user_rule list. Go to the Classification page and select the IP QoS Rules tab. Expert mode -> IP Router -> Classification Then proceed as followed: Click New.
  • Page 107 Chapter 8 Scenario 2: Business user with TOS marking. A second rule needs to be defined for VoIP. This rule will be used for voice packets using the H323 protocol. To do so proceed as followed: Click the New. You will now be able to add a new rule. Set Index to Set Name to VoIP2.
  • Page 108 Chapter 8 Scenario 2: Business user with TOS marking. Management rules Now we will add the three Management rules to the QoS_user_rule list. To do so proceed as followed: Click New . You will now be able to add a new rule. Set Index to Set Name to mngmt1.
  • Page 109 Chapter 8 Scenario 2: Business user with TOS marking. A second rule needs to be defined for Management. This rule will be used for management packets using the ICMP protocol. Click New. You will now be able to add a new rule. Set Index to Set Name to mngmt2.
  • Page 110 Chapter 8 Scenario 2: Business user with TOS marking. A third rule needs to be defined for Management. This rule will be used for management packets using the IKE protocol. Click New. You will now be able to add a new rule. The following values need to be configured: Set Index to 5.
  • Page 111 Chapter 8 Scenario 2: Business user with TOS marking. Gold rule We will now continue by adding the Gold rule to the QoS_user_rule list. Proceed as followed: Click New. You will now be able to add a new rule. Set Index to Set Name to GOLD.
  • Page 112 Chapter 8 Scenario 2: Business user with TOS marking. Silver rule We will now continue by adding the Silver rule to the QoS_user_rule list. Proceed as followed: Click New. You will now be able to add a new rule. Set Index to 7. Set Name to SILVER.
  • Page 113 Chapter 8 Scenario 2: Business user with TOS marking. Bronze rule We will now continue by adding the Bronze rule to the QoS_user_rule list. Proceed as followed: Click New. You will now be able to add a new rule. Set Index to 8. Set Name to BRONZE.
  • Page 114: Ipqos Per Pvc

    Chapter 8 Scenario 2: Business user with TOS marking. 8.3 IPQoS per PVC Introduction Now we need to enable IPQoS on the PVC used to access the internet. In our scenario we will use to access the internet. atm_pvc_0_35 Procedure Proceed as followed: Go to the IP QoS page and select the Configuration tab.
  • Page 115 This can be done in two way’s: By switching the modem off and on again. By opening the Speedtouch menu on the GUI and selecting RESTART This will restart the modem without losing the configuration.
  • Page 116 Chapter 8 Scenario 2: Business user with TOS marking. E-NIT-CTC-20041213-0013 v0.5...
  • Page 117: Scenario 3: Metering

    Chapter 9 Scenario 3: Metering 9 Scenario 3: Metering Introduction To explain interface base metering we will take the setup from the previous scenario. The total upload bandwidth availlable for this scenario is 512Kbps. We reserved 50% of this bandwidth for EF traffic, meaning 256Kbps. Now we would like to limit the bandwidth availlable for the Bronze group to 64Kbps.
  • Page 118 Chapter 9 Scenario 3: Metering We now have a meter configured which will limit the upload bandwidth for the Bronze group to 64Kbps. We still need to start the meter. To do so proceed as followed: Check the status check box. Click Save All to save the changes made.
  • Page 119 Reference List Reference List RFC791 INTERNET PROTOCOL. RFC2475 An Architecture for Differentiated Services. RFC1812 Requirements for IP Version 4 Routers. RFC3140 Per Hop Behavior Identification Codes. RFC3168 The Addition of Explicit Congestion Notification (ECN) to IP. RFC3246 An Expedited Forwarding PHB (Per-Hop Behaviour). RFC3247 Supplemental Information for the New Definition of the EF PHB (Expedited Forwarding Per-Hop Behavior).
  • Page 120 Reference List E-NIT-CTC-20041213-0013 v0.5...
  • Page 121 Abreviation List Abreviation List Available Bit Rate Assured Forwarding Asynchronous Transfer Mode Behavior Agregate Constant Bit Rate Congestion Experienced CDVT Cell Delay Variation Tolerance Command Line Interface Class Selector Denial of Service DSCP Differentiated Services Code Point Explicit Congestion Notification ECN-Capable Transport Expedited Forwarding Generalized Frame Rate...
  • Page 122 Abreviation List E-NIT-CTC-20041213-0013 v0.5...
  • Page 124 Need more help? Additional help is available online at www.speedtouch.com...

Table of Contents