SJ-20101118091715-013-Unitrans ZXCTN 620063006220 (V2.00) MML Configuration Guide (QoS)_405789.pdf

ZXCTN 6200/6300/6220MML Configuration Guide (Qos)

Version: V2.00

ZTE CORPORATIONNO. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: +86-755-26771900Fax: +86-755-26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATIONCopyright 2011 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or

distribution of this document or any portion of this document, in any form by any means, without the prior written

consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by

contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE

CORPORATION or of their respective owners.

This document is provided as is, and all express, implied, or statutory warranties, representations or conditions

are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,

title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the

use of or reliance on the information contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications

covering the subject matter of this document. Except as expressly provided in any written license between ZTE

CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter

herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.2 2011-12-13 Modify the document version.

R1.1 2011-11-13 Modify the document name and preface.

R1.0 2011-09-13 ZXCTN 6200/6300/6220(V2.00) Command Manual (QoS Volume)

first Issued.

Serial Number: SJ-20101118091715-013

Publishing Date: 2011-12-13(R1.2)

Table of ContentsAbout This Manual ......................................................................................... I

Chapter 1 Priority Mapping Configuration ............................................... 1-1

1.1 Priority Mapping Qverview .................................................................................. 1-1

1.2 2.2Configuring DS Domain ................................................................................. 1-2

1.3 Inquiring DS Domain .......................................................................................... 1-3

1.4 Configuration Command Example ....................................................................... 1-3

1.5 Configuration Example of Priority Manpping......................................................... 1-4

1.5.1 802.1P Field Configuration Example.......................................................... 1-4

1.5.2 Pipe Mode Configuration Example............................................................. 1-5

1.6 Troubleshooting of Priority Mapping..................................................................... 1-6

1.6.1 2.6.1 Network Topology ............................................................................ 1-6

1.6.2 2.6.2 Fault Analysis .................................................................................. 1-7

1.6.3 2.6.3 Fault Handling ................................................................................. 1-8

Chapter 2 CAR Configuration.................................................................... 2-1

2.1 Overview ........................................................................................................... 2-1

2.2 3.2 Configuring CAR........................................................................................... 2-1

2.3 3.3 Maintaining CAR........................................................................................... 2-2

2.4 Troubleshooting of CAR...................................................................................... 2-2

2.4.1 3.4.1 Fault Analysis .................................................................................. 2-2

2.4.2 3.4.2 Fault Handling ................................................................................. 2-3

Chapter 3 Configuration of Flow Behavior ............................................. 3-1

3.1 Overview ........................................................................................................... 3-1

3.2 Configuring Flow Queue ..................................................................................... 3-1

3.3 Maintaining Flow Queue ..................................................................................... 3-2

3.4 Configuration Example of Flow Behavior.............................................................. 3-3

3.4.1 Configuring Priority Mark .......................................................................... 3-3

3.4.2 4.4.2 Configure the PQ Queue Dispatching................................................ 3-4

3.4.3 Configuring Shaping ................................................................................. 3-5

3.4.4 4.4.6 Configuring WRED........................................................................... 3-6

3.5 Troubleshooting of Flow Behavior........................................................................ 3-7

3.5.1 4.5.1 Fault Analysis .................................................................................. 3-7

3.5.2 Fault Handling.......................................................................................... 3-8

List of Figure................................................................................................... I

I

List of Table................................................................................................... III

Glossary .........................................................................................................V

II

About This ManualPurpose

This manual is applicable to Unitrans ZXCTN 6200/6300 (ZXCTN 6200/6300 in shorthereinafter).

What Is in This Manual

This manual contains the following chapters:

Chapter Description

Chapter 1, Priority Mapping Configuration Introduces the configuration, maintenance of

Priority Mapping and configuration example, as

well as the fault handling.

Chapter 2, CAR Configuration Introduces the configuration and maintenance of

CAR, and configuration example, as well as the

