I am needing some advice on how to setup the following.
I have in the field T1 connected to a MPLS network coming back to a T3. The T1s are conjested with Lotus Notes, Oracle and Voip traffic. The field routers are 2821 with Call Manager plus they have a 16-port 10/100 module within the router. In my configuration, I have applied CBWFQ for the traffic going out of the serial port. But I need to apply a service-policy for the input since we get killed with Notes and Oracle traffic. I really need help on this..
I did create a serivce-poicy for input but I got this error when appling the policy so I know I got it wrong.
I assume your issue is traffic leaving the main site with the t3 going to the remote site.
As stated above you can only use most these options outbound. You can police the traffic inbound but it doesn't always help because the traffic already used to bandwidth to get to the site before it is dropped. The only reason it partially works is because of how TCP does packet retranmission.
The best options is talk to your provider and see what they can offer. Since you are running VoIP I hope you have at lease some committed or gold bandwidth.
You should be able to mark your packet to correspond to a quality of service model they provide. This will allow them to queue the packets on their routers as they are being sent on the t1 to your remote site. This also solve the problem of any to any traffic where you cannot determine from moment to moment where traffic is coming from. As long as its is consitantly marked the provider will give preference to the traffic you want.
Another not so good option is to shape the traffic as it leaves the main router on the t3. This will only work if there is little traffic between the hub sites.
What you basically do is build a shaper class for each site. You match destination ip to place the data in the correct class which you then shape to a t1. This in effect makes your t3 look like a group of channelized t1's. Withing each of these classes you can apply a quality of service to limit the traffic. This tends to be complex to maintain and gets almost impossible if you have redundant pathing to the remote sites. This may be your only option if your mpls network you bought is all best effort with no commitments
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...