Hqos CX600

Technical Literature
Hierarchical Quality of Service in CX600
Huawei Technologies Co., Ltd.
Table of Contents
1 QoS Policy Deployment................................................................................................................ 2 1.1 Deploy of MPLS DiffServ PIPE............................................................................................. 2 1.2 Service Mapping ................................................................................................................... 3 1.3 An Example........................................................................................................................... 3 2 Implementation .............................................................................................................................. 5 2.1 Understanding H-QoS in CX600........................................................................................... 5 2.1.1 Upstream H-QoS........................................................................................................ 5 2.1.2 Downstream H-QoS ................................................................................................... 6 2.2 Configuration Example ......................................................................................................... 8 2.2.1 General configuration................................................................................................. 8 2.2.2 Residential Services................................................................................................. 10 2.2.3 Business Services QinQ .......................................................................................... 12 2.2.4 Business Services dot1p.......................................................................................... 13
Copyright 2007 Huawei Technologies Co., Ltd. All Rights Reserved http://datacomm.huawei.com

Abstract: Hierarchical Quality of Service can control the bandwidth of each service or the total bandwidth of multiple services to guarantee the QoS on the access side. Different from static queue scheduling, the controller for queue scheduling in H-QoS can be configured dynamically. It is an important technical feature for Huawei Metro Services Platform CX600. This technical literature firstly describes QoS policy in access layer of Metro Area Network, and further discusses H-QoS of CX600 in detail in second part. At last, it gives some real configuration examples. Key words: Metro Services Platform, QoS, H-QoS, CX600, QinQ, DiffServ, MPLS
1 QoS Policy Deployment

1.1 Deploy of MPLS DiffServ PIPE
The Link between DSLAM/Switch and MSP is demarcation point between metro and access. The QoS policy is enforced in this point only as shown in Figure 1-1. Inside of metro node, only MPLS DiffServ Pipe tunneling mode is deployed.
Figure 1-1 QoS Policy Enforcement Point With MPLS DiffServ Pipe tunneling mode, the Operator can use its own DiffServ service-mapping scheme and without inspect or touch the DiffServ code carried by user packet. The benefits of Pipe tunneling mode is that Operator can schedule users packet based on agreed SLA other than users DSCP bits in packet because the DSCP bits in users packet cannot be controlled by operator. The node within the metro schedules the packet based PHB is very scalable and efficient.
1.2
Service Mapping
Following Figure 1-2 is default-mapping relationship between DSCP to EXP. In the MPLS based metro node, we also use this default mapping.
Figure 1-2 802.1p, MPLS EXP and DiffServ Code Mapping The EXP bits can present 8 class of traffic. We assign this class to different service traffic as shown in Table 1-1. Class 7 and 6 is used by network itself. The class 5 is used by VoIP/TDM and using the Expedite Forwarding. The Class 4 is used for Video Application with Assured Forwarding. The Class 3/2/1 is used for business data and service gold/silver/bronze service correspondingly. The internet traffic is mapped to class 0 with Best Effort Forwarding.
Table 1-1 DiffServ Service Mapping
Class 7 6 5 4 3 2 1 0
Description control protocol VoIP/TDM Video Data Gold Data Silver Data Bronze Internet
Content CS7 CS6 EF AF4 AF3 AF2 AF1 BE
1.3
An Example
Following Figure 1-3 the typical scenario for above mentioned QoS enforcement. The DSLAM is attached to the GE0/0/0 of R1. The VLAN planning in DSLAM as following For residential subscriber, per service per VLAN scheme is used. VLAN 2 is used for HSI VLAN 3 is used for VoIP/VoBB VLAN 4 is used for IPTV/VoD unicast traffic
3
VLAN 5 is used for IPTV/VoD multicast traffic
Figure 1-3 QoS Policy Composite View There are two type business customers. The user has their own VLAN tags (VLAN 3 for VoIP, VLAN 10 for data). In addition, DSLAM pre-pend a VLAN tag 1001 to present this specific user. The SLA for this user we assume is gold. The user has not its won VLAN tags. The DSLAM insert a VLAN tag 1002 to present this specific user. The user has three type of traffic that is indicated by 802.1p bits. The data service of this user is class Silver by SLA. Only business data can be mapped to three different service classes according to SLA (gold/silver/bronze). The triple play services, no matter residential or business, are mapped to their service dedicate class as defined above. Table 1-2 gives a design demo.
Table 1-2 QoS Parameter for Different Services Traffic income Inner/outer tag 802.1p bits Policy Enforcement Service CIR(In/out) PIR(in/out) EXP
2, single tag 3, single tag 4, single tag 5, single tag 3/1001 10/1001 1002, single tag 1002, single tag 1002, single tag
any any any any any any 5 2 0
internet VoIP/TDM Video Video VoIP/TDM Data Gold VoIP/TDM Data Silver Internet
0 100M 200M 100M 50M 100M 50M 100M 0
300M 100M 200M 100M 50M 200M 50M 400M 100M
0 5 4 4 5 3 5 2 0
Next chapter gives detailed implementation.
2 Implementation
2.1 Understanding H-QoS in CX600
H-QoS can control the bandwidth of each service or the total bandwidth of multiple services to guarantee the QoS on the access side. Different from static queue scheduling, the controller for queue scheduling in H-QoS can be configured dynamically. The hierarchy of the controllers can also be re-set. A controller of the higher level controls the total bandwidth of a group of controllers of the lower lever, and assigns the CIR and PIR for them based on their level and weight. Using multi-level controllers, H-QoS can control the total bandwidth of multiple queues for different services and thus controls the total QoS of one or more kinds of services. For example, the total bandwidth of all users in a building is 100 Mbit/s. The controllers can be used to control the bandwidth resources in order that the bandwidth is fully shared and the QoS of each user is guaranteed. The line card CX600 provides five levels of scheduling modes for upstream H-QoS and another five levels for downstream H-QoS.
2.1.1 Upstream H-QoS

Upstream H-QoS scheduling falls into five levels: flow - user user group target blade class. See Figure 2-1. The each line card of CX600 supports 24k upstream FQs. FQ is a kind of entity queue and is used to store the data of each flow temporarily. A delay occurs when the data goes into or leaves the queue. You can set the scheduling weight and shaping value for each FQ. Each FQ can belong to only one SQ. The each line card of CX600 supports 3K upstream SQ. SQ is a kind of virtual queue and it does not store data. Therefore, no delay occurs for data going into or leaving the SQ. The line card of CX600 supports 1K upstream GQ. GQ is a kind of virtual queue. You can set the shaping value for each GQ. GQ is used to only limit the rate of traffic. One GQ can contain multiple CQs. The line card of CX600 supports 64 upstream target blades (TB), which fall into four classes. The line card of CX600 supports 260 upstream CQs of which 256 queues are for unicast traffic and the other 4 queues are for multicast traffic.

Flow Queue Packet
FQ
COS3 WFQ UC RR MC
MC UC TB0 ...
WFQ
Figure 2-1 Upstream Scheduling
2.1.2 Downstream H-QoS

Downstream H-QoS scheduling also falls into five levels: flow, user, user group, and class and destination port. See Figure 2-2. The line card of CX600 supports 24k downstream FQs. FQ is a kind of entity queue and is used to store the data of each flow temporarily. A delay occurs when the data goes into or leaves the queue. You can set the scheduling weight and shaping value for each FQ. Each FQ can belong to only one SQ. The line card of CX600 supports 3k downstream SQ. SQ is a kind of virtual queue and it does not store data. Therefore, no delay occurs for data going into or leaving the SQ. Each SQ corresponds to eight FQs. You can configure one to eight FQs for each SQ. The FQs of each SQ shares the
...
UC TB63
...
...
... ... SP/ WFQ SQ SHVC shaping MC
shaping
Level-5
Level-4
Subscriber
Level-3
COS0 MC UC RR WFQ
UC TB0 ... UC TB63
Level-2
Level-1
bandwidth of the SQ. Each SQ corresponds to one user. You can set the CIR and PIR for the SQ. Each SQ can belong to only one GQ. The line card of CX600 supports 1K downstream GQ. GQ is a kind of virtual queue. You can set the shaping value for each GQ. GQ is used to only limit the rate of traffic. One GQ can contain multiple CQs. The line card of CX600 supports two target port (TP) modes: 64 TP and each TP have 4 CQs; 32 TP and each TP has 8 CQs. The default mode is 32 TP of eight-classes.The line card of CX600 supports 256 downstream CQs. Each physical port can have eight CQs. You can set the CIR and PIR for the CQ.

Flow Queue Packet
FQ
COS0
COS1
EF
TP31/63 RR
Figure 2-2 Downstream Scheduling
2.2
2.2.1
Configuration Example
General configuration
Here we define remark policy based on Figure 1-3 definition. The policy is always defined as classifier/behavior pair. The services are present by VLAN tag in our example, and we create sub
Copyright 2007 Huawei Technologies Co., Ltd. All Rights Reserved http://datacomm.huawei.com 8
...
...
... ... SP/ WFQ SQ SHVC shaping AF4 AF3 AF2 WFQ shaping TP0
shaping
Level-5
Level-4
Subscriber
Level-3
AF1
BE
Level-2
shaping
Level-1
interface based VLAN tag, so we simply use the match any for VLAN tag based sub interface to classify the traffic. As shown in following. # traffic classifier internet operator or if-match any traffic classifier bronze operator or if-match any traffic classifier Silver operator or if-match any traffic classifier gold operator or if-match any traffic classifier iptv operator or if-match any traffic classifier voiptdm operator or if-match any # traffic behavior be remark mpls-exp 0 traffic behavior af1 remark mpls-exp 1 traffic behavior af2 remark mpls-exp 2 traffic behavior af3 remark mpls-exp 3 traffic behavior af4 remark mpls-exp 4 traffic behavior ef remark mpls-exp 5 traffic behavior dot1paf4 remark dot1p 4 # traffic policy internetpolicy classifier internet behavior be traffic policy bronzepolicy classifier bronze behavior af1 traffic policy silverpolicy classifier silver behavior af2 traffic policy goldpolicy classifier gold behavior af3 traffic policy iptvpolicy classifier iptv behavior af4
traffic policy voiptdmpolicy classifier voiptdm behavior ef traffic policy mcastpolicy classifier iptv behavior dot1paf4 # interface GigabitEthernet0/0/0 mode user-termination #
2.2.2 Residential Services

Figure 2-3 and Table 2-1 gives the residential service VLAN planning and QoS policy requirement and followed with configuration.
Figure 2-3 Residential QoS Demo

2, single tag 3, single tag 4, single tag 5, single tag #
any any any any
Internet VoIP/TDM Video Video
0 100M 200M 100M
300M 100M 200M 100M
0 5 4 4
interface GigabitEthernet0/0/0.2 control-vid 2 dot1q-termination VLAN-group 1 user-queue cir 0 pir 300000 inbound user-queue cir 0 pir 300000 outbound # dot1q termination vid 2 VLAN-group 1
l2 binding vsi Site1-DSLAM-HSI traffic-policy internetpolicy inbound # interface GigabitEthernet0/0/0.3 control-vid 3 dot1q-termination VLAN-group 1 user-queue cir 100000 pir 100000 inbound user-queue cir 100000 pir 100000 outbound # dot1q termination vid 3 VLAN-group 1 ip binding vpn-instance VoIP-VPN ip address 10.2.1.254 255.255.255.0 traffic-policy voiptdmpolicy inbound # interface GigabitEthernet0/0/0.4 control-vid 4 dot1q-termination VLAN-group 1 user-queue cir 200000 pir 200000 inbound user-queue cir 200000 pir 200000 outbound # dot1q termination vid 4 VLAN-group 1 ip binding vpn-instance IPTV-VPN ip address 10.3.1.254 255.255.255.0 traffic-policy iptvpolicy inbound # interface GigabitEthernet0/0/0/0.5 control-vid 5 dot1q-termination VLAN-group 1 user-queue cir 100000 pir 100000 inbound user-queue cir 100000 pir 100000 outbound # dot1q termination vid 5 VLAN-group 1 ip address 203.1.1.1 255.255.255.0 traffic-policy dot1paf4 outbound igmp enable igmp version 3 pim sm #
11
2.2.3
Business Services QinQ
Some business user has their VLAN tag planning. A VLAN tag pre-pend by operator as identifier of user. Therefore, traffic of this type of user has double tag and feed to the network, CX600 series can terminate the double tag and create sub interface based on it, H-QoS policy can enforce to sub-interface simultaneously. Figure 2-4 and Table 2-2 gives a case with configuration append.
Figure 2-4 QinQ Business Customer QoS Demo

