00479812-ME60 Configuration Guide - QoS(V100R006C05_05)

00479812

Quidway ME60 Multiservice Control GatewayV100R006C05

Configuration Guide - QoS

Issue 05

Date 2010-06-01

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2010. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,and recommendations in this document are provided "AS IS" without warranties, guarantees or representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 05 (2010-06-01) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

About This Document

PurposeThis document describes the QoS service supported by the ME60, involving basic knowledge,protocol implementation, configuration procedures, and configuration examples.

For more information about the configuration commands, refer to "QoS Commands" in theQuidway ME60 Multiservice Control Gateway Command Reference.

Related VersionsThe following table lists the product versions related to this document.

Product Name Version

ME60 V100R006C05

Intended AudienceThis document is intended for:

l Commissioning engineer

l Data configuration engineer

l Network monitoring engineer

l System maintenance engineer

OrganizationThis document organized as follows.

Chapter Content

1 Traffic PolicingConfiguration

This chapter describes how to configure traffic policing,including the concept, configuration procedures, andconfiguration examples of traffic policing.

Quidway ME60 Multiservice Control GatewayConfiguration Guide - QoS About This Document


iii

Chapter Content

2 Class-based QoSConfiguration

This chapter describes how to configure the class-based QoS,including the concept, configuration procedures, andconfiguration examples of QoS.

3 QoS SchedulingConfiguration

This chapter describes how to configure QoS scheduling,including the concept, configuration procedures, andconfiguration examples of QoS scheduling.

4 Link Level QoSConfiguration

This chapter describes how to configure the link level QoSfunction, including the concept, configuration procedures,and configuration examples of the link level QoS function.

5 Multicast ShapingConfiguration

This chapter describes how to configure multicast shaping,including the concept, configuration procedures, andconfiguration examples of the multicast shaping function.

6 QPPB Configuration This chapter describes how to configure QPPB, including theconcept, configuration procedures, and configurationexamples of the QPPB function.

7 VPN QoS Configuration This chapter describes how to configure VPN QoS, includingthe concept, configuration procedures, and configurationexamples of the VPN QoS function.

A Glossary This appendix provides the glossary of this document.

B Acronyms andAbbreviations

This appendix lists the acronyms and abbreviationsmentioned in this manual.

Conventions

Symbol ConventionsThe symbols that may be found in this document are defined as follows.

Symbol Description

DANGERIndicates a hazard with a high level of risk, which if notavoided, will result in death or serious injury.

WARNINGIndicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

CAUTIONIndicates a potentially hazardous situation, which if notavoided, could result in equipment damage, data loss,performance degradation, or unexpected results.

About This DocumentQuidway ME60 Multiservice Control Gateway


iv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-06-01)

Symbol Description

TIP Indicates a tip that may help you solve a problem or savetime.

NOTE Provides additional information to emphasize or supplementimportant points of the main text.

General ConventionsThe general conventions that may be found in this document are defined as follows.

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are inboldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are inCourier New.

Command ConventionsThe command conventions that may be found in this document are defined as follows.


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[ ] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated byvertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated byvertical bars. One item is selected or no item is selected.

{ x | y | ... }* Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.

&<1-n> The parameter before the & sign can be repeated 1 to n times.

# A line starting with the # sign is comments.



v

GUI ConventionsThe GUI conventions that may be found in this document are defined as follows.


Boldface Buttons, menus, parameters, tabs, window, and dialog titlesare in boldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">"signs. For example, choose File > Create > Folder.

Keyboard OperationsThe keyboard operations that may be found in this document are defined as follows.

Format Description

Key Press the key. For example, press Enter and press Tab.

Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt+A means the three keys should be pressed concurrently.

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A meansthe two keys should be pressed in turn.

Mouse OperationsThe mouse operations that may be found in this document are defined as follows.

Action Description

Click Select and release the primary mouse button without movingthe pointer.

Double-click Press the primary mouse button twice continuously andquickly without moving the pointer.

Drag Press and hold the primary mouse button and move thepointer to a certain position.

Update HistoryUpdates between document versions are cumulative. Therefore, the latest document versioncontains all updates made to previous versions.

Updates in Issue 05 (2010-06-01)The fifth commercial release. Fixing bugs.

About This DocumentQuidway ME60 Multiservice Control Gateway


vi Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-06-01)

Updates in Issue 04 (2009-10-15)The fourth commercial release. Fixing bugs.

Updates in Issue 03 (2009-07-01)The third commercial release. Fixing bugs.

Updates in Issue 02 (2009-03-01)The second commercial release. Fixing bugs.

Updates in Issue 01 (2008-11-15)Initial commercial release.



vii

Contents

About This Document...................................................................................................................iii

1 Traffic Policing Configuration................................................................................................1-11.1 Introduction.....................................................................................................................................................1-2

1.1.1 Traffic Policing Overview......................................................................................................................1-21.1.2 Traffic Policing Supported by the ME60...............................................................................................1-2

1.2 Configuring Traffic Policing...........................................................................................................................1-31.2.1 Establishing the Configuration Task......................................................................................................1-41.2.2 Configuring the QoS CAR Profile.........................................................................................................1-41.2.3 Applying the QoS CAR Profile..............................................................................................................1-51.2.4 Enabling CAR Traffic Statistics.............................................................................................................1-61.2.5 Configuring VPLS Broadcast Suppression............................................................................................1-71.2.6 (Optional) Configuring the Interval for Collecting Traffic Statistics.....................................................1-71.2.7 Checking the Configuration...................................................................................................................1-8

1.3 Configuring the CPCAR................................................................................................................................. 1-81.3.1 Establishing the Configuration Task......................................................................................................1-81.3.2 Configuring the Traffic Policy for Host Packets....................................................................................1-91.3.3 (Optional) Configuring the Priority Level of Host Packets................................................................... 1-91.3.4 (Optional) Configuring the Conditions for Generating the CPCAR Logs...........................................1-101.3.5 Checking the Configuration.................................................................................................................1-10

1.4 Configuring the Host CAR............................................................................................................................1-111.4.1 Establishing the Configuration Task....................................................................................................1-111.4.2 Configuring the Host CAR...................................................................................................................1-111.4.3 (Optional) Configuring the Conditions for Generating the Host CAR Logs.......................................1-12

1.5 Maintaining Traffic Policing.........................................................................................................................1-121.5.1 Displaying Information About Traffic Policing...................................................................................1-131.5.2 Clearing the Statistics on the Traffic Policing.....................................................................................1-13

1.6 Configuration Examples................................................................................................................................1-141.6.1 Example for Configuring Traffic Policing...........................................................................................1-14

2 Class-based QoS Configuration..............................................................................................2-12.1 Introduction.....................................................................................................................................................2-2

2.1.1 Class-based QoS Overview....................................................................................................................2-22.1.2 Class-based QoS Supported by the ME60............................................................................................. 2-2

Quidway ME60 Multiservice Control GatewayConfiguration Guide - QoS Contents


ix

2.2 Configuring Traffic Policy..............................................................................................................................2-32.2.1 Establishing the Configuration Task......................................................................................................2-32.2.2 Configuring Traffic Classification.........................................................................................................2-42.2.3 Configuring Traffic Behavior.................................................................................................................2-52.2.4 Configuring the Traffic Policy...............................................................................................................2-72.2.5 Applying the Traffic Policy....................................................................................................................2-72.2.6 Checking the Configuration...................................................................................................................2-8

2.3 Configuring the Priority Mapping...................................................................................................................2-92.3.1 Establishing the Configuration Task......................................................................................................2-92.3.2 Creating the Diff-Serv Domain and Mapping the Priority...................................................................2-102.3.3 Adding an Interface to the Diff-Serv Domain......................................................................................2-142.3.4 Adding a Sub-interface to the Diff-Serv Domain................................................................................2-152.3.5 Checking the Configuration.................................................................................................................2-16

2.4 Configuration Examples................................................................................................................................2-162.4.1 Example for Configuring Traffic Classification-based Traffic Policy.................................................2-162.4.2 Example for Configuring Simple Traffic Classification-based Priority Mapping...............................2-20

3 QoS Scheduling Configuration...............................................................................................3-13.1 Introduction.....................................................................................................................................................3-2

3.1.1 QoS Scheduling Overview.....................................................................................................................3-23.1.2 Application in the ME60........................................................................................................................3-2

3.2 Configuring QoS Scheduling..........................................................................................................................3-43.2.1 Establishing the Configuration Task......................................................................................................3-43.2.2 Configuring the Queue Profile...............................................................................................................3-53.2.3 Configuring the Scheduling Profile........................................................................................................3-63.2.4 Configuring the Drop Profile.................................................................................................................3-73.2.5 Configuring the QoS Profile..................................................................................................................3-83.2.6 Creating a VC Group and Binding a QoS Profile to the Group.............................................................3-93.2.7 Creating a VP Group and Binding a QoS Profile to the Group.............................................................3-93.2.8 Configuring QoS Scheduling...............................................................................................................3-103.2.9 Configuring QoS Scheduling on Network-side Interfaces...................................................................3-123.2.10 (Optional) Configuring Port-based Traffic Shaping..........................................................................3-133.2.11 (Optional) Configuring the Forwarding Line Speed of the 10G Board.............................................3-143.2.12 Checking the Configuration...............................................................................................................3-14

3.3 Configuring QoS Scheduling for the Multi-Play Service.............................................................................3-163.3.1 Establishing the Configuration Task....................................................................................................3-173.3.2 Configuring the Family Identification Mode.......................................................................................3-183.3.3 Binding a QoS Profile to a Family Profile...........................................................................................3-183.3.4 (Optional) Setting the Maximum Number of Access Users Allowed by a Family..............................3-193.3.5 (Optional) Excluding Service Traffic of Users in a Domain from the QoS Scheduling of a Family. .3-193.3.6 Binding a QoS Profile to a Domain.....................................................................................................3-203.3.7 Configuring the Service Identification Mode.......................................................................................3-203.3.8 Binding a Family Profile and a Service Identification Policy to a BAS Interface...............................3-22

ContentsQuidway ME60 Multiservice Control Gateway


x Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-06-01)

3.3.9 Checking the Configuration.................................................................................................................3-233.4 Configuring the L2TP HQoS........................................................................................................................3-24

3.4.1 Establishing the Configuration Task....................................................................................................3-253.4.2 Configuring the Scheduling Profile......................................................................................................3-253.4.3 Configuring the QoS Profile................................................................................................................3-263.4.4 Applying the QoS Profile to the Domain.............................................................................................3-263.4.5 Configuring the L2TP HQoS Scheduling Mode..................................................................................3-273.4.6 Checking the Configuration.................................................................................................................3-28

3.5 Configuration Examples................................................................................................................................3-283.5.1 Example for Configuring QoS Scheduling in Router Mode................................................................3-283.5.2 Example for Configuring QoS Scheduling in PE Mode......................................................................3-323.5.3 Example for Configuring QoS Scheduling in QoD Mode...................................................................3-363.5.4 Example for Configuring QoS Scheduling in DSG Mode...................................................................3-413.5.5 Example for Configuring the Multi-Play Service................................................................................3-463.5.6 Configuring the Added Function in the Multi-Play Service................................................................3-523.5.7 Example for Configuring the L2TP QoS by Tunnels..........................................................................3-583.5.8 Example for Configuring the L2TP QoS by Sessions..........................................................................3-61

4 Link Level QoS Configuration................................................................................................4-14.1 Introduction.....................................................................................................................................................4-2

4.1.1 Link Level QoS Overview..................................................................................................................... 4-24.1.2 Link Level QoS Supported by the ME60...............................................................................................4-2

4.2 Configuring Link Level QoS...........................................................................................................................4-24.2.1 Establishing the Configuration Task......................................................................................................4-34.2.2 Enabling Link Level QoS.......................................................................................................................4-34.2.3 Configuring the Remote Link Mode......................................................................................................4-34.2.4 Configuring the Adjustment Value of the Remote Link........................................................................4-44.2.5 (Optional) Configuring the Adjustment Value of the Local Link..........................................................4-54.2.6 (Optional) Enabling the CAR and Statistics Functions of the Upstream L3 Packets............................4-54.2.7 (Optional) Obtaining Transmission Rate of User Packets Dynamically Through ANCP.....................4-5

4.3 Configuration Examples..................................................................................................................................4-64.3.1 Example for Configuring Link Level QoS in ATM Cell Mode.............................................................4-6

5 Multicast Shaping Configuration...........................................................................................5-15.1 Introduction.....................................................................................................................................................5-2

5.1.1 Multicast Shaping Overview..................................................................................................................5-25.1.2 Multicast Shaping Supported by the ME60........................................................................................... 5-2

5.2 Configuring Multicast Shaping.......................................................................................................................5-25.2.1 Establishing the Configuration Task......................................................................................................5-35.2.2 Configuring the Multicast Program List................................................................................................ 5-35.2.3 Enabling the Function of Multicast Shaping..........................................................................................5-45.2.4 Configuring the Bandwidth of the Multicast List.................................................................................. 5-45.2.5 (Optional) Configuring the Multicast Profile.........................................................................................5-55.2.6 (Optional) Configuring the Multicast Profile in the Domain.................................................................5-5



xi

5.2.7 (Optional) Enabling Authentication for Multicast Users.......................................................................5-65.2.8 Checking the Configuration...................................................................................................................5-6

5.3 Configuration Examples..................................................................................................................................5-75.3.1 Example for Configuring Multicast Shaping.........................................................................................5-7

6 QPPB Configuration..................................................................................................................6-16.1 Introduction.....................................................................................................................................................6-2

6.1.1 QPPB Overview.....................................................................................................................................6-26.1.2 QPPB Supported by the ME60...............................................................................................................6-2

6.2 Configuring QPPB..........................................................................................................................................6-26.2.1 Establishing the Configuration Task......................................................................................................6-36.2.2 Configuring Routing Attributes on the BGP Route Sender...................................................................6-36.2.3 Applying the Routing Policy to the BGP Route Sender........................................................................6-56.2.4 Configuring the Routing Policy on the BGP Route Receiver................................................................6-56.2.5 Applying the Routing Policy to the BGP Route Receiver.....................................................................6-66.2.6 Configuring Class-based Traffic Behavior............................................................................................6-76.2.7 Applying the QPPB Policy to an Interface.............................................................................................6-76.2.8 Checking the Configuration...................................................................................................................6-7

6.3 Configuration Examples..................................................................................................................................6-86.3.1 Example for Configuring QPPB............................................................................................................6-8

7 VPN QoS Configuration...........................................................................................................7-17.1 Introduction.....................................................................................................................................................7-2

7.1.1 VPN QoS Overview...............................................................................................................................7-27.1.2 VPN QoS Supported by the ME60........................................................................................................7-2

7.2 Configuring the Hierarchical Resource Reserved BGP/MPLS IP VPN.........................................................7-37.2.1 Establishing the Configuration Task......................................................................................................7-37.2.2 (Optional) Configuring the Flow Queue................................................................................................7-47.2.3 (Optional) Configuring the DiffServ Model Supported by the BGP/MPLS IP VPN............................7-67.2.4 (Optional) Configuring WRED Parameters...........................................................................................7-77.2.5 Configuring a Tunnel Policy and Applying It to the VPN Instance......................................................7-87.2.6 Configuring Bandwidth of the MPLS TE Tunnel..................................................................................7-97.2.7 Associating the MPLS TE Tunnel with the VPN Instance and Configuring the QoS Policy................7-97.2.8 Checking the Configuration.................................................................................................................7-10

7.3 Configuring the Hierarchical Resource Reserved L2VPN............................................................................7-117.3.1 Establishing the Configuration Task....................................................................................................7-117.3.2 (Optional) Configuring the Flow Queue..............................................................................................7-137.3.3 (Optional) Configuring the DiffServ Model Supported by the L2VPN...............................................7-147.3.4 (Optional) Configuring WRED Parameters.........................................................................................7-157.3.5 Configuring the Tunnel Policy.............................................................................................................7-167.3.6 Applying the MPLS TE Tunnel Policy to the L2VPN.........................................................................7-167.3.7 Configuring Bandwidth of the MPLS TE Tunnel................................................................................7-177.3.8 Associating the MPLS TE Tunnel with the L2VPN and Configuring the QoS Policy.......................7-187.3.9 Checking the Configuration.................................................................................................................7-19

ContentsQuidway ME60 Multiservice Control Gateway


xii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-06-01)

7.4 Configuration Examples................................................................................................................................7-207.4.1 Example for Configuring the Resource Reserved BGP/MPLS IP VPN..............................................7-207.4.2 Example for Configuring the Resource Reserved VLL.......................................................................7-377.4.3 Example for Configuring the Resource Reserved VPLS.....................................................................7-46

A Glossary.....................................................................................................................................A-1

B Acronyms and Abbreviations.................................................................................................B-1



xiii

Figures

Figure 1-1 Networking of the PPPoEoVLAN configuration.............................................................................1-14Figure 2-1 Example of traffic policy configuration...........................................................................................2-16Figure 2-2 Example of priority mapping configuration.....................................................................................2-21Figure 3-1 QoS scheduling supported by the ME60............................................................................................3-3Figure 3-2 Example of the configuration of QoS scheduling in router mode....................................................3-29Figure 3-3 Example of the configuration of QoS scheduling in PE mode.........................................................3-32Figure 3-4 Example of the configuration of QoS scheduling in QoD mode......................................................3-36Figure 3-5 Networking diagram of the Multi-Play service................................................................................3-46Figure 3-6 Networking diagram for the added function in the Multi-Play Service...........................................3-53Figure 3-7 Example of the networking of L2TP QoS scheduling by tunnel......................................................3-58Figure 3-8 Example of the networking of L2TP QoS scheduling by session....................................................3-62Figure 4-1 Example of the configuration of QoS scheduling in ATM cell mode................................................4-6Figure 5-1 Example of multicast shaping configuration......................................................................................5-8Figure 6-1 Networking of the QPPB configuration.............................................................................................6-9Figure 7-1 Networking of the resource reserved BGP/MPLS IP VPN..............................................................7-21Figure 7-2 Networking of the resource reserved VLL.......................................................................................7-38Figure 7-3 Networking of the resource reserved VPLS.....................................................................................7-47

Quidway ME60 Multiservice Control GatewayConfiguration Guide - QoS Figures


xv

Tables

Table 2-1 Mapping of the DSCP values to CoS.................................................................................................2-11Table 2-2 Mapping of the CoS to DSCP values.................................................................................................2-12Table 2-3 Mapping of the EXP values to CoS...................................................................................................2-12Table 2-4 Mapping of the CoS to EXP values...................................................................................................2-13Table 2-5 Mapping of the 802.1p values to CoS................................................................................................2-13Table 2-6 Mapping of the CoS to the 802.1p values..........................................................................................2-14Table 2-7 Mapping of the user priority to CoS..................................................................................................2-14Table 3-1 Default drop thresholds........................................................................................................................3-7

Quidway ME60 Multiservice Control GatewayConfiguration Guide - QoS Tables


xvii

1 Traffic Policing Configuration

About This Chapter

This chapter describes how to configure traffic policing, including the concept, configurationprocedures, and configuration examples of traffic policing.

1.1 IntroductionThis section describes the basic knowledge for traffic policing configuration.

1.2 Configuring Traffic PolicingThis section describes how to configure and use the functions of traffic policing.

1.3 Configuring the CPCARThis section describes how to configure and use the CPCAR function.

1.4 Configuring the Host CARThis section describes how to configure and use the host CAR function.

1.5 Maintaining Traffic PolicingThis section describes the commands for displaying and clearing information about trafficpolicing.

1.6 Configuration ExamplesThis section gives examples for configuring traffic policing.

Quidway ME60 Multiservice Control GatewayConfiguration Guide - QoS 1 Traffic Policing Configuration


1-1

1.1 IntroductionThis section describes the basic knowledge for traffic policing configuration.

1.1.1 Traffic Policing Overview

1.1.2 Traffic Policing Supported by the ME60

1.1.1 Traffic Policing OverviewTraffic policing (TP) is used to monitor the specifications of the traffic that enters a network andkeep traffic volume within a reasonable range. In addition, it restricts the traffic exceeding therate limit to optimize network resources and protect the interests of the carriers.

1.1.2 Traffic Policing Supported by the ME60

CARThe Committed Access Rate (CAR) is applied to limit certain categories of traffic. The packetsthat exceed the specifications are discarded or their priority values are re-set.

Token BucketCAR uses token buckets to implement traffic policing. A token bucket is regarded as a containerof tokens that has a pre-defined capacity. The system places the tokens into the bucket at adefined rate. In case the token bucket is full, no more tokens can be added; otherwise, the tokensoverflow the bucket.

You can use two token buckets to measure traffic in more complex conditions and implementmore flexible traffic policing. The rates for the two token buckets used to deliver tokens are CIRand PIR. As the sizes of the two token buckets are CBS and PBS (CBS is smaller than PBS andthey represent the levels for the allowed bursts), they are called bucket C and bucket P for short.

Traffic Policing ActionAccording to different evaluation results, the ME60 performs the pre-configured policingactions, which are described as follows:

l Pass: Continues to forward the packets evaluated as "conforming" or re-forwards thepackets marked Differentiated Services Code Point (DSCP) by Diff-Serv.

l Discard: Discards the packets evaluated as "non-conforming".

Statistics FunctionTo control and measure users' traffic on a network is necessary. The traditional method ofstatistics based on the interface has the following disadvantages:

l For the upstream traffic, only the traffic volume before the CAR operation is performedcan be measured. The traffic required by users and the loss of packets produced when thetraffic rate exceeds the bandwidth limit cannot be measured.

1 Traffic Policing ConfigurationQuidway ME60 Multiservice Control Gateway


1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-06-01)

l For the downstream traffic, only the interface traffic after the CAR operation is performedat the outgoing interface can be measured. Passed and dropped packets are not counted.

To analyze how users' traffic exceeds the limit, carriers have to collect statistics again after CAR.Based on this statistic data, carriers can raise proposals, advising users to buy a higher bandwidth.

The ME60 can help to realize CAR on the physical interfaces, trunk, and user VLAN. It cancollect statistics on the traffic before CAR and after CAR and keep records on passing and lostpackets, which helps carriers obtain information about the user network traffic.

VPLS Broadcast Packets SuppressionIn a VPLS network, the VPLS transmits broadcast packets, multicast packets, and unknownunicast packets through broadcast and copies them to neighboring ACs and PWs. If largequantities of messages are sent to the access side of the network, the ME60 has to make a lot ofcopies of these broadcast packets, which is meaningless, wastes bandwidth and resources, andaffects the performance of the system.

The ME60 has the function of VPLS broadcast suppression, which helps to suppress broadcasttraffic from the AC to PW based on the interface or sub-interface.

Traffic Policing of Host PacketsFor ordinary IP packets, the ME60 forwards the packets through the LPUs. For special packets,the LPUs must send the packets to the MPU. Such packets include routing protocol packets,packets sent when a user goes online or goes offline, and abnormal and wrong packets. Thesepackets are called host packets.

When the traffic of host packets is too high or malicious attackers send a large amount of hostpackets, the system cannot operate normally. You can configure the traffic policy on theME60 to control host packets and ensure stable operation of the system.

Traffic policing for host packets can be implemented through the following methods:

l CPCARCPCAR controls the traffic of a certain type of host packets on an LPU.

l Host-CARHost CAR controls the traffic of host packets based on users. Host packets sent to theME60 by each user are controlled separately.

1.2 Configuring Traffic PolicingThis section describes how to configure and use the functions of traffic policing.

1.2.1 Establishing the Configuration Task

1.2.2 Configuring the QoS CAR Profile

1.2.3 Applying the QoS CAR Profile

1.2.4 Enabling CAR Traffic Statistics

1.2.5 Configuring VPLS Broadcast Suppression

1.2.6 (Optional) Configuring the Interval for Collecting Traffic Statistics



1-3

1.2.7 Checking the Configuration


Applicable EnvironmentThe network can be more and more crowded if the traffic sent by users is not limited. To usethe limited network resources more effectively and efficiently, you need to limit the user traffic.Traffic policing is a traffic control policy that limits the use of traffic and resource by controllingthe traffic specifications. Traffic policing can be applied to both the incoming and outgoingtraffic at the same time.

Pre-configuration TaskBefore configuring traffic policing, complete the following tasks:

l Configuring the physical parameters of the relevant interfaces

l Configuring the link layer attributes of the relevant interfaces so that the interfaces canwork normally

l Configuring the IP addresses and routing protocols for the relevant interfaces so that theroutes between them are normal (Do this configuration when configuring CAR at the L3interfaces.)

l Configuring BRAS user access so that the BRAS users can go online (Do this configurationwhen configuring CAR at the user VLAN.)

l Configuring the VPLS network (Do this configuration when configuring the VPLSbroadcast messages suppression.)

Data PreparationTo configure traffic policing, you need the following data:

No. Data

1 CIR, PIR, CBS, PBS

2 Interfaces and traffic direction (incoming or outgoing) of the CAR

1.2.2 Configuring the QoS CAR Profile

ContextDo as follows on the ME60:

Procedure

Step 1 Run:system-view

The system view is displayed.




Issue 05 (2010-06-01)

Step 2 Run:qos car car-name cir cir-value [ pir pir-value ] [ cbs cbs-value pbs pbs-value ]

The QoS CAR profile is created.

----End

1.2.3 Applying the QoS CAR Profile

Procedurel Applying the QoS CAR profile to the interface

1. Run:system-view

The system view is displayed.2. Run:

interface interface-type interface-number

The interface view is displayed.3. Run:

qos car { inbound | outbound } car-name

The QoS CAR profile is applied to the interface.l Applying the QoS CAR profile to the Sub-interface

1. Run:system-view


interface interface-type interface-number.subinterface

The sub-interface view is displayed.3. Run:

qos car { inbound | outbound } car-name

The QoS CAR profile is applied to the interface.l Applying the QoS CAR profile to the user VLAN

1. Run:system-view




user-vlan { start-vlan [ end-vlan ] [ qinq start-qinq-id [ end-qinq-id ] ] | any-other }

The user VLAN view is displayed.4. Run:

qos car { inbound | outbound } car-name [ each-vlan ]



1-5

The QoS CAR profile is applied to the user VLAN.

----End

1.2.4 Enabling CAR Traffic Statistics

Procedurel Configuring traffic statistics on interfaces

1. Run:system-view




qos car { inbound | outbound } car-name statistics { before | after | both }

The traffic statistics function is enabled on the interface.l Configuring traffic statistics on sub-interfaces

1. Run:system-view




qos car { inbound | outbound } car-name statistics { before | after | both }

The traffic statistics function is enabled on the interface.l Configuring traffic statistics in user VLAN

1. Run:system-view




user-vlan { start-vlan [ end-vlan ] [ qinq start-qinq-id [ end-qinq-id ] ] | any-other }


qos car { inbound | outbound } car-name statistics { before | after | both }each-vlan




Issue 05 (2010-06-01)

The traffic statistics function is enabled in the user VLAN.

----End

1.2.5 Configuring VPLS Broadcast Suppression

Procedurel Configuring VPLS broadcast suppression on interfaces

1. Run:system-view




vpls broadcast car car-name

The function of VPLS broadcast suppression is configured on the interface.l Configuring VPLS broadcast suppression on sub-interfaces

1. Run:system-view




vpls broadcast car car-name

The function of VPLS broadcast suppression is configured on the sub-interface.

----End

1.2.6 (Optional) Configuring the Interval for Collecting TrafficStatistics


Procedure



Step 2 Run:



1-7

set flow-stat interval interval

The interval for collecting traffic statistics is set.

This command is applied to the qos car and vpls car commands. The value of interval must bea multiple of 10.

----End


Action Command

Check information about the QoSCAR.

display qos car { all |name car-name }

You can run the display qos car command to view the information about the parameters of theQoS CAR profile and the application of the profile.

<Quidway> display qos car name car1CAR Name :car1CAR Index : 1 car cir 1000(kbps) cbs 10240(bytes) pbs 20480(bytes)Applied number on Interface :1Applied number on Vlan :1

1.3 Configuring the CPCARThis section describes how to configure and use the CPCAR function.


1.3.2 Configuring the Traffic Policy for Host Packets

1.3.3 (Optional) Configuring the Priority Level of Host Packets

1.3.4 (Optional) Configuring the Conditions for Generating the CPCAR Logs



Applicable Environment

The ME60 is in an unstable state if the traffic of a type of host packets on one LPU is too heavy.The CPCAR controls the traffic of a certain type of host packets on an LPU. The CRCAR avoidsthe impact of large amount of host packets on the ME60 and ensures stable running of the system.

Pre-configuration Task

Before configuring the CPCAR, complete the following tasks:





Issue 05 (2010-06-01)

l Configuring the link layer attributes of the relevant interfaces

l Configuring the IP addresses of the interfaces or configuring the BRAS features to enableusers to log in

Data Preparation

To configure the CPCAR, you need the following data.

No. Data

1 Type of the messages reported by the LPUs to the MPU

2 (Optional) Name of the traffic policy adopted for the packets sent to the MPU

3 CAR parameters of traffic policing for host packets on the LPU

4 (Optional) Conditions for generating the CPCAR logs, namely, the interval andthreshold for generating CPCAR logs

1.3.2 Configuring the Traffic Policy for Host Packets

Context

Do as follows on the ME60 where traffic policing needs to be performed for host packets

Procedure



Step 2 Run:cpcar host-packet-type slot slot-number

The CPCAR view is displayed.

This command is valid only on an in-service LPU.

Step 3 Configure the traffic policy for host packets. The configuration methods are as follows:

l To allow packets to pass, run the pass command.

l To configure CAR actions, run the car cir cir-value [ cbs cbs-value ] [ green { discard |pass } ] [ yellow { discard | pass } ] [ red { discard | pass } ] command.

l To configure the associated traffic policy, run the traffic-policy policy-name command.

----End

1.3.3 (Optional) Configuring the Priority Level of Host Packets



1-9

Context

Do as follows on the ME60:

Procedure



Step 2 Run:cpcar host-packet-type slot slot-number

The CPCAR view is displayed.

Step 3 Run:set priority priority-value

The priority of host packets is configured.

----End

1.3.4 (Optional) Configuring the Conditions for Generating theCPCAR Logs

Context

Do as follows on the ME60.

Procedure



Step 2 Run:cpcar logging { discard-threshold discard-threshold-value | interval interval-value} *

The interval and threshold for generating the CPCAR logs are configured.

The system queries the number of bytes in the dropped host packets at the set interval. Whenthe number of bytes in the dropped host packets reaches the threshold, the system generates theCPCAR log so that you can monitor the traffic of host packets.

----End

1.3.5 Checking the ConfigurationRun the following command to check the previous configuration.




Issue 05 (2010-06-01)

Action Command

Check the configuration of theCPCAR.

display cpcar host-packet-type configuration slot slot-number

1.4 Configuring the Host CARThis section describes how to configure and use the host CAR function.


1.4.2 Configuring the Host CAR

1.4.3 (Optional) Configuring the Conditions for Generating the Host CAR Logs



The ME60 is in unstable state when the traffic of the host packets of a user is too heavy or a userattacks the ME60 maliciously. After the host CAR is configured, the traffic of the host packetsof each user can be under surveillance, which prevented the host packets from beingoverwhelming.


Before configuring the host CAR, complete the following tasks:



l Configuring the IP addresses of the interfaces or configuring the BRAS features to enableusers to go online

Data Preparation

To configure the host CAR, you need the following data:

No. Data

1 CAR parameters for the traffic policing of user host packets

2 (Optional) Interval for querying information about dropped host packets and thethreshold (in bytes) of the dropped packets

1.4.2 Configuring the Host CAR



1-11

ContextDo as follows on the ME60 where traffic policing needs to be performed for host packets ofusers

Procedure



Step 2 Run:hostcar cir cir-value [ pir pir-value ] [ cbs cbs-value pbs pbs-value ]

The host CAR is configured.

----End

1.4.3 (Optional) Configuring the Conditions for Generating theHost CAR Logs

ContextDo as follows on the ME60 where traffic policing needs to be performed for host packets.

Procedure



Step 2 Run:hostcar logging { discard-threshold discard-threshold-value | interval interval-value} *

The interval and threshold for generating the host CAR logs are configured.

The system queries the number of bytes in the dropped host packets at the set interval. Whenthe number of bytes in the dropped host packets reaches the threshold, the system generates thehost CAR log so that you can monitor the traffic of host packets.

----End

1.5 Maintaining Traffic PolicingThis section describes the commands for displaying and clearing information about trafficpolicing.

1.5.1 Displaying Information About Traffic Policing

1.5.2 Clearing the Statistics on the Traffic Policing




Issue 05 (2010-06-01)

1.5.1 Displaying Information About Traffic PolicingAfter the preceding configuration, run the following display commands in any view to displayinformation about traffic policing and verify the effect of the configuration. For detailedinformation, refer to the Quidway ME60 Multiservice Control Gateway - CommandReference.

Action Command

Display information about the QoSCAR.

display qos car { all |name car-name }

Display the statistics on the QoSCAR traffic of the interface.

display qos car statistics interface interface-typeinterface-number

Display the statistics on the QoSCAR traffic of the sub-interface orthe user VLAN.

display qos car statistics interface interface-typeinterface-number.subinterface [ vlan vlan-id [ qinqqinq-id ] ]

Display the statistics on VPLSbroadcast suppression.

display vpls-broadcast car statistics interfaceinterface-type interface-number

Display the configuration of theCPCAR.

display cpcar host-packet-type configuration slot slot-number

Display the statistics on hostpackets.

display cpcar host-packet-type statistics slot slot-number

1.5.2 Clearing the Statistics on the Traffic Policing

CAUTIONQoS CAR statistics cannot be restored after you clear it. So, confirm the action before you usethe command.

Run the following commands in any view to clear the statistics on the QoS CAR.

Action Command

Clear the statistics on QoS CAR. reset qos car statistics interface interface-typeinterface-number

Clear the statistics on the suppressedVPLS broadcast messages.

reset vpls-broadcast car statistics interfaceinterface-type interface-number

Clear the statistics on the user hostpackets.

reset cpcar host-packet-type statistics slot slot-number



1-13

1.6 Configuration ExamplesThis section gives examples for configuring traffic policing.

1.6.1 Example for Configuring Traffic Policing

1.6.1 Example for Configuring Traffic Policing

Networking Requirement

As shown in Figure 1-1, broadband subscribers access the Internet through PPPoEoVLAN.

l The subscribers belong to domain isp1 and access the network in PPPoEoVLAN modethrough interface GE8/0/1.1 of the ME60. The LAN switch labels user packets with VLAN1 and VLAN 2.

l RADIUS authentication and RADIUS accounting are adopted.

l The IP address of the RADIUS server is 192.168.7.249 and the ports for authentication andaccounting are 1645 and 1646 respectively. The protocol is RADIUS+1.1 and the key isitellin.

l The IP address of the DNS is 192.168.7.252.

l The network side interface is GE7/0/1.

l Every subscriber is given 5 Mbit/s bandwidth and the maximum bandwidth for onesubscriber is 8 Mbit/s.

l CAR is performed for user packets so that you can obtain information about the runningof the network.

l The transmission rate of PPPoE control packets should be within 256 kbps.

l The transmission rate of host packets of each subscriber should be within 512 kbps.

Figure 1-1 Networking of the PPPoEoVLAN configuration

subscriber1@isp1

ME60

RADIUS server192.168.7.249

GE8/0/1.1 GE7/0/1192.168.7.1

DNS server192.168.7.252

subscriber2@isp1

VLAN1

VLAN2




Issue 05 (2010-06-01)

Configuration RoadmapThe configuration roadmap is as follows:

1. Configure subscribers to go online.2. Configure the QoS CAR.

Data PreparationTo complete the configuration, you need the following data:

l User VLAN ID

l Name of the QoS CAR profile

Configuration Procedure1. Configure subscribers to go online.

# Configure a VT interface.<Quidway> system-view[Quidway] interface virtual-template 1[Quidway-Virtual-Template1] ppp authentication-mode chap[Quidway-Virtual-Template1] quit# Configure the authentication scheme.[Quidway] aaa[Quidway-aaa] authentication-scheme auth1[Quidway-aaa-authen-auth1] authentication-mode radius[Quidway-aaa-authen-auth1] quit# Configure the accounting scheme.[Quidway-aaa] accounting-scheme acct1[Quidway-aaa-accounting-acct1] accounting-mode radius[Quidway-aaa-accounting-acct1] quit[Quidway-aaa] quit# Configure the RADIUS server group.[Quidway] radius-server group rd1[Quidway-radius-rd1] radius-server authentication 192.168.7.249 1645[Quidway-radius-rd1] radius-server accounting 192.168.7.249 1646[Quidway-radius-rd1] radius-server type plus11[Quidway-radius-rd1] radius-server shared-key itellin[Quidway-radius-rd1] quit# Configure the address pool.[Quidway] ip pool pool1 local[Quidway-ip-pool-pool1] gateway 172.82.0.1 255.255.0.0[Quidway-ip-pool-pool1] section 0 172.82.0.2 172.82.0.200[Quidway-ip-pool-pool1] dns-server 192.168.7.252[Quidway-ip-pool-pool1] quit# Configure domain isp1.[Quidway] aaa[Quidway-aaa] domain isp1[Quidway-aaa-domain-isp1] authentication-scheme auth1[Quidway-aaa-domain-isp1] accounting-scheme acct1[Quidway-aaa-domain-isp1] radius-server group rd1[Quidway-aaa-domain-isp1] ip-pool pool1[Quidway-aaa-domain-isp1] quit[Quidway-aaa] quit# Specify the VT interface for the sub-interface.[Quidway] interface GigabitEthernet 8/0/1.1[Quidway-GigabitEthernet8/0/1.1] user-vlan 1 2



1-15

[Quidway-GigabitEthernet8/0/1.1-vlan-1-2] quit[Quidway-GigabitEthernet8/0/1.1] pppoe-server bind virtual-template 1# Configure the BAS interface.[Quidway-GigabitEthernet8/0/1.1] bas[Quidway-GigabitEthernet8/0/1.1-bas] access-type layer2-subscriber[Quidway-GigabitEthernet8/0/1.1-bas] authentication-method ppp[Quidway-GigabitEthernet8/0/1.1-bas] quit[Quidway-GigabitEthernet8/0/1.1] quit# Configure the uplink interface.[Quidway] interface GigabitEthernet 7/0/1[Quidway-GigabitEthernet7/0/1] ip address 192.168.7.1 255.255.255.0[Quidway-GigabitEthernet7/0/1] undo shutdown[Quidway-GigabitEthernet7/0/1] quit

2. Configure traffic policing.# Configure the QoS CAR profile.[Quidway] qos car car1 cir 5000 pir 8000# Apply the QoS CAR profile to the user VLAN and configure traffic statistics to becollected before and after the CAR operation.[Quidway] interface GigabitEthernet 8/0/1.1[Quidway-GigabitEthernet8/0/1.1] user-vlan 1 2[Quidway-GigabitEthernet8/0/1.1-vlan-1-2] qos car inbound car1 statistics both each-vlan[Quidway-GigabitEthernet8/0/1.1-vlan-1-2] qos car outbound car1 statistics both each-vlan[Quidway-GigabitEthernet8/0/1.1-vlan-1-2] quit[Quidway-GigabitEthernet8/0/1.1] quit

3. Configure the traffic policy for host packets.# Restrict the transmission rate of PPPoE control messages to 256 kbps.[Quidway] cpcar control-pppoe slot 8[Quidway-cpcar-control-pppoe-slot-8] car cir 256[Quidway-cpcar-control-pppoe-slot-8] quit# Restrict the transmission rate of the host packets of each subscriber to 512 kbps.[Quidway] hostcar cir 512

4. Verify the configuration.[Quidway] display qos car name car1---------------------------------------------------------------- CAR Name : car1 CAR Index : 0 car cir 5000 (Kbps) pir 8000 (Kbps) cbs 625000 (byte) pbs 1000000 (byte) Applied number on interface : 0 Applied number on VLAN : 4 The parameters of profile car1 are displayed and you can see that they are applied to theupstream and downstream traffic of four VLANs.[Quidway] display qos car statistics interface gigabitethernet8/0/1.1 vlan 1Before CAR Inbound Unicast : 10420 bytes, 10 packets Multicast: 0 bytes, 0 packets Broadcast: 0 bytes, 0 packets Last 300 seconds rates: 138 bits/s, 0 packets/sBefore CAR Outbound Unicast : 5210 bytes, 5 packets Multicast: 0 bytes, 0 packets Broadcast: 0 bytes, 0 packets Last 300 seconds rates: 0 bits/s, 0 packets/sAfter CAR Inbound Passed : 0 bytes, 0 packets Dropped: 0 packets Last 300 seconds rate:0 packets/sAfter CAR Outbound




Issue 05 (2010-06-01)

Passed : 5210 bytes, 5 packets Dropped: 0 packets Last 300 seconds rate: 0 packets/s

Configuration Files#sysname Quidway#qos car car1 cir 5000 pir 8000 cbs 625000 pbs 1000000 #hostcar cir 512 cbs 64000 pbs 160256#radius-server group rd1 radius-server authentication 192.168.7.249 1645 weight 0 radius-server accounting 192.168.7.249 1646 weight 0 radius-server shared-key itellin radius-server type plus11#interface Virtual-Template1#interface GigabitEthernet8/0/1 undo shutdown#interface GigabitEthernet8/0/1.1 undo shutdown pppoe-server bind Virtual-Template 1 user-vlan 1 2 qos car inbound car1 statistics both each-vlan qos car outbound car1 statistics both each-vlan bas access-type layer2-subscriber#interface GigabitEthernet7/0/1 undo shutdown ip address 192.168.7.1 255.255.255.0#ip pool pool1 local gateway 172.82.0.1 255.255.255.0 section 0 172.82.0.2 172.82.0.200 dns-server 192.168.7.252#aaa authentication-scheme auth1 accounting-scheme acct1 domain isp1 authentication-scheme auth1 accounting-scheme acct1 radius-server group rd1 ip-pool pool1#cpcar control-pppoe slot 8 car cir 256 cbs 32000 pbs 80128 green pass yellow pass red discard#return



1-17

2 Class-based QoS Configuration

About This Chapter

This chapter describes the knowledge about class-based QoS, including the basic concepts,configuration procedures, and configuration examples.

2.1 IntroductionThis section describes the basic knowledge about class-based QoS.

2.2 Configuring Traffic PolicyThis section describes how to configure and use the traffic policy that is based on trafficclassification.

2.3 Configuring the Priority MappingThis section describes how to configure and use priority mapping that is based on simple trafficclassification.

2.4 Configuration ExamplesThis section gives examples for configuring class-based QoS.

Quidway ME60 Multiservice Control GatewayConfiguration Guide - QoS 2 Class-based QoS Configuration


2-1

2.1 IntroductionThis section describes the basic knowledge about class-based QoS.

2.1.1 Class-based QoS Overview

2.1.2 Class-based QoS Supported by the ME60

2.1.1 Class-based QoS OverviewIn the class-based QoS, traffic is classified according to certain rules. Then, a behavior isassociated with the traffic of the same type to form a policy. After the policy is implemented,the ME60 performs traffic policing, priority marking, and redirection.

2.1.2 Class-based QoS Supported by the ME60

l Traffic classificationTraffic classification is a process of identifying the packets that have certain featuresaccording to rules. Therefore, it is the basis for providing differentiated services. Trafficclassification includes complex traffic classification and simple traffic classification.

l BehaviorThe purpose of traffic classification is to provide differentiated services. The classificationtakes effect only after it is associated with a traffic control or resource allocation behavior.

l The ME60 supports the following traffic behaviors (Multiple behaviors can be usedtogether):– Deny/Permit

– Marking

– Redirection

– Traffic policing

– Random discarding

– Security

l Traffic policyA traffic policy consists of associated traffic behaviors and the QoS behaviors. The trafficpolicy can be applied to an interface, the entire system, or a service for the user. After atraffic policy is applied, the traffic classification and behaviors defined in the traffic policyare also applied.

l Priority mappingThe QoS priority field used depends on the network from which the traffic is received. Forexample, a VLAN uses the 802.1p field, the Diff-Serv network uses the DSCP field, andthe MPLS network uses the EXP field. The mapping between the priority fields must beconfigured on the gateways to retain the priority of the packets when the packets traversedifferent networks.When the ME60 functions as the gateway between different networks, the external priorityfields (including 802.1p, DSCP, and EXP) of all packets received by the ME60 are mappedto the internal priority. The internal priority is represented by the service class and color of

2 Class-based QoS ConfigurationQuidway ME60 Multiservice Control Gateway



Issue 05 (2010-06-01)

the Diff-Serv model. When the ME60 sends packets, it maps the internal priority to anexternal priority flag.

2.2 Configuring Traffic PolicyThis section describes how to configure and use the traffic policy that is based on trafficclassification.


2.2.2 Configuring Traffic Classification

2.2.3 Configuring Traffic Behavior

2.2.4 Configuring the Traffic Policy

2.2.5 Applying the Traffic Policy



Applicable EnvironmentAt the ingress of the network, the ME60 functions as the edge router. To limit the traffic arrivingin the network, you must configure the traffic policy, which is based on the traffic classificationfor providing differentiated services for different service flows. The Diff-Serv provision dependson the parameters of the packets. The parameters are the DSCP value, protocol type, IP address,port number, type of the fragmented packets, and time segment.

In general, the complex traffic classification is configured on the edge routers, and the simpletraffic classification is configured on the internal routers.

Pre-configuration TaskBefore configuring the traffic policy, complete the following tasks:



l Configuring the routing protocol to implement internetworking

l Configuring the IP addresses or BRAS attributes of the relevant interfaces

l Configuring the user-based ACL if the ACL is used as the traffic classification rule

Data PreparationTo configure the traffic policy, you need the following data.

No. Data

1 Classifier name and classification rules

2 Behavior name, features, and relevant parameters



2-3

No. Data

3 Traffic policy name

4 Number of the interface where the policy is applied and the service policy name

2.2.2 Configuring Traffic Classification

Context


Procedure



Step 2 Run:traffic classifier traffice-classifer-name [ operator { and | or } ]

A traffic classifier is created and the traffic classifier view is displayed.

When creating a traffic classifier, you can specify the operator for the rules in the traffic classifierto AND or OR

l Logical AND: indicates that a packet belongs to a classifier only when the packet matchesall the rules in this classifier.

l Logical OR: indicates that a packet belongs to a classifier when the packet matches any ofthe rules in this classifier.

By default, the value of operator is or.

Step 3 Define the rule for matching data packets as follows:l To match the 802.1p field in a packet, run the if-match 8021p 8021p-code command.

l To match the source MAC address of a packet, run the if-match source-mac mac-addresscommand.

l To match the destination MAC address of a packet, run the if-match destination-mac mac-address command.

l To match packets with an ACL, run the if-match acl acl-number command.

l To match the DSCP field of a packet, run the if-match dscp dscp-value command.

l To match the IP precedence of a packet, run the if-match ip-precedence ip-precedence-value command.

l To match the TCP SYN flag of a packet, run the if-match tcp syn-flag flag-value command.

l To specify that all IPv4 packets are matching, run the if-match any command.

----End




Issue 05 (2010-06-01)

2.2.3 Configuring Traffic Behavior

Procedurel Configuring the deny/permit behaviors

1. Run:system-view


traffic behavior behavior-name

The behavior view is displayed.3. Configure the deny or permit feature.

– Run the deny [ packet-length { eq length | gt length | lt length | range min-lengthmax-length } ] command to configure the deny behavior.

– Configure the permit command to configure the permit behavior.

If the behavior is configured to deny, the packets matching the classification rule arediscarded. Therefore, other behaviors cannot be configured.

If the behavior is configured to permit, the packets matching the classification ruleare processed according to the behaviors assigned to them.

l Configuring the marking behaviors1. Run:

system-view



A behavior is created and the behavior view is displayed.3. Configure the marking behaviors as follows:

– To configure the behavior of marking 802.1p, run the remark 8021p 8021p-code command.

– To configure the behavior of marking DSCP, run the remark dscp dscp-valuecommand.

– To configure the behavior of marking the IP precedence, run the remark ip-precedence ip-precedence-value command.

– To configure the behavior of marking MPLS-EXP priority, run the remark mpls-exp mpls-exp-value command.

l Configuring the redirection behaviors1. Run:

system-view



A behavior is created and the behavior view is displayed.



2-5

3. Run:redirect ip-nexthop ip-address [ interface interface-type interface-number ]

The redirection behavior is configured.l Configuring traffic policing behavior

1. Run:system-view



A behavior is created and the behavior view is displayed.3. Run:

car cir cir-value [ pir pir-value ] [ cbs cbs-value pbs pbs-value ] [ green { discard | pass | remark-dscp-pass dscp-value | remark-mpls-exp-pass mpls-exp-value | remark-prec-pass ip-precedence-value } ] [ yellow { discard | pass | remark-dscp-pass dscp-value | remark-mpls-exp-pass mpls-exp-value | remark-prec-pass ip-precedence-value } ] [ red { discard | pass | remark-dscp-pass dscp-value | remark-mpls-exp-pass mpls-exp-value | remark-prec-pass ip-precedence-value } ] [ summary ]

The traffic policing behavior is configured.

NOTE

The traffic policing behavior uses different statistical methods on the transmitted and receivedtraffic. The received traffic is evaluated by the IP payload and the transmitted traffic is evaluatedby the packet length.

l Configuring security behaviors1. Run:

system-view



A behavior is created and the behavior view is displayed.3. Configure the security behaviors as follows:

– To configure the URPF behavior, run the ip urpf strict command.

– To configure the port mirroring behavior, run the port-mirroring to observe-port observe-port-number command.

l Configuring traffic statistics behaviors1. Run:

system-view




traffic-statistic [ summary ]




Issue 05 (2010-06-01)

The traffic statistics behavior is configured.

NOTE

The function of traffic statistics is valid only for the value-added service.

l Configuring random discarding behaviors1. Run:

system-view




random-discard percent

The percentage of packets to be randomly discarded is set.

----End

2.2.4 Configuring the Traffic Policy


Procedure



Step 2 Run:traffic policy traffic-policy-name

A traffic policy is created and the traffic policy view is displayed.

Step 3 Run:classifier traffic-classfier-name behavior behavior-name

The traffic classifier is associated with the behavior.

----End

2.2.5 Applying the Traffic Policy

Procedurel Apply the traffic policy on an interface.

1. Run:system-view




2-7

2. Run:interface interface-type interface-number

The interface view is displayed.

When the user-based ACL (UCL) is configured in the traffic policy, the traffic policyis only globally applied.

3. Run:traffic-policy traffic-policy-name { inbound | outbound }[ link-layer ]

The traffic policy is applied to the interface.

l Apply the traffic policy in the inbound or outbound traffic.

1. Run:system-view


2. Run:traffic-policy traffic-policy-name { inbound | outbound }

The traffic policy is applied to the inbound or outbound traffic.

l Apply the traffic policy to the service policy.

1. Run:system-view


2. Run:value-added-service policy vas-policy-name

The service policy view is displayed.

3. Run:traffic-policy traffic-policy-name { in-policy | out-policy }

The traffic policy is applied to the service policy.

Each board of the ME60 supports 32000 ACL rules. If the number of ACL rulesconfigured for the service policy exceeds this value, all ACL rules become invalid.The total number of ACL rules is the number of rules contained in the policiesmultiplied by the number of users. For example, if a service policy contains 10 rules,and the domain to which the policy is bound has 10 users, the number of rules is 100.

NOTE

If the traffic policy is applied to value-added services, the number of ACL rules in the trafficpolicy cannot exceed 16; otherwise, the traffic policy cannot be applied to the value-addedservice. This limitation is invalid if the traffic policy is not applied to value-added services.

----End

2.2.6 Checking the ConfigurationRun the following commands to check the previous configuration.




Issue 05 (2010-06-01)

Action Command

Check the configuration ofthe traffic behavior.

display traffic behavior { system-defined | user-defined |remote-server-defined } [ behavior-name ]

Check the configuration ofthe traffic classifier.

display traffic classifier { system-defined | user-defined |remote-server-defined } [ classifier-name ]

Check the configuration ofthe traffic policy.

display traffic policy { inbound | outbound | { system-defined | user-defined | remote-server-defined } [ traffic-policy-name [ classifier traffic-classiffier-name ] ] }

2.3 Configuring the Priority MappingThis section describes how to configure and use priority mapping that is based on simple trafficclassification.


2.3.2 Creating the Diff-Serv Domain and Mapping the Priority

2.3.3 Adding an Interface to the Diff-Serv Domain

2.3.4 Adding a Sub-interface to the Diff-Serv Domain



Applicable EnvironmentThe QoS priority field used depends on the network from which the traffic is received. Forexample, a VLAN uses the 802.1p field, the Diff-Serv network uses the DSCP field, and theMPLS network uses the EXP field. The mapping between the priority fields must be configuredon the gateways to retain the priority of the packets when the packets traverse different networks.

NOTE

For the tunnel packets, such as the L2TP/GRE packets, the priority mapping is applied only to externaltunnel packets and priority fields of internal IP packets are not changed.

Pre-configuration TaskBefore configuring the priority mapping, complete the following tasks:



l Configuring the IP addresses and BRAS attributes of the relevant interfaces

Data PreparationTo configure the priority mapping, you need the following data.



2-9

No. Data

1 Diff-Serv domain name

2 802.1p fields, CoS, and colors of inbound/outbound VLAN packets

3 802.1p fields, CoS, and colors of inbound/outbound IP packets

4 User priority, CoS, and colors of inbound/outbound packets

5 EXP-based EXP fields, CoS, and colors of inbound/outbound MPLS packets

6 LSP-based EXP fields, CoS, and colors of inbound MPLS packets

7 Interface number added to the Diff-Serv domain

2.3.2 Creating the Diff-Serv Domain and Mapping the Priority

ContextThe Diff-Serv domain consists of Diff-Serv nodes that use the same service providing policyand implement the same PHB set.

When functioning as a core router in the Diff-Serv domain, the ME60 can either use the DSCPfield of the packet directly, or map the DCSP field to the CoS. When functioning as an edgerouter between the Diff-Serv domain and other networks, the ME60 must map the CoS to theexternal priority fields (802.1p or MPLS EXP).

NOTE

The 802.1p field to be mapped in multicast packets is obtained from the Diff-Serv domain on the interfacethat receives multicast packets, rather than from the user domain.

Procedure



Step 2 Run:diffserv domain { default | ds-domain-name }

The Diff-Serv domain is created and the domain view is displayed. If the domain name is notspecified, the default domain view is displayed.

Step 3 Configure the priority mapping of the Diff-Serv as follows:l To map the internal priority to the 802.1p field of received VLAN packets, run the 8021p-

inbound 8021p-code phb service-class [ color ] command.l To map the internal priority to the 802.1p field of transmitted VLAN packets, run the 8021p-

outbound service-class color map 8021p-code command.l To map the internal priority to the 802.1p field of multicast packets, run the 8021p-

multicast-inbound 8021p-multicast-code phb service-class command.




Issue 05 (2010-06-01)

l To map the internal priority to the 802.1p field of received IP packets, run the ip-dscp-inbound dscp-code phb service-class [ color ] command.

l To map the internal priority to the DSCP field of transmitted IP packets, run the ip-dscp-outbound service-class color map dscp-code command.

l To map the internal priority to the DSCP field of multicast packets, run the ip-multicast-dscp-inbound dscp-code phb service-clas command.

l To map the internal priority to the EXP field of received MPLS packets, run the mpls-exp-inbound exp phb service-class [ color ] command.

l To map the internal priority to the EXP field of transmitted MPLS packets, run the mpls-exp-outbound service-class color map exp command.

l To map the user priority to the internal priority, run the user-priority priority phb service-class [ color ] command.

l If the priority of domain users is configured, you must configure the mapping between theuser priority and the internal priority.

Table 2-1 shows the default mapping of the DSCP fields to the CoS.

Table 2-1 Mapping of the DSCP values to CoS

DSCP Service Color

0-7, 9, 11, 13, 15, 17, 19, 21,23, 25, 27, 29, 31, 33, 35, 37,39, 41-45, 47, 49-55, 57-63

BE Green

8, 10 AF1 Green

12 AF1 Yellow

14 AF1 Red

16, 18 AF2 Green

20 AF2 Yellow

22 AF2 Red

24, 26 AF3 Green

28 AF3 Yellow

30 AF3 Red

32, 34 AF4 Green

36 AF4 Yellow

38 AF4 Red

40, 46 EF Green

48 CS6 Green

56 CS7 Green



2-11

Table 2-2 shows the default mapping of the CoS to the DSCP fields.

Table 2-2 Mapping of the CoS to DSCP values

Service Color DSCP

BE green, yellow, red 0

AF1 Green 10

AF1 Yellow 12

AF1 Red 14

AF2 Green 18

AF2 Yellow 20

AF2 Red 22

AF3 Green 26

AF3 Yellow 28

AF3 Red 30

AF4 Green 34

AF4 Yellow 36

AF4 Red 38

EF Green, yellow, red 46

CS6 Green, yellow, red 48


Table 2-3 shows the default mapping of the EXP fields to the CoS.

Table 2-3 Mapping of the EXP values to CoS

EXP Service Color

0 BE Green

1 AF1 Green

2 AF2 Green

3 AF3 Green

4 AF4 Green

5 EF Green

6 CS6 Green




Issue 05 (2010-06-01)

EXP Service Color

7 CS7 Green

Table 2-4 shows the default mapping of the CoS to the EXP fields.

Table 2-4 Mapping of the CoS to EXP values

Service Color EXP

BE Green, yellow, red 0

AF1 Green, yellow, red 1




EF Green, yellow, red 5



Table 2-5 shows the default mapping of the 802.1p fields to the CoS.

Table 2-5 Mapping of the 802.1p values to CoS

802.1p Service Color

0 BE Green

1 AF1 Green

2 AF2 Green

3 AF3 Green

4 AF4 Green

5 EF Green

6 CS6 Green

7 CS7 Green

Table 2-6 shows the default mapping of the CoS to the 802.1p fields.



2-13

Table 2-6 Mapping of the CoS to the 802.1p values

Service 802.1p Color

BE 0 Green, yellow, red

AF1 1 Green, yellow, red




EF 5 Green, yellow, red

CS6 6 Green, yellow, red

CS7 7 Green, yellow, red

Table 2-7 shows the default mapping of the user priority to the CoS.

Table 2-7 Mapping of the user priority to CoS

User Priority Service Color

0 BE Green

1 AF1 Green

2 AF2 Green

3 AF3 Green

4 AF4 Green

5 EF Green

6 CS6 Green

7 CS7 Green

By default, the 802.1p value or the DSCP value of any multicast packet is mapped to the CoSAF4.

----End

2.3.3 Adding an Interface to the Diff-Serv Domain

ContextAfter the interface is added to the Diff-Serv domain, the priority mapping defined in the Diff-Serv domain applies to the packets automatically, including the inbound and outbound packetsof the interface.




Issue 05 (2010-06-01)


Procedure



Step 2 Run:interface interface-type interface-number


Step 3 Run:trust upstream { ds-domain-name |default }

The Diff-Serv domain is enabled on the interface.

----End

2.3.4 Adding a Sub-interface to the Diff-Serv Domain

Context

After the sub-interface is added to the Diff-Serv domain, the priority mapping defined in theDiff-Serv domain applies to the packets automatically, including the inbound and outboundpackets of the interface.


Procedure



Step 2 Run:interface interface-type interface-number.subinterface

The sub-interface view is displayed.

Step 3 Run:trust upstream { ds-domain-name | default }

The Diff-Serv domain is enabled on the interface.

The Diff-Serv domain can be enabled only on the Gigabit Ethernet sub-interface and the Eth-Trunk sub-interface.

Step 4 Run:trust 8021p [ outer ]

802.1p is enabled on the sub-interface.



2-15

802.1p can be enabled only on the Gigabit Ethernet sub-interface and the Eth-Trunk sub-interface.

----End


Action Command

Check the mapping betweenpriorities in the Diff-Servdomain.

display diffserv domain [ name dsdomain-name ] [ all ]

2.4 Configuration ExamplesThis section gives examples for configuring class-based QoS.

2.4.1 Example for Configuring Traffic Classification-based Traffic Policy

2.4.2 Example for Configuring Simple Traffic Classification-based Priority Mapping

2.4.1 Example for Configuring Traffic Classification-based TrafficPolicy

Networking RequirementAs shown in Figure 2-1, three local networks access the Internet through the ME60. Limit theupstream CAR of subscribers in segment 1.1.1.0 within 10 Mbit/s, that of subscribers in segment1.1.2.0 within 5 Mbit/s, and that of subscribers in segment 1.1.3.0 within 2 Mbit/s. Label themwith different DSCP values.

Figure 2-1 Example of traffic policy configuration

ME60

POS2/0/0

1.1.3.0

GE1/0/0

GE1/0/2

GE1/0/11.1.2.0

1.1.1.0




Issue 05 (2010-06-01)


1. Configure ACL rules.2. Configure the traffic classifier.3. Configure traffic behaviors.4. Configure the traffic policy.5. Apply traffic policies to interfaces.


l ACL 3001, 3002, 3003

l DSCP values 40, 26, and 0 for packets from the three network segments

l Name of the traffic classifier and name of the traffic policy

Configuration ProcedureNOTE

Only the procedures related to the traffic policy are mentioned.

1. Define the ACL rules.[Quidway] acl number 3001[Quidway-acl-adv-3001] rule permit ip source 1.1.1.0 0.0.0.255[Quidway-acl-adv-3001] quit[Quidway] acl number 3002[Quidway-acl-adv-3002] rule permit ip source 1.1.2.0 0.0.0.255[Quidway-acl-adv-3002] quit[Quidway] acl number 3003[Quidway-acl-adv-3003] rule permit ip source 1.1.3.0 0.0.0.255[Quidway-acl-adv-3003] quit

2. Configure the traffic classifier and define the ACL-based traffic classification rules.[Quidway] traffic classifier a[Quidway-classifier-a] if-match acl 3001[Quidway-classifier-a] quit[Quidway] traffic classifier b[Quidway-classifier-b] if-match acl 3002[Quidway-classifier-b] quit[Quidway] traffic classifier c[Quidway-classifier-c] if-match acl 3003[Quidway-classifier-c] quitBy running the display traffic classifier command, you can see the details about theclassification.[Quidway] display traffic classifier user-defined User Defined Classifier Information: Classifier: a Operator: OR Rule(s) : if-match acl 3001 Classifier: c Operator: OR Rule(s) : if-match acl 3003



2-17

Classifier: tc1 Operator: OR Rule(s) : -none- Classifier: b Operator: OR Rule(s) : if-match acl 3002

3. Define the behavior and configure the behavior to mark DSCP.[Quidway] traffic behavior e[Quidway-behavior-e] car cir 10000[Quidway-behavior-e] remark dscp 40[Quidway-behavior-e] quit[Quidway] traffic behavior f[Quidway-behavior-f] car cir 5000[Quidway-behavior-f] remark dscp 26[Quidway-behavior-f] quit[Quidway] traffic behavior g[Quidway-behavior-g] car cir 2000[Quidway-behavior-g] remark dscp 0[Quidway-behavior-g] quit

By running the display traffic behavior command, you can view the information aboutthe defined traffic.[Quidway] display traffic behavior user-defined User Defined Behavior Information: Behavior: e Committed Access Rate: CIR 10000 (Kbps), PIR 0 (Kbps), CBS 1250000 (byte), PBS 3130000 (byte) Conform Action: pass Yellow Action: pass Exceed Action: discard Marking: Remark DSCP cs5 Behavior: tb1 Firewall: permit Behavior: g Committed Access Rate: CIR 2000 (Kbps), PIR 0 (Kbps), CBS 250000 (byte), PBS 626000 (byte) Conform Action: pass Yellow Action: pass Exceed Action: discard Marking: Remark DSCP default Behavior: f Committed Access Rate: CIR 5000 (Kbps), PIR 0 (Kbps), CBS 625000 (byte), PBS 1565000 (byte) Conform Action: pass Yellow Action: pass Exceed Action: discard Marking: Remark DSCP af31

4. Define a traffic policy and associate the traffic classifier with behaviors.[Quidway] traffic policy policy1[Quidway-trafficpolicy-1] classifier a behavior e[Quidway-trafficpolicy-1] quit[Quidway] traffic policy policy2[Quidway-trafficpolicy-2] classifier b behavior f[Quidway-trafficpolicy-2] quit[Quidway] traffic policy policy3[Quidway-trafficpolicy-3] classifier c behavior g[Quidway-trafficpolicy-3] quit

By running the display traffic policy command, you can see the following information.




Issue 05 (2010-06-01)

[Quidway] display traffic policy user-definedUser Defined Traffic Policy Information: Policy: policy1 Classifier: default-class Behavior: be Firewall: permit Classifier: a Behavior: e Committed Access Rate: CIR 10000 (Kbps), PIR 0 (Kbps), CBS 1250000 (byte), PBS 3130000 (byte) Conform Action: pass Yellow Action: pass Exceed Action: discard Marking: Remark DSCP cs5 Policy: policy2 Classifier: default-class Behavior: be Firewall: permit Classifier: b Behavior: f Committed Access Rate: CIR 5000 (Kbps), PIR 0 (Kbps), CBS 625000 (byte), PBS 1565000 (byte) Conform Action: pass Yellow Action: pass Exceed Action: discard Marking: Remark DSCP af31 Policy: policy3 Classifier: default-class Behavior: be Firewall: permit Classifier: c Behavior: g Committed Access Rate: CIR 2000 (Kbps), PIR 0 (Kbps), CBS 250000 (byte), PBS 626000 (byte) Conform Action: pass Yellow Action: pass Exceed Action: discard Marking: Remark DSCP default

5. Apply the traffic policy to the interface.[Quidway] interface GigabitEthernet 1/0/0[Quidway-GigabitEthernet1/0/0] traffic-policy policy1 inbound[Quidway] interface GigabitEthernet 1/0/1[Quidway-GigabitEthernet1/0/1] traffic-policy policy2 inbound[Quidway] interface GigabitEthernet 1/0/2[Quidway-GigabitEthernet1/0/2] traffic-policy policy3 inbound

6. Verify the configuration.After the configuration is complete, you can see that the EF traffic is forwarded with highestpriority when congestion occurs.

Configuration Files# sysname Quidway#acl number 3001 rule 5 permit ip source 1.1.1.0 0.0.0.255



2-19

#acl number 3002 rule 5 permit ip source 1.1.2.0 0.0.0.255#acl number 3003 rule 5 permit ip source 1.1.3.0 0.0.0.255#traffic classifier a operator and if-match acl 3001traffic classifier c operator and if-match acl 3003traffic classifier b operator and if-match acl 3002#traffic behavior e car cir 10000 cbs 1250000 pbs 3130000 green pass yellow pass red discard remark dscp cs5traffic behavior f car cir 5000 cbs 625000 pbs 1565000 green pass yellow pass red discard remark dscp 31traffic behavior g car cir 2000 cbs 250000 pbs 626000 green pass yellow pass red discard remark dscp default#traffic policy policy3 classifier c behavior g traffic policy policy2 classifier b behavior f traffic policy policy1 classifier a behavior e #interface GigabitEthernet1/0/0 undo shutdown ip address 1.1.1.5 255.255.255.0 traffic-policy 1 inbound#interface GigabitEthernet1/0/1 undo shutdown ip address 1.1.2.5 255.255.255.0 traffic-policy 2 inbound#interface GigabitEthernet1/0/2 undo shutdown ip address 1.1.3.5 255.255.255.0 traffic-policy 3 inbound#return

2.4.2 Example for Configuring Simple Traffic Classification-basedPriority Mapping

Networking RequirementAs shown in Figure 2-2, the MPLS adjacency is set up between ME60 A and Router, andbetween ME60 B and Router. The IP packets entering ME60 A are transmitted between therouters through MPLS. After being sent out from ME60 B, the packets are transmitted throughIP.

When ME60 A receives IP packets, it must map their priority to the priority of MPLS packets.When ME60 B sends packets, it must map the MPLS priority to the IP priority.




Issue 05 (2010-06-01)

Figure 2-2 Example of priority mapping configuration

ME60A ME60B

GE1/0/0GE1/0/1

GE1/0/0

GE1/0/0

GE1/0/1

GE1/0/1

Router


1. On ME60 A, configure the mapping between DSCP and the internal priority for inboundpackets.

2. On ME60 A, configure the mapping between the internal priority and EXP for outboundpackets.

3. Apply the priority mapping to the relevant interfaces.4. On ME60 B, configure the mapping between EXP and the internal priority for inbound

packets.5. On ME60 B, configure the mapping between DSCP and the internal priority for outbound

packets.6. Apply the priority mapping to the relevant interfaces.


l The DSCP value 18 in an inbound packet on ME60 A

l The EXP value 5 in an outbound packet on ME60 A

l The EXP value 5 in an inbound packet on ME60 B

l The DSCP value 34 in an outbound packet on ME60 B


Only the procedures related to priority mapping are mentioned.

1. Map the DSCP values to MPLS on GE1/0/0 of ME60 A.<ME60A> system-view [ME60A] diffserv domain ds1[ME60A-dsdomain-ds1] ip-dscp-inbound 18 phb af4 green[ME60A-dsdomain-ds1] mpls-exp-outbound af4 green map 5[ME60A-dsdomain-ds1] quit[ME60A] interface GigabitEthernet 1/0/0[ME60A-GigabitEthernet1/0/0] trust upstream ds1[ME60A] interface GigabitEthernet 1/0/1



2-21

[ME60A-GigabitEthernet1/0/1] trust upstream ds1

2. Map the DSCP values to MPLS on GE1/0/0 of ME60B.<ME60B> system-view [ME60B] diffserv domain ds1[ME60B-dsdomain-ds1] mpls-exp-inbound 5 phb af3 green[ME60B-dsdomain-ds1] ip-dscp-outbound af3 green map 34[ME60B] interface GigabitEthernet 1/0/0[ME60B-GigabitEthernet1/0/0] trust upstream ds1[ME60B] interface GigabitEthernet 1/0/1[ME60B-GigabitEthernet1/0/1] trust upstream ds1

Configuration Filesl Configuration file of ME60 A

# sysname ME60A# mpls lsr-id 1.1.1.9 mpls#mpls ldp#mpls ldp remote-peer peerb remote-ip 3.3.3.9#diffserv domain ds1 ip-dscp-inbound 18 phb af4 green mpls-exp-outbound af4 green map 5# interface GigabitEthernet1/0/0 undo shutdown ip address 10.1.2.1 255.255.255.0 trust upstream ds1#interface GigabitEthernet1/0/1 undo shutdown ip address 10.1.1.1 255.255.255.0 mpls mpls ldp trust upstream ds1#interface LoopBack1 ip address 1.1.1.9 255.255.255.255#ospf 1 area 0.0.0.0 network 10.1.1.0 0.0.0.255 network 10.1.2.0 0.0.0.255 network 1.1.1.9 0.0.0.0#return

l Configuration file of Router# sysname Router# mpls lsr-id 2.2.2.9 mpls#mpls ldp#interface GigabitEthernet1/0/0 undo shutdown ip address 10.1.1.2 255.255.255.0 mpls mpls ldp#




Issue 05 (2010-06-01)

interface GigabitEthernet1/0/1 undo shutdown ip address 20.1.1.1 255.255.255.0 mpls mpls ldp#interface LoopBack1 ip address 2.2.2.9 255.255.255.255#ospf 1 area 0.0.0.0 network 10.1.1.0 0.0.0.255 network 20.1.1.0 0.0.0.255 network 2.2.2.9 0.0.0.0#return

l Configuration file of ME60 B# sysname ME60B# mpls lsr-id 3.3.3.9 mpls#mpls ldp#mpls ldp remote-peer peera remote-ip 1.1.1.9#diffserv domain ds1 ip-dscp-outbound af3 green map 34 mpls-exp-inbound 5 phb af3 green #interface GigabitEthernet1/0/0 undo shutdown ip address 20.1.1.2 255.255.255.0 mpls mpls ldp trust upstream ds1#interface GigabitEthernet1/0/1 undo shutdown ip address 20.1.2.1 255.255.255.0 trust upstream ds1#interface LoopBack1 ip address 3.3.3.9 255.255.255.255#ospf 1 area 0.0.0.0 network 20.1.1.0 0.0.0.255 network 20.1.2.0 0.0.0.255 network 3.3.3.9 0.0.0.0#return



2-23

3 QoS Scheduling Configuration

About This Chapter

This chapter describes the knowledge about QoS scheduling, including the basic concepts,configuration procedures and configuration examples.

3.1 IntroductionThis section describes the basic principles and the implementation of QoS scheduling.

3.2 Configuring QoS SchedulingThis section describes how to configure and use the functions of 5-level QoS scheduling.

3.3 Configuring QoS Scheduling for the Multi-Play ServiceThis section describes how to configure and implement QoS scheduling for the multi-playservice.

3.4 Configuring the L2TP HQoSThis section describes how to configure and use the L2TP HQoS.

3.5 Configuration ExamplesThis section provides several configuration examples of QoS scheduling.

Quidway ME60 Multiservice Control GatewayConfiguration Guide - QoS 3 QoS Scheduling Configuration


3-1

3.1 IntroductionThis section describes the basic principles and the implementation of QoS scheduling.

3.1.1 QoS Scheduling Overview

3.1.2 Application in the ME60

3.1.1 QoS Scheduling OverviewThe broadband access network is constructed with LAN switches or Digital Subscriber LineAccess Multiplexer (DSLAM). It is usually a Layer 2 network with a weak QoS capability.Therefore, the access network cannot support the effective and integrated QoS function for theentire network. The main causes for the weak QoS capability are as follows:

l The QoS policies cannot be deployed statically on the access network .The broadband access network is a public network. The physical locations of subscribersare changable and their requirements for QoS vary. In such circumstances, the carrier cannot determine QoS policies required by the subscriber, in advance.

l The QoS capability of a Layer 2 network device is not powerful.Due to the costs of constructing the network, the Layer 2 devices in the broadband accessnetwork usually have limited QoS capability, for example, limited scheduling queues andbuffer. The Layer 2 devices are not required to provide the QoS capability that matches thecapability of a high-end Layer-3 device.

An effective solution is to consider the QoS capability of the Layer 2 network as a method ofprotecting the network. The real QoS guarantee, however, must be carried out by the edgeconvergence device (for example, the ME60).

QoS scheduling means that the edge convergence device conducts the QoS scheduling inadvance for the downstream traffic (entering the access network from the backbone network).The device takes measures such as traffic shaping and congestion avoidance according to suchfactors as the topology and processing capability of the access network. In this case, the trafficin the access network is stable, and congestion is avoided.

The QoS scheduling on the edge convergence device reduces the requirements on the QoScapability of the Layer 2 device. In addition, the costs for constructing and maintaining the Layer2 network is reduced and the QoS of the entire network can be improved.

3.1.2 Application in the ME60

The model of 5-level QoS scheduling is proposed by the Digital Subscriber Line (DSL) forumin TR-059 and TR-092. The model is applicable to the complex and multi-layer access networks.

The ME60 adopts the specifications in TR-059 and TR-092 and can provide 5-level QoSscheduling. That is, it can conduct QoS scheduling at five levels: session, Virtual Circuit (VC),VC group/VLAN group, Virtual Path (VP), and physical port, as shown in Figure 3-1.

3 QoS Scheduling ConfigurationQuidway ME60 Multiservice Control Gateway



Issue 05 (2010-06-01)

Figure 3-1 QoS scheduling supported by the ME60

Session Queue VC

Queue VC Group Queue

VP Queue

Port Queue

SessionScheduler

VCScheduler

VC GroupScheduler

VPScheduler

PortScheduler

Application Modes of QoS SchedulingIn the ME60, the application mode and configuration method of QoS scheduling vary with thenetwork environment. The application modes include the router mode, provider edge (PE) mode,QoS on demand (QoD) mode, and dynamic service gateway (DSG) mode.

QoS Scheduling for the Multi-Play ServiceWith the development of the Multi-Play service, a family may have several terminals toimplement various services, such as the voice service, video service, and data service. In a family,different services have different requirement for delay, jitter, and bandwidth. In addition,resource must be ensured for the preferential service when the network resource is insufficient.Therefore, QoS scheduling must take a family but not a terminal as a unit; otherwise, the qualityof special services (such as the voice service) cannot be guaranteed when multiple services areimplemented at the same time for a family.

L2TP HQoSThe L2TP QoS scheduling involves the QoS scheduling of the LAC and the QoS scheduling ofthe LNS. The QoS scheduling of the LAC can be a common QoS scheduling.

The L2TP HQoS mainly works on the QoS scheduling for users at the LNS side, which aims atcarrying out a comprehensive and detailed planning on the traffic that goes into the L2TP tunneland the service traffic in the tunnel.



3-3

3.2 Configuring QoS SchedulingThis section describes how to configure and use the functions of 5-level QoS scheduling.


3.2.2 Configuring the Queue Profile

3.2.3 Configuring the Scheduling Profile

3.2.4 Configuring the Drop Profile

3.2.5 Configuring the QoS Profile

3.2.6 Creating a VC Group and Binding a QoS Profile to the Group

3.2.7 Creating a VP Group and Binding a QoS Profile to the Group

3.2.8 Configuring QoS Scheduling

3.2.9 Configuring QoS Scheduling on Network-side Interfaces

3.2.10 (Optional) Configuring Port-based Traffic Shaping

3.2.11 (Optional) Configuring the Forwarding Line Speed of the 10G Board




When functioning as a BRAS, the ME60 is connected to layer-2 devices, which have low QoScapabilities. Configure QoS scheduling on the ME60 so that the ME60 can perform hierarchicalQoS control for the traffic passing through it.


Before configuring the QoS scheduling, complete the following tasks:



l Configuring the IP addresses and BRAS attributes of the relevant interfaces

Data Preparation

To configure the QoS scheduling, you need the following data.

No. Data

1 Queue profile name and the relevant parameters

2 Scheduler profile name and the relevant parameters




Issue 05 (2010-06-01)

No. Data

3 Drop profile name and the relevant parameters

4 QoS profile name, bound queue profile, scheduler profile, and drop profile

5 Names of the domain, VC group, VP group, and interface, which need to be boundwith QoS profiles

3.2.2 Configuring the Queue Profile

ContextDo as follows on the ME60.

Procedure



Step 2 Run:queue-profile queue-profile-name

A queue profile is created.

By default, a QoS profile named default exists in the system. You can modify the parameters ofthis profile, but cannot delete this profile.

Step 3 Run:scheduler-style { sp | wrr }{ sp | wrr }{ sp | wrr }{ sp | wrr }{ sp | wrr }{ sp | wrr }{ sp | wrr }{ sp | wrr }

The scheduling style of the queue is configured.

The queues that match the above scheduling style command are BE, AF1, AF2, AF3, AF4, CS6,and CS7 in order.

The default scheduling style is SP.

NOTE

When you run this command to configure a scheduling style, the number of queues that use the schedulingstyle must be greater than or equal to two and WRR must be configured in adjacent queues if the schedulingstyle contains WRR.

Step 4 Run:queue-class { be | af1 | af2 | af3 | af4 | ef | cs6 | cs7 }

The queue view is displayed.

Step 5 Run:queue length queue-length

The length of the queue is set.



3-5

The default length of a queue is 20480 bytes.

Step 6 Configure the weight as follows:l To configure the WRR weight, run the queue wrr-value wrr-value command.

l To configure the WRED weight, run the wred enable command to enable the WREDalgorithm, and then run the wred weight weight command to configure the WRED weight.

By default, the WRED algorithm is used. The defaut value of WRED weight is 0.

----End



Procedure



Step 2 Run:scheduler-profile scheduler-profile-name

A scheduler profile is created.

By default, a scheduling profile named default exists in the system. You can modify theparameters of this profile, but you cannot delete this profile.

NOTE

If the QoS profile to which the scheduling profile is bound is applied to the domain and the parameters ofthe scheduling profile are modified, the parameters can take effect only when the users in this domain getonline once again. If the VP Group or VC Group corresponding to the QoS profile to which the schedulingprofile is bound has been applied and you modify the parameters of the scheduling profile, you need toreapply the VP Group or VC Group to make the parameters become valid.

Step 3 Run:car cir cir [ pir pir ] [ cbs cbs pbs pbs ] { downstream | upstream }

The CAR function is configured.

NOTE

On the ME01LPUB board, the CIR and PIR are both lower than 70 Kbit/s.

By default, the CAR function is disabled for the inbound and outbound traffic.

Step 4 Run:gts cir cir [ pir pir ] [ queue-length length ] [ inbound | outbound ]

The GTS shapping parameters are set.

It is recommended that set the GTS bandwidth to be equivalent to or larger than 32 kbit/s.

By default, the GTS shaping function is disabled.




Issue 05 (2010-06-01)

Step 5 Run:wfq weight weight

The WFQ weight is configured.

The default WFQ weight is 10.

----End

3.2.4 Configuring the Drop Profile


Procedure



Step 2 Run:drop-profile drop-profile-name

A drop profile is created.

By default, a drop profile named default exists in the system. You can modify the parametersof this profile, but you cannot delete this profile.

Step 3 Run:taildrop-threshold service-name threshold-value

The drop threshold is set.

Table 3-1 shows the mappings between the CoS and the default drop threshold.

Table 3-1 Default drop thresholds

Service Type Default Drop Thresholds

CS7 100

CS6 90

EF 80

AF4 70

AF3 60

AF2 60

AF1 55

BE 55



3-7

Step 4 Run:wred threshold-percent high-limit low-limit

The drop threshold of the WRED algorithm is set.

Step 5 Run:wred guaranteed-threshold threshold-value

The guaranteed pass ratio of packets with the WRED algorithm is configured.

Step 6 Run:wred { green | red } low-limit low-limit-value high-limit high-limit-value discard-percentage discard-percentage

The drop thresholds of the packets with different colors used with the WRED algorithm are set.

NOTE

This command does not take effect for the drop profile default.

----End


Context


Procedure



Step 2 Run:qos-profile qos-profile-name

The QoS profile is created and the QoS profile view is displayed.

By default, a QoS profile named default exists in the system. You can modify the parameters ofthis profile, but you cannot delete this profile.

NOTE

If this QoS profile is applied to the domain and the scheduling profile is deleted or another schedulingprofile is rebound, parameters take effect only after the user in the domain gets online once again. If theVP Group or VC Group corresponding to the QoS profile is applied and you delete the scheduling profileor rebind another scheduling profile, you need to reapply the VP Group or VC Group to make the parametersbecome valid.


A scheduler profile is bound.





Issue 05 (2010-06-01)

A queue profile is bound.


A drop profile is bound.

By default, QoS profile default is bound to scheduler profile default, queue profile default, anddrop profile default. The default settings of the new QoS profile are the same as the defaultsettings of the QoS profile default.

----End

3.2.6 Creating a VC Group and Binding a QoS Profile to the Group


Procedure



Step 2 Run:interface { gigabitethernet | eth-trunk } interface-number


Step 3 Run:vc-group vc-group-name qos-profile qos-profile-name

The VC group is created and is bound to a QoS profile.

----End

3.2.7 Creating a VP Group and Binding a QoS Profile to the Group


Procedurel Creating a VP Group and Binding a QoS Profile to the Group in the Interface View

1. Run:system-view


interface { gigabitethernet | eth-trunk } interface-number



3-9


vp-group vp-group-name qos-profile qos-profile-name

The VP group is created and is bound to a QoS profile.l Creating a VP Group and Binding a QoS Profile to the Group in the System View

1. Run:system-view


vp-group vp-group-name qos-profile qos-profile-name

The VP group is created and is bound to a QoS profile.

----End

3.2.8 Configuring QoS Scheduling

Procedurel Configuring the VC-level scheduler

1. Run:system-view


aaa

The AAA view is displayed.3. Run:

domain domain-name

The domain view is displayed.4. Run:

user-priority { upstream | downstream } { priority | trust-8021p-inner | trust-8021p-outer | trust-dscp | trust-exp-inner | trust-exp-outer | unchangeable }

The user priority is configured.

To configure the user priority when the QoS profile is applied on the domain, do asfollows:

– Specify the user priority value directly. The value ranges from 0 to 7.

– Use the internal or external 802.1p value of the layer 2 packets as the user priority.This method is invalid for the packets from the network to users.

– Use the DSCP value of user packets as the user priority.

– Use the EXP value of MPLS packets as the user priority.

NOTE

For the L2TP user, the user priority is applied to the external L2TP tunnel packets. The priorityof internal user packets is not changed.




Issue 05 (2010-06-01)

5. You can implement VC-level QoS scheduling in either of the following ways:– Run the qos profile qos-profile-name command to bind the QoS profile to the

domain.– Run the qos profile qos-profile-name command to bind the QoS profile to the

tunnel interface.6. Run:

time-range qos-profile { enable | range-name qos-profile-name }

Time range-based QoS control is enabled in the domain.

You can bind the QoS profile to the domain to implement VC-level QoS scheduling.

By default, QoS profile named default is bound to the domain.

You can also bind the QoS profile to the tunnel interface. In this way, the QoS profileparameters are applied to the tunnel and thus the VC-level QoS scheduling isimplemented.

l Configuring the VC group-level scheduler1. Run:

system-view


interface interface-type interface-number.sub-interface-number


user-vlan start-vlan [ end-vlan ] [ qinq start-qinq-vlan [ end-qinq-vlan ] ]


qos vc-group vc-group-name [ each-vlan ]

The VLAN is bound to the VC group.

By default, the QoS profile is not bound to the user VLAN.

You can bind the VC group to the VLAN to implement VC group-level QoSscheduling.

l Configuring the VP-level scheduler1. Run:

system-view


interface interface-type interface-number.sub-interface-number


qos vp-group vp-group-name

The sub-interface is bound to the VP group.

By default, the sub-interface is not bound to the QoS profile.



3-11

You can bind the sub-interface to the VP group to implement VP-level QoSscheduling.

l Configuring the port scheduler1. Run:

system-view




qos profile qos-profile-name port

The QoS profile is bound to the interface.

----End

3.2.9 Configuring QoS Scheduling on Network-side Interfaces


Procedurel Configure QoS scheduling on network-side interfaces when you create a VP group and

bind a QoS profile in the system view.1. Run:

system-view




NOTE

The interface is a GE interface.

3. Run:qos vc-group group-name [ inbound | outbound [before-layer2-encapsulation ] | vp-group group-name { inbound | outbound before-layer2-encapsulation } ]

The VC-level QoS sheduler and the VP-level QoS scheduler are configured on thenetwork-side interface.

l Configure QoS scheduling on network-side interfaces when you create a VP group andbind a QoS profile in the interface view.1. Run:

system-view





Issue 05 (2010-06-01)



NOTE

The interface is a GE interface.

3. Run:qos vc-group vc-group-name [ outbound ]

The VC-level QoS sheduler is configured on the network-side interface.4. Run:

qos vp-group vp-group-name

The VP-level QoS sheduler is configured on the network-side interface.

----End

3.2.10 (Optional) Configuring Port-based Traffic Shaping

Context


Procedure



Step 2 Run:qos port-shaping slot slot-number

Port-based traffic shaping is enabled on the specified board.

By default, port-based traffic shaping is not enabled on a board.

After port-based traffic shaping is enabled on a board, all the interfaces on the board have thetraffic shaping function. By default, shaping value is the maximum traffic volume that aninterface can forward.



NOTE

The interface must be a main GE interface.

Step 4 Run:port shaping shaping-value

The traffic shaping value is set on the interface.



3-13

After the configuration, the total traffic volume of the outbound packets cannot exceed the settraffic shaping value.

----End

3.2.11 (Optional) Configuring the Forwarding Line Speed of the10G Board


Procedure



Step 2 Run:qos tm-schedule simple slot slot-number

The line speed for the 10G board to forward small packets is set to 10 Gbit/s.

By default, the 10G board of the ME60 cannot forward small packets at the line speed of 10G.After this command is run, the line speed for forwarding small packets of the 10G board canreach 10 Gbit/s.

----End

3.2.12 Checking the ConfigurationRun the following commands in any view to check the previous configuration.

Action Command

Check the configuration of thequeue profile.

display queue-profile [ all | name queue-profile-name ]

Check the configuration of thescheduler profile.

display scheduler-profile [ all | name scheduler-profile-name ]

Check the configuration of thedrop profile.

display drop-profile [ all | name drop-profile-name ]

Check the configuration of theQoS profile.

display qos-profile [ all | name qos-profile-name ]

Check the valid QoSparameters.

display qos-parameter access-user user-id

By running the display queue-profile command, you can view the detailed information aboutthe queue profile.




Issue 05 (2010-06-01)

<Quidway> display queue-profile name qp1Description:WR-E: Wred Enable WR-W: Wred Weight Sch-T: Schedule StyleWRR-W: Wrr Weight Q-L: Queue Length D:Disable E:EnableWfq-W: Wfq-Weight gen: general------------------------------------------------------------------------------- Queue profile name : qp1 Queue profile index: 2------------------------------------------------------------------------------- WR-E WR-W Sch-T WRR-W Q-L CIR CBS PIR PBS WFQ-W-------------------------------------------------------------------------------be D 0 sp 1 20480 - - - - -af1 D 0 sp 2 20480 - - - - -af2 D 0 sp 3 20480 - - - - -af3 D 0 sp 4 20480 - - - - -af4 D 0 sp 5 20480 - - - - -ef D 0 sp 6 20480 - - - - -cs6 D 0 sp 7 20480 - - - - -cs7 D 0 sp 8 20480 - - - - -gen - - - - - 1000 125000 1000 125000 80 ARITHMETIC WFQ-W DROP-PROFILE PCT-EN PCT--------------------------------------------------------------------------------be wfq 10 - no 100af1 wfq 10 - no 100af2 wfq 10 - no 100af3 wfq 15 - no 100af4 wfq 15 - no 100ef pq 100 - no 100cs6 pq 100 - no 100cs7 pq 100 - no 100

By running the display scheduler-profile command, you can view the detailed informationabout the scheduler profile.

<Quidway> display scheduler-profile name sp1 ------------------------------------------------------------ Scheduler profile : sp1 Scheduler index : 1 WFQ weight : 10 Upstream: car cir 1000 (Kbps) cbs 125000 (byte) pbs 313000 (byte) gts inbound disable Downstream: car disablegts outbound disable

By running the display drop-profile command, you can view the detailed information aboutthe drop profile.

<Quidway> display drop-profile name dp1 ----------------------------------------------------- drop profile : dp1 drop profile index : 1 Wred threshold-percent(%) : 20 50 threshold-group(%) : be | af1 | af2 | af3 | af4 | ef | cs6 | cs7 55 55 60 60 70 40 90 100 Low-limit High-limit Discard-per green 100 100 100 yellow 100 100 100 red 100 100 100

By running the display qos-profile command, you can view the queue profile, the schedulerprofile, and the drop profile bound to the QoS profile.

<Quidway> display qos-profile name qos1 -------------------------------------------------------- QoS index : 1 QoS profile : qos1



3-15

Scheduler profile : sp1 Queue profile : qp1 Drop profile : dp1 flow-mapping profile : link-adjustment : 14

Run the following commands in any view to check the previous configuration.

Action Command

Check the configuration of theVC group on the interface.

display vc-group [ vc-group-name ]

Check the configuration of theVP group on the interface.

display vp-group [ vp-group-name ]

By running the display vc-group command, you can view the QoS profile bound to the VCgroup.

<Quidway> system-view[Quidway] interface gigabitEthernet 5/0/6[Quidway-GigabitEthernet5/0/6] display vc-group vc1 ---------------------------------------------------------------------- index name profile ---------------------------------------------------------------------- 0 vc1 qos1

By running the display vp-group command, you can view the QoS profile bound to the VPgroup.

<Quidway> system-view[Quidway] interface gigabitEthernet 5/0/6[Quidway-GigabitEthernet5/0/6] display vp-group vp1 ---------------------------------------------------------------------- index name profile ---------------------------------------------------------------------- 0 vp1 qos1

3.3 Configuring QoS Scheduling for the Multi-Play ServiceThis section describes how to configure and implement QoS scheduling for the multi-playservice.

QoS scheduling at the VC level is implemented by binding a family profile to a QoS profile andapplying the family profile to an interface.

After service identification is configured, packets that satisfy the identification condition aremapped to the corresponding domain and the QoS profile is applied to the domain. In this manner,QoS scheduling at the session level is implemented.


3.3.2 Configuring the Family Identification Mode

3.3.3 Binding a QoS Profile to a Family Profile

3.3.4 (Optional) Setting the Maximum Number of Access Users Allowed by a Family

3.3.5 (Optional) Excluding Service Traffic of Users in a Domain from the QoS Scheduling of aFamily




Issue 05 (2010-06-01)

3.3.6 Binding a QoS Profile to a Domain

3.3.7 Configuring the Service Identification Mode

3.3.8 Binding a Family Profile and a Service Identification Policy to a BAS Interface




A family may use multiple terminals to implement various services. These services havedifferent requirements for delay, jitter, and bandwidth. Network resources must be guaranteedfor preferential services when network resources are insufficient. Therefore, QoS schedulingmust be performed based on a family rather than a terminal.

For the Multi-Play service, the ME60 performs QoS scheduling on a logon service according tothe family and service identification results.

Pre-configuration Tasks

Before configuring QoS scheduling for the Multi-Play service, complete the following tasks:

l Configuring the BRAS function on the ME60 so that users can normally go online. Forrelated configurations, refer to the Quidway ME60 Multiservice Control GatewayConfiguration Guide - BRAS Service.

l Configuring the queue profile, drop profile, and scheduling profile of the family. For relatedconfigurations, see 3.2.2 Configuring the Queue Profile, 3.2.3 Configuring theScheduling Profile, and 3.2.4 Configuring the Drop Profile.

l Configuring the queue profile, drop profile, scheduling profile, and QoS profile for eachservice. For related configurations, see 3.2.2 Configuring the Queue Profile, 3.2.3Configuring the Scheduling Profile, and 3.2.4 Configuring the Drop Profile.

l Creating the QoS profile of the family and binding the queue profile, discard profile, andscheduling profile to the QoS profile. For related configurations, see 3.2.5 Configuringthe QoS Profile.

l Creating the QoS profile for each service and binding the queue profile, discard profile,and scheduling profile to the QoS profile. For related configurations, see 3.2.5 Configuringthe QoS Profile.

Data Preparation

To configure basic functions of QoS scheduling for the Multi-Play service, you need thefollowing data.

No. Data

1 Interface number of the access user

2 Family profile name and family identification policy

3 Data related to the specific family identification policy: QinQ ID and VLAN ID



3-17

No. Data

4 Service identification policy name and service identification mode: QinQ ID, CoSvalue in an inner or outer VLAN tag, and DSCP value

5 Queue profile name and related parameters

6 Scheduling profile name and related parameters

7 Drop profile name and related parameters

8 QoS profile name

NOTE

If the parameters for configuring the family profile and the service identification policy are changed aftera family or a user goes online, the related parameters take effect only after the user goes online again.

3.3.2 Configuring the Family Identification Mode

Procedure



Step 2 Run:session-group-profile profile-name

A family profile is created and the family profile view is displayed.

By default, a family profile named default exists.

Step 3 Run:session-group-identify { vlan | inner-vlan | outer-vlan | access-circuit-id }

The family identification mode is configured.

By default, the family identification mode is set to the VLAN mode.

----End

3.3.3 Binding a QoS Profile to a Family Profile

Procedure




The family profile view is displayed.




Issue 05 (2010-06-01)

Step 3 Run:qos-profile profile-name

The QoS profile is bound to the family profile.

----End

3.3.4 (Optional) Setting the Maximum Number of Access UsersAllowed by a Family

Procedure




The family profile view is displayed.

Step 3 Run:session-limit max-number

By default, the maximum number of access users allowed by a family is 256.

----End

3.3.5 (Optional) Excluding Service Traffic of Users in a Domainfrom the QoS Scheduling of a Family

Procedure



Step 2 Run:aaa

The AAA view is displayed.

Step 3 Run:domain

A domain is created and the AAA domain view is displayed.

Step 4 Run:session-group-exclude [ gts | car ]

Service traffic of users in the domain is excluded from the QoS scheduling of the family.

l To exclude the service traffic of users going online from a specified domain from the GTSof family policy scheduling, run the session-group-exclude gts command .



3-19

l To exclude the service traffic of users going online from a specified domain from the CARof family policy scheduling, run the the session-group-exclude car command.

l To exclude the service traffic of users going online from a specified domain from the QoSscheduling of the family, run the the session-group-exclude command. Then, single service-based bandwidth management is implemented.

----End

3.3.6 Binding a QoS Profile to a Domain

ContextQoS scheduling at the session level is implemented by binding a QoS profile to a domain.

Procedure



Step 2 Run:aaa


Step 3 Run:domain domain-name

Domain domain-name is created and the AAA domain view is displayed.

domain-name specifies the name of the domain to which the service is mapped.

Step 4 Run:qos profile profile-name

The QoS profile is bound to the domain.

----End

3.3.7 Configuring the Service Identification Mode

ContextThe ME60 supports four service identification modes. You must set a proper serviceidentification mode according to the network requirements.

NOTE

The ME60 supports the function of configuring service identification for IPoX access users including IPoE,IPoEoVLAN, and IPoEoQ access users.

Procedurel Configuring the inner or outer VLAN ID-based service identification mode

1. Run:system-view




Issue 05 (2010-06-01)


service-identify-policy policy-name

A service identification policy is created and the service identification policy view isdisplayed.

By default, no service identification policy is configured.3. Run:

service-identify { inner-vlan | outer-vlan }

The service identification mode is configured.4. Run:

vlan start-vlan-id [ end-vlan-id ] domain domain-name

The packets with specified VLAN IDs are mapped to a domain.l Configuring the service identification mode based on the CoS values in the inner or outer

VLAN tags1. Run:

system-view





service-identify cos { inner-vlan | outer-vlan }


dot1p start-cos-value [ end-cos-value ] domain domain-name

The packets with the specified CoS values in the inner or outer VLAN tags are mappedto a domain.

l Configuring the DSCP value-based service identification mode1. Run:

system-view





service-identify dscp

The service identification mode is configured.



3-21

4. Run:dscp start-dscp-code [ end-dscp-code ] domain domain-name

The packets with specified DSCP values are mapped to a domain.l Configuring the DHCP Option 60-based service identification mode

1. Run:system-view





service-identify dhcp-option60


option60 partial-match

Partial match of Option 60 strings is configured.

By default, the match mode is domain included.

----End

3.3.8 Binding a Family Profile and a Service Identification Policy toa BAS Interface

Procedure





Step 3 Run:bas

The BAS interface view is displayed.

Step 4 Run:access-type layer2-subscriber

The user access type is configured as the Layer 2 user.

A family profile and a service identification policy can be bound to a BAS interface specifiedto work only in Layer 2 access mode.




Issue 05 (2010-06-01)


The family profile is bound to a BAS interface.

Step 6 Run:service-identify-policy policy-name

The service identification policy is bound to a BAS interface.

----End


Action Command

Check configurations of thefamily profile.

display session-group-profile { all | name profile-name }[ verbose ]

Check configurationinformation of the serviceidentification policy.

display service-identify-policy { all | name profile-name }[ verbose ]

Check information about allthe families bound to aninterface.

display session-group interface interface-type interface-number

Check information about allthe families bound to a board.

display session-group slot slot-id [ session-group-idsession-group-id ]

Check QoS queue resources. display qos-queue { pq | afq | flqg } [ queue-number ]{ slot slot-number }

Check information about aspecified online user.

display qos user-id user-id

Using the display session-group-profile command, you can view configurations of a familyprofile or all family profiles.

<Quidway> display session-group-profile name home verbose -------------------------------------------------------- Session group index : 2 Session group profile : home Qos profile : default Identify type : inner-vlan Binded to IF : GigabitEthernet7/0/7.1

Using the display service-identify-policy command, you can view configuration informationabout a service identification policy.

<Quidway> display service-identify-policy name test verbose---------------------------------------------- Service-identify-policy Index : 5 Used : 1 Service-identify-policy : test Service-Type : inner-vlan Domain Name : default0



3-23

Begin-Vlan: : 100 End-Vlan: : 200 Binded to IF : GigabitEthernet7/0/7.1

Using the display session-group interface command, you can view information about all thefamilies bound to an interface.

<Quidway> display session-group interface gigabitethernet 7/0/7.1------------------------------------------------------------------- The used session-group ID table are : 2-192------------------------------------------------------------------- Current interface contains session-group : 191-------------------------------------------------------------------

Using the display session-group slot command, you can view information about all the familiesbound to a board.

<Quidway> display session-group slot 7 session-group-id 4 Session-group index : 4 Session-group name : Quidway-C05-SRV-02002000000016@guan Session-group access interface : GigabitEthernet7/0/7.1 Session-group indenify mode : User Name Session-group current session count: 11 Session-group contains CID: 196 200 201 202 281 318 380 381 432 435 439 Up CAR enable : YES Up committed info rate : 300 (Kbps) Up peak info rate : 400 (Kbps) Up committed burst size : 37500 (bytes) Up peak burst size : 50000 (bytes) Down CAR enable : YES Down committed info rate : 100 (Kbps) Down peak info rate : 200 (Kbps) Down committed burst size : 12500 (bytes) Down peak burst size : 25000 (bytes) Down GTS enable : NO Up packets number(high,low) : (0,0) Up bytes number(high,low) : (0,0) Down packets number(high,low) : (0,0) Down bytes number(high,low) : (0,0)

Using the display qos-queue command, you can view usage information about a specific typeof queue on a specified interface board.

<Quidway> display qos-queue pq slot 4*-------------------------------- QoS --------------------------------------* Info: PQ total resource :1000 Info: PQ used resource :150

Using the display qos user-id command, you can view information about flow queues of aspecified user.

*------------------------- QoS Queue: 8322 -------------------------------*Flow RxPkt RxByte TxPkt TxByte PktDrop ByteDropCS7 0 0 0 0 0 0CS6 0 0 0 0 0 0EF 0 0 0 0 0 0AF4 0 0 0 0 0 0AF3 0 0 0 0 0 0AF2 0 0 0 0 0 0AF1 0 0 0 0 0 0BE 0 0 0 0 0 0

3.4 Configuring the L2TP HQoSThis section describes how to configure and use the L2TP HQoS.




Issue 05 (2010-06-01)




3.4.4 Applying the QoS Profile to the Domain

3.4.5 Configuring the L2TP HQoS Scheduling Mode



Applicable EnvironmentIn the application scenario of L2TP service wholesale, the LAC works on only the servicewholesale, while the service control point is actually the LNS. Between the LAC and the LNSis an L2TP tunnel. Therefore, you need to carefully plan and control the traffic that goes intothe L2TP tunnel and the service traffic in the tunnel on the LNS to minimize the influence fromthe unnecessary competition for service traffic between the LAC and the LNS on the servicequality. And carriers can control the traffic of different services that goes into the backbonenetwork to limit the abrupt traffic of users in the tunnel.

The L2TP HQoS mainly works on the QoS scheduling for users at the LNS side, which aims atcarrying out a comprehensive and detailed planning on the traffic that goes into the L2TP tunneland the service traffic in the tunnel.

Pre-configuration TaskBefore configuring the L2TP HQoS, complete the following tasks:

l Setting the VSU to the TSU mode

l Configuring the L2TP so that the L2TP users can go online

Data PreparationTo configure the L2TP HQoS, you need the following data.

No. Data

1 Scheduling profile

2 QoS profile

3 Traffic shaping parameters


ContextDo as follows on the ME60 that functions as the LNS.



3-25

Procedure




A scheduler profile is created.

Step 3 Run:gts cir cir [ pir pir ] [ queue-length length ] [ inbound | outbound ]

The GTS shaping parameters are set.

----End


Context

Do as follows on the ME60 that functions as the LNS.

Procedure



Step 2 Run:qos-profile qos-profile-name

The QoS profile is created and the QoS profile view is displayed.

By default, a QoS profile named default exists in the system. You can modify the parameters ofthis profile, but you cannot delete this profile.


A scheduler profile is bound.

----End

3.4.4 Applying the QoS Profile to the Domain

Context

Do as follows on the ME60 that functions as the LNS.




Issue 05 (2010-06-01)

Procedure



Step 2 Run:aaa



The domain view is displayed.

The domain view displayed is the domain where the L2TP users reside.

Step 4 Run:qos profile qos-profile lns-gts

The QoS profile is applied to the domain and the scheduling mode is set to LNS scheduling.

----End

3.4.5 Configuring the L2TP HQoS Scheduling Mode

ContextDo as follows on the ME60 that functions as the LNS.

Procedure



Step 2 Run:l2tp-group group-name

The L2TP group is created and the L2TP group view is displayed.

The L2TP group should be the L2TP group of the LNS.

Step 3 Run:qos scheduling-mode { session | tunnel }

The L2TP HQoS scheduling mode is set.

The L2TP HQoS has the following two scheduling modes:

l Scheduling by tunnels: In this mode, user services are not the concern. So users are not givenuser queues; while tunnels are allocated user queues.

l Scheduling by sessions: In this mode, users are given user queues and tunnels are allocatedgroup queues. Each user is given 8 user queues with a priority from 1 to 8 and the SP or WFQscheduling can be performed between any of the user queues.



3-27

By default, the scheduling is performed by tunnels.

Step 4 (Optional) Run:qos profile qos-profile2 [ inbound | outbound ]

The QoS profile is bound.

NOTE

If the scheduling is set to be performed by sessions, this command must be run; otherwise, you do not needto run this command.

----End

3.4.6 Checking the ConfigurationAction Command

Check the configuration of thedomain.

display domain name domain-name

Check the configuration of theL2TP group.

display l2tp-group group-name

3.5 Configuration ExamplesThis section provides several configuration examples of QoS scheduling.

3.5.1 Example for Configuring QoS Scheduling in Router Mode

3.5.2 Example for Configuring QoS Scheduling in PE Mode

3.5.3 Example for Configuring QoS Scheduling in QoD Mode

3.5.4 Example for Configuring QoS Scheduling in DSG Mode

3.5.5 Example for Configuring the Multi-Play Service

3.5.6 Configuring the Added Function in the Multi-Play Service

3.5.7 Example for Configuring the L2TP QoS by Tunnels

3.5.8 Example for Configuring the L2TP QoS by Sessions

3.5.1 Example for Configuring QoS Scheduling in Router Mode

Networking RequirementAs shown in Figure 3-2, the ME60 functions as a router. Two local networks 1.1.1.0/24 and1.1.2.0/24 access the ME60 through GE1/0/0.1 and GE1/0/0.2.

At sub-interface GE1/0/0.1, the maximum downstream rate is 500 Mbit/s and the downstreamcommitted rate is 100 Mbit/s. At sub-interface GE1/0/0.2, the maximum downstream rate is 600Mbit/s and the downstream committed rate is 150 Mbit/s.

The drop thresholds of the service flows EF, AF4, AF3, AF2, AF1, CS6, CS7, and BE at theinterface and the sub-interface are 100, 80, 70, 60, 50, 40, 30, and 20. Each queue contains 60




Issue 05 (2010-06-01)

kbytes. The scheduling styles of the eight queues at session level are WRR. The WRR weightsare 45, 40, 35, 30, 25, 20, 15, and 10.

Figure 3-2 Example of the configuration of QoS scheduling in router mode

Loopback010.10.10.10/32

ME60

MPLS VPN

GE8/0/0.13.3.3.2/24

Tunnel8/0/0

Router

Loopback020.20.20.20/32


1. Configure the queue profile.2. Configure the scheduler profile.3. Configure the drop profile.4. Configure the QoS profile.5. Configure the VP group.6. Bind the VP group to a sub-interface.7. Apply the QoS profile to the interface.

Data PreparationNone.


Only the procedures related to QoS scheduling are mentioned.

1. Configure the queue profile.[Quidway] queue-profile queue1[Quidway-queue-queue1] scheduler-style wrr wrr wrr wrr wrr wrr wrr wrr[Quidway-queue-queue1] queue-class ef[Quidway-queue-queue1-ef] queue length 60[Quidway-queue-queue1-ef] queue wrr-value 45[Quidway-queue-queue1-ef] quit[Quidway-queue-queue1] queue-class af4[Quidway-queue-queue1-af4] queue length 60[Quidway-queue-queue1-af4] queue wrr-value 40[Quidway-queue-queue1-af4] quit[Quidway-queue-queue1] queue-class af3[Quidway-queue-queue1-af3] queue length 60[Quidway-queue-queue1-af3] queue wrr-value 35[Quidway-queue-queue1-af3] quit[Quidway-queue-queue1] queue-class af2[Quidway-queue-queue1-af2] queue length 60



3-29

[Quidway-queue-queue1-af2] queue wrr-value 30[Quidway-queue-queue1-af2] quit[Quidway-queue-queue1] queue-class af1[Quidway-queue-queue1-af1] queue length 60[Quidway-queue-queue1-af1] queue wrr-value 25[Quidway-queue-queue1-af1] quit[Quidway-queue-queue1] queue-class cs6[Quidway-queue-queue1-cs6] queue length 60[Quidway-queue-queue1-cs6] queue wrr-value 20[Quidway-queue-queue1-cs6] quit[Quidway-queue-queue1] queue-class cs7[Quidway-queue-queue1-cs7] queue length 60[Quidway-queue-queue1-cs7] queue wrr-value 15[Quidway-queue-queue1-cs7] quit[Quidway-queue-queue1] queue-class be[Quidway-queue-queue1-be] queue length 60[Quidway-queue-queue1-be] queue wrr-value 10[Quidway-queue-queue1-be] quit[Quidway-queue-queue1] quit

2. Configure the drop profile.[Quidway] drop-profile drop1[Quidway-drop-drop1] taildrop-threshold ef 100[Quidway-drop-drop1] taildrop-threshold af4 80[Quidway-drop-drop1] taildrop-threshold af3 70[Quidway-drop-drop1] taildrop-threshold af2 60[Quidway-drop-drop1] taildrop-threshold af1 50[Quidway-drop-drop1] taildrop-threshold cs6 40[Quidway-drop-drop1] taildrop-threshold cs7 30[Quidway-drop-drop1] taildrop-threshold be 20[Quidway-drop-drop1] quit

3. Configure the scheduler profile.[Quidway] scheduler-profile sch1[Quidway-scheduler-sch1] gts cir 100000 pir 500000 outbound[Quidway-scheduler-sch1] quit[Quidway] scheduler-profile sch2[Quidway-scheduler-sch2] gts cir 100000 pir 600000 outbound[Quidway-scheduler-sch2] quit[Quidway] scheduler-profile sch[Quidway-scheduler-sch] gts cir 200000 pir 800000 outbound[Quidway-scheduler-sch] quit

4. Configure the QoS profile.[Quidway] qos-profile pro1[Quidway-qos-pro1] scheduler-profile sch1 [Quidway-qos-pro1] queue-profile queue1 [Quidway-qos-pro1] drop-profile drop1 [Quidway-qos-pro1] quit[Quidway] qos-profile pro2[Quidway-qos-pro2] scheduler-profile sch2[Quidway-qos-pro2] queue-profile queue1[Quidway-qos-pro2] drop-profile drop1 [Quidway-qos-pro2] quit[Quidway] qos-profile pro[Quidway-qos-pro] scheduler-profile sch[Quidway-qos-pro] queue-profile queue1[Quidway-qos-pro] drop-profile drop1 [Quidway-qos-pro] quit

5. Configure the VP group.[Quidway] interface GigabitEthernet 1/0/0[Quidway-GigabitEthernet1/0/0] vp-group group1 qos-profile pro1[Quidway-GigabitEthernet1/0/0] vp-group group2 qos-profile pro2

6. Bind the VP group to a sub-interface.[Quidway] interface GigabitEthernet 1/0/0.1[Quidway-GigabitEthernet1/0/0.1] qos vp-group group1[Quidway-GigabitEthernet1/0/0.1] quit




Issue 05 (2010-06-01)

[Quidway] interface GigabitEthernet 1/0/0.2[Quidway-GigabitEthernet1/0/0.2] qos vp-group group2[Quidway-GigabitEthernet1/0/0.2] quit

Configuration Files#sysname Quidway#drop-profile drop1 taildrop-threshold be 20 taildrop-threshold af1 50 taildrop-threshold af3 70 taildrop-threshold af4 80 taildrop-threshold ef 100 taildrop-threshold cs6 40 taildrop-threshold cs7 30#scheduler-profile sch gts cir 100000 pir 500000 queue-length 65536 outbound#scheduler-profile sch1gts cir 100000 pir 500000 queue-length 65536 outbound#scheduler-profile sch2 gts cir 100000 pir 600000 queue-length 65536 outbound#queue-profile queue1 cheduler-style wrr wrr wrr wrr wrr wrr wrr wrr queue-class be queue length 60 queue wrr-value 10 queue-class af1 queue length 60 queue wrr-value 25 queue-class af2 queue length 60 queue wrr-value 30 queue-class af3 queue length 60 queue wrr-value 35 queue-class af4 queue length 60 queue wrr-value 40 queue-class ef queue length 60 queue wrr-value 45 queue-class cs6 queue length 60 queue wrr-value 20 queue-class cs7 queue length 60queue wrr-value 15#qos-profile pro scheduler-profile sch queue-profile queue1 drop-profile drop1#qos-profile pro1 scheduler-profile sch1 queue-profile queue1 drop-profile drop1#qos-profile pro2 scheduler-profile sch2 queue-profile queue1 drop-profile drop1#



3-31

interface GigabitEthernet1/0/0 undo shutdown vp-group group1 qos-profile pro1 vp-group group2 qos-profile pro2#interface GigabitEthernet1/0/0.1 undo shutdown ip address 1.1.1.1 255.255.255.0 qos vp-group group1#interface GigabitEthernet1/0/0.2 undo shutdown ip address 1.1.2.1 255.255.255.0 qos vp-group group2#return

3.5.2 Example for Configuring QoS Scheduling in PE Mode


As shown in Figure 3-3, the ME60 functions as the PE. The MPLS VPN is configured betweenthe ME60 and the peer router through Tunnel8/0/0 of the LSP tunnel.

At sub-interface GE8/0/0.1, the maximum downstream rate is 500 Mbit/s and the downstreamcommitted rate is 100 Mbit/s. At Tunnel8/0/0, the maximum downstream rate is 600 Mbit/s andthe downstream committed rate is 150 Mbit/s.

The drop thresholds of the service flows EF, AF4, AF3, AF2, AF1, CS6, CS7, and BE at theinterface, the sub-interface, and the tunnel interface are 100, 80, 70, 60, 50, 40, 30, and 20. Eachqueue contains 60 kbytes. The scheduling styles of the eight queues at session level are WRR.The WRR weights are 45, 40, 35, 30, 25, 20, 15, and 10. The WFQ weight of the VC-level QoSscheduler at the tunnel interface is 20.

Figure 3-3 Example of the configuration of QoS scheduling in PE mode

Loopback010.10.10.10/32

ME60

MPLS VPN

GE8/0/0.13.3.3.2/24

Tunnel8/0/0

Router

Loopback020.20.20.20/32

Configuration Roadmap

The configuration roadmap is as follows:

1. Configure the queue profile.2. Configure the scheduler profile.3. Configure the drop profile.




Issue 05 (2010-06-01)

4. Configure the QoS profile.5. Configure the VP group.6. Bind the VP group to a sub-interface.7. Apply the QoS profile to the interface and the tunnel interface.




1. Configure the queue profile.[Quidway] queue-profile queue1[Quidway-queue-queue1] scheduler-style wrr wrr wrr wrr wrr wrr wrr wrr[Quidway-queue-queue1] queue-class ef[Quidway-queue-queue1-ef] queue length 60[Quidway-queue-queue1-ef] queue wrr-value 45[Quidway-queue-queue1-ef] quit[Quidway-queue-queue1] queue-class af4[Quidway-queue-queue1-af4] queue length 60[Quidway-queue-queue1-af4] queue wrr-value 40[Quidway-queue-queue1-af4] quit[Quidway-queue-queue1] queue-class af3[Quidway-queue-queue1-af3] queue length 60[Quidway-queue-queue1-af3] queue wrr-value 35[Quidway-queue-queue1-af3] quit[Quidway-queue-queue1] queue-class af2[Quidway-queue-queue1-af2] queue length 60[Quidway-queue-queue1-af2] queue wrr-value 30[Quidway-queue-queue1-af2] quit[Quidway-queue-queue1] queue-class af1[Quidway-queue-queue1-af1] queue length 60[Quidway-queue-queue1-af1] queue wrr-value 25[Quidway-queue-queue1-af1] quit[Quidway-queue-queue1] queue-class cs6[Quidway-queue-queue1-cs6] queue length 60[Quidway-queue-queue1-cs6] queue wrr-value 20[Quidway-queue-queue1-cs6] quit[Quidway-queue-queue1] queue-class cs7[Quidway-queue-queue1-cs7] queue length 60[Quidway-queue-queue1-cs7] queue wrr-value 15[Quidway-queue-queue1-cs7] quit[Quidway-queue-queue1] queue-class be[Quidway-queue-queue1-be] queue length 60[Quidway-queue-queue1-be] queue wrr-value 10[Quidway-queue-queue1-be] quit[Quidway-queue-queue1] quit


3. Configure the scheduler profile.



3-33

[Quidway] scheduler-profile sch1[Quidway-scheduler-sch1] gts cir 100000 pir 500000 outbound[Quidway-scheduler-sch1] quit[Quidway] scheduler-profile sch2[Quidway-scheduler-sch2] gts cir 100000 pir 600000 outbound[Quidway-scheduler-sch2] wfq weight 20[Quidway-scheduler-sch2] quit[Quidway] scheduler-profile sch[Quidway-scheduler-sch] gts cir 200000 pir 800000 outbound[Quidway-scheduler-sch] quit

4. Configure the QoS profile.[Quidway] qos-profile pro1[Quidway-qos-pro1] scheduler-profile sch1[Quidway-qos-pro1] queue-profile queue1[Quidway-qos-pro1] drop-profile drop1[Quidway-qos-pro1] quit[Quidway] qos-profile pro2[Quidway-qos-pro2] scheduler-profile sch2[Quidway-qos-pro2] queue-profile queue1[Quidway-qos-pro2] drop-profile drop1[Quidway-qos-pro2] quit[Quidway] qos-profile pro[Quidway-qos-pro] scheduler-profile sch[Quidway-qos-pro] queue-profile queue1[Quidway-qos-pro] drop-profile drop1[Quidway-qos-pro] quit

5. Configure the VP group.[Quidway] interface GigabitEthernet 8/0/0[Quidway-GigabitEthernet8/0/0] vp-group group1 qos-profile pro1# Bind the VP group to a sub-interface.[Quidway] interface GigabitEthernet 8/0/0.1[Quidway-GigabitEthernet8/0/0.1] qos vp-group group1[Quidway-GigabitEthernet8/0/0.1] quit# Apply the QoS profile to the interface.[Quidway] interface Tunnel 8/0/0[Quidway-Tunnel8/0/0] qos profile pro2[Quidway-Tunnel8/0/0] quit

Configuration Files#sysname Quidway#mpls lsr-id 2.2.2.2 mpls mpls te#drop-profile drop1 taildrop-threshold be 20 taildrop-threshold af1 50 taildrop-threshold af3 70 taildrop-threshold af4 80 taildrop-threshold ef 100 taildrop-threshold cs6 40 taildrop-threshold cs7 30#scheduler-profile sch gts cir 200000 pir 800000 queue-length 65536 outbound#scheduler-profile sch1 gts cir 100000 pir 500000 queue-length 65536 outbound#scheduler-profile sch2 gts cir 100000 pir 600000 queue-length 65536 outbound wfq weight 20




Issue 05 (2010-06-01)

#queue-profile queue1 scheduler-style wrr wrr wrr wrr wrr wrr wrr wrr queue-class be queue length 60 queue wrr-value 10 queue-class af1 queue length 60 queue wrr-value 25 queue-class af2 queue length 60 queue wrr-value 30 queue-class af3 queue length 60 queue wrr-value 35 queue-class af4 queue length 60 queue wrr-value 40 queue-class ef queue length 60 queue wrr-value 45 queue-class cs6 queue length 60 queue wrr-value 20 queue-class cs7 queue length 60 queue wrr-value 15#qos-profile pro scheduler-profile sch queue-profile queue1 drop-profile drop1#qos-profile pro1 scheduler-profile sch1 queue-profile queue1 drop-profile drop1#qos-profile pro2 scheduler-profile sch2 queue-profile queue1 drop-profile drop1#qos-profile pro scheduler-profile sch queue-profile queue1 drop-profile drop1#interface GigabitEthernet8/0/0 undo shutdown vp-group group1 qos-profile pro1#interface GigabitEthernet8/0/0.1 undo shutdown ip address 3.3.3.2 255.255.255.0 mpls mpls te qos vp-group group1#interface LoopBack0 ip address 10.10.10.10 255.255.255.255#interface Tunnel8/0/0 undo shutdown ip address unnumbered interface GigabitEthernet8/0/0.1 tunnel-protocol mpls te destination 20.20.20.20 mpls te signal-protocol cr-static mpls te tunnel-id 2



3-35

mpls te commit qos profile pro2#ip route-static 20.20.20.20 255.255.255.255 3.3.3.1#static-cr-lsp egress Tunnel8/0/0 incoming-interface GigabitEthernet8/0/0.1 in-label 100 lsrid 1.1.1.1 tunnel-id 1#return

3.5.3 Example for Configuring QoS Scheduling in QoD Mode

Networking RequirementAs shown in Figure 3-4, the ME60 functions as the BRAS and provides access service for users.Users access VLAN 1 through interface GE8/0/0.1, access the Internet by using the accounts ofdomain isp1, and then access the Portal server to define their own QoS parameters.

For users in domain isp1, the maximum downstream rate is 80 Mbit/s and the committeddownstream is 20 Mbit/s. In VLAN 1, the maximum downstream rate is 100 Mbit/s and theminimum traffic rate is 60 Mbit/s. At sub-interface GE8/0/0.1, the maximum downstream rateis 500 Mbit/s and the committed downstream rate is 100 Mbit/s.

The drop thresholds of the service flows EF, AF4, AF3, AF2, AF1, CS6, CS7, and BE in theQoS scheduling at all levels are 100, 80, 70, 60, 50, 40, 30, and 20. The queues at port, VP, andVC group levels contain 60 kbytes. Each queue at VC level contains 50 kbytes. The schedulingstyles of the eight queues at session level are WRR. The WRR weights are 45, 40, 35, 30, 25,20, 15, and 10. The WFQ weight of the VC-level QoS scheduler is 20 and that of the VC group-level QoS scheduler is 30.

Figure 3-4 Example of the configuration of QoS scheduling in QoD mode

ME60

GE8/0/0.1VLAN 1

user1@isp1

user2@isp1

RADIUSserver

Portalserver

Policyserver

AccessNetwork

CoreNetwork


1. Configure the queue profile.2. Configure the scheduler profile.3. Configure the drop profile.4. Configure the QoS profile.5. Configure the VC group.




Issue 05 (2010-06-01)

6. Configure the VP group.7. Bind the VLAN to the VC group.8. Bind the VP group to a sub-interface.9. Apply the QoS profile to the domain and the interface.




1. Configure the queue profile.[Quidway] queue-profile queue1[Quidway-queue-queue1] scheduler-style wrr wrr wrr wrr wrr wrr wrr wrr[Quidway-queue-queue1] queue-class ef[Quidway-queue-queue1-ef] queue length 60[Quidway-queue-queue1-ef] queue wrr-value 45[Quidway-queue-queue1-ef] quit[Quidway-queue-queue1] queue-class af4[Quidway-queue-queue1-af4] queue length 60[Quidway-queue-queue1-af4] queue wrr-value 40[Quidway-queue-queue1-af4] quit[Quidway-queue-queue1] queue-class af3[Quidway-queue-queue1-af3] queue length 60[Quidway-queue-queue1-af3] queue wrr-value 35[Quidway-queue-queue1-af3] quit[Quidway-queue-queue1] queue-class af2[Quidway-queue-queue1-af2] queue length 60[Quidway-queue-queue1-af2] queue wrr-value 30[Quidway-queue-queue1-af2] quit[Quidway-queue-queue1] queue-class af1[Quidway-queue-queue1-af1] queue length 60[Quidway-queue-queue1-af1] queue wrr-value 25[Quidway-queue-queue1-af1] quit[Quidway-queue-queue1] queue-class cs6[Quidway-queue-queue1-cs6] queue length 60[Quidway-queue-queue1-cs6] queue wrr-value 20[Quidway-queue-queue1-cs6] quit[Quidway-queue-queue1] queue-class cs7[Quidway-queue-queue1-cs7] queue length 60[Quidway-queue-queue1-cs7] queue wrr-value 15[Quidway-queue-queue1-cs7] quit[Quidway-queue-queue1] queue-class be[Quidway-queue-queue1-be] queue length 60[Quidway-queue-queue1-be] queue wrr-value 10[Quidway-queue-queue1-be] quit[Quidway-queue-queue1] quit[Quidway] queue-profile queue2[Quidway-queue-queue2] scheduler-style wrr wrr wrr wrr wrr wrr wrr wrr[Quidway-queue-queue2] queue-class ef[Quidway-queue-queue2-ef] queue length 50[Quidway-queue-queue2-ef] queue wrr-value 45[Quidway-queue-queue2-ef] quit[Quidway-queue-queue2] queue-class af4[Quidway-queue-queue2-af4] queue length 50[Quidway-queue-queue2-af4] queue wrr-value 40[Quidway-queue-queue2-af4] quit[Quidway-queue-queue2] queue-class af3[Quidway-queue-queue2-af3] queue length 50[Quidway-queue-queue2-af3] queue wrr-value 35[Quidway-queue-queue2-af3] quit



3-37

[Quidway-queue-queue2] queue-class af2[Quidway-queue-queue2-af2] queue length 50[Quidway-queue-queue2-af2] queue wrr-value 30[Quidway-queue-queue2-af2] quit[Quidway-queue-queue2] queue-class af1[Quidway-queue-queue2-af1] queue length 50[Quidway-queue-queue2-af1] queue wrr-value 25[Quidway-queue-queue2-af1] quit[Quidway-queue-queue2] queue-class cs6[Quidway-queue-queue2-cs6] queue length 50[Quidway-queue-queue2-cs6] queue wrr-value 20[Quidway-queue-queue2-cs6] quit[Quidway-queue-queue2] queue-class cs7[Quidway-queue-queue2-cs7] queue length 50[Quidway-queue-queue2-cs7] queue wrr-value 15[Quidway-queue-queue2-cs7] quit[Quidway-queue-queue2] queue-class be[Quidway-queue-queue2-be] queue length 50[Quidway-queue-queue2-be] queue wrr-value 10[Quidway-queue-queue1-be] quit[Quidway-queue-queue2] quit


3. Configure the scheduler profile.[Quidway] scheduler-profile sch1[Quidway-scheduler-sch1] gts cir 20000 pir 80000 outbound[Quidway-scheduler-sch1] wfq weight 20[Quidway-scheduler-sch1] quit[Quidway] scheduler-profile sch2[Quidway-scheduler-sch2] gts cir 60000 pir 100000 outbound [Quidway-scheduler-sch2] wfq weight 30[Quidway-scheduler-sch2] quit[Quidway] scheduler-profile sch3[Quidway-scheduler-sch3] gts cir 100000 pir 500000 outbound[Quidway-scheduler-sch3] quit[Quidway] scheduler-profile sch4[Quidway-scheduler-sch4] gts cir 200000 pir 800000 outbound[Quidway-scheduler-sch4] quit

4. Configure the QoS profile.[Quidway] qos-profile pro1[Quidway-qos-pro1] scheduler-profile sch1 [Quidway-qos-pro1] queue-profile queue2 [Quidway-qos-pro1] drop-profile drop1[Quidway-qos-pro1] quit[Quidway] qos-profile pro2[Quidway-qos-pro2] scheduler-profile sch2 [Quidway-qos-pro2] queue-profile queue1 [Quidway-qos-pro2] drop-profile drop1[Quidway-qos-pro2] quit[Quidway] qos-profile pro3[Quidway-qos-pro3] scheduler-profile sch3[Quidway-qos-pro3] queue-profile queue1 [Quidway-qos-pro3] drop-profile drop1[Quidway-qos-pro3] quit[Quidway] qos-profile pro4[Quidway-qos-pro4] scheduler-profile sch4[Quidway-qos-pro4] queue-profile queue1[Quidway-qos-pro4] drop-profile drop1




Issue 05 (2010-06-01)

[Quidway-qos-pro4] quit5. Create a VC group and bind a QoS profile to the group.

[Quidway] interface GigabitEthernet8/0/0[Quidway-GigabitEthernet8/0/0] vc-group group1 qos-profile pro2[Quidway-GigabitEthernet8/0/0] qos vc-group group1 outbound

6. Create a VP group and bind a QoS profile to the group.[Quidway] interface GigabitEthernet8/0/0[Quidway-GigabitEthernet8/0/0] vp-group group2 qos-profile pro3

7. Configure the QoS scheduling level.# Apply QoS profile named pro1 to domain isp1.[Quidway] aaa[Quidway-aaa] domain isp1[Quidway-aaa-domain-isp1] qos profile pro1[Quidway-aaa-domain-isp1] quit[Quidway-aaa] quit# Bind the VLAN to the VC group named group1.[Quidway] interface GigabitEthernet 8/0/0.1[Quidway-GigabitEthernet8/0/0.1] user-vlan 1[Quidway-GigabitEthernet8/0/0.1-vlan-1-1] qos vc-group group1[Quidway-GigabitEthernet8/0/0.1-vlan-1-1] quit# Bind the VP group named group2 to a sub-interface.[Quidway-GigabitEthernet8/0/0.1] qos vp-group group2[Quidway-GigabitEthernet8/0/0.1] quit

Configuration Files#sysname Quidway#radius-server group rd1 radius-server authentication 192.168.7.249 1645 weight 0 radius-server accounting 192.168.7.249 1646 weight 0 radius-server shared-key itellin radius-server type plus11 radius-server traffic-unit kbyte#drop-profile drop1 taildrop-threshold be 20 taildrop-threshold af1 50 taildrop-threshold af3 70 taildrop-threshold af4 80 taildrop-threshold ef 100 taildrop-threshold cs6 40 taildrop-threshold cs7 30# scheduler-profile sch1 gts cir 200000 pir 800000 queue-length 65536 outbound wfq weight 20# scheduler-profile sch2 gts cir 60000 pir 100000 queue-length 65536 outbound wfq weight 30# scheduler-profile sch3 gts cir 100000 pir 500000 queue-length 65536 outbound# scheduler-profile sch4 gts cir 200000 pir 800000 queue-length 65536 outbound#queue-profile queue1 scheduler-style wrr wrr wrr wrr wrr wrr wrr wrr queue-class be queue length 60



3-39

queue wrr-value 10 queue-class af1 queue length 60 queue wrr-value 25 queue-class af2 queue length 60 queue wrr-value 30queue-class af3 queue length 60 queue wrr-value 35 queue-class af4 queue length 60 queue wrr-value 40 queue-class ef queue length 60 queue wrr-value 45 queue-class cs6 queue length 60 queue wrr-value 20 queue-class cs7 queue length 60 queue wrr-value 15#queue-profile queue2 scheduler-style wrr wrr wrr wrr wrr wrr wrr wrr queue-class be queue length 50 queue wrr-value 10 queue-class af1 queue length 50 queue wrr-value 25 queue-class af2 queue length 50 queue wrr-value 30 queue-class af3 queue length 50 queue wrr-value 35 queue-class af4 queue length 50 queue wrr-value 40 queue-class ef queue length 50 queue wrr-value 45 queue-class cs6 queue length 50 queue wrr-value 20 queue-class cs7 queue length 50queue wrr-value 15#qos-profile pro1 scheduler-profile sch1 queue-profile queue2 drop-profile drop1#qos-profile pro2 scheduler-profile sch2 queue-profile queue1 drop-profile drop1#qos-profile pro3 scheduler-profile sch3 queue-profile queue1 drop-profile drop1#qos-profile pro4 scheduler-profile sch4 queue-profile queue1 drop-profile drop1




Issue 05 (2010-06-01)

#aaa authentication-scheme auth1 authentication-mode radius-local accounting-scheme acct1 accounting-mode radius domain isp1 authentication-scheme auth1 accounting-scheme acct1 radius-server group rd1 ip-pool pool1 qos profile pro1#interface Virtual-Template1#interface GigabitEthernet8/0/0 undo shutdown vp-group group2 qos-profile pro3 vc-group group1 qos-profile pro2 qos vc-group group1 outbound#interface GigabitEthernet8/0/0.1 undo shutdown pppoe-server bind Virtual-Template 1 qos vp-group group2 user-vlan 1 qos vc-group group1 user-vlan 2 bas access-type layer2-subscriber#ip pool pool1 local gateway 172.82.0.1 255.255.255.0 section 0 172.82.0.2 172.82.0.200 dns-server 192.168.7.252#return

3.5.4 Example for Configuring QoS Scheduling in DSG Mode

Networking RequirementAs shown in Figure 3-4, the ME60 functions as a BRAS and DSG to provide access service andvalue-added service for users. Users access VLAN1 through interface GE8/0/0.1 and access thePortal server to select value-added services.

The maximum downstream rate of the value-added service is 80 Mbit/s and the committeddownstream rate is 20 Mbit/s. In VLAN 1, the maximum downstream rate is 100 Mbit/s and thecommitted downstream rate is 60 Mbit/s. At sub-interface GE8/0/0.1, the maximum downstreamrate is 500 Mbit/s and the committed downstream rate is 100 Mbit/s.

The drop thresholds of the service flows EF, AF4, AF3, AF2, AF1, CS6, CS7, and BE in theQoS scheduling at all levels are 100, 80, 70, 60, 50, 40, 30, and 20. The queues at port, VP, andVC group levels contain 60 kbytes. Each queue at VC level contains 50 kbytes. The schedulingstyles of the eight queues at session level are WRR. The WRR weights are 45, 40, 35, 30, 25,20, 15, and 10. The WFQ weight of the VC group-level QoS scheduler is 30.


1. Configure the queue profile.



3-41

2. Configure the scheduler profile.3. Configure the drop profile.4. Configure the QoS profile.5. Configure the traffic policy.6. Configure the VC group.7. Configure the VP group.8. Bind the VLAN to the VC group.9. Bind the VP group to a sub-interface.10. Configure the service policy and apply it to the domain.11. Apply the QoS profile to the interface.




1. Configure the queue profile.[Quidway] queue-profile queue1[Quidway-queue-queue1] scheduler-style wrr wrr wrr wrr wrr wrr wrr wrr[Quidway-queue-queue1] queue-class ef[Quidway-queue-queue1-ef] queue length 60[Quidway-queue-queue1-ef] queue wrr-value 45[Quidway-queue-queue1-ef] quit[Quidway-queue-queue1] queue-class af4[Quidway-queue-queue1-af4] queue length 60[Quidway-queue-queue1-af4] queue wrr-value 40[Quidway-queue-queue1-af4] quit[Quidway-queue-queue1] queue-class af3[Quidway-queue-queue1-af3] queue length 60[Quidway-queue-queue1-af3] queue wrr-value 35[Quidway-queue-queue1-af3] quit[Quidway-queue-queue1] queue-class af2[Quidway-queue-queue1-af2] queue length 60[Quidway-queue-queue1-af2] queue wrr-value 30[Quidway-queue-queue1-af2] quit[Quidway-queue-queue1] queue-class af1[Quidway-queue-queue1-af1] queue length 60[Quidway-queue-queue1-af1] queue wrr-value 25[Quidway-queue-queue1-af1] quit[Quidway-queue-queue1] queue-class cs6[Quidway-queue-queue1-cs6] queue length 60[Quidway-queue-queue1-cs6] queue wrr-value 20[Quidway-queue-queue1-cs6] quit[Quidway-queue-queue1] queue-class cs7[Quidway-queue-queue1-cs7] queue length 60[Quidway-queue-queue1-cs7] queue wrr-value 15[Quidway-queue-queue1-cs7] quit[Quidway-queue-queue1] queue-class be[Quidway-queue-queue1-be] queue length 60[Quidway-queue-queue1-be] queue wrr-value 10[Quidway-queue-queue1-be] quit[Quidway-queue-queue1] quit

2. Configure the drop profile.[Quidway] drop-profile drop1[Quidway-drop-drop1] taildrop-threshold ef 100




Issue 05 (2010-06-01)

[Quidway-drop-drop1] taildrop-threshold af4 80[Quidway-drop-drop1] taildrop-threshold af3 70[Quidway-drop-drop1] taildrop-threshold af2 60[Quidway-drop-drop1] taildrop-threshold af1 50[Quidway-drop-drop1] taildrop-threshold cs6 40[Quidway-drop-drop1] taildrop-threshold cs7 30[Quidway-drop-drop1] taildrop-threshold be 20[Quidway-drop-drop1] quit

3. Configure the scheduler profile.[Quidway] scheduler-profile sch1[Quidway-scheduler-sch1] gts cir 60000 pir 100000 outbound[Quidway-scheduler-sch1] wfq weight 30[Quidway-scheduler-sch1] quit[Quidway] scheduler-profile sch2[Quidway-scheduler-sch2] gts cir 100000 pir 500000 outbound[Quidway-scheduler-sch2] quit[Quidway] scheduler-profile sch3[Quidway-scheduler-sch3] gts cir 200000 pir 800000 outbound[Quidway-scheduler-sch3] quit

4. Configure the QoS profile.[Quidway] qos-profile pro1[Quidway-qos-pro1] scheduler-profile sch1 [Quidway-qos-pro1] queue-profile queue1[Quidway-qos-pro1] drop-profile drop1[Quidway-qos-pro1] quit[Quidway] qos-profile pro2[Quidway-qos-pro2] scheduler-profile sch2 [Quidway-qos-pro2] queue-profile queue1 [Quidway-qos-pro2] drop-profile drop1[Quidway-qos-pro2] quit[Quidway] qos-profile pro3[Quidway-qos-pro3] scheduler-profile sch3 [Quidway-qos-pro3] queue-profile queue1 [Quidway-qos-pro3] drop-profile drop1[Quidway-qos-pro3] quit

5. Create a VC group and binding a QoS profile to the group.[Quidway] interface GigabitEthernet8/0/0[Quidway-GigabitEthernet8/0/0] vc-group group1 qos-profile pro1[Quidway-GigabitEthernet8/0/0] qos vc-group group1 outbound

6. Create a VP group and bind a QoS profile to the group.[Quidway] interface GigabitEthernet8/0/0[Quidway-GigabitEthernet8/0/0] vp-group group2 qos-profile pro2

7. Configure the traffic policy.[Quidway] user-group isp1[Quidway] acl 6001[Quidway-acl-ucl-6001] rule permit ip source user-group isp1 destination any[Quidway-acl-ucl-6001] quit[Quidway] traffic classifier class1[Quidway-classifier-class1] if-match acl 6001[Quidway-classifier-class1] quit[Quidway] traffic behavior behavior1[Quidway-behavior-behavior1] car cir 20000 pir 80000[Quidway-behavior-behavior1] quit[Quidway] traffic policy policy1[Quidway-trafficpolicy-policy1] classifier class1 behavior behavior1[Quidway-trafficpolicy-policy1] quit

8. Configure the service policy.[Quidway] value-added-service policy policy1[Quidway-vas-policy-policy1] traffic-policy policy1 in-policy[Quidway-vas-policy-policy1] traffic-policy policy1 out-policy[Quidway-vas-policy-policy1] quit

9. Configure the QoS scheduling level.



3-43

# Apply the service policy to the domain.[Quidway] aaa[Quidway-aaa] domain isp1[Quidway-aaa-domain-isp1] value-added-service policy policy1[Quidway-aaa-domain-isp1] user-group isp1 [Quidway-aaa-domain-isp1] quit[Quidway-aaa] quit

# Bind the VLAN to the VC group named group1.[Quidway] interface GigabitEthernet 8/0/0.1[Quidway-GigabitEthernet8/0/0.1] user-vlan 1[Quidway-GigabitEthernet8/0/0.1-vlan-1-1] qos vc-group group1[Quidway-GigabitEthernet8/0/0.1-vlan-1-1] quit

# Bind the VP group named group 2 to a sub-interface.[Quidway-GigabitEthernet8/0/0.1] qos vp-group group2[Quidway-GigabitEthernet8/0/0.1] quit

Configuration Files# sysname Quidway# user-group isp1#radius-server group rd1 radius-server authentication 192.168.7.249 1645 weight 0 radius-server accounting 192.168.7.249 1646 weight 0 radius-server shared-key itellin radius-server type plus11 radius-server traffic-unit kbyte#acl number 6001 rule 5 permit ip source user-group isp1#traffic classifier class1 operator and if-match acl 6001#traffic behavior behavior1 car cir 2000 pir 8000 cbs 250000 pbs 1000000 green pass yellow pass red discard#traffic policy policy1 classifier class1 behavior behavior1#drop-profile drop1 taildrop-threshold be 20 taildrop-threshold af1 50 taildrop-threshold af3 70 taildrop-threshold af4 80 taildrop-threshold ef 100 taildrop-threshold cs6 40 taildrop-threshold cs7 30#scheduler-profile sch1 gts cir 60000 pir 100000 queue-length 65536 outbound wfq weight 30#scheduler-profile sch2 gts cir 100000 pir 500000 queue-length 65536 outbound#scheduler-profile sch3 gts cir 200000 pir 800000 queue-length 65536 outbound#queue-profile queue1 scheduler-style wrr wrr wrr wrr wrr wrr wrr wrr queue-class be queue length 60 queue wrr-value 10




Issue 05 (2010-06-01)

queue-class af1 queue length 60 queue wrr-value 25 queue-class af2 queue length 60 queue wrr-value 30 queue-class af3 queue length 60 queue wrr-value 35 queue-class af4 queue length 60 queue wrr-value 40 queue-class ef queue length 60 queue wrr-value 45 queue-class cs6 queue length 60 queue wrr-value 20 queue-class cs7 queue length 60 queue wrr-value 15#qos-profile pro1 scheduler-profile sch1 queue-profile queue1 drop-profile drop1#qos-profile pro2 scheduler-profile sch2 queue-profile queue1 drop-profile drop1#qos-profile pro3 scheduler-profile sch3 queue-profile queue1 drop-profile drop1#aaaauthentication-scheme auth1 authentication-mode radius-local accounting-scheme acct1 accounting-mode radius-local domain isp1 authentication-scheme auth1 accounting-scheme acct1 radius-server group rd1 user-group isp1 ip-pool pool1 value-added-service policy policy1#value-added-service policy policy1 traffic-policy policy1 in-policy traffic-policy policy1 out-policy#interface Virtual-Template1#interface GigabitEthernet8/0/0 undo shutdown vp-group group2 qos-profile pro2 vc-group group1 qos-profile pro1 qos vc-group group1 outbound#interface GigabitEthernet8/0/0.1 undo shutdown pppoe-server bind Virtual-Template 1 qos vp-group group2 user-vlan 1 qos vc-group group1#



3-45

ip pool pool1 local gateway 172.82.0.1 255.255.255.0 section 0 172.82.0.2 172.82.0.200 dns-server 192.168.7.252#return

3.5.5 Example for Configuring the Multi-Play Service

Networking RequirementsAs shown in Figure 3-5, IPTV and VoIP in IPoE mode and the High Speed Internet (HSI) serviceon the PC in PPPoE mode access the Internet through the sub-interface GE 2/0/1.2 on theME60. All services on the sub-interface GE 2/0/1.2 are performed family identification basedon the inner VLAN ID and are performed the family scheduling. The IPTV and VoIP servicesare performed service identification based on the CoS value in the inner VLAN tag and the QoSscheduling for a single service is performed. The access mode of the HSI service on the PC isPPPoE. Therefore, service identification does not need to be performed.

The priorities of the VoIP, IPTV, and HSI services are in descending order. The HSI servicecannot affect the IPTV or VoIP service.

Figure 3-5 Networking diagram of the Multi-Play service

Modem

DNS server192.168.7.252


IPTV

IPPhone

AccessNetwork GE2/0/1.2

ME60

Internet

PC


1. Configure the BRAS service on the ME60 to ensure that the user can go online.2. Configure the user VLAN.3. Configure the scheduling profile and QoS profile for a service and family.4. Configure the family identification mode.




Issue 05 (2010-06-01)

5. Bind the QoS profile to the family profile to implement the family scheduling.6. Bind the QoS profile of a service to a domain to implement the scheduling of the service.7. Configure the service identification mode.8. Bind the family profile and the service identification policy to the BAS interface.


l Number of the interface that the user accesses

l QinQ ID

l Scheduling profile name and related parameters

l QoS profile name

l Family profile name

l Name of the service identification policy

l CoS values

Configuration Procedure1. Configure the BRAS service on the ME60 to ensure that the user can go online.

The configuration details are not mentioned here. For details, refer to Chapter "BRASAccess Configuration" in the Quidway ME60 Multiservice Control Gateway ConfigurationGuide - BRAS Services.

2. # Configure the user group.<Quidway> system-view[Quidway] interface GigabitEthernet 1/0/0.2[Quidway-GigabitEthernet2/0/1.2] user-vlan 100 qinq 100[Quidway-GigabitEthernet2/0/1.2-vlan-100-100-QinQ-100-100] quit[Quidway-GigabitEthernet2/0/1.2] quit

3. Configure the scheduling profiles and the QoS profiles.# Configure the scheduling profile for the HSI service.[Quidway] scheduler-profile hsi[Quidway-scheduler-hsi] car cir 2000 pir 2000 cbs 250000 pbs 250000 downstream[Quidway-scheduler-hsi] quit# Configure the scheduling profile for the IPTV service.[Quidway] scheduler-profile iptv[Quidway-scheduler-iptv] car cir 3000 pir 3000 cbs 375000 pbs 375000 downstream[Quidway-scheduler-iptv] quit# Configure the scheduling profile for the VoIP service.[Quidway] scheduler-profile voip[Quidway-scheduler-voip] car cir 32 pir 32 cbs 10000 pbs 10000 downstream[Quidway-scheduler-voip] quit# Configure the scheduling profile for the family.[Quidway] scheduler-profile e_home[Quidway-scheduler-e_home] gts cir 4000 pir 4000 queue-length 65536 outbound[Quidway-scheduler-e_home] gts cir 4000 pir 4000 queue-length 65536 outbound[Quidway-scheduler-e_home] quit# Configure the QoS profile for the HSI service.[Quidway] qos-profile hsi[Quidway-qos-hsi] scheduler-profile hsi[Quidway-qos-hsi] quit



3-47

# Configure the QoS profile for the IPTV service.[Quidway] qos-profile iptv[Quidway-qos-iptv] scheduler-profile iptv[Quidway-qos-iptv] quit# Configure the QoS profile for the VoIP service.[Quidway] qos-profile voip[Quidway-qos-voip] scheduler-profile voip[Quidway-qos-voip] quit# Configure the QoS profile for the family.[Quidway] qos-profile e_home[Quidway-qos-e_home] scheduler-profile e_home[Quidway-qos-e_home] quit

4. Configure the family identification mode.[Quidway] session-group-profile e_home[Quidway-session-group-e_home] session-group-identify inner-vlan

5. Bind the QoS profile to the family profile.[Quidway-session-group-e_home] qos-profile e_home[Quidway-session-group-e_home] quit

6. Bind the QoS profile to the domain.[Quidway] aaa[Quidway-aaa] domain e_home_hsi[Quidway-aaa-domain-e_home_hsi] qos profile hsi[Quidway-aaa-domain-e_home_hsi] quit[Quidway-aaa] domain e_home_iptv[Quidway-aaa-domain-e_home_iptv] qos profile iptv[Quidway-aaa-domain-e_home_iptv] quit[Quidway-aaa] domain e_home_voip[Quidway-aaa-domain-e_home_voip] qos profile voip[Quidway-aaa-domain-e_home_voip] quit[Quidway-aaa] quit

7. Configure the service identification mode.[Quidway] service-identify-policy e_home[Quidway-serviceid-policy-e_home] service-identify cos inner-vlan[Quidway-serviceid-policy-e_home] dot1p 2 domain e_home_iptv[Quidway-serviceid-policy-e_home] dot1p 6 domain e_home_voip[Quidway-serviceid-policy-e_home] quit

8. Bind the family profile and the service identification policy to the BAS interface.[Quidway] interface GigabitEthernet 1/0/0.2[Quidway-GigabitEthernet2/0/1.2] bas[Quidway-GigabitEthernet2/0/1.2-bas] access-type layer2-subscriber[Quidway-GigabitEthernet2/0/1.2-bas] ip-trigger[Quidway-GigabitEthernet2/0/1.2-bas] session-group-profile e_home[Quidway-GigabitEthernet2/0/1.2-bas] service-identify-policy e_home[Quidway-GigabitEthernet2/0/1.2-bas] quit[Quidway-GigabitEthernet2/0/1.2] quit[Quidway] quit

9. Verify the configuration.# Display configurations of the family profile.<Quidway> display session-group-profile name e_home verbose -------------------------------------------------------- Session group index : 1 Session group profile : e_home Qos profile : e_home Identify type : inner-vlan session-limit : 256 Binded to IF : GigabitEthernet2/0/1.2# Display configurations of the service identification policy.<Quidway> display service-identify-policy name e_home verbose




Issue 05 (2010-06-01)

---------------------------------------------- Service-identify-policy Index : 0 Used : 1 Service-identify-policy : e_home Service-Type : inner-cos Domain Name : e_home_iptv Begin-Cos: : 2 End-Cos: : 2 Domain Name : e_home_voip Begin-Cos: : 6 End-Cos: : 6 Binded to IF : GigabitEthernet2/0/1.2

Configuration FilesThe following lists the configuration file of the ME60.# sysname Quidway # sbc h323 q931 wellknownport 1720 # sbc sip enable sbc sip field-limit enable undo sbc sip register-reduce enable # radius-server group rd1 radius-server authentication 192.168.7.249 1645 weight 0 radius-server accounting 192.168.7.249 1646 weight 0 radius-server shared-key itellin radius-server type plus11 radius-server traffic-unit kbyte # # # # diffserv domain default # scheduler-profile e_home gts cir 4000 pir 4000 queue-length 65536 outbound gts cir 4000 pir 4000 queue-length 65536 inbound # scheduler-profile hsi car cir 2000 pir 2000 cbs 250000 pbs 250000 downstream # scheduler-profile iptv car cir 3000 pir 3000 cbs 375000 pbs 375000 downstream # scheduler-profile voip car cir 32 pir 32 cbs 10000 pbs 10000 downstream # qos-profile default # qos-profile e_home scheduler-profile e_home # qos-profile hsi scheduler-profile hsi # qos-profile iptv scheduler-profile iptv # qos-profile voip scheduler-profile voip # session-group-profile default # session-group-profile e_home qos-profile e_home



3-49

session-group-identify inner-vlan # family-profile default # interface Aux0/0/1 # interface Virtual-Template0 # interface NULL0 # l2tp-group default-lac # l2tp-group default-lns # ip pool pool1 local gateway 172.82.0.1 255.255.0.0 section 0 172.82.0.2 172.82.0.200 dns-server 192.168.7.252 # iptn # dpi pts # dpi global-policy # dpi dsu-mac # dpi restricted-policy # ancp neighbor-profile default-neighbor # dot1x-template 1 # aaa authentication-scheme auth1 accounting-scheme acct1 domain default0 ip-pool pool1 domain default1 domain default_admin domain isp1 authentication-scheme auth1 accounting-scheme acct1 radius-server group rd1 ip-pool pool1 domain e_home_hsi authentication-scheme auth1 accounting-scheme acct1 radius-server group rd1 ip-pool pool1 qos profile hsi domain e_home_iptv authentication-scheme auth1 accounting-scheme acct1 radius-server group rd1 ip-pool pool1 qos profile iptv domain e_home_voip authentication-scheme auth1 accounting-scheme acct1 radius-server group rd1 ip-pool pool1 qos profile voip # # local-aaa-server # service-identify-policy e_home




Issue 05 (2010-06-01)

service-identify cos inner-vlan dot1p 2 domain e_home_iptv dot1p 6 domain e_home_voip # interface GigabitEthernet0/0/0 undo shutdown ip address 172.1.200.7 255.255.0.0 speed auto duplex auto # interface GigabitEthernet2/0/0 undo shutdown bas access-type layer2-subscriber ip-trigger arp-trigger # interface GigabitEthernet2/0/1 undo shutdown # interface GigabitEthernet2/0/1.2 user-vlan 100 QinQ 100 bas access-type layer2-subscriber default-domain authentication isp1 ip-trigger session-group-profile e_home service-identify-policy e_home # interface GigabitEthernet2/0/2 undo shutdown # interface GigabitEthernet2/0/3 undo shutdown # interface GigabitEthernet2/0/4 undo shutdown # interface GigabitEthernet2/0/5 undo shutdown # interface GigabitEthernet2/0/6 undo shutdown # interface GigabitEthernet2/0/7 undo shutdown # interface GigabitEthernet2/0/8 undo shutdown # interface GigabitEthernet2/0/9 undo shutdown # interface GigabitEthernet2/0/10 undo shutdown # interface GigabitEthernet2/0/11 undo shutdown # interface GigabitEthernet2/0/12 undo shutdown # interface GigabitEthernet2/0/13 undo shutdown # interface GigabitEthernet2/0/14 undo shutdown # interface GigabitEthernet2/0/15 undo shutdown



3-51

# interface GigabitEthernet2/0/16 undo shutdown # interface GigabitEthernet2/0/17 undo shutdown # interface GigabitEthernet2/0/18 undo shutdown # interface GigabitEthernet2/0/19 undo shutdown # interface GigabitEthernet2/0/20 undo shutdown # interface GigabitEthernet2/0/21 undo shutdown # interface GigabitEthernet2/0/22 undo shutdown # interface GigabitEthernet2/0/23 undo shutdown # sbc roamlimit default deny # sbc keepalive-packet empty # sbc backup reg-user enable # sbc backup reg-user at 0 # # sbc sip expire enable # # # undo sbc roamlimit-extend enable undo sbc roamlimit enable sbc roamlimit default deny # sbc default # user-interface con 0 user-interface aux 0 user-interface vty 0 authentication-mode none user privilege level 3 idle-timeout 0 0 user-interface vty 1 4 authentication-mode none user privilege level 3 user-interface vty 16 20 # multicast shaping # multicastbandwidth # return

3.5.6 Configuring the Added Function in the Multi-Play Service

Networking RequirementsAs shown in Figure 3-6, the function that the ME60 supports roaming Wireless Local AreaNetwork (WLAN) users after the Multi-Play service is deployed. WLAN users participate in




Issue 05 (2010-06-01)

the family scheduling and share the family bandwidth. Each WLAN user occupies up to the 512kbit/s bandwidth and up to four roaming WLAN users can go online.

NOTE

Roaming WLAN users go online in PPP dialup mode and user packets carry domain names, the serviceidentification does not need to be performed.The parameters related to the new function take effect only after the user goes online again.

Figure 3-6 Networking diagram for the added function in the Multi-Play Service

PC Modem

DNS server192.168.7.252


IPTV

IPPhone

AccessNetwork GE2/0/1.2

ME60

InternetPC

WLAN


1. Configure the scheduling profile and QoS profile for the WLAN service.2. Bind the QoS profile of the WLAN service to a domain.3. Set the maximum number of access users allowed by a family.


l Scheduling profile name of the WLAN service and the related parameters

l QoS profile name of the WLAN service

l Maximum number of access users allowed by a family

Configuration Procedure1. Configure the scheduling profile and QoS profile for the WLAN service.

# Configure the scheduling profile for the WLAN service.[Quidway] scheduler-profile wlan



3-53

[Quidway-scheduler-wlan] car cir 512 pir 512 cbs 250000 pbs 250000 downstream[Quidway-scheduler-wlan] quit# Configure the QoS profile for the WLAN service.[Quidway] qos-profile voip[Quidway-qos-wlan] scheduler-profile wlan[Quidway-qos-wlan] quit

2. Bind the QoS profile of the WLAN service to a domain.[Quidway] aaa[Quidway-aaa] domain e_home_wlan[Quidway-aaa-domain-e_home_wlan] qos profile wlan[Quidway-aaa-domain-e_home_wlan] quit[Quidway-aaa] quit

3. Set the maximum number of access users allowed by a family.[Quidway] session-group-profile e_home[Quidway-session-group-e_home] session-limit 7

4. Verify the configuration.# Display configurations of the family profile.<Quidway> display session-group-profile name e_home verbose -------------------------------------------------------- Session group index : 1 Session group profile : e_home Qos profile : e_home Identify type : inner-vlan session-limit : 7 Binded to IF : GigabitEthernet2/0/1.2

Configuration FilesConfiguration file of the ME60# sysname Quidway # sbc h323 q931 wellknownport 1720 # sbc sip enable sbc sip field-limit enable undo sbc sip register-reduce enable # radius-server group rd1 radius-server authentication 192.168.7.249 1645 weight 0 radius-server accounting 192.168.7.249 1646 weight 0 radius-server shared-key itellin radius-server type plus11 radius-server traffic-unit kbyte # # # # diffserv domain default # scheduler-profile e_home gts cir 4000 pir 4000 queue-length 65536 outbound gts cir 4000 pir 4000 queue-length 65536 inbound # scheduler-profile hsi car cir 2000 pir 2000 cbs 250000 pbs 250000 downstream # scheduler-profile iptv gts cir 4000 pir 4000 queue-length 65536 outbound # scheduler-profile voip car cir 32 pir 32 cbs 10000 pbs 10000 downstream #




Issue 05 (2010-06-01)

scheduler-profile wlan car cir 512 pir 512 cbs 250000 pbs 250000 downstream # qos-profile default # qos-profile e_home scheduler-profile e_home # qos-profile hsi scheduler-profile hsi # qos-profile iptv scheduler-profile iptv # qos-profile voip scheduler-profile voip # qos-profile wlan scheduler-profile wlan # session-group-profile default # session-group-profile e_home qos-profile e_home session-group-identify inner-vlan session-limit 7 # family-profile default # interface Aux0/0/1 # interface Virtual-Template0 # interface NULL0 # l2tp-group default-lac # l2tp-group default-lns # ip pool pool1 local gateway 172.82.0.1 255.255.0.0 section 0 172.82.0.2 172.82.0.200 dns-server 192.168.7.252 # iptn # dpi pts # dpi global-policy # dpi dsu-mac # dpi restricted-policy # ancp neighbor-profile default-neighbor # dot1x-template 1 # aaa authentication-scheme auth1 accounting-scheme acct1 domain default0 ip-pool pool1 domain default1 domain default_admin domain isp1 authentication-scheme auth1 accounting-scheme acct1



3-55

radius-server group rd1 ip-pool pool1 domain e_home_hsi authentication-scheme auth1 accounting-scheme acct1 radius-server group rd1 ip-pool pool1 qos profile hsi domain e_home_iptv authentication-scheme auth1 accounting-scheme acct1 radius-server group rd1 ip-pool pool1 qos profile iptv domain e_home_voip authentication-scheme auth1 accounting-scheme acct1 radius-server group rd1 ip-pool pool1 qos profile voip domain e_home_wlan authentication-scheme auth1 accounting-scheme acct1 radius-server group rd1 ip-pool pool1 qos profile wlan # # local-aaa-server # service-identify-policy e_home service-identify cos inner-vlan dot1p 2 domain e_home_iptv dot1p 6 domain e_home_voip # interface GigabitEthernet0/0/0 undo shutdown ip address 172.1.200.7 255.255.0.0 speed auto duplex auto # interface GigabitEthernet2/0/0 undo shutdown bas access-type layer2-subscriber ip-trigger arp-trigger # interface GigabitEthernet2/0/1 undo shutdown # interface GigabitEthernet2/0/1.2 user-vlan 100 QinQ 100 bas access-type layer2-subscriber default-domain authentication isp1 ip-trigger session-group-profile e_home service-identify-policy e_home # interface GigabitEthernet2/0/2 undo shutdown # interface GigabitEthernet2/0/3 undo shutdown # interface GigabitEthernet2/0/4 undo shutdown # interface GigabitEthernet2/0/5




Issue 05 (2010-06-01)

undo shutdown # interface GigabitEthernet2/0/6 undo shutdown # interface GigabitEthernet2/0/7 undo shutdown # interface GigabitEthernet2/0/8 undo shutdown # interface GigabitEthernet2/0/9 undo shutdown # interface GigabitEthernet2/0/10 undo shutdown # interface GigabitEthernet2/0/11 undo shutdown # interface GigabitEthernet2/0/12 undo shutdown # interface GigabitEthernet2/0/13 undo shutdown # interface GigabitEthernet2/0/14 undo shutdown # interface GigabitEthernet2/0/15 undo shutdown # interface GigabitEthernet2/0/16 undo shutdown # interface GigabitEthernet2/0/17 undo shutdown # interface GigabitEthernet2/0/18 undo shutdown # interface GigabitEthernet2/0/19 undo shutdown # interface GigabitEthernet2/0/20 undo shutdown # interface GigabitEthernet2/0/21 undo shutdown # interface GigabitEthernet2/0/22 undo shutdown # interface GigabitEthernet2/0/23 undo shutdown # sbc roamlimit default deny # sbc keepalive-packet empty # sbc backup reg-user enable # sbc backup reg-user at 0 # # sbc sip expire enable # # #



3-57

undo sbc roamlimit-extend enable undo sbc roamlimit enable sbc roamlimit default deny # sbc default # user-interface con 0 user-interface aux 0 user-interface vty 0 authentication-mode none user privilege level 3 idle-timeout 0 0 user-interface vty 1 4 authentication-mode none user privilege level 3 user-interface vty 16 20 # multicast shaping # multicastbandwidth # return

3.5.7 Example for Configuring the L2TP QoS by Tunnels

Networking RequirementAs shown in Figure 3-7, the ME60 functions as the LNS of the L2TP tunnel. The process forVPN users to visit the company headquarters is as follows:

l A user dials up to access the Internet.l The NAS initiates a request for building a tunnel to the LNS when it authenticates the user

and finds that the user is a VPN user.l After a tunnel is built between the NAS and the LNS, the NAS sends the contents of the

negotiation with the VPN user to the LNS as packets.l The LNS decides whether to accept the connection according to the negotiation.l The user communicates with the company headquarters through the tunnel between the

NAS and the LNS.l The user is connected through the domain1 domain and obtains its IP address from the

pool1 address pool.

The L2TP QoS scheduling mode needs to be set for the LNS. Configure multiple users to goonline through one tunnel and all the users in the domain share committed bandwidth of 100Mbit/s and peak bandwidth of 200 Mbit/s.

Figure 3-7 Example of the networking of L2TP QoS scheduling by tunnel

VPN Client LAC LNS

NAS ME60

Headquarter

Internet

TunnelIPTN/ISDN




Issue 05 (2010-06-01)


1. Configure the LAC.2. Configure the LNS. The ME60 functions as the LNS.3. Configure the scheduling profile and the QoS profile.4. Apply the QoS profile to the domain.5. Configure the function of L2TP QoS by tunnel for the L2TP group.


l Loopback address

l Address pool name, address pool segment, and address pool gateway

l Name of the domain where users are

l Name of the scheduling profile and name of the QoS profile

Configuration Procedure1. Perform configuration at the user side.

In the window for dial-in access, enter vpdnuser@domain1 as the VPN user name and 170as the dial-in number. In the pop-up dial-in terminal window, enter username as the username for the authentication by the RADIUS and userpass as the password.

2. Perform configuration at the NAS side.Use the Quidway A8010 as the LAC.# Configure 170 as the dial-in number on the Quidway A8010.# Create a VPN user on the RADIUS server with user name username and passworduserpass, and configure the IP address for the LNS (In this case, the IP address of the LNSis 192.168.0.1).# Set the local device name to A8010 and perform tunnel authentication on it. The tunnelauthentication password is quidway.

3. Confgure the ME60 (LNS).# Create a VT interface and configure it.<Quidway> system-view[Quidway] interface virtual-template 1[Quidway-Virtual-Template1] ppp authentication-mode chap[Quidway-Virtual-Template1] quit

# Enable the L2TP service and create an L2TP group.[Quidway] l2tp enable[Quidway] l2tp-group lns1

# Configure the L2TP connection at the LNS side.[Quidway-l2tp-lns1] tunnel name LNS[Quidway-l2tp-lns1] allow l2tp virtual-template 1 remote A8010

# Configure the tunnel authentication and set the password for tunnel authentication.[Quidway-l2tp-lns1] tunnel authentication[Quidway-l2tp-lns1] tunnel password simple quidway[Quidway-l2tp-lns1] quit



3-59

# Define an address pool and allocate IP addresses for the dial-in users.[Quidway] ip pool pool1 local[Quidway-ip-pool-pool1] gateway 10.10.10.1 255.255.255.0[Quidway-ip-pool-pool1] section 0 10.10.10.2 10.10.10.100[Quidway-ip-pool-pool1] quit# Configure the domain named domain1.[Quidway] aaa[Quidway-aaa] domain domain1[Quidway-aaa-domain-domain1] authentication-scheme default0[Quidway-aaa-domain-domain1] accounting-scheme default0[Quidway-aaa-domain-domain1] ip-pool pool1[Quidway-aaa-domain-domain1] quit[Quidway-aaa] quit# Configure a loopback interface (loopback 0).[Quidway] interface loopback 0[Quidway-LoopBack0] ip address 192.168.0.1 255.255.255.255[Quidway-LoopBack0] quit# Create an LNS group named group1.[Quidway] lns-group group1# Bind loopback 0 to the LNS group.[Quidway-lns-group-group1] bind source loopback 0# Specify the tunnel board in slot 1 for the LNS group.[Quidway-lns-group-group1] bind slot 1[Quidway-lns-group-group1] quit

4. Configure the scheduling profile and the QoS profile.# Configure the scheduling profile.<Quidway> system-view[Quidway] scheduler-profile sche1 [Quidway-scheduler-sche1] gts cir 100000 pir 200000[Quidway-scheduler-sche1] quit# Configure the QoS profile.[Quidway] qos-profile pro1[Quidway-qos-pro1] scheduler-profile sche1[Quidway-qos-pro1] quit

5. Apply the QoS profile to the domain.[Quidway] aaa[Quidway-aaa] domain doma1[Quidway-aaa-domain-doma1] qos profile pro1 lns-gts

6. Set the scheduling mode to scheduling by tunnels for the L2TP group.[Quidway] l2tp-group lns1[Quidway-l2tp-lns1] qos scheduling-mode tunnel

Configuration Files# sysname Quidway# l2tp enable#scheduler-profile sche1 gts cir 100000 pir 200000 queue-length 65536 outbound gts cir 100000 pir 200000 queue-length 65536 inbound#qos-profile pro1 scheduler-profile sche1#interface Virtual-Template1#




Issue 05 (2010-06-01)

interface GigabitEthernet7/0/0 undo shutdown #interface GigabitEthernet7/0/1.2 pppoe-server bind Virtual-Template 1 undo shutdown bas access-type layer2-subscriber#interface LoopBack0 ip address 192.168.0.1 255.255.255.255#l2tp-group lns1 allow l2tp virtual-template 1 remote A8010 tunnel password simple quidway tunnel name LNS qos scheduling-mode tunnel#lns-group group1 bind source LoopBack0 bind slot 1#ip pool pool1 local gateway 10.10.10.1 255.255.255.0 section 0 10.10.10.2 10.10.10.100#aaadomain domain1 authentication-scheme default0 accounting-scheme default0 ip-pool pool1 qos profile pro1 lns-gts#return

3.5.8 Example for Configuring the L2TP QoS by Sessions

Networking RequirementAs shown in Figure 3-8, the ME60 functions as the LNS of the L2TP tunnel. The process forVPN users to visit the company headquarters is as follows:

l A user dials up to access the Internet.

l The NAS initiates a request for building a tunnel to the LNS when it authenticates the userand finds that the user is a VPN user.

l After a tunnel is built between the NAS and the LNS, the NAS sends the contents of thenegotiation with the VPN user to the LNS as packets.

l The LNS decides whether to accept the connection according to the negotiation.

l The user communicates with the company headquarters through the tunnel between theNAS and the LNS.

l The user is connected through the domain1 domain and obtains its IP address from thepool1 address pool.

Configure the LNS with the scheduling mode of L2TP QoS scheduling by tunnels.

l All the users in the domain share committed bandwidth of 100 Mbit/s and peak bandwidthof 200 Mbit/s.

l Each user is configured with committed bandwidth of 5 Mbit/s and peak bandwidth of 10Mbit/s.



3-61

Figure 3-8 Example of the networking of L2TP QoS scheduling by session

VPN Client LAC LNS

NAS ME60

Headquarter

Internet

TunnelIPTN/ISDN


1. Configure the LAC.2. Configure the LNS. The ME60 functions as the LNS.3. Configure the scheduling profile and the QoS profile.4. Apply the QoS profile to the domain.5. Set the scheduling mode of the L2TP group to scheduling by sessions.


l Loopback address

l Address pool name, address pool segment, and address pool gateway

l Name of the domain where users are

l Name of the scheduling profile and name of the QoS profile

Configuration Procedure1. Perform configuration at the user side.

In the window for dial-in access, enter vpdnuser@domain1 as the VPN user name and 170as the dial-in number. In the pop-up dial-in terminal window, enter username as the username for the authentication by the RADIUS and userpass as the password.

2. Perform configuration at the NAS side.Use the Quidway A8010 as the LAC.# Configure 170 as the dial-in number on the Quidway A8010.# Create a VPN user on the RADIUS server with user name username and passworduserpass, and configure the IP address for the LNS (In this case, the IP address of the LNSis 192.168.0.1).# Set the local device name to A8010 and perform tunnel authentication on it. The tunnelauthentication password is quidway.

3. Confgure the ME60 (LNS).# Create a VT interface and configure it.<Quidway> system-view




Issue 05 (2010-06-01)

[Quidway] interface virtual-template 1[Quidway-Virtual-Template1] ppp authentication-mode chap[Quidway-Virtual-Template1] quit# Enable the L2TP service and create a L2TP group.[Quidway] l2tp enable[Quidway] l2tp-group lns1# Configure the name of the LNS and the name of the peer end of the tunnel.[Quidway-l2tp-lns1] tunnel name LNS[Quidway-l2tp-lns1] allow l2tp virtual-template 1 remote A8010# Configure the tunnel authentication and set the password for tunnel authentication.[Quidway-l2tp-lns1] tunnel authentication[Quidway-l2tp-lns1] tunnel password simple quidway[Quidway-l2tp-lns1] quit# Define an address pool and allocate IP addresses for the dial-in users.[Quidway] ip pool pool1 local[Quidway-ip-pool-pool1] gateway 10.10.10.1 255.255.255.0[Quidway-ip-pool-pool1] section 0 10.10.10.2 10.10.10.100[Quidway-ip-pool-pool1] quit# Configure the domain named domain1.[Quidway] aaa[Quidway-aaa] domain domain1[Quidway-aaa-domain-domain1] authentication-scheme default0[Quidway-aaa-domain-domain1] accounting-scheme default0[Quidway-aaa-domain-domain1] ip-pool pool1[Quidway-aaa-domain-domain1] quit[Quidway-aaa] quit# Configure a loopback interface (loopback 0).[Quidway] interface loopback 0[Quidway-LoopBack0] ip address 192.168.0.1 255.255.255.255[Quidway-LoopBack0] quit# Create an LNS group named group1.[Quidway] lns-group group1# Bind loopback 0 to the LNS group.[Quidway-lns-group-group1] bind source loopback 0# Specify the tunnel board in slot 1 for the LNS group.[Quidway-lns-group-group1] bind slot 1[Quidway-lns-group-group1] quit

4. Configure the scheduling profile and the QoS profile.# Configure scheduling profile sche1 for setting the parameters of traffic shaping fortunnels.<Quidway> system-view[Quidway] scheduler-profile sche1 [Quidway-scheduler-sche1] gts cir 100000 pir 200000[Quidway-scheduler-sche1] quit# Configure scheduling profile sche2 for setting the parameters of traffic shaping for users.<Quidway> system-view[Quidway] scheduler-profile sche2 [Quidway-scheduler-sche2] gts cir 5000 pir 10000[Quidway-scheduler-sche2] quit# Configure the QoS profile.[Quidway] qos-profile pro1[Quidway-qos-pro1] scheduler-profile sche1[Quidway-qos-pro1] quit[Quidway] qos-profile pro2[Quidway-qos-pro2] scheduler-profile sche2



3-63

[Quidway-qos-pro1] quit

5. Configure the QoS profile in the domain.[Quidway] aaa[Quidway-aaa] domain doma1[Quidway-aaa-domain-doma1] qos profile pro2 lns-gts[Quidway-aaa-domain-doma1] quit[Quidway-aaa] quit

6. Set the scheduling mode of the L2TP group to scheduling by sessions. Apply QoS profilepro1 to the L2TP group and schedule all the user packets in the domain according to thepro1 profile.[Quidway] l2tp-group lns1[Quidway-l2tp-lns1] qos scheduling-mode session[Quidway-l2tp-lns1] qos profile pro1

Configuration Files# sysname Quidway# l2tp enable#scheduler-profile sche1 gts cir 100000 pir 200000 queue-length 65536 outbound gts cir 100000 pir 200000 queue-length 65536 inbound#scheduler-profile sche2 gts cir 5000 pir10000 queue-length 65536 outbound gts cir 5000 pir 10000 queue-length 65536 inbound#qos-profile pro1 scheduler-profile sche1#qos-profile pro2 scheduler-profile sche2#interface Virtual-Template1#interface GigabitEthernet7/0/0 undo shutdown #interface GigabitEthernet7/0/1.2 pppoe-server bind Virtual-Template 1 undo shutdown bas access-type layer2-subscriber#interface LoopBack0 ip address 192.168.0.1 255.255.255.255#l2tp-group lns1 allow l2tp virtual-template 1 remote A8010 tunnel password simple quidway tunnel name LNS qos scheduling-mode session qos profile pro1#lns-group group1 bind source LoopBack0 bind slot 1#ip pool pool1 local gateway 10.10.10.1 255.255.255.0 section 0 10.10.10.2 10.10.10.100#aaa domain domain1




Issue 05 (2010-06-01)

authentication-scheme default0 accounting-scheme default0 ip-pool pool1 qos profile pro2 lns-gts#return



3-65

4 Link Level QoS Configuration

About This Chapter

This chapter describes the knowledge about link level QoS, including the basic concepts,configuration procedures and configuration examples.

4.1 IntroductionThis section describes the basic principles and the implementation of link level QoS.

4.2 Configuring Link Level QoSThis section describes how to configure and use the functions of link level QoS.

4.3 Configuration ExamplesThis section provides several configuration examples of link level QoS.

Quidway ME60 Multiservice Control GatewayConfiguration Guide - QoS 4 Link Level QoS Configuration


4-1

4.1 IntroductionThis section describes the basic principles and the implementation of link level QoS.

4.1.1 Link Level QoS Overview

4.1.2 Link Level QoS Supported by the ME60

4.1.1 Link Level QoS OverviewLink level QoS is also called last mile QoS. The last mile is the delivering connectivity betweena user and the DSLAM. The ME60 can adjust the downstream traffic based on the link layerprotocol that works on the link between the user and the DSLAM. The ME60 can make QoSshaping more accurate by deducting extra costs such as the cell of ATM users, which helps toprevent the congestion when extra costs are not included and the DSLAM traffic exceeds thecapacity of the line.

4.1.2 Link Level QoS Supported by the ME60

The link level QoS scheduling has two modes:

l Link level QoS scheduling by using ATM cells

The user and the DSLAM communicate through the ATM network, and the packetsbetween the ME60 and the DSLAM are PPPoE packets. To keep the transmission rate atthe link layer the same, the ME60 needs to adjust the packet size according to the ATMand Ethernet encapsulation rules.

l Link level QoS scheduling by using Ethernet frames

The user and the DSLAM communicate with each other through the Ethernet, and theDSLAM and the ME60 communicate through the VLAN or by using the QinQ technology.When configured with link level QoS, the ME60 can deduct the cost of the VLAN headerfor packets transmitted between the BRAS and the DSLAM.

4.2 Configuring Link Level QoSThis section describes how to configure and use the functions of link level QoS.


4.2.2 Enabling Link Level QoS

4.2.3 Configuring the Remote Link Mode

4.2.4 Configuring the Adjustment Value of the Remote Link

4.2.5 (Optional) Configuring the Adjustment Value of the Local Link

4.2.6 (Optional) Enabling the CAR and Statistics Functions of the Upstream L3 Packets

4.2.7 (Optional) Obtaining Transmission Rate of User Packets Dynamically Through ANCP

4 Link Level QoS ConfigurationQuidway ME60 Multiservice Control Gateway



Issue 05 (2010-06-01)



When the ME60 functions as a BRAS, you can configure link level QoS for it so that theME60 can perform QoS shaping more accurate by deducting extra costs, such as the cell of ATMusers. This helps to prevent the congestion that occurs when the downstream traffic of theME60 exceeds the capacity of the DSLAM line.


Before configuring link level QoS, complete the following task:

l Configuring the BRAS function for the ME60 so that users can go online

Data Preparation

To configure link level QoS, you need the following data.

No. Data

1 Adjustment value of remote packet size of the ME60

2 Adjustment value of the ME60 local link

4.2.2 Enabling Link Level QoS

Context


Procedure



Step 2 Run:qos link-adjustment remote enable [ slot slot-id ]

Link level QoS is enabled.

----End

4.2.3 Configuring the Remote Link Mode



4-3

Context

The ME60 adjusts the packet size according to the link types on the two ends of the DSLAM.If users are accessed through PPPoA mode, the remote link type should be set to cell; if usersare accessed through PPPoE mode, the remote link type should be set to frame.

The ME60 can perform link level QoS scheduling on two types of links.


Procedure





Step 3 Run:qos link-adjustment shaping-mode { frame | cell }

The mode of link level QoS is set.

By default, the mode is frame mode.

----End

4.2.4 Configuring the Adjustment Value of the Remote Link

Context


Procedure





Step 3 Run:qos link-adjustment adjust-value remote

The adjustment value of the remote link is configured.

----End




Issue 05 (2010-06-01)

4.2.5 (Optional) Configuring the Adjustment Value of the LocalLink


Procedure



Step 2 Run:qos link-adjustment adjust-value local [ slot slot-id ]

The adjustment value of the local link is configured.

----End

4.2.6 (Optional) Enabling the CAR and Statistics Functions of theUpstream L3 Packets


Procedure



Step 2 Run:qos link-adjustment link-layer-exclude [ slot slot-id ]

The CAR and statistics functions of the upstream L3 packets are enabled.

----End

4.2.7 (Optional) Obtaining Transmission Rate of User PacketsDynamically Through ANCP

ContextThe ME60 has the function of the ANCP. When using the ANCP protocol together with linklevel QoS, the ME60 automatically sets the upstream and downstream transmission ratesaccording to the rate parameters reported by the ANCP protocol.




4-5

Procedure



Step 2 Run:aaa




Step 4 Run:ancp auto-qos-adapt

Users can obtain the packet transmission rate through the ANCP protocol.

----End

4.3 Configuration ExamplesThis section provides several configuration examples of link level QoS.

4.3.1 Example for Configuring Link Level QoS in ATM Cell Mode

4.3.1 Example for Configuring Link Level QoS in ATM Cell Mode

Networking RequirementAs shown in Figure 4-1, the ME60 functions as the BRAS. The user is connected to the networkthrough PPPoA, and the link between the ME60 and the DSLAM is an Ethernet link. You needto configure link level QoS on the ME60 to prevent congestion from occurring at the DSLAM.

l The user belongs to the isp1 domain and is connected to the network through the GE2/0/0.1sub-interface of the ME60.

l RADIUS authentication and RADIUS accounting are adopted.

l The IP address of the RADIUS server is 192.168.7.249 and the ports for authentication andaccounting are 1645 and 1646 respectively. The protocol is RADIUS+1.1 and the key isitellin.

l The IP address of the DNS is 192.168.7.252.

Figure 4-1 Example of the configuration of QoS scheduling in ATM cell mode

Ethernet

PC CPE ATM DSLAM ME60(BRAS)

IPoE PPPoA PPPoE GE2/0/0




Issue 05 (2010-06-01)


1. Configure the DSLAM.2. Configure the BRAS function on the ME60 so that users can log in.3. Configure link level QoS.


l The adjustment value of remote link packets: -20

NOTE

The adjustment value of remote link packets is calculated by the following formula:

l The cost of PPPoA packets: The cost of the ATM header is 0; the cost of the ATM tail is 8.

l The cost of PPPoE packets: The cost of the Ethernet header is 14; the cost of the QinQ is 8; the costof the PPPoE header is 6.

l The adjustment value = (0 + 8) - (14 + 8 + 6) = -20

Configuration Procedure1. Configure the DSLAM.

The configuration process is omitted here. For details on the process, refer to the relevantmanual.

2. Configure the BRAS service of the ME60 so that users can go online.For configuration procedure, refer to the Quidway ME60 Multiservice Control GatewayConfiguration Guide - BRAS Services.

3. Configure the link level QoS.# Enable link level QoS.<Quidway> system-view[Quidway] qos link-adjustment remote enable slot 2# Configure the type of the remote link at the sub-interface.[Quidway] interface GigabitEthernet 2/0/0.1[Quidway-GigabitEthernet2/0/0.1] qos link-adjustment shaping-mode cell# Configure the remote adjustment value at the sub-interface.[Quidway-GigabitEthernet2/0/0.1] qos link-adjustment -20 remote[Quidway-GigabitEthernet2/0/0.1] quit

Configuration Filesl Configuration file of the ME60

# sysname Quidway#radius-server group rd1 radius-server authentication 192.168.7.249 1645 weight 0 radius-server accounting 192.168.7.249 1646 weight 0 radius-server shared-key itellin radius-server type plus11



4-7

radius-server traffic-unit kbyte# qos link-adjustment remote enable slot 2#interface Virtual-Template1#interface GigabitEthernet2/0/0 undo shutdown#interface GigabitEthernet2/0/0.1 undo shutdown qos link-adjustment shaping-mode cell qos link-adjustment -20 remote user-vlan 1 QinQ 10 pppoe-server bind Virtual-Template 1 bas access-type layer2-subscriber#ip pool pool1 local gateway 172.82.0.1 255.255.255.0 section 0 172.82.0.2 172.82.0.200 dns-server 192.168.7.252#aaaauthentication-scheme auth1accounting-scheme acct1domain default0domain default1domain default_admindomain isp1 authentication-scheme auth1 accounting-scheme acct1 radius-server group rd1 ip-pool pool1#return




Issue 05 (2010-06-01)

5 Multicast Shaping Configuration

About This Chapter

This chapter describes the knowledge about multicast shaping, including the basic concepts,configuration procedures and configuration examples.

5.1 IntroductionThis section describes the basic principles and the implementation of multicast shaping.

5.2 Configuring Multicast ShapingThis section describes how to configure and use the functions of multicast shaping.

5.3 Configuration ExamplesThis section provides several configuration examples of multicast shaping.

Quidway ME60 Multiservice Control GatewayConfiguration Guide - QoS 5 Multicast Shaping Configuration


5-1

5.1 IntroductionThis section describes the basic principles and the implementation of multicast shaping.

5.1.1 Multicast Shaping Overview

5.1.2 Multicast Shaping Supported by the ME60

5.1.1 Multicast Shaping OverviewAfter the IPTV multicast service is deployed, the multicast source may jitter when the multicasttraffic is huge. The ME60 can shape the multicast traffic so that the jitter of the multicast sourcecan be limited in an acceptable degree. If the ME60 is configured with the function of multicastshaping, the ME60 can control the multicast traffic of users in the domain when users usemulticast services. This prevents the multicast traffic from bursting and can help to send multicastpackets smoothly and control the jitter of the multicast source in an acceptable degree.

5.1.2 Multicast Shaping Supported by the ME60

Traffic shaping (TP) is typically used to limit the traffic going out an interface and to enable theME60 to transmit packets at a rather steady speed. TP is a mechanism for adjusting the trafficoutput rate. TP is usually realized with the help of a buffer and a token bucket. The process ofTP is as follows:

Packets are classified when they are received by the interface, and then they undergo differentprocesses as follows:

l Packets are sent directly if they do not need to be shaped.

l For the packets that are going to be shaped, when there is no general traffic shaping (GTS)queue, the ME60 compares the packet length with the number of tokens in the bucket. Ifthe tokens in the bucket are sufficient, the packets are forwarded; otherwise, the ME60retains excess packets in a GTS queue to buffer the delayed packets. The token bucket putstokens into the bucket at the configured rate and the number of tokens decreases when thepackets are sent. When there are packets waiting in the GTS queue, GTS sends out themat fixed intervals. Every time before GTS sends the packets out, it compares the packetnumber with the number of the tokens in the bucket. When the tokens in the bucket are notsufficient for sending the packets in the GTS queue or there is no packets left in the GTSqueue, GTS stops sending the packets out.

l For packets that are going to be shaped, when there is the GTS queue, the packets are putinto the queue to wait to be scheduled and forwarded by the GTS at a fixed interval later.

l When a packet is sent to the GTS queue, the packet is dropped if the queue is full.

5.2 Configuring Multicast ShapingThis section describes how to configure and use the functions of multicast shaping.


5.2.2 Configuring the Multicast Program List

5.2.3 Enabling the Function of Multicast Shaping

5 Multicast Shaping ConfigurationQuidway ME60 Multiservice Control Gateway



Issue 05 (2010-06-01)

5.2.4 Configuring the Bandwidth of the Multicast List

5.2.5 (Optional) Configuring the Multicast Profile

5.2.6 (Optional) Configuring the Multicast Profile in the Domain

5.2.7 (Optional) Enabling Authentication for Multicast Users



Applicable EnvironmentAfter the IPTV multicast service is deployed, the multicast source may jitter when the multicasttraffic is huge. When configured with the function of multicast shaping, the ME60 can shapethe multicast traffic so that the jitter of the multicast source can be limited in an acceptabledegree.

Pre-configuration TaskBefore configuring multicast shaping, complete the following task:

l Configuring the multicast service

Data PreparationTo configure multicast shaping, you need the following data.

No. Data

1 Name of the multicast list

2 CIR and PIR of the multicast traffic

5.2.2 Configuring the Multicast Program List


Procedure



Step 2 Run:multicast-list multicast-list-name [ index index-value ] [ source-address source-ip-address [ mask-length ] ] group-address group-ip-address [ mask-length ] [ vpn-instance vpn-instace-name ]



5-3

The multicast program list is configured.

The group-address field specifies the multicast address.

----End

5.2.3 Enabling the Function of Multicast Shaping

Procedurel Enabling the function of multicast shaping globally

1. Run:system-view


multicast shaping enable

Multicast shaping is enabled.l Enabling the function of multicast shaping at an interface

1. Run:system-view




multicast shaping enable

Multicast shaping is enabled.

----End

5.2.4 Configuring the Bandwidth of the Multicast List


Procedure



Step 2 Run:multicast shaping

The multicast shaping view is displayed.




Issue 05 (2010-06-01)

Step 3 Run:multicast-list { name group-list-name | list-index start-index-value [ end-index-value ] } cir cir-value [ pir pir-value ] [ queue-length length ]

The bandwidth of the multicast list is configured.

----End

5.2.5 (Optional) Configuring the Multicast Profile


Procedure



Step 2 Run:aaa


Step 3 Run:multicast-profile profile-name

The multicast profile is created and the multicast profile view is displayed.

If the multicast profile already exists, the multicast profile view is displayed directly.

Step 4 Run:multicast-list { name group-list-name | list-index start-index-value [ end-index-value ] }

The multicast list is applied in the multicast profile view.

This operation is optional. You do not need to perform this operation if you do not want toconfigure the multicast profile.

----End

5.2.6 (Optional) Configuring the Multicast Profile in the Domain


Procedure





5-5

Step 2 Run:aaa




Step 4 Run:multicast-profile profile-name

The multicast profile is bound to the domain.

This operation is optional. You do not need to perform this operation if you do not want toauthenticate the multicast users.

----End

5.2.7 (Optional) Enabling Authentication for Multicast Users

Context


Procedure





Step 3 Run:igmp enable

IGMP is enabled.

Step 4 Run:multicast authorization-enable

Authentication of multicast users is enabled.

This operation is optional. You do not need to perform this operation if you do not want toauthenticate the multicast users.

----End





Issue 05 (2010-06-01)

Action Command

Check the configuration of themulticast profile.

display multicast-profile [ profile-name ]

Check the configuration of themulticast shaping list.

display multicast-list [ group-list-name ]

By running the display multicast-profile command, you can view the information about themulticast shaping list that is bound to the multicast profile.

<Quidway> display multicast-profile pro1 Profile-name : pro1 If-authentic : Yes Multicast-list-name : list1

By running the display multicast-list command, you can view the detailed information aboutthe multicast shaping list.

<Quidway> display multicast-list list1 ----------------------------------------------------------------------- Multicast-list name : list1 Index : 0 Source IP/mask : 1.1.1.1/24 Group IP/mask : 239.1.1.1/24 Group vpn-instance : -- -----------------------------------------------------------------------

5.3 Configuration ExamplesThis section provides several configuration examples of multicast shaping.

5.3.1 Example for Configuring Multicast Shaping

5.3.1 Example for Configuring Multicast ShapingAs shown in Figure 5-1, the ME60 functions as the BRAS to provide the Internet service andthe IPTV multicast service for users in the isp1 domain. The IGMP protocol is used at the hostside and the SM mode is used for the PIM network.

The requirements on multicast shaping are as follows:

l The function of multicast shaping uses 5 Mbit/s committed bandwidth and 10 Mbit/s peakbandwidth.

l The IP address of the multicast source is 111.1.1.1 and the IP address of the multicast groupis 225.1.1.1.

l The multicast service users need to be authenticated.



5-7

Figure 5-1 Example of multicast shaping configuration

S1

user2@isp1

user1@isp1

ME60

225.1.1.1AccessNetwork

PIM-SMGE2/0/0

GE1/0/0


1. Configure the IP address of the interface and the unicast routing protocol.2. Configure the BRAS service so that users can go online.3. Configure the IGMP and the PIM-SM protocols.4. Configure the function of multicast shaping.


l Name of the Multicast shaping list

l Multicast profile name

Configuration Procedure1. Configure the IP address of the interface and the unicast routing protocol.

For configuration procedure, refer to the Quidway ME60 Multiservice Control GatewayConfiguration Guide - IP Routing.

2. Configure the access service.For configuration procedure, refer to the Quidway ME60 Multiservice Control GatewayConfiguration Guide - BRAS Services.

3. Configure the IGMP and the PIM-SM protocols.Enable the multicast function and enable the IGMP function at the interfaces at the hostside.# Enable the multicast function on the ME60 and enable the IGMP function at the interfaceson the host side. Enable the IGMP function at the GE2/0/0 interface. The version of theIGMP protocol is v2.<Quidway> system-view[Quidway] multicast routing-enable[Quidway] interface gigabitethernet 2/0/0[Quidway-GigabitEthernet2/0/0] igmp enable[Quidway-GigabitEthernet2/0/0] igmp version 2[Quidway-GigabitEthernet2/0/0] quit

NOTE

The BAS interface does not support IGMPv3.




Issue 05 (2010-06-01)

# Enable the PIM-SM function at the GE1/0/0 interface of the ME60.[Quidway] interface gigabitethernet 1/0/0[Quidway-GigabitEthernet1/0/0] pim sm[Quidway-GigabitEthernet1/0/0] quit

4. Configure multicast shaping.# Configure the multicast shaping list.[Quidway] multicast-list list1 source-address 111.1.1.1 group-address 225.1.1.1# Enable the function of multicast shaping.[Quidway] multicast shaping enable# Set the parameters of multicast shaping to guarantee 5 Mbit/s bandwidth and 10 Mbit/speak bandwidth.[Quidway] multicast shaping[Quidway-qos-mshaping] multicast-list name list1 cir 5000 pir 10000[Quidway-qos-mshaping] quit# Enable the function of authenticating multicast users.[Quidway] interface gigabitethernet 2/0/0[Quidway-GigabitEthernet2/0/0] multicast authorization-enable# Configure the multicast profile and bind the multicast shaping list to the multicast profile.[Quidway] aaa[Quidway-aaa] multicast-profile pro1[Quidway-aaa-mprofile-pro1] multicast-list name list1[Quidway-aaa-mprofile-pro1] quit# Apply the multicast profile to the isp1domain.[Quidway-aaa] domain isp1[Quidway-aaa-domain-isp1] multicast-profile pro1

5. Verify the configuration.By running the display multicast-list command, you can view the detailed informationabout the multicast shaping list.[Quidway] display multicast-list list1 ----------------------------------------------------------------------- Multicast-list name : list1 Index : 0 Source IP/mask : 111.1.1.1/32 Group IP/mask : 225.1.1.1/32 Group vpn-instance : -- -----------------------------------------------------------------------

Configuration Filesl Configuration file of the ME60# sysname Quidway# multicast routing-enable# # multicast shaping enable#radius-server group rd1 radius-server authentication 192.168.7.249 1645 weight 0 radius-server authentication 10.10.10.2 1812 weight 0 radius-server accounting 192.168.7.249 1646 weight 0 radius-server shared-key itellin radius-server type plus11 radius-server traffic-unit kbyte# interface GigabitEthernet1/0/0 undo shutdown



5-9

pim sm# interface GigabitEthernet2/0/0 undo shutdown pppoe-server bind Virtual-Template 1 igmp enable bas access-type layer2-subscriber multicast authorization-enable #ip pool pool1 local gateway 192.168.1.1 255.255.255.0 section 0 192.168.1.2 192.168.1.200 dns-server 192.168.7.252# multicast-list list1 source-address 111.1.1.1 group-address 225.1.1.1aaa multicast-profile max-list multicast-profile pro1 multicast-list name list1 authentication-scheme auth1 accounting-scheme acct1 domain isp1 authentication-scheme auth1 accounting-scheme acct1 radius-server group rd1 ip-pool pool1 multicast-profile pro1#multicast shaping multicast-list name list1 cir 5000 pir 10000#return




Issue 05 (2010-06-01)

6 QPPB Configuration

About This Chapter

This chapter describes the knowledge about QPPB, including the basic concepts, configurationprocedures and configuration examples.

6.1 IntroductionThis section describes how to propagate QoS policies through the Border Gateway Protocol(BGP).

6.2 Configuring QPPBThis section describes how to configure QPPB to propagate QoS policies through BGP on thenetwork.

6.3 Configuration ExamplesThis section provides a configuration example of QPPB.

Quidway ME60 Multiservice Control GatewayConfiguration Guide - QoS 6 QPPB Configuration


6-1

6.1 IntroductionThis section describes how to propagate QoS policies through the Border Gateway Protocol(BGP).

6.1.1 QPPB Overview

6.1.2 QPPB Supported by the ME60

6.1.1 QPPB OverviewQoS Policy Propagation through the Border Gateway Protocol (QPPB) is a technology thatpropagate QoS policies through the BGP protocol. The routes are classified according to theBGP attributes such as community list, AS paths list, ACL, and prefix list. Each class matchesa QoS policy. The QPPB feature can be configured on BGP senders and BGP receivers.

6.1.2 QPPB Supported by the ME60

For the BGP route sender, you can set QoS parameters for BGP routes that match the routingpolicy.

For the BGP route receiver, the operation process is as follows:

1. Set QoS parameters for the routes whose attributes are configured as BGP by the routesenders. The QoS parameters include the IP precedence, QoS local-ID and the specifictraffic behavior.

2. Classify the traffic according to the QoS parameters, and then configure QoS traffic policiesfor the classified traffic.

3. Forward messages based on the local QoS policy configured so that the QoS policy can bedelivered through BGP.The IP precedence, QoS local ID, and traffic behavior for BGP routes are set on the BGProute receiver based on the following route attributes:l ACL

l AS path list

l Community list

l Route cost

l Address prefix list

In complex networking, QoS policies are modified dynamically. QPPB simplifies thepolicy modification that is required only on the BGP route sender.

NOTE

Currently, the QoS parameters supported by the ME60 are IP precedence and traffic behavior.

6.2 Configuring QPPBThis section describes how to configure QPPB to propagate QoS policies through BGP on thenetwork.

6 QPPB ConfigurationQuidway ME60 Multiservice Control Gateway



Issue 05 (2010-06-01)


6.2.2 Configuring Routing Attributes on the BGP Route Sender

6.2.3 Applying the Routing Policy to the BGP Route Sender

6.2.4 Configuring the Routing Policy on the BGP Route Receiver

6.2.5 Applying the Routing Policy to the BGP Route Receiver

6.2.6 Configuring Class-based Traffic Behavior

6.2.7 Applying the QPPB Policy to an Interface



Applicable EnvironmentIn a complex network, the complex traffic classification must be performed several times tomeet QoS requirements. In addition, packets cannot be classified based on the communityattribute and autonomous system (AS). Changing the configuration requires great workload andmany even fails. You can configure QPPB to enable the BGP route sender to set the BGP attributefor route classification. Thus, the route receiver can easily change the routing policy. In this case,you need to configure the BGP routing policy.

QPPB is applicable to both IBGP and EBGP. That is, QPPB can advertise QoS policies withinan AS or between two ASs.

Pre-configuration TaskBefore configuring a domain, complete the following tasks:

l Configuring basic BGP functions

l Configuring the local routes advertised by BGP

l Configuring interfaces for the setup of BGP connections

l Configuring BGP attributes on BGP route sender

l Configuring the traffic behavior

Data PreparationTo configure QPPB, you need the following data.

No. Data

1 Name of the traffic class

2 ACL number, MAC address, interface type and number, DSCP value, IP precedence,RTP port number, type of IP protocol, MPLS EXP value, and 802.1P value

6.2.2 Configuring Routing Attributes on the BGP Route Sender



6-3

Context

Do as follows on the BGP route sender.

Procedure



Step 2 Run:route-policy route-policy-name { permit | deny } node node-number

A routing policy is created and the routing policy view is displayed.

Step 3 Configure the match rule for the routing policy.l To specify the ACL, run the if-match acl basic-acl-number command.

l To specify the AS path list, run the if-match as-path-filter { as-path-acl-number } &<1-16>command.

l To specify the community attributes, run the if-match community-filter { basic-comm-filter-num [ whole-match ] | advace-comm-filter-num } &<1-16> command.

l To specify the route cost, run the if-match cost cost-value command.

l To specify the address prefix list, run the if-match ip-prefix ip-prefix-name command.

l To specify the extcommunity list number to match the routes of the specified extcommunity,run the if-match extcommunity-filter ext-comm-list-number&<1-16> command.

l To configure the match rule for the outgoing interface used for filter routes, run the if-match interface interface-type interface-number&<1-16> command.

l To configure the IPv4 match rule used to filter routes, run the if-match ip { next-hop | route-source } { acl acl-number | ip-prefix ip-prefix-name } command.

l To configure the MPLS label that matches the route update packet, run the if-match mpls-label command.

l To configure BGP to import routes of specified types, run the if-match route-type[ internal | external-type1 | external-type2 | external-type1or2 | is-is-level-1 | is-is-level-2 | nssa-external-type1 | nssa-external-type2 | nssa-external-type1or2 ] command.

l To configure the MPLS label that matches the OSPF routing information, run the if-matchtag value command.

The packets are matched one by one according to the traffic policy.

Step 4 Configure the route attributes as follows:l Run the apply as-path as-number &<1-10> [ additive ] command to add the specified AS

number to the BGP AS_Path attribute.l Run the apply community none or apply community { community-number | aa:nn | no-

advertise | no-export | no-export-subconfed | internet } * & <1-16> [ additive ] commandto set the community attributes of the BGP routes.

l Run the apply extcommunity [ rt { as-number: nn | ipv4-address : nn }* ] &<1-16>[ additive ] command to set the extcommunity attributes (router-target) of the BGP routes.

----End




Issue 05 (2010-06-01)

6.2.3 Applying the Routing Policy to the BGP Route Sender

ContextDo as follows on the BGP route sender.

Procedure



Step 2 Run:bgp as-number

The BGP view is displayed.

Step 3 Run:ipv4-family unicast

The IPv4 unicast address family view is displayed.

Step 4 Run:peer { ip-address | group-name } route-policy route-policy-name export

The outbound routing policy for BGP routes is configured.

----End

6.2.4 Configuring the Routing Policy on the BGP Route Receiver

ContextDo as follows on the BGP route receiver.

Procedure



Step 2 Run:route-policy route-policy-name { permit | deny } node node-number

A routing policy is created and the routing policy view is displayed.

Step 3 Configure the match rule for the routing policy.l To specify the ACL, run the if-match acl acl-number command.

l To specify the AS path list, run the if-match as-path-filter { as-path-acl-number } &<1-16>command.

l To specify the community attributes, run the if-match community-filter { basic-comm-filter-num [ whole-match ] | adv-comm-filter-num } &<1-16> command.



6-5

l To specify the route cost, run the if-match cost cost-value command.

l To specify the address prefix list, run the if-match ip-prefix ip-prefix-name command.

l To specify the extcommunity list number to match the routes of the specified extcommunity,run the if-match extcommunity-filter ext-comm-list-number&<1-16> command.

l To configure the match rule for the outgoing interface used for filter routes, run the if-match interface interface-type interface-number&<1-16> command.

l To configure the IPv4 match rule used to filter routes, run the if-match ip { next-hop | route-source } { acl acl-number | ip-prefix ip-prefix-name } command.

l To configure the MPLS label that matches the route update packet, run the if-match mpls-label command.

l To configure BGP to import routes of specified types, run the if-match route-type[ internal | external-type1 | external-type2 | external-type1or2 | is-is-level-1 | is-is-level-2 | nssa-external-type1 | nssa-external-type2 | nssa-external-type1or2 ] command.

The packets are matched one by one according to the traffic policy.

NOTE

The routing attributes used by the BGP route receiver to match route must be the attributes configured onthe BGP router sender.

Step 4 Set QoS parameters as follows:l To set the IP precedence, run the apply ip-precedence ip-precedence command.

l To configure the associated traffic behavior, run the apply behavior behavior-namecommand.

The IP precedence and the traffic behavior are mutually exclusive. You can set only one of them.The traffic behavior specified for the routing policy must be an existing one.

The IP precedence and the traffic behavior are mutually exclusive. You can set only one of them.The traffic behavior specified for the routing policy must be an existing one.

----End

6.2.5 Applying the Routing Policy to the BGP Route Receiver


Procedure



Step 2 Run:bgp as-number

The BGP protocol is started and the BGP view is displayed.

Step 3 Run:ipv4-family unicast




Issue 05 (2010-06-01)

The IPv4 unicast address family view is displayed.

Step 4 Run:peer ip-address as-number as-number

The BGP peer is created.

Step 5 Run:peer ip-address route-policy route-policy-name import

The inbound routing policy for BGP routes is configured.

----End

6.2.6 Configuring Class-based Traffic BehaviorDo as follows on the BGP route receiver.

For configuration procedure, see 2.2.3 Configuring Traffic Behavior.

NOTE

The ME60 supports the following behaviors:

l Deny and permit

l Traffic policing

l Marking

6.2.7 Applying the QPPB Policy to an Interface


Procedure





Step 3 Run:qppb-policy { ip-precedence | behavior } { destination | source }

The QPPB is applied.

NOTE

This command cannot be configured on an Eth-Trunk member interface.

----End




6-7

Run the following command to check the previous configuration.

Action Command

Display the QPPBinformation.

display fib verbose [ | { begin | exclude | include } regular-expression ]

After the configuration is complete, run the above commands and you can see that the value ofthe QosInfo field in the FIB is 0x20000001.

<Quidway> display fib verboseFIB Table: Total number of Routes : 1Destination: 66.1.1.1 Mask : 255.255.255.255 Nexthop : 100.1.1.2 OutIf : Pos1/0/0 LocalAddr : 100.1.1.1 LocalMask: 0.0.0.0 Flags : DGU Age : 165sec ATIndex : 0 Slot : 1 LspFwdFlag : 0 LspToken : 0x0 InLabel : NULL OriginAs : 200 BGPNextHop : 2.2.2.2 PeerAs : 200 QosInfo : 0x20000001 OriginQos: 0x0 NexthopBak : 0.0.0.0 OutIfBak : [No Intf] LspTokenBak: 0x0 InLabelBak : NULL LspToken_ForInLabelBak : 0x0 EntryRefCount : 1 rt_ulVlanId : 0x0 rt_ulVlinkBak : NULL

6.3 Configuration ExamplesThis section provides a configuration example of QPPB.

6.3.1 Example for Configuring QPPB

6.3.1 Example for Configuring QPPB

Networking RequirementAs shown in Figure 6-1, ME60 A and ME60 B are BGP neighbors. ME60 B is the sender ofBGP routes and ME60 A is the receiver of BGP routes.

The BGP routes sent by ME60 B to ME60 A are configured with the group attribute. WhenME60 A receives the BGP routes from ME60 B, it checks whether the community attribute ofthe BGP route matches the community attribute configured on it through the routing policy. Ifthe community attribute matches, ME60 A sets the associated traffic behavior for the BGP route.Then the associated traffic behavior is applied to all the packet traveling through ME60 A andmatching the BGP community attribute.




Issue 05 (2010-06-01)

Figure 6-1 Networking of the QPPB configuration

AS100ME60AME60C

POS1/0/0100.1.1.1/24

POS1/0/0100.1.1.2/24

GE1/0/0200.1.1.1/24

GE1/0/0200.1.1.2/24 AS200

ME60B


1. Configure the basic functions of BGP.2. Configure the routing policy on ME60 B, set the community attribute for the routes to be

sent, and configure BGP to advertise the routing policy.3. Apply the routing policy on ME60 A, check the attribute of the BGP route, and then set

the associated traffic behavior.4. Apply QPPB to the incoming interface of the traffic.


l IP addresses of each interface

l Name of the routing policy, matching rules, and route attributes

l Name and action of the traffic behavior associated

Configuration Procedure1. Configure the basic BGP functions on ME60 A and ME60 B.

# Configure the IP address of the loopback interface of ME60 B.[ME60B] interface loopback 10[ME60B-LoopBack10] ip address 66.1.1.1 255.255.255.255[ME60B-LoopBack10] return

# Configure the IP address of the interface that ME60 A uses to connect ME60 B directlyand configure the IP address of the interface that ME60 A uses to connect ME60 C directly.[ME60A] interface pos 1/0/0[ME60A-Pos1/0/0] ip address 100.1.1.1 255.255.255.0[ME60A-Pos1/0/0] undo shutdown[ME60A-Pos1/0/0] quit[ME60A] interface gigabitethernet 1/0/0[ME60A-GigabitEthernet1/0/0] ip address 200.1.1.2 255.255.255.0[ME60A-GigabitEthernet1/0/0] undo shutdown[ME60A-GigabitEthernet1/0/0] quit

# Configure the IP address of the interface that ME60 B uses to connect ME60 A directly.[ME60B] interface pos 1/0/0[ME60B-Pos1/0/0] ip address 100.1.1.2 255.255.255.0



6-9

[ME60B-Pos1/0/0] undo shutdown[ME60B-Pos1/0/0] quit# Configure the IP address of the interface that ME60 C uses to connect ME60 A directly.[ME60C] interface gigabitethernet 1/0/0[ME60C-GigabitEthernet1/0/0] ip address 200.1.1.1 255.255.255.0[ME60C-GigabitEthernet1/0/0] undo shutdown[ME60C-GigabitEthernet1/0/0] quit# Enable the OSPF protocol on ME60 A and advertise the routes of the interface address.[ME60A] ospf[ME60A-ospf-1] area 0[ME60A-ospf-1-area-0.0.0.0] network 100.1.1.0 0.0.0.255[ME60A-ospf-1-area-0.0.0.0] network 200.1.1.0 0.0.0.255[ME60A-ospf-1-area-0.0.0.0] quit# Enable the OSPF protocol on ME60 B and advertise the routes of the interface address.[ME60B] ospf[ME60B-ospf] area 0[ME60B-ospf-1-area-0.0.0.0] network 100.1.1.0 0.0.0.255[ME60B-ospf-1-area-0.0.0.0] quit[ME60B-ospf-1] quit# Enable the OSPF protocol on ME60 C and advertise the routes of the interface address.[ME60C] ospf[ME60C-ospf] area 0[ME60C-ospf-1-area-0.0.0.0] network 200.1.1.0 0.0.0.255[ME60C-ospf-1-area-0.0.0.0] quit# Configure the BGP protocol on ME60 A and set up the EBGP connection between ME60A and ME60 B.[ME60A] bgp 100[ME60A-bgp] peer 100.1.1.2 as-number 200[ME60A-bgp] import-route direct[ME60A-bgp] quit# Configure the BGP protocol on ME60 B and set up the EBGP connection between ME60A and ME60 B.[ME60B] bgp 200[ME60B-bgp] peer 100.1.1.1 as-number 100[ME60B-bgp] import-route direct[ME60B-bgp] quit# Configure the BGP protocol on ME60 and set up the IBGP connection between ME60A and ME60 C.[ME60A] bgp 100[ME60A-bgp] peer 200.1.1.1 as-number 100[ME60A-bgp] import-route direct[ME60C-bgp] quit# Configure the BGP protocol on ME60 C and set up the IBGP connection between ME60A and ME60 C.[ME60C] bgp 100[ME60C-bgp] peer 200.1.1.2 as-number 100[ME60C-bgp] import-route direct[ME60C-bgp] quitYou can see that ME60 A, ME60 B, and ME60 C are interconnected after the configurationis complete.

2. Configure and apply the routing policy on the route sender ME60 B.# Configure ip-prefix of the route sender.[ME60B] ip ip-prefix bb permit 66.1.1.1 32[ME60B] quit# Configure the routing policy of the route sender.[ME60B] route-policy aa permit node 10




Issue 05 (2010-06-01)

[ME60B-route-policy] if-match ip-prefix bb[ME60B-route-policy] apply community 10:10[ME60B-route-policy] quit

# Advertise the routing policy on the route sender through BGP.[ME60B] bgp 200[ME60B-bgp] peer 100.1.1.1 route-policy aa export[ME60B-bgp] peer 100.1.1.1 advertise-community[ME60B-bgp] quit

3. Configure the route receiving policy for the route receiver ME60 A and apply the associatedtraffic behavior to the traffic that matches the route attribute.

# Configure the QoS policy, namely, the associated traffic behavior.[ME60A] traffic behavior dd[ME60A-behavior-dd] remark ip-precedence 1[ME60A-behavior-dd] quit

# Configure the route receiving policy to apply the associated traffic behavior to the routethat matches the community attribute.[ME60A] ip community-filter 10 permit 10:10[ME60A] route-policy aa permit node 10[ME60A-route-policy] if-match community-filter 10[ME60A-route-policy] apply behavior dd[ME60A-route-policy] quit

# On ME60 A, apply the receiving route policy to the route sent from ME60 B, which isthe peer of ME60 A.[ME60A] bgp 100[ME60A-bgp] peer 100.1.1.2 route-policy aa import[ME60A-bgp] quit

4. Apply QPPB to the incoming interface on ME60 A.

l Configure QPPB on incoming interface POS1/0/0 when the traffic goes from ME60 Bto ME60 C.[ME60A] interface pos 1/0/0[ME60A-Pos1/0/0] qppb-policy behavior source [ME60A-Pos1/0/0] quit

l Configure QPPB on outgoing interface GE1/0/0 when the traffic goes from ME60 C toME60 B, as illustrated by the example here.[ME60A] interface gigabitethernet 1/0/0[ME60A-GigabitEthernet1/0/0] qppb-policy behavior destination[ME60A-GigabitEthernet1/0/0] quit

5. Verify the configuration.

# Display the FIB information ME60 A as follows:[ME60A] display fib verboseFIB Table: Total number of Routes : 1Destination: 66.1.1.1 Mask : 255.255.255.255 Nexthop : 100.1.1.2 OutIf : Pos1/0/0 LocalAddr : 100.1.1.1 LocalMask: 0.0.0.0 Flags : DGU Age : 165sec ATIndex : 0 Slot : 1 LspFwdFlag : 0 LspToken : 0x0 InLabel : NULL OriginAs : 200 BGPNextHop : 2.2.2.2 PeerAs : 200 QosInfo : 0x20000001 OriginQos: 0x0 NexthopBak : 0.0.0.0 OutIfBak : [No Intf] LspTokenBak: 0x0 InLabelBak : NULL LspToken_ForInLabelBak : 0x0 EntryRefCount : 1 rt_ulVlanId : 0x0 rt_ulVlinkBak : NULL



6-11

Configuration Filesl Configuration file of ME60 A

# sysname ME60 A#traffic behavior dd remark ip-precedence 1#interface GigabitEthernet1/0/0 undo shutdown ip address 200.1.1.2 255.255.255.0 qppb-policy behavior destination#interface Pos1/0/0 undo shutdown ip address 100.1.1.1 255.255.255.0 qppb-policy behavior source#bgp 100 peer 100.1.1.2 as-number 200 peer 200.1.1.1 as-number 100#ipv4-family unicast undo synchronization import-route direct peer 100.1.1.2 enable peer 100.1.1.2 route-policy aa import peer 200.1.1.1 enable #ospf 1 area 0.0.0.0 network 100.1.1.0 0.0.0.255 network 200.1.1.0 0.0.0.255#route-policy aa permit node 10 if-match community-filter 10 apply behavior dd# ip community-filter 10 permit 10:10#return

l Configuration file of ME60 B# sysname ME60 B#interface Pos1/0/0 undo shutdown ip address 100.1.1.2 255.255.255.0#interface LoopBack10 ip address 66.1.1.1 255.255.255.255#bgp 200 peer 100.1.1.1 as-number 100 peer 100.1.1.1 connect-interface LoopBack0 # ipv4-family unicast undo synchronizationimport-route direct peer 100.1.1.1 enable peer 100.1.1.1 route-policy aa export peer 100.1.1.1 advertise-community quit#ospf 1 area 0.0.0.0 network 100.1.1.0 0.0.0.255




Issue 05 (2010-06-01)

#route-policy aa permit node 10 if-match ip-prefix bb apply community 10:10# ip ip-prefix bb index 10 permit 66.1.1.1 32#return

l Configuration file of ME60 C# sysname ME60 C#interface gigabitethernet1/0/0 undo shutdown ip address 200.1.1.1 255.255.255.0#bgp 100 peer 200.1.1.2 as-number 100 # ipv4-family unicast undo synchronization import-route direct peer 200.1.1.2 enable#ospf 1 area 0.0.0.0 network 200.1.1.0 0.0.0.255#return



6-13

7 VPN QoS Configuration

About This Chapter

This chapter describes the knowledge about QPPB, including the basic concepts, configurationprocedures and configuration examples.

7.1 IntroductionThis section describes the knowledge about VPN QoS.

7.2 Configuring the Hierarchical Resource Reserved BGP/MPLS IP VPNThis section describes the procedure for configuring the hierarchical resource reserved BGP/MPLS IP VPN.

7.3 Configuring the Hierarchical Resource Reserved L2VPNThis section describes the procedure for configuring the resource reserved L2VPN.

7.4 Configuration ExamplesThis section provides several configuration examples of the resource reserved VPN.

Quidway ME60 Multiservice Control GatewayConfiguration Guide - QoS 7 VPN QoS Configuration


7-1

7.1 IntroductionThis section describes the knowledge about VPN QoS.

7.1.1 VPN QoS Overview

7.1.2 VPN QoS Supported by the ME60

7.1.1 VPN QoS OverviewThe VPN service is developing and becoming a well-established service. Carriers andsubscribers require QoS guarantee in the VPN, which is generally used in physical leased line.The ME60 integrates the features of MPLS, VPN, InterServ, and DiffServ. By using the resourcereserved VPN (RRVPN), the ME60 provides a VPN QoS deployment solution that can beapplied to the entire network.

7.1.2 VPN QoS Supported by the ME60l RRVPN overview

The MPLS TE tunnel provides the QoS-guaranteed VPN service. In VPN application,multiple VPNs may use the same MPLS TE tunnel, and these VPNs have differentrequirements for resources. If packets of different service classes, such as expeditedforwarding (EF), assured forwarding (AF), and best-effort (BE), are transmitted on theMPLS TE tunnel, these services affect each other. In addition, the VPNs compete forresources, which degrades the QoS. If a VPN is attacked, the other VPNs are affected.To solve this problem, you can set up a QoS-guaranteed MPLS TE tunnel between everytwo CE routers. But this method exhausts resources because the backbone network requiresa large number of label switch paths (LSPs).The RRVPN is an effective solution to this problem. The RRVPN differentiates VPN userson the MPLS TE tunnel and services for each VPN user, ensures bandwidth for the VPNusers, and provides end-to-end QoS for VPN users.

l End-to-end VPN QoS solution

l DiffServ modelThe DiffServ model consists of three models: pipe, short pipe, and uniform.– If the pipe model is configured in the VPN, the value of the EXP field in the MPLS

label that the ingress PE added to a packet is determined by the service class and colorspecified by the user. The egress PE strips the MPLS label off the packet withoutchanging the DSCP value of the IP packet, and then determines how to forward thepacket according to the EXP value in the MPLS label.

– If the pipe model is configured in the VPN, the value of the EXP field in the MPLSlabel that the ingress PE added to a packet is determined by the service class and colorspecified by the user. The egress PE strips the MPLS label off the packet withoutchanging the DSCP value of the IP packet, and then determines how to forward thepacket according to the EXP value in the MPLS label.

– If the uniform model is configured in the VPN, the EXP value in the MPLS label thatthe ingress PE added to a packet depends on the mapping between the EXP value andthe DSCP value. The egress PE strips the MPLS label off the packet and maps the EXPvalue to the DSCP value of the IP packet. Then, the egress PE determines how to forward

7 VPN QoS ConfigurationQuidway ME60 Multiservice Control Gateway



Issue 05 (2010-06-01)

the packet according to the DSCP value of the IP packet. By default, the uniform modelis used.

7.2 Configuring the Hierarchical Resource Reserved BGP/MPLS IP VPN

This section describes the procedure for configuring the hierarchical resource reserved BGP/MPLS IP VPN.


7.2.2 (Optional) Configuring the Flow Queue

7.2.3 (Optional) Configuring the DiffServ Model Supported by the BGP/MPLS IP VPN

7.2.4 (Optional) Configuring WRED Parameters

7.2.5 Configuring a Tunnel Policy and Applying It to the VPN Instance

7.2.6 Configuring Bandwidth of the MPLS TE Tunnel

7.2.7 Associating the MPLS TE Tunnel with the VPN Instance and Configuring the QoS Policy



Applicable EnvironmentIn the BGP/MPLS IP VPN application, multiple VPNs may use the same MPLS TE tunnel. Inthis case, the VPNs compete for resources. When VPN packets are forwarded or discarded, thebandwidth of the services in the VPNs cannot be guaranteed according to their priorities, andother types of packets occupy the bandwidth of the VPNs. VPNs using the same MPLS TEtunnel have different requirements for resources. To meet the requirement of each VPN fornetwork resources without affecting the QoS of other VPNs, you need to configure thehierarchical resource reserved BGP/MPLS IP VPN.

Based on the hierarchical resource reserved BGP/MPLS IP VPN, the ME60 reserves differentbandwidth resources for the VPNs that use the same MPLS TE tunnel and services of differentpriorities in each VPN. In this way, services on the MPLS TE tunnel are prevented from affectingeach other and occupying each other's bandwidth. Thus, VPN users are provided end-to-endQoS guarantee.

NOTE

All the hierarchical resource reserved BGP/MPLS IP VPNs are configured on the ingress PE router. Afterthe configuration, you can configure the interface-level HQoS on the user-side interface of the egress PE.Then, the egress PE can perform hierarchical scheduling on the packets sent out from the MPLS network.

In the network, traffic is bidirectional, and you can configure the hierarchical resource reservedBGP/MPLS IP VPN on the peer PE for the packets transmitted in the reverse direction.

Pre-configuration TaskBefore configuring the hierarchical resource reserved BGP/MPLS IP VPN, complete thefollowing tasks:



7-3

l Configuring the physical parameters and link layer attributes of the relevant interface sothat the interfaces can function normally

l Configuring the MPLS TE tunnel between the PE routersFor the configuration procedure, refer to the chapter "MPLS TE Configuration" in theQuidway ME60 Multiservice Control Gateway Configuration Guide - MPLS.

l Configuring BGP/MPLS IP VPNs to implement network internetworkingFor the configuration procedure, refer to the chapter "BGP MPLS IP VPN Configuration"in the Quidway ME60 Multiservice Control Gateway Configuration Guide - VPN.

l Configuring simple or complex traffic classification on the user-side interface of the ingressPEFor the configuration procedure, refer to the chapter "Class-based QoS Configuration" inthe Quidway ME60 Multiservice Control Gateway Configuration Guide - QoS.

NOTE

The task of configuring simple traffic classification is optional.

l If you configure simple traffic classification and the pipe or short pipe model simultaneously on theuser-side interface of the ingress PE, the pipe or short pipe DiffServ model takes effect in the BGP/MPLS IP VPN.

l If the BGP/MPLS IP VPN is configured to support the pipe model, you do not need to configure simpletraffic classification.

l If the BGP/MPLS IP VPN is configured to support short pipe mode, simple traffic classification isrecommended, because the egress PE needs to schedule packets according to the original DSCP valuesof the packets.

Data PreparationTo configure the hierarchical resource reserved BGP/MPLS IP VPN, you need the followingdata.

No. Data

1 (Optional) Parameters of the drop profile, scheduling algorithm used in the queueprofile, and parameters of the scheduling algorithm

2 (Optional) Service class and color of the IP packets in the DiffServ model

3 (Optional) Port-WRED parameters referenced by the port queue, schedulingalgorithm used for the port queue, scheduling parameters, and traffic shaping rate

4 Name and parameters of the tunnel policy

5 Bandwidth of the MPLS TE tunnel and the flow queue profile referenced by the MPLSTE tunnel

6 CIR, PIR, and flow queue profile of the VPN


ContextFlow queues can be applied to VPNs or the MPLS TE tunnel.




Issue 05 (2010-06-01)

l Packets in a VPN are added to corresponding flow queues for the VPN according to theirpriorities after simple or complex traffic classification. The system schedules packets inthe flow queues and assigns bandwidth to each flow queue, and thus the services in theVPN obtain bandwidth matching their priorities.

l Packets on an MPLS TE tunnel are added to corresponding flow queues for the MPLS TEtunnel according to their priorities. The system schedules packets in the queues and assignsbandwidth to each queue, and thus services on the MPLS TE tunnel obtain bandwidthmatching their priorities.

l The VPN and MPLS TE tunnel can use the same flow queues. You can also configure flowqueues for the VPN and MPLS TE tunnel according to the network requirements.

l If you do not configure flow queues for the VPN and MPLS TE tunnels, the system usesthe default flow queue profile. It is recommended that you configure flow queues for theVPN and MPLS TE tunnel according to the network requirements.

Do as follows on the ME60 that functions as the ingress PE.

Procedure




A drop profile is created and the drop profile view is displayed.

Step 3 Run:wred { green | yellow | red } low-limit low-limit-value high-limit high-limit-value discard-percentage discard-percentage-value

The weighted random early detection (WRED) object of the flow queue is configured and thelower drop threshold, upper drop threshold, and drop probability of the packets with the specifiedcolor are set.

Step 4 Run:quit



The flow queue view is displayed.

Step 6 Run:queue-class cos-value

The queue class view is displayed.

Step 7 Run the following commands as required:l Run the pq command to apply priority queue (PQ) scheduling to the flow queue.

l Run the lpq command to apply low PQ scheduling to the flow queue.

l Run the queue weight weight-value command to configure the weight of the flow queueused in the WFQ scheduling algorithm.



7-5

l Run the queue cir { shaping-percentage value | cir [ pir pir ] [ cbs cbs ] [ pbs pbs ] }command to configure bandwidth for the flow queue.

l Run the drop-profile drop-name command to configure the drop profile to the flow queue.

The WRED object must be configured in the drop profile.

NOTE

You can set the scheduling parameters for eight flow queues of a user.If the queue scheduling parameters are not set, the system uses the default queue scheduling parameters.The default queue scheduling parameters are as follows:

l PQ scheduling is used for the queues of EF, CS6, and CS7 classes.

l WFQ scheduling is used for the class queues of the BE, AF1, AF2, AF3, and AF4 classes. Their weightsare 10, 10, 10, 15, and 15 respectively.

l The traffic shaping value is the maximum bandwidth on the interface.

l The packet dropping policy is tail drop.

----End

7.2.3 (Optional) Configuring the DiffServ Model Supported by theBGP/MPLS IP VPN

ContextDo as follows on the ME60 that functions as the ingress PE.

ProcedureStep 1 Run:

system-view


Step 2 Run:ip vpn-instance vpn-instance-name

A VPN instance is created and the VPN instance view is displayed.

Step 3 Run:diffserv-mode { pipe service-class color | short-pipe service-class color | uniform }

The DiffServ model is configured for the VPN instance.

NOTE

l The DiffServ model is optional, and you can configure it according to the network requirements. If theDiffServ model supported by the VPN is not configured, the uniform model is used by default.

l The pipe and short pipe models are not applicable to simple traffic classification. If the pipe or shortpipe model and simple traffic classification are configured simultaneously, the pipe or short pipe modeltakes effect.

l For the procedure for configuring the DiffServ model supported by the MPLS network, refer to thechapter "MPLS TE Configuration" of the Quidway ME60 Multiservice Control GatewayConfiguration Guide - MPLS.

----End




Issue 05 (2010-06-01)


ContextNOTE

To avoid packet loss due to the congestion in the public network, it is recommended that you configure thescheduling policy and bandwidth for the port queue. The reason is that the traffic sent from the networkinterface of the ingress PE consists of the VPN traffic, MPLS TE traffic, and other types of traffic.


Procedure



Step 2 Run:port-wred port-wred-name

A port WRED object is created and the port WRED view is displayed.

Step 3 Run:color { green | yellow | red } low-limit low-limit-value high-limit high-limit-value discard-percentage discard-percentage-value

The weighted random early detection (WRED) object of the class queue is configured and thelower drop threshold, upper drop threshold, and drop probability of the packets with the specifiedcolor are set.

NOTE

l If the WRED object of the class queue is not configured, the system uses the tail drop policy by default.

l You can create multiple port WRED objects that are referenced by the class queues. The systemsupports up to seven port WRED objects and a default port WRED object.

Step 4 Run:quit




Step 6 Run:port-queue cos-value { pq | wfq weight weight-value | lpq } [ shaping { shaping-value | shaping-percentage shaping-percentage-value } | port-wred wred-name ] * outbound

The class queue is configured and the scheduling policies for different queue levels areconfigured.

On an interface, you can configure the scheduling parameters for up to eight port queues.

If the queue profile is not configured, the system uses the default queue profile. The configurationof the default queue profile is as follows:



7-7

l PQ scheduling is used for the class queues of the EF, CS6, and CS7 classes.

l WFQ scheduling is used for the flow queues of the BE, AF1, AF2, AF3, and AF4 classes.Their weights are 10, 10, 10, 15, and 15 respectively.


The packet dropping policy is tail drop.

----End

7.2.5 Configuring a Tunnel Policy and Applying It to the VPNInstance


Procedure



Step 2 Run:tunnel-policy policy-name

A tunnel policy is created and the tunnel policy view is displayed.

Step 3 Run:tunnel select-seq { cr-lsp | lsp } * load-balance-number number

The MPLS TE tunnel is specified for the BGP/MPLS IP VPN.

NOTE

load-balance-number: specifies the number of tunnels functioning in load balancing mode. The value ofthis parameter is determined by the license. The value ranges from 1 to 6. When the default license is used,the value is 1.

If the tunnel policy is not configured, the LSP is used as the tunnel for the VPN and load balancing is notimplemented.

Step 4 Run:quit


Step 5 Run:ip vpn-instance vpn-instance-name

The VPN instance view is displayed.

Step 6 Run:tnl-policy policy-name

The tunnel policy is applied to the VPN instance.

----End




Issue 05 (2010-06-01)



Procedure



Step 2 Run:interface tunnel tunnel-number

The MPLS TE tunnel interface view is displayed.

Step 3 Run:tunnel-protocol { gre | mpls te | ipv6-ipv4 [ 6to4 | auto-tunnel | isatap ] | none }

The encapsulation mode of the tunnel is set.

The encapsulation mode of the tunnel must be set to MPLS TE; otherwise, the commands of theMPLS TE tunnel cannot be displayed.

Step 4 Run:mpls te bandwidth bandwidth [ flow-queue flow-queue-name ]

The total bandwidth of the MPLS TE tunnel and proportions of the bandwidth for variousservices on the tunnel are configured.

NOTE

The mpls te bandwidth command configures the bandwidth and flow queue profile of the MPLS TEtunnel. By using the flow queue profile, you can specify the proportions of bandwidth for services ofdifferent priorities on the MPLS TE tunnel. By using the flow queue profile, you can specify the proportionsof the bandwidth for services of different priorities on the MPLS TE tunnel.

When the configured bandwidth of the MPLS TE tunnel is greater than 28630 kbit/s, bandwidth may notbe allocated accurately on the MPLS TE tunnel. The MPLS TE tunnel, however, can still be established.

----End

7.2.7 Associating the MPLS TE Tunnel with the VPN Instance andConfiguring the QoS Policy


Procedure




7-9


Step 2 Run:interface tunnel interface-number


Step 3 Run:mpls te reserved-for-binding

The VPN binding feature is enabled on the tunnel.

A tunnel can be used by the VPN only after it is enabled with the VPN binding feature.

Step 4 Run:mpls te vpn-binding vpn-instance vpn-name cir cir pir pir [ flow-queue flow-queue-name ]

The BGP/MPLS IP VPN is bound to the MPLS TE tunnel statically, and the bandwidth of theVPN and service traffic in the VPN is configured.

The CIR parameter limits the committed information rate, namely, the guaranteed bandwidth ofthe VPN. The PIR parameter in the command limits the peak rate, namely, the burst bandwidthof the VPN. Generally, the PIR is set to the guaranteed bandwidth for all the VPN packets onthe MPLS TE tunnel. The PIR cannot exceed the total bandwidth of the MPLS TE tunnel. Theflow queue profile specifies the bandwidth proportions and scheduling parameters of servicesof different priorities.

Step 5 Run:mpls te commit

The configuration of the MPLS TE tunnel is submitted.

NOTE

When the parameters of the MPLS TE tunnel are changed, run the mpls te commit command to make thenew parameters take effect.By ensuring the bandwidth of the MPLS TE tunnel and the bandwidth of all the VPN packets, you can alsoensure the bandwidth of other types of packets.

----End


Action Command

Check the information about thehierarchical resource reserved BGP/MPLS IP VPN on the MPLS TEtunnel.

display mpls te rrvpn-tunnel Tunnel interface-number

By running the display mpls te rrvpn-tunnel Tunnel interface-number command, you canview information about the hierarchical resource reserved BGP/MPLS IP VPN on the MPLSTE tunnel.

<Quidway> display mpls te rrvpn-tunnel Tunnel 1/0/1




Issue 05 (2010-06-01)

Tunnel Name Interface Id Status Bandwidth L3RRVPN VLLRRVPN VPLSRRVPNTunnel1/0/1 0x1c001685 up 10000 1 0 0--------------------------------------------------------------------- *********L3RRVPN********* Vpn Instance :vpna Vpn Type :L3RRVPN Sub Tunnel Id :0x61c2100d Qos Token :0x61c2100e Backup QosToken :- Qos Policy :- Policy Value :- Cir Bandwidth :100 Pir Bandwidth :200 Status :up

7.3 Configuring the Hierarchical Resource Reserved L2VPNThis section describes the procedure for configuring the resource reserved L2VPN.



7.3.3 (Optional) Configuring the DiffServ Model Supported by the L2VPN


7.3.5 Configuring the Tunnel Policy

7.3.6 Applying the MPLS TE Tunnel Policy to the L2VPN


7.3.8 Associating the MPLS TE Tunnel with the L2VPN and Configuring the QoS Policy



Applicable EnvironmentIn the L2VPN application, multiple VPNs may use the same MPLS TE tunnel. In this case, theVPNs compete for resources. When VPN packets are forwarded or discarded, the bandwidth ofthe services in the VPNs cannot be guaranteed according to their priorities, and other types ofpackets occupy the bandwidth of the VPNs. VPNs using the same MPLS TE tunnel have differentrequirements for resources. To meet the requirement of each VPN for network resources withoutaffecting the QoS of other VPNs, you need to configure the hierarchical resource reservedL2VPN.

Based on the hierarchical resource reserved L2VPN, the ME60 reserves different bandwidthresources for the VPNs that use the same MPLS TE tunnel and services of different prioritiesin each VPN. In this way, services on the MPLS TE tunnel are prevented from affecting eachother or occupying each other's bandwidth. Thus, VPN users are provided end-to-end QoSguarantee.

The hierarchical resource reserved L2VPN supports two networking modes: virtual leased line(VLL) and virtual private LAN segment (VPLS).



7-11

NOTE

All the resource reserved L2VPNs are configured on the ingress PE router. After the configuration, youcan configure the interface-level HQoS on the user-side interface of the egress PE. Then, the egress PEcan perform hierarchical scheduling on the packets sent out from the MPLS network.

In the network, traffic is bidirectional, and you can configure the hierarchical resource reservedL2VPN on the peer PE for the VPN data transmitted in the reverse direction.

Pre-configuration TaskBefore configuring the hierarchical resource reserved L2VPN, complete the following tasks:

l Configuring the physical parameters and link layer attributes of the relevant interface sothat the interfaces can function normally

l Configuring the MPLS TE tunnel between the PE routersFor the configuration procedure, refer to the chapter "MPLS TE Configuration" in theQuidway ME60 Multiservice Control Gateway Configuration Guide - MPLS.

l Configuring the MPLS L2VPN to implement interworking in the L2VPNFor the configuration procedure, refer to the chapter "VLL Configuration" in the QuidwayME60 Multiservice Control Gateway Configuration Guide - VPN.

l Configuring simple, forced, or complex traffic classification on the user-side interface ofthe ingress PEFor the configuration procedure, refer to the chapter "Class-based QoS Configuration" inthe Quidway ME60 Multiservice Control Gateway Configuration Guide - QoS.

NOTE

The task of configuring simple or forced traffic classification is optional.

l If you configure simple traffic classification and the pipe or short pipe model simultaneously on theuser-side interface of the ingress PE, the pipe or short pipe DiffServ model takes effect in the L2VPN.

l If the L2VPN is configured to support the pipe model, you do not need to configure simple trafficclassification.

l If the L2VPN is configured to support the short pipe model, simple traffic classification isrecommended, because the egress PE needs to schedule packets according to the original DSCP valuesof the packets.

Data PreparationTo configure the hierarchical resource reserved L2VPN, you need the following data.

No. Data

1 (Optional) Parameters of the drop profile, scheduling algorithm used in the queueprofile, and parameters of the scheduling algorithm

2 (Optional) Service class and color of the IP packets in the DiffServ model

3 (Optional) Port-WRED parameters referenced by the port queue, schedulingalgorithm used for the port queue, scheduling parameters, and traffic shaping rate

4 Name and parameters of the tunnel policy

5 Bandwidth of the MPLS TE tunnel and the flow queue profile referenced by the MPLSTE tunnel




Issue 05 (2010-06-01)

No. Data

6 CIR, PIR, and flow queue profile of the VPN



Procedure




A drop profile is created and the drop profile view is displayed.

Step 3 Run:wred { green | yellow | red } low-limit low-limit-value high-limit high-limit-value discard-percentage discard-percentage-value

The weighted random early detection (WRED) object of the flow queue is configured and thelower drop threshold, upper drop threshold, and drop probability of the packets with the specifiedcolor are set.

Step 4 Run:quit



The flow queue view is displayed.

Step 6 Run:queue-class cos-value

The queue class view is displayed.

Step 7 Run the following commands as required:l Run the pq command to apply PQ scheduling to the flow queue.

l Run the lpq to apply LPQ scheduling to the flow queue.

l Run the queue weight weight-value command to configure the weight of the flow queueused in the WFQ scheduling algorithm.

l Run the queue cir { shaping-percentage value | cir [ pir pir ] [ cbs cbs ] [ pbs pbs ] }command to configure bandwidth for the flow queue.



7-13

l Run the drop-profile drop-name command to configure the drop profile to the flow queue.

The WRED object must be configured in the drop profile.

NOTE

You can set the scheduling parameters for eight flow queues of a user.

If the queue scheduling parameters are not set, the system uses the default queue scheduling parameters.The default queue scheduling parameters are as follows:

l PQ scheduling is used for the queues of EF, CS6, and CS7 classes.

l WFQ scheduling is used for the class queues of the BE, AF1, AF2, AF3, and AF4 classes. Their weightsare 10, 10, 10, 15, and 15 respectively.


l The packet dropping policy is tail drop.

----End

7.3.3 (Optional) Configuring the DiffServ Model Supported by theL2VPN

Procedurel VLL networking mode

1. Do as follows on the AC-side interface of the ME60 that functions as the ingress PErouter. Run:system-view



The user-side interface view is displayed.

3. Run:diffserv-mode { pipe service-class color | uniform }

The DiffServ model is configured for the VLL.

l VPLS networking mode

1. Do as follows on the ME60 that functions as the ingress PE. Run:system-view


2. Run:vsi vsi-name [ auto | static ]

A virtual switch instance (VSI) is created and the VSI view is displayed.

3. Run:diffserv-mode { pipe service-class color | short-pipe service-class color | uniform }

The DiffServ model is configured for the VSI.




Issue 05 (2010-06-01)

NOTE

The configuration of DiffServ model supported by the L2VPN is optional, and you canconfigure it according to the network requirements. If the DiffServ model supported by theVPN is not configured, the uniform model is used by default.

The pipe and short pipe models are not applicable to simple and forced traffic classification.If the pipe or short pipe model and simple or forced traffic classification are configuredsimultaneously, the pipe or short pipe model takes effect.

----End


ContextNOTE

To avoid packet loss due to the congestion in the public network, it is recommended that you configure thescheduling and the bandwidth for the class queue. The reason is that the traffic sent from the networkinterface of the ingress PE consists of the VPN traffic, MPLS TE traffic, and other types of traffic.


Procedure



Step 2 Run:port-wred port-wred-name

A port WRED object is created and the port WRED view is displayed.

Step 3 Run:color { green | yellow | red | user-defined-threshold } low-limit low-limit-value high-limit high-limit-value discard-percentage discard-percentage-value

The weighted random early detection (WRED) object of the class queue is configured and thelower drop threshold, upper drop threshold, and drop probability of the packets with the specifiedcolor are set.

NOTE

If the WRED object of the class queue is not configured, the system uses the tail drop policy by default.

You can create multiple port WRED objects that are referenced by the class queues. The system supportsup to seven port WRED objects and a default port WRED object.

Step 4 Run:quit






7-15

Step 6 Run:port-queue cos-value { pq | wfq weight weight-value | lpq } [ shaping { shaping-value | shaping-percentage shaping-percentage-value } | port-wred wred-name ] * outbound

The class queue is configured and the scheduling policies for different queue levels areconfigured.

On an interface, you can configure the scheduling parameters for up to eight port queues.

If the queue profile is not configured, the system uses the default queue profile. The configurationof the default queue profile is as follows:

l PQ scheduling is used for the class queues of the EF, CS6, and CS7 classes.

l WFQ scheduling is used for the flow queues of the BE, AF1, AF2, AF3, and AF4 classes.Their weights are 10, 10, 10, 15, and 15 respectively.


The packet dropping policy is tail drop.

----End

7.3.5 Configuring the Tunnel Policy

Context

Do as follows on the ingress PE configured with the resource reserved L2VPN.

Procedure



Step 2 Run:tunnel-policy policy-name

A tunnel policy is created and the tunnel policy view is displayed.

Step 3 Run:tunnel select-seq { cr-lsp | lsp } * load-balance-number number

The MPLS TE tunnel is specified for the L2VPN.

NOTE

load-balance-number: specifies the number of tunnels functioning in load balancing mode. The value ofthis parameter is determined by the license. The value ranges from 1 to 6. When the default license is used,the value is 1.

----End

7.3.6 Applying the MPLS TE Tunnel Policy to the L2VPN




Issue 05 (2010-06-01)





The user-side interface view is displayed.3. Run:

mpls l2vc dest-ip-address vc-id tunnel-policy policy-name

The tunnel policy is applied to the virtual circuit (VC) of the Martini L2VPN.l VPLS networking mode



vsi vsi-name

The VSI view is displayed.3. Run:

tnl-policy policy-name

The tunnel policy is applied to the VSI.

----End



Procedure



Step 2 Run:interface tunnel tunnel-number


Step 3 Run:tunnel-protocol { gre | ipv6-ipv4 [ 6to4 | auto-tunnel | isatap ] | ipv4-ipv6 | mpls te | none }

The encapsulation mode of the tunnel is set.



7-17

The encapsulation mode of the tunnel must be set to MPLS TE; otherwise, the commands of theMPLS TE tunnel cannot be displayed.

Step 4 Run:mpls te bandwidth bandwidth [ flow-queue flow-queue-name ]

The total bandwidth of the MPLS TE tunnel and proportions of the bandwidth for variousservices on the tunnel are configured.

NOTE

The mpls te bandwidth command configures the bandwidth and flow queue profile of the MPLS TEtunnel. By using the flow queue profile, you can specify the proportions of bandwidth for services ofdifferent priorities on the MPLS TE tunnel. By using the flow queue profile, you can specify the proportionsof the bandwidth for services of different priorities on the MPLS TE tunnel.

When the configured bandwidth of the MPLS TE tunnel is greater than 28630 kbit/s, bandwidth may notbe allocated accurately on the MPLS TE tunnel. The MPLS TE tunnel, however, can still be established.

----End

7.3.8 Associating the MPLS TE Tunnel with the L2VPN andConfiguring the QoS Policy




interface tunnel interface-number

The MPLS TE tunnel interface view is displayed.3. Run:

mpls te reserved-for-binding

The VPN binding feature is enabled on the tunnel.

A tunnel can be used by the VPN only after it is enabled with the VPN binding feature.4. Run:

mpls te vpn-binding l2vpn interface interface-type interface-number cir cir pir pir [ flow-queue flow-queue-name ]

The VLL is bound to the MPLS TE tunnel, and the bandwidth for forwarding VPNpackets on the MPLS TE tunnel and the bandwidth of each type of traffic in the VPNare configured.

NOTE

The interface at the attachment circuit (AC) side of the VLL is bound to the tunnel statically,and thus VLL traffic can be forwarded on the MPLS TE tunnel.

5. Run:mpls te commit





Issue 05 (2010-06-01)

NOTE

When the parameters of the MPLS TE tunnel are changed, run the mpls te commit commandto make the new parameters take effect.

l MPLS networking mode1. Do as follows on the ME60 that functions as the ingress PE router. Run:

system-view


interface tunnel interface-number

The MPLS TE tunnel interface view is displayed.3. Run:

mpls te vpn-binding l2vpn vsi vsi-name cir cir pir pir [ flow-queue flow-queue-name ]

The VLL is bound to the MPLS TE tunnel, and the bandwidth for forwarding VPNpackets on the MPLS TE tunnel and the bandwidth of each type of traffic in the VPNare configured.

In the VLL and VPLS networking modes, the CIR parameter in the command thatbinds the L2VPN to the MPLS TE tunnel limits the committed information rate of theVPN, namely, the guaranteed bandwidth of the VPN. The PIR parameter in thecommand limits the peak rate, namely, the burst bandwidth of the VPN. Generally,the PIR is set to the guaranteed bandwidth for all the VPN packets on the MPLS TEtunnel. The PIR cannot exceed the total bandwidth of the MPLS TE tunnel. The flowqueue profile specifies the bandwidth proportions and scheduling parameters ofservices of different priorities.

By ensuring the bandwidth of the MPLS TE tunnel and the bandwidth of all the VPNpackets, you can also ensure the bandwidth of other types of packets.

4. Run:mpls te commit


NOTE

When the parameters of the MPLS TE tunnel are changed, run the mpls te commit commandto make the new parameters take effect.

----End


Action Command

Check the information about thehierarchical resource reserved BGP/MPLS IP VPN on the MPLS TEtunnel.

display mpls te rrvpn-tunnel Tunnel interface-number



7-19

By running the display mpls te rrvpn-tunnel Tunnel interface-number command, you canview information about the hierarchical resource reserved L2VPN on the MPLS TE tunnel.

<Quidway> display mpls te rrvpn-tunnel Tunnel 1/0/1Tunnel Name Interface Id Status Bandwidth L3RRVPN VLLRRVPN VPLSRRVPNTunnel1/0/1 0x1c001685 up 10000 0 1 1--------------------------------------------------------------------- *********VLL RRVPN********* Vpn Instance :GigabitEthernet1/0/0.1 Vpn Type :L2RRVPN VLL Sub Tunnel Id :0x61c21017 Qos Token :0x61c21019 Backup QosToken :- Qos Policy :- Policy Value :- Cir Bandwidth :100 Pir Bandwidth :200 Status :up *********VPLS RRVPN********* Vpn Instance :vsia Vpn Type :L2RRVPN VPLS Sub Tunnel Id :0x61c21018 Qos Token :0x61c2101a Backup QosToken :- Qos Policy :- Policy Value :- Cir Bandwidth :100 Pir Bandwidth :200 Status :up

7.4 Configuration ExamplesThis section provides several configuration examples of the resource reserved VPN.

7.4.1 Example for Configuring the Resource Reserved BGP/MPLS IP VPN

7.4.2 Example for Configuring the Resource Reserved VLL

7.4.3 Example for Configuring the Resource Reserved VPLS

7.4.1 Example for Configuring the Resource Reserved BGP/MPLSIP VPN

Networking RequirementAs shown in Figure 7-1, the ME60 functions as the PE of the MPLS backbone. CE1 and CE2belong to VPNA, and CE3 and CE4 belongs to VPNB. VPNA and VPNB share the MPLS TEtunnel between the edge routers of the public network, namely, PE1 and PE2. Bandwidth shouldbe reserved for VPNA, VPNB, and services in the VPNs respectively. In addition, the VPNsand services do not occupy each other's bandwidth.

The MPLS backbone uses the OSPF protocol as the IGP protocol. VPNA and VPNB areconfigured with the BGP/MPLS IP VPN function.

The networking requirements are as follows:




Issue 05 (2010-06-01)

l Establish an MPLS TE tunnel between PE1 and PE2 through RSVP-TE to transmit packetsof the BGP/MPLS IP VPN. The bandwidth of the MPLS TE tunnel is 80 Mbit/s. Themaximum bandwidth of the links along the tunnel is 200 Mbit/s, and the maximum reservedbandwidth is 100 Mbit/s.

l On the MPLS TE tunnel, 50 Mbit/s bandwidth is reserved for VPNA. In VPNA, the VoIPservice packets are forwarded as the EF class and have 15 Mbit/s guaranteed bandwidth.The video service packets are forwarded as the AF4 class and have 10 Mbit/s guaranteedbandwidth. Packets of important data services are forwarded as the AF3 class and have 5Mbit/s guaranteed bandwidth.

l On the MPLS TE tunnel, 30 Mbit/s bandwidth is reserved for VPNB. In VPNB, the voiceservice of the EF class has 10 Mbit/s guaranteed bandwidth. Other data services occupythe remaining bandwidth of VPNB according to the default configuration of the system.

l VPNA uses the uniform DiffServ model on the MPLS TE tunnel. The egress router of theMPLS backbone maps the EXP values to the DSCP values, and then schedules the packetsaccording to the DSCP values. VPNB uses the short pipe DiffServ model on the MPLS TEtunnel. The egress router of the MPLS backbone schedules the packets according to theDSCP values of the packets.

Figure 7-1 Networking of the resource reserved BGP/MPLS IP VPN

VPNB

PE1 PE2

CE1 CE2

Backbone

Loopback12.2.2.9/32

Loopback11.1.1.9/32

GE2/0/010.1.1.2/24

POS1/0/0200.1.1.2/24

POS1/0/0100.1.1.1/24

GE1/0/010.1.1.1/24

GE1/0/010.2.1.1/24

GE2/0/010.2.1.2/24

VPNA

VPNB

VPNA

GE3/0/010.4.1.2/24

GE3/0/010.3.1.2/24

GE1/0/010.3.1.1/24

CE3 CE4GE1/0/010.4.1.1/24

Loopback13.3.3.9/32

POS1/0/0100.1.1.2/24

POS2/0/0200.1.1.1/24

BGP100

BGP300

BGP200

BGP400BGP500

P



1. Configure IP addresses and routes of the interfaces to implement interworking of thenetwork layer.

2. Configure the MPLS TE tunnel between the PE routers. Create a tunnel interface on PE1.The MPLS TE tunnel is unidirectional, so you need to create only one tunnel interface.

3. Configure the BGP/MPLS IP VPN.



7-21

4. Configure simple traffic classification and configure the equipment to trust the DSCP valueof the upstream packets.

5. Configure VPNA to use the uniform DiffServ model and VPNB to use the short pipeDiffServ model on the MPLS TE tunnel.

6. Configure the resource reservation function and guaranteed bandwidth in VPNA andVPNB.

NOTE

In this example, the resource reservation function is applied to only the VPN data from PE1 to PE2. In thenetwork, traffic is bidirectional, and you can configure the resource reserved BGP/MPLS IP VPN on thepeer PE for the packets transmitted in the reverse direction.


l IP addresses of all the interfaces

l MPLS LSR IDs of the PE and P routers, maximum bandwidth, and maximum reservedbandwidth of the physical link along the MPLS TE tunnel

l Tunnel interface, tunnel encapsulation mode (MPLS TE), tunnel ID, and signaling protocolof the tunnel, namely, Resource Reservation Protocol (RSVP)

l Name of the VPN instance and the VPN target

l Service classes and colors of the packets from VPNA and VPNB, which are used for labelmapping on the ingress of the MPLS TE tunnel

l Guaranteed bandwidth and scheduling parameters of VPNA, VPNB, and flow queues onthe MPLS TE tunnel

l Bandwidth limits of VPNA, VPNB, and MPLS TE tunnel

Configuration Procedure1. Configure IP addresses of the interfaces in the MPLS backbone and the IGP protocol

(OSPF) to implement interworking between PE1, P, and PE2.# Configure PE1.<PE1> system-view[PE1] interface loopback 1[PE1-LoopBack1] ip address 1.1.1.9 32[PE1-LoopBack1] quit[PE1] interface pos 1/0/0[PE1-POS1/0/0] undo shutdown[PE1-POS1/0/0] ip address 100.1.1.1 24[PE1-POS1/0/0] quit[PE1] ospf[PE1-ospf-1] area 0[PE1-ospf-1-area-0.0.0.0] network 100.1.1.0 0.0.0.255[PE1-ospf-1-area-0.0.0.0] network 1.1.1.9 0.0.0.0[PE1-ospf-1-area-0.0.0.0] quit# Configure P.<P> system-view[P] interface loopback 1[P-LoopBack1] ip address 3.3.3.9 32[P-LoopBack1] quit[P] interface pos 1/0/0[P-POS1/0/0] undo shutdown[P-POS1/0/0] ip address 100.1.1.2 24[P-POS1/0/0] quit




Issue 05 (2010-06-01)

[P] interface pos 2/0/0[P-POS2/0/0] undo shutdown[P-POS2/0/0] ip address 200.1.1.1 24[P-POS2/0/0] quit[P] ospf[P-ospf-1] area 0[P-ospf-1-area-0.0.0.0] network 100.1.1.0 0.0.0.255[P-ospf-1-area-0.0.0.0] network 200.1.1.0 0.0.0.255[P-ospf-1-area-0.0.0.0] network 3.3.3.9 0.0.0.0[P-ospf-1-area-0.0.0.0] quit

# Configure PE2.<PE2> system-view[PE2] interface loopback 1[PE2-LoopBack1] ip address 2.2.2.9 32[PE2-LoopBack1] quit[PE2] interface pos 1/0/0[PE2-POS1/0/0] undo shutdown[PE2-POS1/0/0] ip address 200.1.1.2 24[PE2-POS1/0/0] quit[PE2] ospf[PE2-ospf-1] area 0[PE2-ospf-1-area-0.0.0.0] network 200.1.1.0 0.0.0.255[PE2-ospf-1-area-0.0.0.0] network 2.2.2.9 0.0.0.0[PE2-ospf-1-area-0.0.0.0] quit

After the configuration, OSPF adjacencies are established between PE1, P, and PE2. Byrunning the display ospf peer command, you can see that the status of the OSPF adjacencyis Full. By running the display ip routing-table command, you can see that the PE routerscan learn the routes of each other's Loopback1 interface.Take the display on PE1 for example.[PE1] display ip routing-tableRoute Flags: R - relied, D - download to fib------------------------------------------------------------------------------Routing Tables: Public Destinations : 9 Routes : 9 Destination/Mask Proto Pre Cost Flags NextHop Interface 1.1.1.9/32 Direct 0 0 D 127.0.0.1 InLoopBack1 2.2.2.9/32 OSPF 10 2 D 100.1.1.2 POS1/0/0 3.3.3.9/32 OSPF 10 3 D 100.1.1.2 POS1/0/0 100.1.1.0/24 Direct 0 0 D 100.1.1.1 POS1/0/0 100.1.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack1 100.1.1.2/32 Direct 0 0 D 100.1.1.2 POS1/0/0 200.1.1.0/24 OSPF 10 2 D 100.1.1.2 POS1/0/0[PE1] display ospf peer OSPF Process 1 with Router ID 1.1.1.9 Neighbors Area 0.0.0.0 interface 100.1.1.1(POS1/0/0)'s neighbors Router ID: 3.3.3.9 Address: 100.1.1.2 GR State: Normal State: Full Mode:Nbr is Master Priority: 1 DR: None BDR: None MTU: 1500 Dead timer due in 38 sec Neighbor is up for 00:02:44 Authentication Sequence: [ 0 ]

2. Configure the MPLS TE tunnel.# Enable the basic MPLS capability on the MPLS backbone and establish an LDP LSP.l Configure PE1.

<PE1> system-view[PE1] mpls lsr-id 1.1.1.9[PE1] mpls[PE1-mpls] quit[PE1] mpls ldp[PE1-mpls-ldp] quit[PE1] interface pos 1/0/0



7-23

[PE1-POS1/0/0] mpls[PE1-POS1/0/0] mpls ldp[PE1-POS1/0/0] quit

l Configure P.<P> system-view[P] mpls lsr-id 3.3.3.9[P] mpls[P-mpls] quit[P] mpls ldp[P-mpls-ldp] quit[P] interface pos 1/0/0[P-POS1/0/0] mpls[P-POS1/0/0] mpls ldp[P-POS1/0/0] quit[P] interface pos 2/0/0[P-POS2/0/0] mpls[P-POS2/0/0] mpls ldp[P-POS2/0/0] quit

l Configure PE2.<PE2> system-view[PE2] mpls lsr-id 2.2.2.9[PE2] mpls[PE2-mpls] quit[PE2] mpls ldp[PE2-mpls-ldp] quit[PE2] interface pos 1/0/0[PE2-POS1/0/0] mpls[PE2-POS1/0/0] mpls ldp[PE2-POS1/0/0] quit

# Set up the peer session between PE1 and PE2.

l Configure PE1.<PE1> system-view[PE1] mpls ldp[PE1-mpls-ldp] quit[PE1] mpls ldp remote-peer 2.2.2.9[PE1-mpls-ldp-remote-2.2.2.9] remote-ip 2.2.2.9[PE1-mpls-ldp-remote-2.2.2.9] quit

l Configure PE2.<PE2> system-view[PE2] mpls ldp[PE2-mpls-ldp] quit[PE2] mpls ldp remote-peer 1.1.1.9[PE2-mpls-ldp-remote-1.1.1.9] remote-ip 1.1.1.9[PE2-mpls-ldp-remote-1.1.1.9] quit

After the configuration, LDP sessions are established between PE1 and P, and betweenP and PE2. By running the display mpls ldp session command, you can see that thestatus of the LSP sessions is Operational. By running the display mpls ldp lspcommand, you can see the establishment status of the LDP LSP.

Take the display on PE1 for example.[PE1] display mpls ldp session LDP Session(s) in Public Network ------------------------------------------------------------------------------ Peer-ID Status LAM SsnRole SsnAge KA-Sent/Rcv ------------------------------------------------------------------------------ 2.2.2.9:0 Operational DU Passive 000:00:22 89/89 3.3.3.9:0 Operational DU Passive 000:00:24 98/98




Issue 05 (2010-06-01)

------------------------------------------------------------------------------ TOTAL: 2 session(s) Found. LAM : Label Advertisement Mode SsnAge Unit : DDD:HH:MM [PE1] display mpls ldp lsp LDP LSP Information ------------------------------------------------------------------ SN DestAddress/Mask In/OutLabel Next-Hop In/Out-Interface ------------------------------------------------------------------ 1 1.1.1.9/32 3/NULL 127.0.0.1 POS1/0/0/InLoop12 2.2.2.9/32 NULL/1027 100.1.1.2 -------/POS1/0/0 3 3.3.3.9/32 NULL/3 100.1.1.2 -------/POS1/0/0------------------------------------------------------------------ TOTAL: 4 Normal LSP(s) Found. TOTAL: 0 Liberal LSP(s) Found. A '*' before an LSP means the LSP is not established A '*' before a Label means the USCB or DSCB is stale

# Enable MPLS TE, RSVP-TE, Constraint Shortest Path First (CSPF), and OSPF TE.l Configure PE1.

[PE1] mpls[PE1-mpls] mpls te[PE1-mpls] mpls rsvp-te[PE1-mpls] mpls te cspf[PE1-mpls] quit[PE1] interface pos1/0/0[PE1-POS1/0/0] mpls te[PE1-POS1/0/0] mpls rsvp-te[PE1-POS1/0/0] quit[PE1] ospf[PE1-ospf-1] opaque-capability enable[PE1-ospf-1] area 0[PE1-ospf-1-area-0.0.0.0] mpls-te enable[PE1-ospf-1-area-0.0.0.0] quit[PE1-ospf-1] quit

l Configure P.[P] mpls[P-mpls] mpls te[P-mpls] mpls rsvp-te[P-mpls] mpls te cspf[P-mpls] quit[P] interface pos1/0/0[P-POS1/0/0] mpls te[P-POS1/0/0] mpls rsvp-te[P-POS1/0/0] quit[P] interface pos2/0/0[P-POS2/0/0] mpls te[P-POS2/0/0] mpls rsvp-te[P-POS2/0/0] quit[P] ospf[P-ospf-1] opaque-capability enable[P-ospf-1] area 0[P-ospf-1-area-0.0.0.0] mpls-te enable[P-ospf-1-area-0.0.0.0] quit[P-ospf-1] quit

l Configure PE2.[PE2] mpls[PE2-mpls] mpls te[PE2-mpls] mpls rsvp-te[PE2-mpls] mpls te cspf[PE2-mpls] quit[PE2] interface pos1/0/0[PE2-POS1/0/0] mpls te[PE2-POS1/0/0] mpls rsvp-te[PE2-POS1/0/0] quit[PE2] ospf



7-25

[PE2-ospf-1] opaque-capability enable[PE2-ospf-1] area 0[PE2-ospf-1-area-0.0.0.0] mpls-te enable[PE2-ospf-1-area-0.0.0.0] quit[PE2-ospf-1] quit # Configure the maximum bandwidth and maximum reserved bandwidth of the physicallink along the MPLS TE tunnel.

NOTE

To configure the MPLS TE tunnel, you need to configure the maximum bandwidth and maximumreserved bandwidth of the physical link and bandwidth of the MPLS TE tunnel.The maximum reserved bandwidth of the physical link cannot exceed the maximum bandwidth.Bandwidth of the MPLS TE tunnel cannot exceed the maximum reserved bandwidth of thephysical link.

– Configure PE1.[PE1] interface pos 1/0/0[PE1-POS1/0/0] mpls te max-link-bandwidth 200000[PE1-POS1/0/0] mpls te max-reservable-bandwidth 100000[PE1-POS1/0/0] quit

l Configure P.[P] interface pos 1/0/0[P-POS1/0/0] mpls te max-link-bandwidth 200000[P-POS1/0/0] mpls te max-reservable-bandwidth 100000[P-POS1/0/0] quit[P] interface pos 2/0/0[P-POS2/0/0] mpls te max-link-bandwidth 200000[P-POS2/0/0] mpls te max-reservable-bandwidth 100000[P-POS2/0/0] quit

l Configure PE2.[PE2] interface pos 1/0/0[PE2-POS1/0/0] mpls te max-link-bandwidth 200000[PE2-POS1/0/0] mpls te max-reservable-bandwidth 100000[PE2-POS1/0/0] quit

# Configure the MPLS TE tunnel on PE1.[PE1] interface tunnel 1/0/0[PE1-Tunnel1/0/0] ip address unnumbered interface loopback 1[PE1-Tunnel1/0/0] tunnel-protocol mpls te[PE1-Tunnel1/0/0] destination 2.2.2.9[PE1-Tunnel1/0/0] mpls te tunnel-id 100[PE1-Tunnel1/0/0] mpls te signal-protocol rsvp-te[PE1-Tunnel1/0/0] mpls te commit[PE1-Tunnel1/0/0] quit

NOTE

In this example, only the TE tunnel from PE1 to PE2 is configured. To configure a bidirectionalMPLS TE tunnel, you need to configure the MPLS TE tunnel on PE2.

By running the display interface tunnel command on PE1, you can see that the status ofthe tunnel interface is Up.[PE1] display interface TunnelTunnel1/0/0 current state : UPLine protocol current state : UPLast up time: 2008-06-19, 03:04:51Description:HUAWEI, Quidway Series, Tunnel1/0/0 InterfaceRoute Port,The Maximum Transmit Unit is 1500Internet Address is unnumbered, using address of LoopBack0(1.1.1.9/32)Encapsulation is TUNNEL, loopback not setTunnel destination 2.2.2.9Tunnel up/down statistics 1Tunnel protocol/transport MPLS/MPLS, ILM is available,primary tunnel id is 0x1408003, secondary tunnel id is 0x0 300 seconds output rate 0 bits/sec, 0 packets/sec




Issue 05 (2010-06-01)

0 packets output, 0 bytes 0 output errorBy running the display mpls te cspf tedb all command on PE1, you can view the linkinformation in the TEDB.[PE1] display mpls te cspf tedb allMaximum Node Supported: 2048 Maximum Link Supported: 8192Current Total Node Number: 3 Current Total Link Number: 4ID Router-ID IGP Process-ID Area Link-Count1 3.3.3.9 OSPF 1 0 22 1.1.1.9 OSPF 1 0 13 2.2.2.9 OSPF 1 0 1

3. Configure the MPLS BGP/MPLS IP VPN.# Configure VPN instances on the PE routers and bind the VPN instances to the interfacesconnected to the CE routers.l Configure CE1.

<CE1> system-view[CE1] interface gigabitethernet 1/0/0[CE1-GigabitEthernet1/0/0] undo shutdown[CE1-GigabitEthernet1/0/0] ip address 10.1.1.1 255.255.255.0[CE1-GigabitEthernet1/0/0] quit

l Configure CE3.<CE3> system-view[CE3] interface gigabitethernet 1/0/0[CE3-GigabitEthernet1/0/0] undo shutdown[CE3-GigabitEthernet1/0/0] ip address 10.3.1.1 255.255.255.0[CE3-GigabitEthernet1/0/0] quit

l Configure a VPN instance on PE1.[PE1] ip vpn-instance VPNA[PE1-vpn-instance-VPNA] route-distinguisher 1:1[PE1-vpn-instance-VPNA] vpn-target 1:1 export-extcommunity[PE1-vpn-instance-VPNA] vpn-target 1:1 import-extcommunity[PE1-vpn-instance-VPNA] quit[PE1] interface gigabitethernet2/0/0[PE1-GigabitEthernet2/0/0] undo shutdown[PE1-GigabitEthernet2/0/0] ip binding vpn-instance VPNA[PE1-GigabitEthernet2/0/0] ip address 10.1.1.2 255.255.255.0[PE1-GigabitEthernet2/0/0] quit[PE1] ip vpn-instance VPNB[PE1-vpn-instance-VPNB] route-distinguisher 2:2[PE1-vpn-instance-VPNB] vpn-target 2:2 export-extcommunity[PE1-vpn-instance-VPNB] vpn-target 2:2 import-extcommunity[PE1-vpn-instance-VPNB] quit[PE1] interface gigabitethernet3/0/0[PE1-GigabitEthernet3/0/0] undo shutdown[PE1-GigabitEthernet3/0/0] ip binding vpn-instance VPNB[PE1-GigabitEthernet3/0/0] ip address 10.3.1.2 255.255.255.0[PE1-GigabitEthernet3/0/0] quit

l Configure CE2.<CE2> system-view[CE2] interface gigabitethernet 1/0/0[CE2-GigabitEthernet1/0/0] undo shutdown[CE2-GigabitEthernet1/0/0] ip address 10.2.1.1 255.255.255.0[CE2-GigabitEthernet1/0/0] quit

l Configure CE4.<CE4> system-view[CE4] interface gigabitethernet 1/0/0[CE4-GigabitEthernet1/0/0] undo shutdown[CE4-GigabitEthernet1/0/0] ip address 10.4.1.1 255.255.255.0[CE4-GigabitEthernet1/0/0] return

l Configure a VPN instance on PE2.



7-27

[PE2] ip vpn-instance VPNA[PE2-vpn-instance-VPNA] route-distinguisher 1:1[PE2-vpn-instance-VPNA] vpn-target 1:1 export-extcommunity[PE2-vpn-instance-VPNA] vpn-target 1:1 import-extcommunity[PE2-vpn-instance-VPNA] quit[PE2] interface gigabitethernet2/0/0[PE2-GigabitEthernet2/0/0] undo shutdown[PE2-GigabitEthernet2/0/0] ip binding vpn-instance VPNA[PE2-GigabitEthernet2/0/0] ip address 10.2.1.2 255.255.255.0[PE2-Ethernet2/0/0] quit[PE2] ip vpn-instance VPNB[PE2-vpn-instance-VPNB] route-distinguisher 2:2[PE2-vpn-instance-VPNB] vpn-target 2:2 export-extcommunity[PE2-vpn-instance-VPNB] vpn-target 2:2 import-extcommunity[PE2-vpn-instance-VPNB] quit[PE2] interface gigabitethernet3/0/0[PE2-GigabitEthernet3/0/0] undo shutdown[PE2-GigabitEthernet3/0/0] ip binding vpn-instance VPNB[PE2-GigabitEthernet3/0/0] ip address 10.4.1.2 255.255.255.0[PE2-GigabitEthernet3/0/0] quitBy running the display ip vpn-instance verbose command on the PE routers, you cansee the configurations of the VPN instances.Take PE1 as an example:[PE1] display ip vpn-instance verbose Total VPN-Instances configured : 2 VPN-Instance Name and ID : VPNA, 1 Create date : 2007/07/21 11:30:35 Up time : 0 days, 00 hours, 05 minutes and 19 seconds Route Distinguisher : 1:1 Export VPN Targets : 1:1 Import VPN Targets : 1:1 Label policy: label per routeThe diffserv-mode Information is : uniform The ttl-mode Information is : pipe Interfaces : GigabitEthernet2/0/0 VPN-Instance Name and ID : VPNB, 2 Create date : 2007/07/21 11:31:18 Up time : 0 days, 00 hours, 04 minutes and 36 seconds Route Distinguisher : 2:2 Export VPN Targets : 2:2 Import VPN Targets : 2:2The diffserv-mode Information is : uniform The ttl-mode Information is : pipe Interfaces : GigabitEthernet3/0/0The PE routers can ping through the CE routers connected to them successfully.[PE1] ping -vpn-instarce VPNA 10.3.1.1 PING 10.3.1.1: 56 data bytes, press CTRL_C to break Reply from 10.3.1.1: bytes=56 Sequence=1 ttl=128 time=2 ms Reply from 10.3.1.1: bytes=56 Sequence=2 ttl=128 time=1 ms Reply from 10.3.1.1: bytes=56 Sequence=3 ttl=128 time=1 ms Reply from 10.3.1.1: bytes=56 Sequence=4 ttl=128 time=1 ms Reply from 10.3.1.1: bytes=56 Sequence=5 ttl=128 time=1 ms --- 10.3.1.1 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 1/1/2 ms # Establish an IBGP adjacency between PE1 and PE2.[PE1] bgp 500[PE1-bgp] peer 2.2.2.9 as-number 500[PE1-bgp] peer 2.2.2.9 connect-interface loopback1[PE1-bgp] ipv4-family vpnv4[PE1-bgp-af-vpnv4] peer 2.2.2.9 enable




Issue 05 (2010-06-01)

[PE1-bgp-af-vpnv4] quit<PE2> system-view[PE2] bgp 500[PE2-bgp] peer 1.1.1.9 as-number 500[PE2-bgp] peer 1.1.1.9 connect-interface LoopBack1[PE2-bgp] ipv4-family vpnv4[PE2-bgp-af-vpnv4] peer 1.1.1.9 enable[PE2-bgp-af-vpnv4] quit

# Establish EBGP adjacencies between PE1 and CE1, PE1 and CE3, PE2 and CE2, PE2and CE4.l Configure CE1.

[CE1] bgp 100[CE1-bgp] peer 10.1.1.2 as-number 500[CE1-bgp] import-route direct[CE1-bgp] quit

l Configure CE3.[CE3] bgp 300[CE3-bgp] peer 10.3.1.2 as-number 500[CE3-bgp] import-route direct[CE3-bgp] quit

l Configure PE1.[PE1] bgp 500[PE1-bgp] ipv4-family vpn-instance VPNA[PE1-bgp-VPNA] peer 10.1.1.1 as-number 100[PE1-bgp-VPNAa] import-route direct[PE1-bgp-VPNA] quit[PE1-bgp] ipv4-family vpn-instance VPNB[PE1-bgp-VPNB] peer 10.3.1.1 as-number 300[PE1-bgp-VPNB] import-route direct[PE1-bgp-VPNB] quit



l Configure PE2.[PE2] bgp 500[PE2-bgp] ipv4-family vpn-instance VPNA[PE2-bgp-VPNA] peer10.2.1.1 as-number 200[PE2-bgp-VPNA] import-route direct[PE2-bgp-VPNA] quit[PE2-bgp] ipv4-family vpn-instance VPNB[PE2-bgp-VPNB] peer 10.4.1.1 as-number 300[PE2-bgp-VPNB] import-route direct[PE2-bgp-VPNB] quit

After the configuration, by running the display bgp peer and display bgp vpn-instancepeer commands on the PE routers, you can see that BGP adjacencies are establishedbetween the PE routers, and between the PE routers and the CE routers connected to them.The BGP adjacencies are in Established state.Take the display on PE1 as an example:[PE1] display bgp peer BGP local router ID : 1.1.1.9 Local AS number : 500 Total number of peers : 1 Peers in established state : 1



7-29

Peer V AS MsgRcvd MsgSent OutQ Up/Down State PrefRcv 2.2.2.9 4 500 3 3 0 00:00:11 Established 0 [PE1] display bgp vpnv4 all peerBGP local router ID : 1.1.1.9 Local AS number : 500 Total number of peers : 3 Peers in established state : 3 Peer V AS MsgRcvd MsgSent OutQ Up/Down State PrefRcv 2.2.2.9 4 500 12 18 0 00:09:38 Established 0 Peer of vpn instance: vpn instance VPNA :10.1.1.1 4 100 25 25 0 00:17:57 Established 1 vpn instance VPNB :10.3.1.1 4 300 21 22 0 00:17:10 Established 1

CE1 and CE2 can ping through each other successfully; CE3 and CE4 can ping througheach other successfully. The CE routers in different VPNs cannot ping through each other.[CE1] ping 10.2.1.1 PING 10.2.1.1: 56 data bytes, press CTRL_C to break Reply from 10.2.1.1: bytes=56 Sequence=1 ttl=128 time=2 ms Reply from 10.2.1.1: bytes=56 Sequence=2 ttl=128 time=1 ms Reply from 10.2.1.1: bytes=56 Sequence=3 ttl=128 time=1 ms Reply from 10.2.1.1: bytes=56 Sequence=4 ttl=128 time=1 ms Reply from 10.2.1.1: bytes=56 Sequence=5 ttl=128 time=1 ms --- 10.2.1.1 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 1/1/2 ms

4. Configure a tunnel policy to specify that the VPNs use the MPLS TE tunnel. Apply thetunnel policy to the VPNs.[PE1] tunnel-policy policy1[PE1-tunnel-policy-policy1] tunnel select-seq cr-lsp load-balance-number 1[PE1-tunnel-policy-policy1] quit[PE1] ip vpn-instance VPNA[PE1-vpn-instance-VPNA] tnl-policy policy1[PE1-vpn-instance-VPNA] quit[PE1] ip vpn-instance VPNB[PE1-vpn-instance-VPNB] tnl-policy policy1[PE1-vpn-instance-VPNB] quit

NOTE

In this example, only the TE tunnel from PE1 to PE2 is configured. To configure a bidirectionalMPLS TE tunnel, you need to configure a tunnel policy on PE2 and apply the tunnel policy to theVPNs.

By running the display mpls forwarding-table command on PE1, you can see an LSP to2.2.2.9/32 in the MPLS forwarding table.[PE1] display mpls forwarding-tableFec Outlabel Out-IF Nexthop LspIndex3.3.3.9/32 3 POS1/0/0 100.1.1.2 307352.2.2.9/32 1025 POS1/0/0 100.1.1.2 30743

By running the display tunnel-info all command on PE1, you can see that an MPLS TEtunnel to 2.2.2.9 is established on PE1.[PE1] display tunnel-info all * -> Allocated VC TokenTunnel ID Type Destination Token----------------------------------------------------------------------0x1808027 lsp 3.3.3.9 390x1808028 lsp 20.20.20.9 400x1808029 lsp 30.30.30.9 410x180802a lsp -- 420x180802b lsp -- 43




Issue 05 (2010-06-01)

0x180802c lsp -- 440x180802d lsp -- 450x61818003 cr lsp 2.2.2.9 327710x41818005 lsp -- 327730x41818006 lsp -- 32774

5. Configure simple traffic classification on PE1 and configure PE1 to trust the DSCP valuesof the upstream packets.[PE1] interface gigabitethernet 2/0/0[PE1-GigabitEthernet2/0/0] trust upstream default[PE1-GigabitEthernet2/0/0] quit[PE1] interface gigabitethernet 3/0/0[PE1-GigabitEthernet3/0/0] trust upstream default[PE1-GigabitEthernet3/0/0] quit

NOTE

If the BGP/MPLS IP VPN is configured to support the short pipe model, simple traffic classificationis recommended, because the egress PE needs to schedule packets according to the original DSCPvalues of the packets.

6. Configure flow queues for VPNA, VPNB, and the MPLS TE tunnel on PE1.# Configure the WRED object to be referenced by the flow queues.[PE1] drop-profile drop1[PE1-drop-drop1] wred green low-limit 20 high-limit 50 discard-percentage 100[PE1-drop-drop1] quit

# Configure the scheduling algorithm, WRED parameters, and traffic shaping rates for theflow queues.[PE1] queue-profile VPNA[PE1-queue-vpna] queue-class ef [PE1-queue-vpna-ef] pq [PE1-queue-vpna-ef] drop-profile drop1 [PE1-queue-vpna-ef] queue cir 15000[PE1-queue-vpna-ef] quit[PE1-queue-vpna] queue-class af4 [PE1-queue-vpna-af4] queue weight 15[PE1-queue-vpna-af4] drop-profile drop1 [PE1-queue-vpna-af4] queue cir 10000[PE1-queue-vpna-af4] quit[PE1-queue-vpna] queue-class af3 [PE1-queue-vpna-af3] queue weight 10[PE1-queue-vpna-af3] drop-profile drop1 [PE1-queue-vpna-af3] queue cir 5000[PE1-queue-vpna-af3] quit[PE1-queue-vpna] quit[PE1] queue-profile VPNB[PE1-queue-vpnb] queue-class ef[PE1-queue-vpnb-ef] pq [PE1-queue-vpnb-ef] drop-profile drop1[PE1-queue-vpnb-ef] queue cir 10000[PE1-queue-vpnb-ef] quit[PE1-queue-vpnb] quit[PE1] queue-profile te[PE1-queue-te] queue-class ef [PE1-queue-te-ef] pq [PE1-queue-te-ef] drop-profile drop1[PE1-queue-te-ef] queue cir 25000[PE1-queue-te-ef] quit[PE1-queue-te] queue-class af4 [PE1-queue-te-af4] queue weight 15[PE1-queue-te-af4] drop-profile drop1[PE1-queue-te-af4] queue cir 15000[PE1-queue-te-af4] quit[PE1-queue-te] queue-class af3 [PE1-queue-te-af3] queue weight 10 [PE1-queue-te-af3] drop-profile drop1[PE1-queue-te-af3] queue cir 10000



7-31

[PE1-queue-te-af3] quit[PE1-queue-te] quit

7. Configure the DiffServ model supported by the BGP/MPLS IP VPN.[PE1] ip vpn-instance VPNA[PE1-vpn-instance-VPNA] diffserv-mode uniform [PE1-vpn-instance-VPNA] quit

NOTE

l If you configure VPNA to support the uniform model for the first time, you do not need to runthe preceding commands. The system adopts the uniform model by default.

l If VPNA supports the pipe or short pipe model and you want to configure it to support the uniformmodel, run the preceding commands.

[PE1] ip vpn-instance VPNB[PE1-vpn-instance-VPNB] diffserv-mode short-pipe af3 green[PE1-vpn-instance-VPMB] quit

8. Configure class queues on the network-side interface of PE1.[PE1] interface pos 1/0/0[PE1-POS1/0/0] port-queue ef pq shaping 25 outbound[PE1-POS1/0/0] port-queue af4 wfq weight 15 shaping 15 outbound[PE1-POS1/0/0] port-queue af3 wfq weight 10 shaping 10 outbound[PE1-POS1/0/0] quit

9. Configure bandwidth of the MPLS TE tunnel and bind the VPN instances to the MPLS TEtunnel.[PE1] interface tunnel 1/0/0[PE1-Tunnel1/0/0] tunnel-protocol mpls te[PE1-Tunnel1/0/0] mpls te bandwidth 80000 flow-queue te[PE1-Tunnel1/0/0] mpls te reserved-for-binding[PE1-Tunnel1/0/0] mpls te vpn-binding vpn-instance VPNA cir 50000 pir 80000 flow-queue vpna[PE1-Tunnel1/0/0] mpls te vpn-binding vpn-instance VPNB cir 30000 pir 80000 flow-queue vpnb[PE1-Tunnel1/0/0] mpls te commit

Configuration Filesl Configuration file of PE1

# sysname PE1#ip vpn-instance VPNA route-distinguisher 1:1 tnl-policy policy1 vpn-target 1:1 export-extcommunity vpn-target 1:1 import-extcommunity#ip vpn-instance VPNB route-distinguisher 2:2 tnl-policy policy1 vpn-target 2:2 export-extcommunity vpn-target 2:2 import-extcommunity diffserv-mode short-pipe af4 green#mpls lsr-id 1.1.1.9mpls mpls te mpls rsvp-te mpls te cspf#mpls ldp#mpls ldp remote-peer 2.2.2.9 remote-ip 2.2.2.9#




Issue 05 (2010-06-01)

diffserv domain default#drop-profile drop1 wred green low-limit 20 high-limit 50 discard-percentage 100# queue-profile queue1#queue-profile te queue-class af3 queue weight 10 drop-profile drop1 queue cir 10000 cbs 125000 pbs 125000 queue-class af4 drop-profile drop1 queue cir 15000 cbs 125000 pbs 125000 queue-class ef drop-profile drop1 queue cir 25000 cbs 125000 pbs 125000#queue-profile vpna queue-class af3 queue weight 10 drop-profile drop1 queue cir 5000 cbs 125000 pbs 125000 queue-class af4 drop-profile drop1 queue cir 10000 cbs 125000 pbs 125000 queue-class ef drop-profile drop1 queue cir 15000 cbs 125000 pbs 125000#queue-profile vpnb queue-class ef drop-profile drop1 queue cir 10000 cbs 125000 pbs 125000 #interface Pos1/0/0 undo shutdown ip address 100.1.1.1 255.255.255.0 mpls mpls te mpls te max-link-bandwidth 200000 mpls te max-reservable-bandwidth 100000 mpls rsvp-te mpls ldp port-queue af3 wfq weight 10 shaping 10 outbound port-queue af4 wfq weight 15 shaping 15 outbound port-queue ef pq shaping 25 outbound#interface LoopBack1 ip address 1.1.1.9 255.255.255.252#interface Tunnel1/0/0 ip address unnumbered interface LoopBack1 tunnel-protocol mpls te destination 2.2.2.9 mpls te tunnel-id 100 mpls te bandwidth bc0 80000 flow-queue te mpls te reserved-for-binding mpls te vpn-binding vpn-instance VPNA cir 50000 pir 80000 flow-queue vpna mpls te vpn-binding vpn-instance VPNB cir 30000 pir 80000 flow-queue vpnb mpls te commit#bgp 500 peer 2.2.2.9 as-number 500 peer 2.2.2.9 connect-interface LoopBack1# ipv4-family unicast undo synchronization



7-33

import-route direct peer 2.2.2.9 enable # ipv4-family vpnv4 policy vpn-target peer 2.2.2.9 enable# ipv4-family vpn-instance VPNA peer 10.1.1.1 as-number 100 import-route direct# ipv4-family vpn-instance VPNB peer 10.3.1.1 as-number 300 import-route direct#interface GigabitEthernet2/0/0 undo shutdown ip binding vpn-instance VPNA ip address 10.1.1.2 255.255.255.0 trust upstream default#interface GigabitEthernet3/0/0 undo shutdown ip binding vpn-instance VPNB ip address 10.3.1.2 255.255.255.0 trust upstream default#ospf 1 opaque-capability enable area 0.0.0.0 network 100.1.1.0 0.0.0.255 network 1.1.1.9 0.0.0.0 mpls-te enable#tunnel-policy policy1 tunnel select-seq cr-lsp load-balance-number 1#return

l Configuration file of P# sysname P# mpls lsr-id 3.3.3.9 mpls mpls te mpls rsvp-te mpls te cspf#mpls ldp# bfd#diffserv domain default#interface Pos1/0/0 undo shutdown ip address 100.1.1.2 255.255.255.0 mpls mpls te mpls te max-link-bandwidth 200000 mpls te max-reservable-bandwidth 100000 mpls rsvp-te mpls ldp#interface Pos2/0/0 undo shutdown ip address 200.1.1.1 255.255.255.0 mpls mpls te




Issue 05 (2010-06-01)

mpls te max-link-bandwidth 200000 mpls te max-reservable-bandwidth 100000 mpls rsvp-te mpls ldp#interface LoopBack1 ip address 2.2.2.9 255.255.255.252#domain default#ospf 1 opaque-capability enable area 0.0.0.0 network 100.1.1.0 0.0.0.255 network 200.1.1.0 0.0.0.255 network 3.3.3.9 0.0.0.0 mpls-te enable#return

l Configuration file of PE2# sysname PE2#ip vpn-instance VPNA route-distinguisher 1:1 vpn-target 1:1 export-extcommunity vpn-target 1:1 import-extcommunity#ip vpn-instance VPNB route-distinguisher 2:2 vpn-target 2:2 export-extcommunity vpn-target 2:2 import-extcommunity#mpls lsr-id 2.2.2.9 mpls mpls te mpls rsvp-te mpls te cspf#mpls ldp#mpls ldp remote-peer 1.1.1.9 remote-ip 1.1.1.9#interface POS1/0/0 undo shutdown ip address 200.1.1.2 255.255.255.0 mpls mpls te mpls te max-link-bandwidth 200000 mpls te max-reservable-bandwidth 100000 mpls rsvp-te mpls ldp#interface LoopBack1 ip address 2.2.2.9 255.255.255.252#ipv4-family vpnv4 peer 1.1.1.9 enable#ipv4-family vpn-instance VPNA peer10.2.1.1 as-number 200 import-route direct#ipv4-family vpn-instance VPNB peer 10.4.1.1 as-number 300 import-route direct#ipv4-family unicast



7-35

undo synchronization import-route direct peer 2.2.2.9 enable#bgp 500 peer 1.1.1.9 as-number 500 peer 1.1.1.9 connect-interface LoopBack1#interface GigabitEthernet2/0/0 undo shutdown ip binding vpn-instance VPNA ip address 10.2.1.2 255.255.255.0#interface GigabitEthernet3/0/0 undo shutdown ip binding vpn-instance VPNB ip address 10.4.1.2 255.255.255.0#ospf 1 opaque-capability enable area 0.0.0.0 network 200.1.1.0 0.0.0.255 network 2.2.2.9 0.0.0.0 mpls-te enable#return

l Configuration file of CE1# sysname CE1#interface GigabitEthernet1/0/0 undo shutdown ip address 10.1.1.1 255.255.255.0#bgp 100 peer 10.1.1.2 as-number 500 # undo synchronization import-route direct peer 10.1.1.2 enable#return

l Configuration file of CE2# sysname CE2#interface GigabitEthernet1/0/0 undo shutdown ip address 10.2.1.1 255.255.255.0#bgp 200 peer 10.2.1.2 as-number 500 #undo synchronization import-route direct peer 10.2.1.2 enable#return

l Configuration file of CE3# sysname CE3#interface GigabitEthernet1/0/0 undo shutdown ip address 10.3.1.1 255.255.255.0#bgp 300




Issue 05 (2010-06-01)

peer 10.3.1.2 as-number 500 # undo synchronization import-route direct peer 10.3.1.2 enable#return

l Configuration file of CE4# sysname CE4#interface GigabitEthernet1/0/0 undo shutdown ip address 10.4.1.1 255.255.255.0#bgp 400 peer 10.4.1.2 as-number 500 # undo synchronization import-route direct peer 10.4.1.2 enable#return

7.4.2 Example for Configuring the Resource Reserved VLL


As shown in Figure 7-2, the ME60 functions as the PE of the MPLS backbone. CE1 and CE2belong to VLL-A, and CE3 and CE4 belong to VLL-B. The two VLLs share the MPLS TEtunnel between the edge routers of the public network, namely, PE1 and PE2. Bandwidth shouldbe reserved for the VLLs and services in the VLLs respectively. In addition, the VLLs andservices do not occupy each other's bandwidth.

The MPLS backbone uses the OSPF protocol as the IGP protocol. CE1 and CE2 belong to thesame VLL, and CE3 and CE4 belong to the same VLL.


l Establish an MPLS TE tunnel between PE1 and PE2 through RSVP-TE to transmit packetsof the VLLs. Bandwidth of the MPLS TE tunnel is 80 Mbit/s. The maximum bandwidthof the links along the tunnel is 200 Mbit/s, and the maximum reserved bandwidth is 100Mbit/s.

l CE1 and CE2 access PE1 and PE2 through VLANs. CE3 and CE4 also access PE1 andPE2 through VLANs.

l VLL-A uses the uniform DiffServ model on the MPLS TE tunnel.

l Packets in VLL-B are common IP packets. VLL-B uses the pipe DiffServ model on theMPLS TE tunnel. The egress router of the MPLS backbone schedules the packets accordingto the EXP values of the packets.

l On the MPLS TE tunnel, 50 Mbit/s bandwidth is reserved for VLL-A. In VLL-A, the VoIPservice packets are forwarded as the EF class and have 15 Mbit/s guaranteed bandwidth.The video service packets are forwarded as the AF4 class and have 10 Mbit/s guaranteedbandwidth. Packets of important data services are forwarded as the AF3 class and have 5Mbit/s guaranteed bandwidth. Other data services occupy the remaining bandwidth ofVLL-A according to the default configuration of the system.



7-37

l On the MPLS TE tunnel, 30 Mbit/s bandwidth is reserved for VLL-B. In VLL-B, the voiceservice of the EF class has 10 Mbit/s guaranteed bandwidth. Other data services occupythe remaining bandwidth of VLL-B according to the default configuration of the system.

Figure 7-2 Networking of the resource reserved VLL

VLL-B

PE1 PE2

CE1 CE2

Backbone

Loopback12.2.2.9/32

Loopback11.1.1.9/32

GE2/0/0.1

POS1/0/0200.1.1.2/24

POS1/0/0100.1.1.1/24

GE1/0/0.110.1.1.1/24

GE1/0/0.110.1.1.2/24

GE2/0/0.1

VLL-A

VLL-B

VLL-A

GE3/0/0.1GE3/0/0.1

GE1/0/0.110.3.1.1/24

CE3 CE4GE1/0/0.110.3.1.2/24

Loopback13.3.3.9/32

POS1/0/0100.1.1.2/24

POS2/0/0200.1.1.1/24

BGP100

BGP300

BGP200

BGP400BGP500

P





3. Configure the Martini VLLs.4. Configure VLL-B to use the pipe DiffServ model on the MPLS TE tunnel.5. Configure the resource reservation function and guaranteed bandwidth in VLL-A and VLL-

B.

NOTE

In this example, the resource reservation function is applied to only the VPN data from PE1 to PE2.In the network, traffic is bidirectional, and you can configure the hierarchical resource reservedL2VPN on the peer PE for the VPN data transmitted in the reverse direction.

Data Preparation

To complete the configuration, you need the following data:

l Name of the peer PE and VC ID

l VLAN IDs of CE1, CE2, CE3, and CE4

l Service classes used in forced traffic classification on the GE interface in VLL-A




Issue 05 (2010-06-01)

l Service classes and colors of the packets from VLL-B, which are used for label mappingon the ingress of the MPLS TE tunnel

l Guaranteed bandwidth and scheduling parameters of VLL-A, VLL-B, and flow queues onthe MPLS TE tunnel

l Bandwidth limits of VLL-A, VPNB, and the MPLS TE tunnel


(OSPF) to implement interworking between PE1, P, and PE2.For the configuration procedure, see 7.4.1 Example for Configuring the ResourceReserved BGP/MPLS IP VPN.

2. Configure the MPLS TE tunnel.For the configuration procedure, see 7.4.1 Example for Configuring the ResourceReserved BGP/MPLS IP VPN.

3. Configure the Martini VLLs.# Configure the CE routers. CE1 and CE2 access PE1 and PE2 through VLANs. CE3 andCE4 also access PE1 and PE2 through VLANs.l Configure CE1.

<CE1> system-view[CE1] interface gigabitethernet 1/0/0.1[CE1-GigabitEthernet1/0/0.1] shutdown[CE1-GigabitEthernet1/0/0.1] vlan-type dot1q 100[CE1-GigabitEthernet1/0/0.1] ip address 10.1.1.1 24[CE3-GigabitEthernet1/0/0.1] undo shutdown[CE3-GigabitEthernet1/0/0.1] quit

l # Configure CE2.<CE2> system-view[CE2] interface gigabitethernet 1/0/0.1[CE2-GigabitEthernet1/0/0.1] shutdown[CE3-GigabitEthernet1/0/0.1] vlan-type dot1q 200[CE2-GigabitEthernet1/0/0.1] ip address 10.1.1.2 24[CE2-GigabitEthernet1/0/0.1] undo shutdown[CE2-GigabitEthernet1/0/0.1] quit

l Configure CE3.<CE3> system-view[CE3] interface gigabitethernet 1/0/0.1[CE3-GigabitEthernet1/0/0.1] shutdown[CE3-GigabitEthernet1/0/0.1] vlan-type dot1q 10[CE3-GigabitEthernet1/0/0.1] ip address 10.3.1.1 24[CE3-GigabitEthernet1/0/0.1] undo shutdown[CE3-GigabitEthernet1/0/0.1] quit

l Configure CE4.<CE4> system-view[CE4] interface gigabitethernet 1/0/0.1[CE4-GigabitEthernet1/0/0.1] shutdown[CE4-GigabitEthernet1/0/0.1] vlan-type dot1q 20[CE4-GigabitEthernet1/0/0.1] ip address 10.3.1.2 24[CE4-GigabitEthernet1/0/0.1] undo shutdown[CE4-GigabitEthernet1/0/0.1] quit

# Enable MPLS L2VPN and create VC connections on the PE routers.l Configure PE1. Create VCs on the interfaces connected to CE1 and CE3.

<PE1> system-view[PE1] mpls l2vpn[PE1-l2vpn] mpls l2vpn default martini



7-39

[PE1-l2vpn] quit[PE1] interface gigabitethernet2/0/0.1[PE1-GigabitEthernet2/0/0.1] shutdown[PE1-GigabitEthernet2/0/0.1] vlan-type dot1q 100[PE1-GigabitEthernet2/0/0.1] mpls l2vc 2.2.2.9 102[PE1-GigabitEthernet2/0/0.1] undo shutdown[PE1-GigabitEthernet2/0/0.1] quit[PE1] interface gigabitethernet 3/0/0.1[PE1-GigabitEthernet3/0/0.1] shutdown[PE1-GigabitEthernet3/0/0.1] vlan-type dot1q 10[PE1-GigabitEthernet3/0/0.1] mpls l2vc 2.2.2.9 101[PE1-GigabitEthernet3/0/0.1] undo shutdown[PE1-GigabitEthernet3/0/0.1] quit

l Configure PE2. Create VC connections on the interfaces connected to CE2 and CE4.<PE2> system-view[PE2] mpls l2vpn[PE2-l2vpn] quit[PE2-l2vpn] mpls l2vpn default martini[PE2] interface gigabitethernet 3/0/0.1[PE2-GigabitEthernet3/0/0.1] shutdown[PE2-GigabitEthernet3/0/0.1] vlan-type dot1q 20[PE2-GigabitEthernet3/0/0.1] mpls l2vc 1.1.1.9 101[PE2-GigabitEthernet3/0/0.1] undo shutdown[PE2-GigabitEthernet3/0/0.1] quit[PE2] interface gigabitethernet 2/0/0.1[PE2-GigabitEthernet2/0/0.1] shutdown[PE2-GigabitEthernet2/0/0.1] vlan-type dot1q 200[PE2-GigabitEthernet2/0/0.1] mpls l2vc 1.1.1.9 102[PE2-GigabitEthernet2/0/0.1] undo shutdown[PE2-GigabitEthernet2/0/0.1] quit

After the configuration, by running the display mpls l2vc command on the PE routers, youcan see that two L2VC connections are created and they are in Up state. Take the displayon PE1 for example.[PE1] display mpls l2vcTotal ldp vc : 2 2 up 0 down *Client Interface : GigabitEthernet2/0/0.1 Session State : up AC Status : up VC State : up VC ID : 102 VC Type : vlan Destination : 2.2.2.9 Local VC Label : 1025 Remote VC Label : 1024 Control Word : Disable Local VC MTU : 1500 Remote VC MTU : 1500 Tunnel Policy Name : -- Traffic Behavior Name: -- PW Template Name : -- Create time : 0 days, 0 hours, 3 minutes, 14 seconds UP time : 0 days, 0 hours, 1 minutes, 48 seconds Last change time : 0 days, 0 hours, 1 minutes, 48 seconds *Client Interface : GigabitEthernet3/0/0.1 Session State : up AC Status : up VC State : up VC ID : 101 VC Type : vlan Destination : 2.2.2.9 Local VC Label : 17408 Remote VC Label : 17408 Control Word : Disable Local ATM Cells : 1 Remote ATM Cells : 1




Issue 05 (2010-06-01)

Tunnel Policy Name : -- Traffic Behavior Name: -- PW Template Name : -- Create time : 0 days, 0 hours, 3 minutes, 14 seconds UP time : 0 days, 0 hours, 1 minutes, 48 seconds Last change time : 0 days, 0 hours, 1 minutes, 48 secondsCE1 and CE2 can ping through each other successfully; CE3 and CE4 can ping througheach other successfully.[CE1] ping 10.1.1.2 PING 10.1.1.2: 56 data bytes, press CTRL_C to break Reply from 10.1.1.2: bytes=56 Sequence=1 ttl=128 time=2 ms Reply from 10.1.1.2: bytes=56 Sequence=2 ttl=128 time=1 ms Reply from 10.1.1.2: bytes=56 Sequence=3 ttl=128 time=1 ms Reply from 10.1.1.2: bytes=56 Sequence=4 ttl=128 time=1 ms Reply from 10.1.1.2: bytes=56 Sequence=5 ttl=128 time=1 ms --- 10.1.1.2 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 1/1/2 ms

4. Configure a tunnel policy to specify that the VLLs use the MPLS TE tunnel. Apply thetunnel policy to the VLLs.[PE1] tunnel-policy policy1[PE1-tunnel-policy-policy1] tunnel select-seq cr-lsp load-balance-number 1[PE1-tunnel-policy-policy1] quit[PE1] interface gigigabitethernet2/0/0.1[PE1-GigabitEthernet2/0/0.1] undo mpls l2vc[PE1-GigabitEthernet2/0/0.1] mpls l2vc 2.2.2.9 102 tunnel-policy policy1[PE1-GigabitEthernet2/0/0.1] quit[PE1] interface gigabitethernet 3/0/0.1[PE1-GigabitEthernet3/0/0.1] undo mpls l2vc[PE1-GigabitEthernet3/0/0.1] mpls l2vc 2.2.2.9 101 tunnel-policy policy1[PE1-GigabitEthernet3/0/0.1] quit

NOTE

In this example, only the TE tunnel from PE1 to PE2 is configured. To configure a bidirectionalMPLS TE tunnel, you need to configure a tunnel policy on PE2 and apply the tunnel policy to theVLLs.

5. Configure flow queues for VLL-A, VLL-B, and the MPLS TE tunnel on PE1.# Configure the WRED object to be referenced by the flow queues.[PE1] drop-profile drop1[PE1-drop-drop1] wred green low-limit 20 high-limit 50 discard-percentage 100[PE1-drop-drop1] quit# Configure the scheduling algorithm, WRED parameters, and traffic shaping rates for theflow queues.[PE1] queue-profile vlla[PE1-queue-vlla] queue-class ef [PE1-queue-vlla-ef] pq [PE1-queue-vlla-ef] drop-profile drop1[PE1-queue-vlla-ef] queue cir 15000[PE1-queue-vlla-ef] quit[PE1-queue-vlla] queue-class af4 [PE1-queue-vlla-af4] queue weight 15 [PE1-queue-vlla-af4] drop-profile drop1[PE1-queue-vlla-af4] queue cir 10000[PE1-queue-vlla-af4] quit[PE1-queue-vlla] queue-class af3 [PE1-queue-vlla-af3] queue weight 10 [PE1-queue-vlla-af3] drop-profile drop1[PE1-queue-vlla-af3] queue cir 5000[PE1-queue-vlla-af3] quit[PE1-queue-vlla] quit



7-41

[PE1] queue-profile vllb[PE1-queue-vllb] queue-class ef [PE1-queue-vllb-af3] pq [PE1-queue-vllb-af3] drop-profile drop1[PE1-queue-vllb-af3] queue cir 10000[PE1-queue-vllb-af3] quit[PE1-queue-vllb] quit[PE1] queue-profile te[PE1-queue-te] queue-class ef[PE1-queue-te-ef] pq [PE1-queue-te-ef] drop-profile drop1[PE1-queue-te-ef] queue cir 25000[PE1-queue-te-ef] quit[PE1-queue-te] queue-class af4 [PE1-queue-te-af4] queue weight 15 [PE1-queue-te-af4] drop-profile drop1[PE1-queue-te-af4] queue cir 15000[PE1-queue-te-af4] quit[PE1-queue-te] queue-class af3 [PE1-queue-te-af3] queue weight 10 [PE1-queue-te-af3] drop-profile drop1[PE1-queue-te-af3] queue cir 10000[PE1-queue-te-af3] quit[PE1-queue-te] quit

6. Configure the DiffServ model supported by the VLL.[PE1] interface gigabitethernet2/0/0.1[PE1-GigabitEthernet2/0/0.1] diffserv-mode uniform[PE1-GigabitEthernet2/0/0.1] quit

NOTE

l If you configure the VLL to support the uniform model for the first time, you do not need to runthe preceding commands. The system adopts the uniform model by default.

l If the VLL supports the pipe or short pipe model and you want to configure it to support theuniform model, run the preceding commands.

[PE1] interface gigabitethernet 3/0/0.1[PE1-GigabitEthernet3/0/0.1] diffserv-mode pipe af3 green[PE1-GigabitEthernet3/0/0.1] quit

NOTE

Because the VLL is configured to support the pipe model, you do not need to configure simple trafficclassification on the ingress PE for the traffic of the VLL.


8. Configure bandwidth of the MPLS TE tunnel and bind the VLLs to the MPLS TE tunnel.[PE1] interface tunnel 1/0/0[PE1-Tunnel1/0/0] tunnel-protocol mpls te[PE1-Tunnel1/0/0] mpls te bandwidth 80000 flow-queue te[PE1-Tunnel1/0/0] mpls te reserved-for-binding[PE1-Tunnel1/0/0] mpls te vpn-binding l2vpn interface gigabitethernet 2/0/0.1 cir 50000 pir 80000 flow-queue vlla[PE1-Tunnel1/0/0] mpls te vpn-binding l2vpn interface gigabitethernet 3/0/0.1 cir 30000 pir 80000 flow-queue vllb[PE1-Tunnel1/0/0] mpls te commit


# sysname PE1




Issue 05 (2010-06-01)

#mpls lsr-id 1.1.1.9 mpls mpls te mpls rsvp-te mpls te cspf#mpls l2vpn mpls l2vpn default martini#mpls ldp#mpls ldp remote-peer 2.2.2.9 remote-ip 2.2.2.9#diffserv domain vlla#drop-profile drop1 wred green low-limit 20 high-limit 50 discard-percentage 100#queue-profile queue1#queue-profile te queue-class af3 queue weight 10 drop-profile drop1 queue cir 10000 cbs 125000 pbs 125000 queue-class af4 drop-profile drop1 queue cir 15000 cbs 125000 pbs 125000 queue-class ef drop-profile drop1 queue cir 25000 cbs 125000 pbs 125000#queue-profile vlla queue-class af3 queue weight 10 drop-profile drop1 queue cir 5000 cbs 125000 pbs 125000 queue-class af4 drop-profile drop1 queue cir 10000 cbs 125000 pbs 125000 queue-class ef drop-profile drop1 queue cir 15000 cbs 125000 pbs 125000#queue-profile vllb queue-class ef drop-profile drop1 queue cir 10000 cbs 125000 pbs 125000#interface Pos1/0/0 undo shutdown ip address 100.1.1.1 255.255.255.0 mpls mpls te mpls te max-link-bandwidth 200000 mpls te max-reservable-bandwidth 100000 mpls rsvp-te mpls ldp port-queue af3 wfq weight 10 shaping 10 outbound port-queue af4 wfq weight 15 shaping 15 outbound port-queue ef pq shaping 25 outbound#interface LoopBack1 ip address 1.1.1.9 255.255.255.252#interface Tunnel1/0/0 ip address unnumbered interface LoopBack1



7-43

tunnel-protocol mpls te destination 2.2.2.9 mpls te tunnel-id 100 mpls te bandwidth bc0 80000 flow-queue te mpls te reserved-for-binding mpls te vpn-binding l2vpn interface GigabitEthernet2/0/1.1 cir 50000 pir 80000 flow-queue vlla mpls te vpn-binding l2vpn interface GigabitEthernet3/0/0.1 cir 30000 pir 80000 flow-queue vllb mpls te commit#interface GigabtiEthernet2/0/0 undo shutdown#interface GigabtiEthernet2/0/0.1 vlan-type dot1q 100 ip address 10.1.1.2 255.255.255.0 mpls l2vc 2.2.2.9 102 tunnel-policy policy1#interface GigabitEthernet3/0/0 undo shutdown#interface GigabitEthernet3/0/0.1 vlan-type dot1q 10 mpls l2vc 2.2.2.9 101 tunnel-policy policy1 diffserv-mode pipe af3 green#ospf 1 opaque-capability enable area 0.0.0.0 network 100.1.1.0 0.0.0.255 network 1.1.1.9 0.0.0.0 mpls-te enable#tunnel-policy policy1tunnel select-seq cr-lsp load-balance-number 1#return

l Configuration file of P# sysname P# mpls lsr-id 3.3.3.9 mpls mpls te mpls rsvp-te mpls te cspf#mpls ldp#diffserv domain default#interface Pos1/0/0 undo shutdown ip address 100.1.1.2 255.255.255.0 mpls mpls te mpls te max-link-bandwidth 200000 mpls te max-reservable-bandwidth 100000 mpls rsvp-te mpls ldp#interface Pos2/0/0 undo shutdown ip address 200.1.1.1 255.255.255.0 mpls mpls te mpls te max-link-bandwidth 200000 mpls te max-reservable-bandwidth 100000




Issue 05 (2010-06-01)

mpls rsvp-te mpls ldp#interface LoopBack1 ip address 2.2.2.9 255.255.255.252#ospf 1 opaque-capability enable area 0.0.0.0 network 100.1.1.0 0.0.0.255 network 200.1.1.0 0.0.0.255 network 3.3.3.9 0.0.0.0 mpls-te enable#return

l Configuration file of PE2# sysname PE2# mpls lsr-id 2.2.2.9 mpls mpls te mpls rsvp-te mpls te cspf#mpls l2vpn mpls l2vpn default martini#mpls ldp#mpls ldp remote-peer 1.1.1.9 remote-ip 1.1.1.9#interface POS1/0/0 undo shutdown ip address 200.1.1.2 255.255.255.0 mpls mpls te mpls te max-link-bandwidth 200000 mpls te max-reservable-bandwidth 100000 mpls rsvp-te mpls ldp#interface LoopBack1 ip address 2.2.2.9 255.255.255.252#interface GigabitEthernet2/0/0 undo shutdown#interface GigabitEthernet2/0/0.1 undo shutdown vlan-type dot1q 200 mpls l2vc 1.1.1.9 102#interface GigabitEthernet3/0/0 undo shutdown#interface GigabitEthernet3/0/0.1 undo shutdown vlan-type dot1q 20 mpls l2vc 1.1.1.9 101#ospf 1 opaque-capability enable area 0.0.0.0 network 200.1.1.0 0.0.0.255 network 2.2.2.9 0.0.0.0 mpls-te enable#



7-45

returnl Configuration file of CE1

# sysname CE1#interface GigabitEthernet1/0/0 undo shutdown#interface GigabitEthernet1/0/0.1 vlan-type dot1q 100 ip address 10.1.1.1 255.255.255.0#return

l Configuration file of CE2# sysname CE2#interface GigabitEthernet1/0/0 undo shutdown#interface GigabitEthernet1/0/0.1 vlan-type dot1q 200 ip address 10.1.1.2 255.255.255.0#return



7.4.3 Example for Configuring the Resource Reserved VPLS

Networking RequirementAs shown in Figure 7-3, the ME60 functions as the PE of the MPLS backbone. CE1 and CE2belong to VSI1, and CE3 and CE4 belong to VSI2. VSI1 and VSI2 share the MPLS TE tunnelbetween the edge routers of the public network, namely, PE1 and PE2. Bandwidth should bereserved for VSI1, VSI2, and services in the VSIs respectively. In addition, the VSIs and servicesdo not occupy each other's bandwidth.

The MPLS backbone uses the OSPF protocol as the IGP protocol.




Issue 05 (2010-06-01)


l Establish an MPLS TE tunnel between PE1 and PE2 through RSVP-TE to transmit packetsof the VPLSs. Bandwidth of the MPLS TE tunnel is 80 Mbit/s. The maximum bandwidthof the links along the tunnel is 200 Mbit/s, and the maximum reserved bandwidth is 100Mbit/s.

l The CE routers access PE1 and PE2 through VLANs.

l Packets in VSI1 contain VLAN tags. Configure the mapping from the 802.1p value to theEXP value for simple traffic classification on the incoming interface of PE1.

l Packets in VSI2 are common IP packets. Configure the mapping from the DSCP value tothe EXP value for simple traffic classification on the incoming interface of PE1.

l VSI1 and VSI2 use the uniform DiffServ model on the MPLS TE tunnel. The egress routerof the MPLS backbone schedules the packets according to the DSCP values of packets afterlabel mapping.

l On the MPLS TE tunnel, 50 Mbit/s bandwidth is reserved for VSI1. In VSI1, the VoIPservice packets are forwarded as the EF class and have 15 Mbit/s guaranteed bandwidth.The video service packets are forwarded as the AF4 class and have 10 Mbit/s guaranteedbandwidth. Packets of important data services are forwarded as the AF3 class and have 5Mbit/s guaranteed bandwidth.

l On the MPLS TE tunnel, 30 Mbit/s bandwidth is reserved for VSI2. In VSI2, the voiceservice of the EF class has 10 Mbit/s guaranteed bandwidth. Other data services occupythe remaining bandwidth of VPNB according to the default configuration of the system.

Figure 7-3 Networking of the resource reserved VPLS

vsi2

PE1 PE2

CE1 CE2

Backbone

Loopback12.2.2.9/32

Loopback11.1.1.9/32

GE2/0/0.1

POS1/0/0200.1.1.2/24

POS1/0/0100.1.1.1/24

GE1/0/0.110.1.1.1/24

GE1/0/0.110.2.1.1/24

GE2/0/0.110.2.1.2/24

vsi1

vsi2

vsi1

GE3/0/0.110.4.1.2/24

GE3/0/0.1

GE1/0/0.110.3.1.1/24

CE3 CE4GE1/0/0.110.4.1.1/24

Loopback13.3.3.9/32

POS1/0/0100.1.1.2/24

POS2/0/0200.1.1.1/24

BGP100

BGP300

BGP200

BGP400BGP500

P






7-47


3. Configure the Martini VPLS.4. Configure the mapping used in simple traffic classification for the packets from VSI1 and

VSI2 to PE1 to re-mark the priorities of the packets.5. Configure the uniform DiffServ model on the MPLS TE tunnel for the packets from VSI1

and VSI2.

NOTE

l If you configure the VPLS to support the uniform model for the first time, you do not need torun the following commands. The system adopts the uniform model by default.

l If the VPLS supports the pipe or short pipe model and you want to configure it to support theuniform model, run the commands for configuring the DiffServ model.

6. Configure the resource reservation function and guaranteed bandwidth in VSI1 and VSI2.

NOTE

In this example, the resource reservation function is applied to only the VPN data from PE1 to PE2.In the network, traffic is bidirectional, and you can configure the hierarchical resource reserved VPLSon the peer PE for the packets transmitted in the reverse direction.


l Names and IDs of the VSIs, and VLAN IDs of the sub-interfaces at the AC side

l Service classes used in simple traffic classification in VSI1 and VSI2

l Guaranteed bandwidth and scheduling parameters of VSI1, VSI2, and flow queues on theMPLS TE tunnel

l Bandwidth limits of VSI1, VSI2, and MPLS TE tunnel


(OSPF) to implement interworking between PE1, P, and PE2.For the configuration procedure, see 7.4.1 Example for Configuring the ResourceReserved BGP/MPLS IP VPN.

2. Configure the MPLS TE tunnel.For the configuration procedure, see 7.4.1 Example for Configuring the ResourceReserved BGP/MPLS IP VPN.

3. Configure the Martini VPLS.# Enable MPLS L2VPN and configure VSIs on the PE routers.l Configure PE1.

<PE1> system-view[PE1] mpls l2vpn[PE1-l2vpn] quit[PE1] vsi vsi1 static[PE1-vsi-vsi1] pwsignal ldp[PE1-vsi-vsi1-ldp] vsi-id 1[PE1-vsi-vsi1-ldp] peer 2.2.2.9[PE1-vsi-vsi1-ldp] quit[PE1-vsi-vsi1] quit[PE1] vsi vsi2 static




Issue 05 (2010-06-01)

[PE1-vsi-vsi2] pwsignal ldp[PE1-vsi-vsi2-ldp] vsi-id 2[PE1-vsi-vsi2-ldp] peer 2.2.2.9[PE1-vsi-vsi1-ldp] quit[PE1-vsi-vsi1] quit

l Configure PE2.<PE2> system-view[PE2] mpls l2vpn[PE2-l2vpn] quit[PE2] vsi vsi1 static[PE2-vsi-vsi1] pwsignal ldp[PE2-vsi-vsi1-ldp] vsi-id 1[PE2-vsi-vsi1-ldp] peer 1.1.1.9[PE2-vsi-vsi1-ldp] quit[PE2-vsi-vsi1] quit[PE2] vsi vsi2 static[PE2-vsi-vsi2] pwsignal ldp[PE2-vsi-vsi2-ldp] vsi-id 2[PE2-vsi-vsi2-ldp] peer 1.1.1.9[PE2-vsi-vsi1-ldp] quit

# Bind the VSIs to the interfaces on the PE routers.l Configure PE1.

<PE1> system-view[PE1] interface gigabitethernet2/0/0.1[PE1-GigabitEthernet2/0/0.1] shutdown[PE1-GigabitEthernet2/0/0.1] vlan-type dot1q 100[PE1-GigabitEthernet2/0/0.1] l2 binding vsi vsi1[PE1-GigabitEthernet2/0/0.1] undo shutdown[PE1-GigabitEthernet2/0/0.1] quit[PE1] interface gigabitethernet3/0/0.1[PE1-GigabitEthernet3/0/0.1] shutdown[PE1-GigabitEthernet3/0/0.1] vlan-type dot1q 20[PE1-GigabitEthernet3/0/0.1] l2 binding vsi vsi2[PE1-GigabitEthernet3/0/0.1] undo shutdown[PE1-GigabitEthernet3/0/0.1] quit

l Configure PE2.[PE2] interface gigabitethernet2/0/0.1[PE2-GigabitEthernet2/0/0.1] shutdown[PE2-GigabitEthernet2/0/0.1] vlan-type dot1q 200[PE2-GigabitEthernet2/0/0.1] l2 binding vsi vsi1[PE2-GigabitEthernet2/0/0.1] undo shutdown[PE2-GigabitEthernet2/0/0.1] quit[PE2] interface gigabitethernet3/0/0.1[PE2-GigabitEthernet3/0/0.1] shutdown[PE2-GigabitEthernet3/0/0.1] vlan-type dot1q 20[PE2-GigabitEthernet3/0/0.1] l2 binding vsi vsi2[PE2-GigabitEthernet3/0/0.1] undo shutdown[PE2-GigabitEthernet3/0/0.1] quit

l Configure CE1.<CE1> system-view[CE1] interface gigabitethernet1/0/0.1[CE1-GigabitEthernet1/0/0.1] shutdown[CE1-GigabitEthernet1/0/0.1] vlan-type dot1q 100[CE1-GigabitEthernet1/0/0.1] ip address 10.1.1.1 255.255.255.0[CE1-GigabitEthernet1/0/0.1] undo shutdown[CE1-GigabitEthernet1/0/0.1] quit

l Configure CE2.<CE2> system-view[CE2] interface gigabitethernet1/0/0.1[CE2-GigabitEthernet1/0/0.1] shutdown[CE2-GigabitEthernet1/0/0.1] vlan-type dot1q 200[CE2-GigabitEthernet1/0/0.1] ip address 10.2.1.1 255.255.255.[CE2-GigabitEthernet1/0/0.1] undo shutdown



7-49

[CE2-GigabitEthernet1/0/0.1] quit



By running the display vsi name vsi1 verbose command on PE1, you can find that VSI1sets up a PW to PE2, and the status of VSI1 is Up.CE1 and CE2 can ping through each other successfully; CE3 and CE4 can ping througheach other successfully.

4. Configure a tunnel policy to specify that the VPNs use the MPLS TE tunnel. Apply thetunnel policy to the VSIs.[PE1] tunnel-policy policy1[PE1-tunnel-policy-policy1] tunnel select-seq cr-lsp load-balance-number 1[PE1-tunnel-policy-policy1] quit[PE1] vsi vsi1[PE1-vsi-vsi1] tnl-policy policy1[PE1-vsi-vsi1] quit[PE1] vsi vsi2[PE1-vsi-vsi2] tnl-policy policy1[PE1-vsi-vsi2] quit

NOTE

In this example, only the TE tunnel from PE1 to PE2 is configured. To configure a bidirectionalMPLS TE tunnel, you need to configure a tunnel policy on PE2 and apply the tunnel policy to theVSIs.

By running the display mpls forwarding-table command on PE1, you can see an LSP to2.2.2.9/32 in the MPLS forwarding table.[PE1] display mpls forwarding-tableFec Outlabel Out-IF Nexthop LspIndex3.3.3.9/32 3 POS1/0/0 100.1.1.2 307352.2.2.9/32 1025 POS1/0/0 100.1.1.2 30743

By running the display tunnel-info all command on PE1, you can see that an MPLS TEtunnel to 2.2.2.9 is established on PE1.[PE1] display tunnel-info all * -> Allocated VC TokenTunnel ID Type Destination Token----------------------------------------------------------------------0x1808027 lsp 3.3.3.9 390x180802a lsp -- 420x180802b lsp -- 430x180802c lsp -- 440x180802d lsp -- 450x61818003 cr lsp 2.2.2.9 327710x41818005 lsp -- 327730x41818006 lsp -- 32774

5. Configure the mapping used in simple traffic classification on the incoming interface ofPE1.




Issue 05 (2010-06-01)

In VSI1, map the 802.1p values 3 and 2 of the packets in VLANs to the EXP values of 4and 3 in the MPLS field. In VSI2, map DSCP 34 to EXP value 3 in the MPLS field.[PE1] diffserv domain vsi1[PE1-dsdomain-vsi1] 8021p-inbound 3 phb af4 green[PE1-dsdomain-vsi1] mpls-exp-outbound af2 green map 3[PE1-dsdomain-vsi1] quit[PE1] interface gigabitethernet 2/0/0.1[PE1-GigabitEthernet2/0/0.1] trust upstream vsi1[PE1-GigabitEthernet2/0/0.1] trust 8021p[PE1-GigabitEthernet2/0/0.1] quit[PE1] diffserv domain vsi2[PE1-dsdomain-vsi2] ip-dscp-inbound 34 phb af3 green[PE1-dsdomain-vsi2] quit[PE1] interface gigabitethernet 3/0/0.1[PE1-GigabitEthernet3/0/0.1] trust upstream vsi2[PE1-GigabitEthernet3/0/0.1] return

6. Configure flow queues for VSI1, VSI2, and the MPLS TE tunnel on PE1.# Configure the WRED object to be referenced by the flow queues.[PE1] drop-profile drop1[PE1-drop-drop1] wred green low-limit 20 high-limit 50 discard-percentage 100[PE1-drop-drop1] quit# Configure the scheduling algorithm, WRED parameters, and traffic shaping rates for theflow queues.[PE1] queue-profile vsi1[PE1-queue-vsi1] queue-class ef [PE1-queue-vsi1-ef] pq [PE1-queue-vsi1-ef] drop-profile drop1[PE1-queue-vsi1-ef] queue cir 15000[PE1-queue-vsi1-ef] quit[PE1-queue-vsi1] queue-class af4 [PE1-queue-vsi1-af4] queue weight 15 [PE1-queue-vsi1-af4] drop-profile drop1[PE1-queue-vsi1-af4] queue cir 10000[PE1-queue-vsi1-af4] quit[PE1-queue-vsi1] queue-class af3 [PE1-queue-vsi1-af3] queue weight 10 [PE1-queue-vsi1-af3] drop-profile drop1[PE1-queue-vsi1-af3] queue cir 5000[PE1-queue-vsi1-af3] quit[PE1-queue-vsi1] quit[PE1] queue-profile vsi2[PE1-queue-vsi2] queue-class af3 [PE1-queue-vsi2-af3] pq [PE1-queue-vsi2-af3] drop-profile drop1[PE1-queue-vsi2-af3] queue cir 10000[PE1-queue-vsi2-af3] quit[PE1-queue-vsi2] quit[PE1] queue-profile te[PE1-queue-te] queue-class ef [PE1-queue-te-ef] pq [PE1-queue-te-ef] drop-profile drop1 [PE1-queue-te-ef] queue cir 25000[PE1-queue-te-ef] quit[PE1-queue-te] queue-class af4 [PE1-queue-te-af4] queue weight 15 [PE1-queue-te-af4] drop-profile drop1[PE1-queue-te-af4] queue cir 15000[PE1-queue-te-af4] quit[PE1-queue-te] queue-class af3 [PE1-queue-te-af3] queue weight 10 [PE1-queue-te-af3] drop-profile drop1[PE1-queue-te-af3] queue cir 10000[PE1-queue-te-af3] quit[PE1-queue-te] quit



7-51

7. Configure the DiffServ model supported by the VPLS.

NOTE

l If you configure the VPLS to support the uniform model for the first time, you do not need torun the following commands. The system adopts the uniform model by default.

l If the VPLS supports the pipe or short pipe model and you want to configure it to support theuniform model, run the following commands.

[PE1] vsi vsi1[PE1-vsi-vsi1] diffserv-mode uniform[PE1-vsi-vsi1] quit[PE1] vsi vsi2[PE1-vsi-vsi2] diffserv-mode uniform[PE1-vsi-vsi2] quit


9. Configure bandwidth of the MPLS TE tunnel and bind the VSIs to the MPLS TE tunnel.[PE1] interface tunnel 1/0/0[PE1-Tunnel1/0/0] tunnel-protocol mpls te[PE1-Tunnel1/0/0] mpls te bandwidth 80000 flow-queue te[PE1-Tunnel1/0/0] mpls te reserved-for-binding[PE1-Tunnel1/0/0] mpls te vpn-binding l2vpn vsi vsi1 cir 50000 pir 80000 flow-queue vsi1[PE1-Tunnel1/0/0] mpls te vpn-binding l2vpn vsi vsi2 cir 30000 pir 80000 flow-queue vsi2[PE1-Tunnel1/0/0] mpls te commit


# sysname PE1#mpls lsr-id 1.1.1.9 mpls mpls te mpls rsvp-te mpls te cspf#mpls l2vpn#vsi vsi1 static pwsignal ldp vsi-id 1 peer 2.2.2.9 tnl-policy policy1 diffserv-mode uniform#vsi vsi2 static pwsignal ldp vsi-id 2 peer 2.2.2.9 tnl-policy policy1 diffserv-mode uniform#mpls ldp#mpls ldp remote-peer 2.2.2.9 remote-ip 2.2.2.9#diffserv domain vsi1




Issue 05 (2010-06-01)

8021p-inbound 3 phb af4 green mpls-exp-outbound af2 green map 3#diffserv domain vsi2 ip-dscp-inbound 34 phb af3 green#drop-profile drop1 wred green low-limit 20 high-limit 50 discard-percentage 100# queue-profile te queue-class af3 queue weight 10 drop-profile drop1 queue cir 10000 cbs 125000 pbs 125000 queue-class af4 drop-profile drop1 queue cir 15000 cbs 125000 pbs 125000 queue-class ef drop-profile drop1 queue cir 25000 cbs 125000 pbs 125000# queue-profile vsi1 queue-class af3 queue weight 10 drop-profile drop1 queue cir 5000 cbs 125000 pbs 125000 queue-class af4 drop-profile drop1 queue cir 10000 cbs 125000 pbs 125000 queue-class ef drop-profile drop1 queue cir 15000 cbs 125000 pbs 125000# queue-profile vsi2 queue-class af3 pq drop-profile drop1queue cir 10000 cbs 125000 pbs 125000#interface Pos1/0/0 undo shutdown ip address 100.1.1.1 255.255.255.0 mpls mpls te mpls te max-link-bandwidth 200000 mpls te max-reservable-bandwidth 100000 mpls rsvp-te mpls ldp port-queue af3 wfq weight 10 shaping 10 outbound port-queue af4 wfq weight 15 shaping 15 outbound port-queue ef pq shaping 25 outbound#interface LoopBack1 ip address 1.1.1.9 255.255.255.252#interface Tunnel1/0/0 ip address unnumbered interface LoopBack1 tunnel-protocol mpls te destination 2.2.2.9 mpls te tunnel-id 100 mpls te bandwidth bc0 80000 flow-queue te mpls te reserved-for-binding mpls te vpn-binding l2vpn vsi vsi1 cir 50000 pir 80000 flow-queue vsi1 mpls te vpn-binding l2vpn vsi vsi2 cir 30000 pir 80000 flow-queue vsi2 mpls te commit#interface GigabitEthernet2/0/0 undo shutdown#



7-53

interface GigabitEthernet2/0/0.1 vlan-type dot1q 100 l2 binding vsi vsi1 trust upstream vsi1 trust 8021p#interface GigabitEthernet3/0/0 undo shutdown#interface GigabitEthernet3/0/0.1 vlan-type dot1q 20 l2 binding vsi vsi2 trust upstream vsi2#ospf 1 opaque-capability enable area 0.0.0.0 network 100.1.1.0 0.0.0.255 network 1.1.1.9 0.0.0.0 mpls-te enable#tunnel-policy policy1 tunnel select-seq cr-lsp load-balance-number 1#return

l Configuration file of P# sysname P# mpls lsr-id 3.3.3.9 mpls mpls te mpls rsvp-te mpls te cspf#mpls ldp#diffserv domain default#interface Pos1/0/0 undo shutdown ip address 100.1.1.2 255.255.255.0 mpls mpls te mpls te max-link-bandwidth 200000 mpls te max-reservable-bandwidth 100000 mpls rsvp-te mpls ldp#interface Pos2/0/0 undo shutdown ip address 200.1.1.1 255.255.255.0 mpls mpls te mpls te max-link-bandwidth 200000 mpls te max-reservable-bandwidth 100000 mpls rsvp-te mpls ldp#interface LoopBack1 ip address 2.2.2.9 255.255.255.252#ospf 1 opaque-capability enable area 0.0.0.0 network 100.1.1.0 0.0.0.255 network 200.1.1.0 0.0.0.255 network 3.3.3.9 0.0.0.0 mpls-te enable




Issue 05 (2010-06-01)

#return

l Configuration file of PE2# sysname PE2# mpls lsr-id 2.2.2.9 mpls mpls te mpls rsvp-te mpls te cspfmpls l2vpn#vsi vsi1 static pwsignal ldp vsi-id 1 peer 1.1.1.9#vsi vsi2 static pwsignal ldp vsi-id 2 peer 1.1.1.9#mpls ldp#mpls ldp remote-peer 1.1.1.9 remote-ip 1.1.1.9#interface POS1/0/0 undo shutdown ip address 200.1.1.2 255.255.255.0 mpls mpls te mpls te max-link-bandwidth 200000 mpls te max-reservable-bandwidth 100000 mpls rsvp-te mpls ldp#interface LoopBack1 ip address 2.2.2.9 255.255.255.252#interface GigabitEthernet2/0/0 undo shutdown #interface GigabitEthernet2/0/0.1 vlan-type dot1q 100 l2 binding vsi vsi1#interface GigabitEthernet3/0/0 undo shutdown #interface GigabitEthernet3/0/0.1 vlan-type dot1q 20 l2 binding vsi vsi2#ospf 1 opaque-capability enable area 0.0.0.0 network 200.1.1.0 0.0.0.255 network 2.2.2.9 0.0.0.0 mpls-te enable#return

l Configuration file of CE1# sysname CE1#interface GigabitEthernet1/0/0



7-55

undo shutdown#interface GigabitEthernet1/0/0.1 vlan-type dot1q 100 ip address 10.1.1.1 255.255.255.0#return







Issue 05 (2010-06-01)

A Glossary

This appendix describes the glossaries mentioned in the manual.

A

A kind of serviceproviding QoSsimilar to that ofBE withoutnetworkoverload.

Even if a network is overloaded (namely, during the network congestion),it can guarantee low delay and low packet loss ratio for some applications.

C

congestion A symptom of low service rate resulting from the scarcity of networkresource.

D

drop profile A set of parameters specifying the policy for discarding packets.

F

first in first out(FIFO)

A mechanism in which the router allocates resources for forwardingaccording to the arrival time of the packets. All the packets share theresources such as the network and the bandwidth for the router accordingto their arrival time.

G

guaranteedservice

A kind of service providing guaranteed bandwidth and limiting delay tosatisfy the requirement of an application.

Q

quality of service A technology estimating the packet forwarding capability of a network.

queue profile A queue parameter set specifying the policies for processing inboundpackets and outbound packets.

Quidway ME60 Multiservice Control GatewayConfiguration Guide - QoS A Glossary


A-1

QoS scheduling A measure taken by the edge convergence device according to suchfactors as the topology and the network processing capability to maketraffic entering the access network become stable, and thus congestioncan be avoided.

QoS profile An aggregation of QoS scheduling parameters.

R

redirection A method that transmits packets to the specified next hop address or nextLSP label, rather than forwarding the packets by using the route of thepackets.

S

schedulingprofile

A scheduler group specifying the packet scheduling policy used by theschedulers.

scheduling style The algorithm used to schedule the packets in different queues.

service levelagreements(SLA)

A service agreement signed between customers, including individual,enterprise and adjacent ISPs, and service providers.

T

traffic policy A policy combining the traffic behaviors and the QoS behaviors.

traffic policing A traffic control policy that restricts the use of traffic and resource bymonitoring the traffic specification.

A GlossaryQuidway ME60 Multiservice Control Gateway


A-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-06-01)

B Acronyms and Abbreviations

This appendix describes the acronyms and abbreviations mentioned in the manual.

A

AAA Authentication, Authorization and Accounting

ACL Access Control List

AF Assured Forwarding

B

BA Behavior Aggregate

BE Best-Effort

BRAS Broadband Remote Access Server

C

CAR Committed Access Rate

CBS Committed Burst Size

CIR Committed Information Rate

CoS Class of Service

CPU Central Processing Unit

CSCP Class Selector Code Point

D

DS Differentiated Service

DSCP Differentiated Services Code Point

DSL Digital Subscriber Line

DSLAM Digital Subscriber Line Access Multiplexer

Quidway ME60 Multiservice Control GatewayConfiguration Guide - QoS B Acronyms and Abbreviations


B-1

DSG Dynamic Service Gateway

E

EBS Excess Burst Size

EF Expedited Forwarding

F

FIFO First In First Out

FTP File Transfer Protocol

G

GTS Generic Traffic Shaping

I

IETF Internet Engineering Task Force

IP Internet Protocol

ISP Internet Service Provider

L

LAN Local Area Network

LER Labeled Edge Router

LSP Label Distribution Path

LSR Label Switched Router

M

MAC Media Access Control

MIB Management Information Base

MPLS Multiprotocol Label Switching

P

PBS Peak Burst Size

PE Provider Edge

PHB Per-Hop Behaviors

PIR Peak Information Rate

PVC Pre-defined virtual connection

Q

B Acronyms and AbbreviationsQuidway ME60 Multiservice Control Gateway


B-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-06-01)

QoD QoS on Demand

QoS Quality of Service

R

RED Random Early Detection

RFC Requirement for Comments

RSVP Resource Reservation Protocol

S

SLA Service Level Agreement

SLS Service Level Specification

SP Strict Priority

srTCM A Single Rate Three Color Marker

T

TCA Traffic Conditioning Agreement

TCP Transmission Control Protocol

TCS Traffic Conditioning Specification

ToS Type of Service

trTCM A Two Rate Three Color Marker

U

UDP User Datagram Protocol

URPF Unicast Reverse Path Forwarding

V

VC Virtual Circuit

VLAN Virtual LAN

VoIP Voice over IP

VP Virtual Path

VPN Virtual Private Network

W

WFQ Weighted Fair Queue

WRED Weighted Random Early Detection

WRR Weighted Round Robin

Quidway ME60 Multiservice Control GatewayConfiguration Guide - QoS B Acronyms and Abbreviations


B-3

WWW World Wide Web

B Acronyms and AbbreviationsQuidway ME60 Multiservice Control Gateway


B-4 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 05 (2010-06-01)

00479812-ME60 Configuration Guide - QoS(V100R006C05_05)

Documents

Transcript of 00479812-ME60 Configuration Guide - QoS(V100R006C05_05)