fault handling.

Chapter 3, Flow Behavior Configuration Introduces the configuration and maintenance of

Flow Behavior, and configuration example, as well

as the fault handling.

Conventions

This document uses the following typographical conventions.

Typeface Meaning

Italics Variables in commands. It may also refers to other related manuals and documents.

Bold Menus, menu options, function names, input fields, option button names, check boxes,

drop-down lists, dialog box names, window names, parameters and commands.

CAPS Keys on the keyboard and buttons on screens and company name.

Constant

width

Text that you type, program codes, filenames, directory names, function names.

[ ] Optional parameters.

{ } Mandatory parameters.

| Separates individual parameter in series of parameters.

I

Typeface Meaning

Danger: Indicates an imminently hazardous situation, which if not avoided, will result in

death or serious injury.

Warning: Indicates a hazard that, if not avoided, could result in serious injuries,

equipment damages or interruptions of major services.

Caution: Indicates a potential hazard that, if not avoided, could result in moderate

injuries, equipment damages or partial service interruption.

Note: Provides additional information about a certain topic.

Tip: Indicates a suggestion or hint to make things easier or more productive for the

reader.

II

Chapter 1Priority MappingConfigurationTable of Contents

Priority Mapping Qverview..........................................................................................1-12.2Configuring DS Domain.........................................................................................1-2Inquiring DS Domain ..................................................................................................1-3Configuration Command Example ..............................................................................1-3Configuration Example of Priority Manpping ...............................................................1-4Troubleshooting of Priority Mapping ...........................................................................1-6

1.1 Priority Mapping QverviewThe priority mapping is an important function of QoS module.

The functions that can be realized with priority mapping are shown below:

l Local congestion managementl Local congestion controlling.

Processable Packet

Packets that can be processed with system priority mapping function are as follow:

l General IP packetsl VLAN packetsl MPLS packets

DS Domain

Priority mapping in system is the DS domain. DS domain is a set which consist of thefollowing two relation tables:

l Packet priorityinternal priority + colorl Internal priority + colorpacket priority

system support ten DS domains:

l Eight mapping relation table for permissive customer configurationl One default mapping relation tablel One 5P3D model mapping relation table

1-1

SJ-20101118091715-013|2011-12-13(R1.2) ZTE Proprietary and Confidential

ZXCTN 6200/6300/6220 MML Configuration Guide (Qos)

Priority Mapping Mode

Service Type Supported Priority Mapping Mode

General L2 service. 8021p mode.

IP network. 8021p and DSCP modes.

MPLS network. 8021p and EXP modes.

VPN-QoS

In system, L2VPN support the VPN-QoS.

VPN-QoS can be configured in vfi, vll, and static tunnel, and the referred customer prioritiesare Vlan Cos of the customer packets.

The handling ways of different PE nodes in different modes are shown in .

Mode Uniform Pipe ShortPipe

Upstream PE ingress

mapping mode.

cos of UserVlan Specified Specified

Upstream PE egress

packet forwarding priority.

cos of inheriting

UserVlan

Specified Specified

Downstream PE ingress

mapping mode.

Exp Exp cos of UserVlan

Downstream PE egress

packet forwarding priority.

Inheriting Exp Invariant Invariant

1.2 2.2Configuring DS DomainUse the following command to create a DS domain.

Step Command Function

1 ZXR10(config)#diffserv-domain Create a DS domain with a specified name, or

enter an existent DS domain.

Use the following command group to define the priority mapping relation of DS domain.


1 ZXR10(config)#diffserv-domain Create a DS domain.

2 ZXR10(config-ds-domain)#8021p-inbound

phb {af1|af2|af3|af4|be|cs6|cs7|ef}

Configure 802.1P inbound PHB

mapping.

3 ZXR10(config-ds-domain)#8021p-outbound

{af1|af2|af3|af4|be|cs6|cs7|ef}{green|red|yellow}ma

p

Configure 802.1P outbound PHB

mapping.

1-2


Chapter 1 Priority Mapping Configuration


4 ZXR10(config-ds-domain)#ip-dscp-inbound

phb {af1|af2|af3|af4|be|cs6|cs7|ef}[gre

en|red|yellow]

Configure DSCP inbound PHB

mapping.

5 ZXR10(config-ds-domain)#ip-dscp-outbound


p

Configure DSCP outbound PHB

mapping.

6 ZXR10(config-ds-domain)#mpls-exp-inbound

phb {af1|af2|af3|af4|be|cs6|cs7|e

f}[green|red|yellow]

Configure Exp inbound PHB mapping.

7 ZXR10(config-ds-domain)#mpls-exp-outbound


p

Configure Exp outbound PHBmapping.

Use the following command to apply DS domain in specified interface.


1 ZXR10(config-[x]gei_x/y)#trust

upstream {| default}

Apply DS domain in specified interface.

2 ZXR10(config-[x]gei_x/y)#trust {8021p

| dscp}

Trust mode binding.

1.3 Inquiring DS DomainUse the following command to inquire the configuration information of DS domain.


1 ZXR10(config)#show diffserv-domain

{word | all | default}

ShowsDS domain configuration information,

and it is configured not to show by default.

2 ZXR10(config)#show diffserv-domain {

reference }

Shows the interfaces binding to the

specified DS domain or all DS domains.

1.4 Configuration Command Example1. Configure a DS domain and name it DS1, and configure the interface xgei_1/1 to trust

8021p mode.ZXR10(config)#diffserv-domain

ZXR10(config-ds-domain)#8021p-inbound 0 phb cs7 green

ZXR10(config-ds-domain)#exit

ZXR10(config)#int xgei_1/1

1-3



ZXR10(config-xgei_1/1)#trust upstream ds1

2. Run the show diffserv-domain all command.ZXR10(config)#show diffserv-domain all

domain 5p3d

domain default

domain ds1

ip-dscp-inbound 0 phb cs7 green

3. Run the show diffserv-domain ds1 command.ZXR10(config)#show diffserv-domain ds1

domain ds1

ip-dscp-inbound 0 phb cs7 green

4. Run the show diffserv-domain reference all command.ZXR10(config)#show diffserv-domain all

[diffserv-domain reference information]

domain-name : 5p3d

Name domain-name : ds1

Name xgei_1/1

5. Delete DS1.ZXR10(config-xgei_1/1)#no trust upstream ds1

ZXR10(config-xgei_1/1)#exit

ZXR10(config)#no diffserv-domain ds1

1.5 Configuration Example of Priority Manpping

1.5.1 802.1P Field Configuration Example

Configuration Description

As shown in Figure 1-1, L2 service pass through , gei_1/1 as the entrance and gei_1/2 asthe exit of the packet. The VLAN priority of packet is required to be modified from 1 to 7.

Figure 1-1 802.1p Field Inheriting Configuration Example

Configuration Method

Mapping relations in the default mapping relation table are as follow:

l For the in direction, external priority 1af1+green.l For the out direction, cs7+greenexternal priority 7.

1-4



If the VLAN priority of packet is required to be modified from 1 to 7, only need to modifythe mapping relation of a direction.

1. Modify the in-direction mapping relation.

In-direction mapping relation modification: 1cs7+green; out-direction use the defaultmapping relation: cs7+green->7.

2. Modify the out-direction mapping relation.

In-direction use the default mapping relation: 1af1+green out-direction mappingrelation modification: af1+green7.

This example use the waymodifying the in-direction mapping relation to make the followingconfiguration.

1. Take gei_1/1 as the entrance interface, and need to configure the in-direction mapping.2. Take gei_1/2 as the exit interface, and need to configure the out-direction mapping.3. Modify the vlan priority of packet, the interface need to bind the 8021p.

