11-09-2020 11:17 AM
We apply QOS via Radius but lately we've got reports of customers not being restricted to their bandwidth we set especially on the download side. When i check the customers policy-map it looks like their not getting matched on the outbound. I'm not sure what could be causing it or how to fix it anyone here have experience?
Customer traffic is over a 4x10GB MC-LAG Bundle (BE100), we're using GeoRedundancy between 2 ASR9001 units.
On AccessAccept we are sending for an example client
cisco-avpair="subscriber:sub-qos-policy-out=10240kb"
cisco-avpair="subscriber:sub-qos-policy-in=3078kb"
show running policy-map has an entry like the following (we have different capacity policy maps for our various packages)...
11-10-2020 09:41 AM
When using a bundle the policy-map gets replicated to each member, so if you have a 100mb output policy and traffic is load-balanced on all 4 links then the user gets 400mb.
To work around this we can force the user to take only one bundle member.
bundle load-balancing hash dst-ip
Add that to the bundle config and it should fix your issue.
Sam
11-14-2020 11:06 AM - edited 11-14-2020 11:11 AM
Any other idea? Already have that set in the configs for both unit. And like i said based on policy-map it's not matching somehow (you can see the sample above)
11-10-2020 10:57 AM - edited 11-14-2020 11:07 AM
.
11-11-2020 08:28 AM - edited 11-14-2020 11:10 AM
.
11-30-2020 02:44 AM
Try changing your egress policer to a "flat" policer so the config looks something like the following and then check the packet matches on the PPPoE session once it has been re-established with the revised config.
policy-map 10240kb
class class-default
police rate 10240 kbps
end-policy-map
Rgds, Jim.W.
11-30-2020 08:48 AM
We worked this through a TAC SR and found it to be due to CSCvo43692.
Sam
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: