{"id":19189,"date":"2022-06-23T10:10:00","date_gmt":"2022-06-23T10:10:00","guid":{"rendered":"https:\/\/made4it.com.br\/blog\/selective-bandwidth-control-in-huawei-router\/"},"modified":"2026-07-01T15:15:12","modified_gmt":"2026-07-01T15:15:12","slug":"selective-bandwidth-control-in-huawei-router","status":"publish","type":"post","link":"https:\/\/made4it.com.br\/en\/blog\/selective-bandwidth-control-in-huawei-router\/","title":{"rendered":"Selective Bandwidth Control in Huawei Router"},"content":{"rendered":"\n

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.<\/p>\n\n

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.<\/p>\n\n

But, after all, what is selective band control all about?<\/p>\n\n

\"\"<\/a><\/figure>\n\n

Typically, in BNG\/BRAS\/PPPoE Server implementations, it is common to have global bandwidth control (from the user\u2019s 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, \u201cy\u201d to traffic within your network, and \u201cz\u201d 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. <\/p>\n\n

Anyway, enough talk, let’s get to the cool part \ud83d\ude42<\/p>\n\n

In our test scenario, we have:<\/p>\n\n

– 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<\/p>\n\n

Prerequisites:<\/p>\n\n

– ERP\/RADIUS with support for the “Huawei-Policy-Name” AVP– Client authentication domain with a declared \u201cuser-group\u201d (If you don\u2019t know what a user-group is, stay tuned to the Made blog\u2014there\u2019ll be a post about firewalls coming up soon that will explain exactly what it\u2019s all about \ud83d\ude09<\/p>\n\n

Step 1: Configure, in the system-view, the necessary Radius parameters and activate the “Value Added Service” function in the router.<\/p>\n

[code]
\nsystem-view
\nradius-server coa-request hw-policy-name daa same-policy reply-ack
\nradius-server coa-request hw-policy-name daa coexist-with-user
\nvalue-added-service enable
\n[\/code]<\/p>\n\n

Step 2: In the Radius-group used for authentication, enable value-added-service accounting support<\/p>\n

[code]
\nsystem-view
\naaa
\ndomain made4it
\nvalue-added-service account-type radius made4it
\n[\/code]<\/p>\n\n

Step 3: Configure access ACLs delimiting CDN traffic and general traffic<\/p>\n

[code]
\nsystem-view
\nacl number 7000
\ndescription CDN
\nrule 10 permit ip source user-group any destination ip-address 192.0.2.0 0.0.0.255
\nrule 11 permit ip source ip-address 192.0.2.0 0.0.0.255 destination user-group any
\n#
\nacl number 7001
\ndescription GERAL
\nrule 10 permit ip source user-group any destination ip-address any
\nrule 11 permit ip source ip-address any destination user-group any<\/p>\n

acl ipv6 number 7002
\ndescription CDN PILOTO 500MBPS IPv6
\nrule 10 permit ipv6 source user-group any destination ipv6-address 2001:DB8::\/64
\nrule 11 permit ipv6 source ipv6-address 2001:DB8::\/64 destination user-group any
\n#
\nacl ipv6 number 7003
\ndescription GERAL PILOTO 100MBPS
\nrule 10 permit ipv6 source user-group any destination ipv6-address any
\nrule 11 permit ipv6 source ipv6-address any destination user-group any
\n[\/code]<\/p>\n\n

Step 4: Configure “classifiers” to classify traffic from ACLs<\/p>\n

[code]
\nsystem-view
\ntraffic classifier tc1 operator or
\nif-match acl 7000
\nif-match ipv6 acl 7002
\n#
\ntraffic classifier tc8 operator or
\nif-match acl 7001
\nif-match ipv6 acl 7003
\n[\/code]<\/p>\n\n

Step 5: Configure the behaviors we will use to identify each of the classifiers<\/p>\n

[code]
\nsystem-view
\ntraffic behavior tb1
\ncar
\ntariff-level 1
\ntraffic-statistic
\n#
\ntraffic behavior tb8
\ncar
\ntariff-level 8
\ntraffic-statistic
\n#
\n[\/code]<\/p>\n\n

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<\/p>\n

[code]
\nsystem-view
\ntraffic policy DAA_1
\nshare-mode
\nclassifier tc1 behavior tb1 precedence 1
\nclassifier tc8 behavior tb8 precedence 8
\n#
\n[\/code]<\/p>\n\n

Step 7: Apply the traffic-policy globally.<\/p>\n

[code]
\nsystem-view
\naccounting-service-policy DAA_1
\n[\/code]<\/p>\n\n

Step 8: Configure the qos-profiles that will delimit the bandwidth of the respective contents<\/p>\n

[code]
\nsystem-view
\nqos-profile 100M
\ncar cir 103424 cbs 18700000 green pass red discard inbound
\ncar cir 103424 cbs 18700000 green pass red discard outbound
\nqos-profile 500M
\ncar cir 512000 cbs 18700000 green pass red discard inbound
\ncar cir 512000 cbs 18700000 green pass red discard outbound
\n[\/code]<\/p>\n\n

Step 9: Configure the policy that will control the client’s bandwidth<\/p>\n

[code]
\nsystem-view
\nvalue-added-service policy 100m daa
\naccounting-scheme made4it
\nuser-group made4it
\ntariff-level 1 qos-profile 500M
\ntariff-level 8 qos-profile 100M
\n[\/code]<\/p>\n\n

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!<\/p>\n\n

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.<\/p>\n\n

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.”<\/p>\n\n

That’s it\u2014see 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. <\/a> <\/p>\n","protected":false},"excerpt":{"rendered":"

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\u2019s 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, \u201cy\u201d to traffic within your network, and \u201cz\u201d 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 \ud83d\ude42 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 \u201cuser-group\u201d (If you don\u2019t know what a user-group is, stay tuned to the Made blog\u2014there\u2019ll be a post about firewalls coming up soon that will explain exactly what it\u2019s all about \ud83d\ude09 Step 1: Configure, in the system-view, the necessary Radius parameters and activate the “Value Added Service” function in the router. Step 2: In the Radius-group used for authentication, enable value-added-service accounting support Step 3: Configure access ACLs delimiting CDN traffic and general traffic Step 4: Configure “classifiers” to classify traffic from ACLs Step 5: Configure the behaviors we will use to identify each of the classifiers 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 Step 7: Apply the traffic-policy globally. Step 8: Configure the qos-profiles that will delimit the bandwidth of the respective contents Step 9: Configure the policy that will control the client’s bandwidth 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\u2014see 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.<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[31],"tags":[],"class_list":["post-19189","post","type-post","status-publish","format-standard","hentry","category-nao-categorizado"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t