Hello, my name is Gabriel Henrique. I’m a network analyst here at Made4it, and today I’m going to show you how to configure selective bandwidth control for access-layer users on Huawei NE series routers.
Selective bandwidth control opens up the possibility of new products or the improvement, increment or “charm” in the delivery of the service to the end user being a very interesting differential, especially for ISPs that have local CDN.
But, after all, what is selective band control all about?
Typically, in BNG/BRAS/PPPoE Server implementations, it is common to have global bandwidth control (from the user’s perspective), in which all content is limited by the value of the subscribed plan. With selective bandwidth control, you can assign different bandwidth limits to different services; for example, you can assign a bandwidth limit of “X” to your local CDN content, “y” to traffic within your network, and “z” when the source or destination of the traffic is external (links, transit, peering, IX/PTT, PNI, transport, etc.), We can say that we implement selective QoS or that we specifically control how much bandwidth is allocated per content type; alternatively, it could be said that we can remove bandwidth control from the CDN or implement selective PBR.
Anyway, enough talk, let’s get to the cool part 🙂
In our test scenario, we have:
– Customers with a 100 Mbps plan
– Need to allow up to 500 Mbps when the source/destination is a local CDN
– Need to maintain 100 Mbps when the source/destination is not a local CDN
– Local CDNs are addressed with 192.0.2.0/24 and 2001:DB8::/64
Prerequisites:
– ERP/RADIUS with support for the “Huawei-Policy-Name” AVP
– Client authentication domain with a declared “user-group” (If you don’t know what a user-group is, stay tuned to the Made blog—there’ll be a post about firewalls coming up soon that will explain exactly what it’s all about 😉
Step 1: Configure, in the system-view, the necessary Radius parameters and activate the “Value Added Service” function in the router.
[code]
system-view
radius-server coa-request hw-policy-name daa same-policy reply-ack
radius-server coa-request hw-policy-name daa coexist-with-user
value-added-service enable
[/code]
Step 2: In the Radius-group used for authentication, enable value-added-service accounting support
[code]
system-view
aaa
domain made4it
value-added-service account-type radius made4it
[/code]
Step 3: Configure access ACLs delimiting CDN traffic and general traffic
[code]
system-view
acl number 7000
description CDN
rule 10 permit ip source user-group any destination ip-address 192.0.2.0 0.0.0.255
rule 11 permit ip source ip-address 192.0.2.0 0.0.0.255 destination user-group any
#
acl number 7001
description GERAL
rule 10 permit ip source user-group any destination ip-address any
rule 11 permit ip source ip-address any destination user-group any
acl ipv6 number 7002
description CDN PILOTO 500MBPS IPv6
rule 10 permit ipv6 source user-group any destination ipv6-address 2001:DB8::/64
rule 11 permit ipv6 source ipv6-address 2001:DB8::/64 destination user-group any
#
acl ipv6 number 7003
description GERAL PILOTO 100MBPS
rule 10 permit ipv6 source user-group any destination ipv6-address any
rule 11 permit ipv6 source ipv6-address any destination user-group any
[/code]
Step 4: Configure “classifiers” to classify traffic from ACLs
[code]
system-view
traffic classifier tc1 operator or
if-match acl 7000
if-match ipv6 acl 7002
#
traffic classifier tc8 operator or
if-match acl 7001
if-match ipv6 acl 7003
[/code]
Step 5: Configure the behaviors we will use to identify each of the classifiers
[code]
system-view
traffic behavior tb1
car
tariff-level 1
traffic-statistic
#
traffic behavior tb8
car
tariff-level 8
traffic-statistic
#
[/code]
Step 6: Configure the traffic-policy that will be linked globally, containing the previously configured classifier and behavior, effecting the differentiated classification of the flows
[code]
system-view
traffic policy DAA_1
share-mode
classifier tc1 behavior tb1 precedence 1
classifier tc8 behavior tb8 precedence 8
#
[/code]
Step 7: Apply the traffic-policy globally.
[code]
system-view
accounting-service-policy DAA_1
[/code]
Step 8: Configure the qos-profiles that will delimit the bandwidth of the respective contents
[code]
system-view
qos-profile 100M
car cir 103424 cbs 18700000 green pass red discard inbound
car cir 103424 cbs 18700000 green pass red discard outbound
qos-profile 500M
car cir 512000 cbs 18700000 green pass red discard inbound
car cir 512000 cbs 18700000 green pass red discard outbound
[/code]
Step 9: Configure the policy that will control the client’s bandwidth
[code]
system-view
value-added-service policy 100m daa
accounting-scheme made4it
user-group made4it
tariff-level 1 qos-profile 500M
tariff-level 8 qos-profile 100M
[/code]
Ready. Now, ERP/Radius just needs to deliver the AVP Huawei-Policy-Name := 150m to the customer, and the customer will have bandwidth control limiting up to 500Mbps when the origin/destination are the local CDNs, and up to 100Mbps for the other origins /destinations.
Please note that if the ERP/Radius provides the Huawei-Input-Average-Rate, the BRAS/BNG will use it by default and will not apply the policy name!
The traffic-policy allows up to 8 “tariff-levels” where you can classify your traffic into up to 8 service types and apply different bandwidth controls for each of them.
In this example, if you want to configure differentiated bandwidth control for other plans, simply create new “qos-profile” and “value-added-service policy” entries with the values you want to apply, since CDN and general traffic are already classified into distinct “tariff-levels.”
That’s it—see you next time! If you have any questions about how to implement this configuration on your network, please contact us and speak with one of our experts.