Configuration Procedure

ZXR10(config)#diffsev-domain ds1

ZXR10(config-ds-domainiffserv)#8021p-inbound 1 phb cs7 green

ZXR10(config)#interface gei_1/1

ZXR10(config-gei_1/1)#trust upstream ds1

ZXR10(config-gei_1/1)#trust 8021p

Configuration Verification

Configuration verification on

ZXR10(config)#show diffserv-domain all

diffserv-domain 5p3d

diffserv-domain default

diffserv-domain ds1

8021p-inbound 1 phb cs7 green

1.5.2 Pipe Mode Configuration Example


As shown in Figure 1-2, the tester is sending packet with cos 7, which enter via gei_1/1interface on PE1, exit from gei_1/6 on PE2, and the VLAN cos is required to be invariant.

1-5



Figure 1-2 Pipe Mode Configuration Example


Configure the VPN-QoS mode to be Uniform on PE1 and EXP field in packet is Vlan cos.Configure VPN-QoS mode to be ShortPipe on PE2, and Vlan cos of the forwarding packetkeep invariant.


The configuration of PE1:

PE1(config)#vfi pe1_vfi

PE1(config-vfi)#mode vlan 106

PE1(config-vfi)#mpls xconnect pw pe1_pw

PE1(config-vfi)#diffserv-mode uniform

PE1(config)#cip 16384

PE1(config-cip16384)#service-type ethernet gei_1/2 pe1_cmp

PE1(config-cip16384)#xconnect pe1_vfi

The configuration of PE3:

PE3(config)#vfi pe3_vfi

PE3(config-vfi)#mode vlan 106

PE3(config-vfi)#mpls xconnect pw pe3_pw

PE3(config-vfi)#diffserv-mode short-pipe af2 yellow

PE3(config)#cip 16384

PE3(config-cip16384)#service-type ethernet gei_1/5pe3_cmp

PE3(config-cip16384)#xconnect pe3_vfi

1.6 Troubleshooting of Priority Mapping

1.6.1 2.6.1 Network TopologyNetwork Topology is shown in Figure 1-3, and the configuration is as follow.

Figure 1-3 Network Topology of Handling a Priority Inheriting Fault

1-6



SW1(config)#diffsev-domain ds_sw1

SW1(config-diffserv-domain)#8021p-inbound 1 phb cs7 green

SW1(config)#interface gei_1/1

SW1(config-gei_1/1)#trust upstream ds_sw1

SW1(config-gei_1/1)#trust 8021p

SW2(config)#diffsev-domain ds_sw2

SW2(config-diffserv-domain)#8021p-outbound cs7 green map 1

SW2(config)#interface gei_1/4

SW2(config-gei_1/4)#trust upstream ds_sw2

SW2(config-gei_1/4)#trust 8021p

P1

Configure a DS, and one of themapping relation is: external priority 1 represent the internalpriority cs7.

P2

Configure a DS, and one of the mapping relation is: internal priority cs7+green representthe external priority 1.

1.6.2 2.6.2 Fault Analysis

Expecting Result

After mapping through the in-interface of P1 and out-interface of P2, the priority of packetis 1.

Testing Result

On the interface gei_1/4 of P2, testing result of packet priority is 7, which is inconsistentwith the expecting result.

Fault Analysis

1. Priority of packet received by in-interface gei_1/1 on P1 is 1. According to the DSbound to the interface, it represent the internal priority cs7+green.

2. There is not any DS bound to the out-interface on P1, and according to the default DSdomain mapping table, cs7+green represent the external priority 7.

3. Priority of packet received by in-interface gei_1/3 on P2 is 7. There is no specifiedmapping table of priority 7 in gei_1/3, according to the default DS domain mappingtable, priority mapping of packet is cs7.

4. Priority of packet received by out-interface gei_1/4 on P2 is 7. There is no specifiedmapping table of priority 7 in gei_1/3, according to the default DS domain mappingtable, priority mapping of packet is cs7.

5. Priority of packet sent by out-interface gei_1/4 on P2 is 7 rather than 1.

1-7



1.6.3 2.6.3 Fault Handling

Tip:

Take the 802.1p priority mapping shown in Figure 1-4 as an example in this section, andothers can refer to this handling procedure.

Figure 1-4 Flow to Handle Priority Mapping Fault

Handling Method

The handling procedure of a priority inheriting fault is shown below:

1. Shows whether the DS domain configuration is correct.ZXR10(config)#show diffserv-domain all

diffserv-domain 5p3d

diffserv-domain default

diffserv-domain ds1

8021p-inbound 0 phb cs7 green

2. Shows whether the configured DS domain is used in the specified interface.ZXR10(config)#show diffserv-domain reference all

[diffserv-domain reference information]

diffserv-domain-name : 5p3d

Type Name

diffserv-domain-name : ds1

Type Name

interface xgei_1/1

If the fault still persists, contact the technical support engineer for help.

1-8


Chapter 2CAR ConfigurationTable of Contents

Overview....................................................................................................................2-13.2 Configuring CAR ..................................................................................................2-13.3 Maintaining CAR ..................................................................................................2-2Troubleshooting of CAR .............................................................................................2-2

2.1 OverviewCAR Committed Access Rate is an application of traffic policing to restrict the traffic of acertain type of packets, for example, HTTP packets cannot occupy more than 50% of thenetwork bandwidth.

CAR consist of the following two parts:

l Packet classification

Packet classification is based on:

802.1p

IP priority

DSCP

MPLS-EXP

l Traffic restricting

Traffic restricting use the token pail algorithm.

In , CAR is classified as below:

l Interface restrictingl Traffic restricting

2.2 3.2 Configuring CARUse these commands to configure CAR.


1 ZXR10(config)#interface

Enter the interface configuration mode.

2 ZXR10(config-[x]gei_x/y)#qos car

inbound cir cbs

In the interface configuration mode, configure

the traffic policing in the input direction.

2-1



Use these commands to delete CAR SET.


1 ZXR10(config)#interface Enter the interface configuration mode.

2 ZXR10(config-[x]gei_x/y)#no qos car

inbound

In the interface configuration mode, delete

the CAR.

Use these commands to configure traffic restricting.


1 ZXR10(config)#qos car acl {|}

group-id mode {blind | aware} cir

cbs pir pbs

Configure CAR based on

ACL.

2 ZXR10(config)#no qos car acl {|}

group-id

Delete CAR based on ACL.

2.3 3.3 Maintaining CARStep Command Function

1 ZXR10(config)#show qos Check QOS configuration result, and there is the CAR

based on ACL.

2.4 Troubleshooting of CAR

2.4.1 3.4.1 Fault Analysis

Fault Symptom

l Actual restricting value is not consistent with the configured one.l The configuration does not take effect.

Fault Analysis

1. Check whether the interface is configured correctly.

a. Make sure CAR is configured on the correct interface.

b. Make sure CAR can work properly on the interface.

2. Check whether the configured interface support the CAR policy.3. Check whether CAR take the correct action.

2-2


Chapter 2 CAR Configuration

2.4.2 3.4.2 Fault HandlingCAR fault handling flow is shown in Figure 2-1.

Figure 2-1 Flow to Handle CAR Fault

Handling Procedure

The procedure to handle a CAR fault is to check whether CAR is configured in the correctinterface:

ZXR10(config)#show running-config -interface gei_1/3

qos

interface gei_1/3

rate-limit input localport cir 10000 cbs 15000

$

!

!

interface gei_1/3

no shutdown

ip address 125.1.1.1 255.255.255.0

!

!

ZXR10(config)#


2-3



This page intentionally left blank.

2-4


Chapter 3Configuration of FlowBehaviorTable of Contents

Overview....................................................................................................................3-1Configuring Flow Queue.............................................................................................3-1Maintaining Flow Queue.............................................................................................3-2Configuration Example of Flow Behavior ....................................................................3-3Troubleshooting of Flow Behavior ..............................................................................3-7

3.1 OverviewThe business (service) refers to data packets in a network. Before providing end-to-endQoS for a service, the system needs to classifies, and marks or colors the packetsaccessed to the network. This ensures that special data packets are processeddifferentially.

Flow behavior consist of:

l Packet taggingl Traffic policing and shapingl Congestion avoidancel Congestion management

3.2 Configuring Flow QueueStep Command Function

1 ZXR10(config)#flow-queue Create a flow-queue or enter an already

created one.

2 ZXR10(config-flow-queue)#queue

[{ pq | wrr |

dwrr }][shaping cir

pir ][flow-wred

[]|flow-taildrop[]]

Configure the dispatching parameter,

traffic shaping parameter, and WRED

discarding parameter of the queue.

3 ZXR10(config)#flow-wred Create a WRED template.

Enter an already created WRED

template.

3-1




4 ZXR10(config-[x]gei_x/y)#flow-queue

Apply the packet classification on the

interface.

The parameter of the steps are described in the table below.

Parameter Description

cos-value Indicate the service level, .

pq Strict priority dispatching.

shaping Configure the shaping behavior of the flow-queue.

cir Indicate the committed information rate, the value ranges from 1 to

32000000.

pir Indicate the peak information rate, the value ranges from 64 to

32000000.

flow-taildrop

Indicate the name of the applied tail-drop template.

flow-wred Indicate the name of the applied wred template.

3.3 Maintaining Flow Queue

ZXR10(config)#show flow-queue {brief |{detail {all |}|{reference |< flow-queue-name >| all }}

Shows the flow-queue.

The examples to use the command are shown below.

1. Create an empty flow-queue.ZXR10(config)#flow-queue fq1

ZXR10(config-flow-queue)#exit

ZXR10(config)#int gei_3/1

ZXR10(config-gei_3/1)#flow-queue fq1

2. Shows the interface bound to the flow-queue.ZXR10(config)#show flow-queue reference all

[flow-queue reference information]

flow-queue-name : fq1

Type Name

interface gei_3/1

3. Shows the details of a flow-queue named fq1.ZXR10(config)#show flow-queue detail fq1

[flow-queue-template detail information]

total number : 1

3-2


Chapter 3 Configuration of Flow Behavior

Table Description:

Sche-Arith ------> Schedule Arithmetic

U-Weight --------> User configure schedule weight

Shp-Cir ---------> Shaping CIR value, unit: kbps

Shp-Cbs ---------> Shaping CBS value, unit: kbyte

Shp-Pir ---------> Shaping PIR value, unit: kbps

Shp-Pbs ---------> Shaping PBS value, unit: kbyte

flow-queue-template-name : fq1

Sche-Arith U-Weight Shp-Cir Shp-Cbs Shp-Pir Shp-Pbs Drop-Arith

Tip:

If there is no configuration in a flow-queue, it will be shown as an empty template.

3.4 Configuration Example of Flow Behavior

3.4.1 Configuring Priority Mark


Map a data flow (source IP: 10.1.1.0) to be a red packet (local priority: af1).


1. Configure the ACL rules in advance, and filter the required traffic.2. Associate the priority mark and ACL.3. Modify the mapping value of the traffic matching the ACL.


1. Create an extended ACL.ZXR10(config)#acl extended number 100

ZXR10(config-ext-acl)#permit ip 10.1.1.0 0.0.0.0 any

ZXR10(config-ext-acl)#exit

2. Configure the corresponding priority-mark.ZXR10(config)#priority-mark 100 group-id 5 service-class af1 color red

3. Bind ACL 100 to the specified interface.


Use the show qos command to view the configured priority-mark.

