I'm looking for guidance for how to properly design a traffic shaping policy for the following scenario:
WAN based on ELAN offering from telco. The hub site has a 300Mb/s connection into the ELAN and spokes are at 20Mb/s. Traffic pattern I'm concerned about is from Hub to spoke only as that constitutes 99% of the traffic in the ELAN. The challenge I have is that some of my traffic is latency sensitive and I'm running into issues. Checking with the telco they are showing inbound policing drops at the 20Mb/s sites, and are suggesting that the site is trying to pull down more than the subscribed 20Mb/s.
To combat this problem, it seems like I need a two-level shaping policy at the hub site: 1st level limits each remote site to the subscribed rate of 20Mb/s so they stop hitting the inbound policer, 2nd level gives the low latency traffic XMb/s, in this case 10Mb/s. To do this, I can create access-lists to match the subnet allocated to the remote site. I will create 2 access-lists: 1 for the low latency traffic, and one for everything else that is destined for the remote site's subnet.
I've put together the following configuration on the hub site router, which is a Cisco ISR4431:
192.168.127.0 = Remote Subnet 10.30.1.0 = Source of low latency traffic ip access-list extended acl-REMOTESITE-SHAPE20MEG permit ip any 192.168.127.0 0.0.0.255 class-map match-all cm-REMOTESITE-SHAPE20MEG match access-group name acl-REMOTESITE-SHAPE20MEG ip access-list extended acl-REMOTESITE-PRIORITY permit ip 10.30.1.0 0.0.0.255 192.168.127.0 0.0.0.255 class-map match-all cm-REMOTESITE-PRIORITY match access-group name acl-REMOTESITE-PRIORITY policy-map pm-Child-REMOTESITE-PRIORITY class cm-REMOTESITE-PRIORITY priority 10000 policy-map pm-QOS-Parent class cm-REMOTESITE-SHAPE20MEG shape average 17825792 service-policy pm-Child-REMOTESITE-PRIORITY class class-default shape average 267386880 interface GigabitEthernet0/0/2 service-policy output pm-QOS-Parent
Will this accomplish what I'm looking for? Is there a better way to do it?
Thanks in advance for any suggestions!
No comments:
Post a Comment