1001/3 1001/10 #
any any
VoIP/TDM Data Gold
50M 100M
50M 200M
5 3
interface GigabitEthernet0/0/0.1001 control-vid 1001 qinq-termination VLAN-group 1 user-queue cir 50 pir 50 inbound user-queue cir 50 pir 50 outbound # qinq termination pe-vid 1001 ce-vid 3 VLAN-group 1 ip binding vpn-instance VoIP-VPN ip address 100.1.1.1 255.255.255.0 traffic-policy voippolicy inbound # interface GigabitEthernet0/0/0.2001 control-vid 2001 qinq-termination VLAN-group 2 user-queue cir 100 pir 200 inbound user-queue cir 100 pir 200 outbound
# qinq termination pe-vid 1001 ce-vid 10 VLAN-group 2 traffic-policy goldpolicy inbound mpls l2vc 172.16.0.40 123457 #
2.2.4
Business Services dot1p
For business user without their VLAN tag in traffic, a tag is also inserting to the packet as identifier of the user. As insertion of VLAN tag, 802.1p bits are also correctly marked based on traffic type (TOS in IP) so we can use 802.1p bits to enforce QoS policy as shown in Figure 2-5 and Table 2-3.
Figure 2-5 802.1q Business Customer QoS Demo

1002, single tag 1002, single tag 1002, single tag #
5 2 0
VoIP/TDM Data Silver Internet
50M 100M 0
50M 400M 100M
5 2 0
flow-queue model-3 queue be pq shaping 18 queue af1 pq shaping 0 queue af2 pq shaping 73 queue af3 pq shaping 0 queue af4 pq shaping 0 queue ef pq shaping 9 queue cs6 pq shaping 0 queue cs7 pq shaping 0
# interface GigabitEthernet0/0/0.1002 control-vid 1002 dot1q-termination VLAN-group 1 user-queue cir 150000 pir 550000 flow-queue model-3 inbound user-queue cir 150000 pir 550000 flow-queue model-3 outbound # dot1q termination vid 1002 VLAN-group 1 l2 binding vsi VPLS-A-Company trust upstream default #
14

Hqos CX600

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Hqos CX600

Încărcat de

Drepturi de autor:

Formate disponibile

Technical Literature

Hierarchical Quality of Service in CX600

Huawei Technologies Co., Ltd.

Hierarchical Quality of Service in CX600

Hierarchical Quality of Service in CX600

Hierarchical Quality of Service in CX600

1 QoS Policy Deployment

Hierarchical Quality of Service in CX600

Content CS7 CS6 EF AF4 AF3 AF2 AF1 BE

Hierarchical Quality of Service in CX600

VLAN 5 is used for IPTV/VoD multicast traffic

any any any any any any 5 2 0

0 100M 200M 100M 50M 100M 50M 100M 0

300M 100M 200M 100M 50M 200M 50M 400M 100M

Next chapter gives detailed implementation.

Hierarchical Quality of Service in CX600

2.1.1 Upstream H-QoS

Hierarchical Quality of Service in CX600

Figure 2-1 Upstream Scheduling

2.1.2 Downstream H-QoS

... ... SP/ WFQ SQ SHVC shaping MC

UC TB0 ... UC TB63

Hierarchical Quality of Service in CX600

Hierarchical Quality of Service in CX600

Figure 2-2 Downstream Scheduling

Hierarchical Quality of Service in CX600

Hierarchical Quality of Service in CX600

2.2.2 Residential Services

Figure 2-3 Residential QoS Demo

2, single tag 3, single tag 4, single tag 5, single tag #

any any any any

Internet VoIP/TDM Video Video

0 100M 200M 100M

300M 100M 200M 100M

Hierarchical Quality of Service in CX600

Hierarchical Quality of Service in CX600

Business Services QinQ

Figure 2-4 QinQ Business Customer QoS Demo

VoIP/TDM Data Gold

Hierarchical Quality of Service in CX600

Business Services dot1p

Figure 2-5 802.1q Business Customer QoS Demo

1002, single tag 1002, single tag 1002, single tag #

VoIP/TDM Data Silver Internet

50M 400M 100M

Hierarchical Quality of Service in CX600

S-ar putea să vă placă și