ZXR10(config)#show qos

priority-mark 100 rule-id 5 service-class af1 color red

3-3



3.4.2 4.4.2 Configure the PQ Queue Dispatching


1. The configuration should be ranged from higher priority to the lower one.2. Restrict the traffic of the higher priority properly, to leave a certain sending opportunity

to the lower priority.


1. Create a flow-queue.ZXR10(config)#flow-queue fq2

2. Configure the dispatching mode in flow-queue.ZXR10(config-flow-queue)#queue cs7 pq

ZXR10(config-flow-queue)#queue cs6 pq

ZXR10(config-flow-queue)#queue ef pq

ZXR10(config-flow-queue)#queue af4 pq




3. Bind an interface in flow-queue.ZXR10(config)#int gei_3/1



Verify the configured PQ queue dispatching.

1. Shows the interface bound in the flow-queue.ZXR10(config)#show flow-queue reference all



Type Name

interface gei_3/1

2. Shows the details of a certain flow-queue.ZXR10(config)#show flow-queue detail fq2


total number : 1

Table Description:








3-4



Sche-Arith U-Weight Shp-Cir Shp-Cbs Shp-Pir Shp-Pbs Drop-Arith

cs7 pq N/A N/A N/A N/A N/A Default

cs6 pq N/A N/A N/A N/A N/A Default

ef pq N/A N/A N/A N/A N/A Default

af4 pq N/A N/A N/A N/A N/A Default




be pq N/A N/A N/A N/A N/A Default

3.4.3 Configuring Shaping


1. Shaping of the queue, combined with the PQ, can restrict the traffic of higher priorityin PQ queue, and make it possible to send the traffic of lower priority.

2. Burst size of shaping is burst traffic permitted to pass through rather than the size ofbuffer memory. The packets not sent in real-time are buffered in the queue, waitingfor a permitting condition.

3. Shaping of the current version only supports cir and pir, but not supports cbs and pbs.


l cs7 queue configure shaping, cir=200Mbpscbs=2000bytes.l cs6 queue configure shaping, cir=100Mbps, cbs=3000bytes.


1. Create a flow-queue.ZXR10(config)#flow-queue fq5

2. Configure dispatching mode in flow-queue.ZXR10(config-flow-queue)#queue cs7 pq shaping cir 200000 pir 2000

ZXR10(config-flow-queue)#queue cs6 pq shaping cir 100000 pir 3000


3. Bind an interface to the flow-queue.ZXR10(config)#int gei_3/1



1. Shows the interface Bound to the flow-queue.ZXR10(config)#show flow-queue reference all



Type Name

interface gei_3/1

3-5





total number : 1

Table Description:








Sche-Arith U-Weight Shp-Cir Shp-Pir Drop-Arith

cs7 pq N/A 200000 N/A Default

cs6 pq N/A 100000 N/A Default

3.4.4 4.4.6 Configuring WRED


1. When configuring WRED, set a maximum and a minimum thresholds. When theaverage queue length exceeds the minimum threshold, WRED start to discarddata packets by a certain probability. When the average queue length exceeds themaximum threshold, the packets arriving posteriorly will be discarded.

2. WRED is intended to preserve the length of queue between the minimum and themaximum thresholds.


1. Create a flow-wred template and name it fw1. Configure the parameters of threecolors.

2. Configure fw1 to the flow-queue.


Tip:

It is supposed that there is already a flow-queue template named fq1 before configuration.

There is a flow-queue template at present.

1. Create a wred template and configure the wred.ZXR10(config)#flow-wred fw1

ZXR10(config-flow-wred)#color green low-limit 10 high-limit 70 discard-percentage 10

3-6



ZXR10(config-flow-wred)#color yellow low-limit 15 high-limit 80 discard-percentage 15

ZXR10(config-flow-wred)#color red low-limit 20 high-limit 90 discard-percentage 20

ZXR10(config-flow-wred)#exit

2. Quote the wred template in flow-queue.ZXR10(config)#flow-queue fq1

ZXR10(config-flow-queue)#queue ef flow-wred fw1


1. Shows the usage of wred.ZXR10(config)#show flow-wred brief

[flow-wred brief information]

total number : 1

Flow-Wred-Name Is-Used

fw1 yes

2. Shows the configuration details in flow-queue.ZXR10(config)#show flow-queue d fq1


total number : 1

Table Description:







cs7 pq N/A N/A N/A Default


ef wfq 4 N/A N/A wred-fw1

af4 wfq 2 N/A N/A Default



3.5 Troubleshooting of Flow Behavior

3.5.1 4.5.1 Fault AnalysisAfter configuring the flow behavior, some errors may be prompted as follow:

1. The priority-mark does not take effect after configuration.

Fault analysis: check whether the corresponding acl was bound the interface.

2. After configuring some queue, it shows the following information:The configuration cannot be supported!

ZXR10(config)#flow-queue test

ZXR10(config-flow-queue)#queue ef pq

3-7



%Error 5667: The configuration cannot be supported!

Fault analysis: Queue dispatching need to configure the queue from the highest to thelowest priority, not to configure the intermediate queue directly.

3.5.2 Fault HandlingCheck and handle a fault according to the following steps:

1. Shows the interface bound to the flow-queue.ZXR10(config)#show flow-queue reference all



Type Name

interface gei_3/1



total number : 1

Table Description:











ef pq N/A N/A N/A Default

af4 pq N/A N/A N/A Default




be pq N/A N/A N/A Default


3-8


List of FigureFigure 1-1 802.1p Field Inheriting Configuration Example ......................................... 1-4

Figure 1-2 Pipe Mode Configuration Example ........................................................... 1-6

Figure 1-3 Network Topology of Handling a Priority Inheriting Fault........................... 1-6

Figure 1-4 Flow to Handle Priority Mapping Fault...................................................... 1-8

Figure 2-1 Flow to Handle CAR Fault........................................................................ 2-3

I

List of Figure


List of Table

III

List of Table


GlossaryCAR- Committed Access Rate

DSCP- Differentiated Services Code Point

QoS- Quality of Service

V

About This ManualChapter 1 Priority Mapping Configuration1.1 Priority Mapping Qverview1.2 2.2Configuring DS Domain1.3 Inquiring DS Domain1.4 Configuration Command Example1.5 Configuration Example of Priority Manpping1.5.1 802.1P Field Configuration Example1.5.2 Pipe Mode Configuration Example

1.6 Troubleshooting of Priority Mapping1.6.1 2.6.1 Network Topology1.6.2 2.6.2 Fault Analysis1.6.3 2.6.3 Fault Handling

Chapter 2 CAR Configuration2.1 Overview2.2 3.2 Configuring CAR2.3 3.3 Maintaining CAR2.4 Troubleshooting of CAR2.4.1 3.4.1 Fault Analysis2.4.2 3.4.2 Fault Handling

Chapter 3 Configuration of Flow Behavior 3.1 Overview3.2 Configuring Flow Queue3.3 Maintaining Flow Queue3.4 Configuration Example of Flow Behavior3.4.1 Configuring Priority Mark3.4.2 4.4.2 Configure the PQ Queue Dispatching3.4.3 Configuring Shaping3.4.4 4.4.6 Configuring WRED

3.5 Troubleshooting of Flow Behavior3.5.1 4.5.1 Fault Analysis3.5.2 Fault Handling

List of FigureList of TableGlossary

SJ-20101118091715-013-Unitrans ZXCTN 620063006220 (V2.00) MML Configuration Guide (QoS)_405789.pdf

Documents

Transcript of SJ-20101118091715-013-Unitrans ZXCTN 620063006220 (V2.00) MML Configuration Guide (QoS)_405789.pdf