I need advice and hope this is the right forum. I have a dedicated T1link between one branch office and our home office. I would like all traffic from all users in the branch that go to certain hosts in the home office to get higher priority than other destinations. I do not wish to dedicate a certain amount of bandwidth to these host destinations, just priority. No VOIP on this link, just data. I am confused at this point from all the different options, please help. Thanks.
one way to prioritize your traffic would be to set the precedence or DSCP, depending on your IOS version (the ´ip precedence´ option has been replaced with the ´set dscp´ option, starting with IOS 12.2(2)T).
So, in your case, the configuration could look like this (the IP addresses and interfaces in this example are likely different from yours, just make sure that the access list matches the sourec and destination hosts you want to give priority to):
class-map match-all PRIORITY
match access-group 101
set dscp cs5
set dscp cs1
service-policy output DSCP
access-list 101 permit ip 192.168.1.0 0.0.0.255 172.16.1.0 0.0.0.255
Be aware though that the prioritized hosts might starve other traffic, that is why usually a certain amount of bandwidth is guaranteed...
Thank you but have more stupid questions ---- if I did assign a certain amount of bandwidth to Priority, would priority be able to use more if there were more available and vice versa, would default get more if Priority were not using all its bandwidth or is this a carved in stone value which would never fluctuate depending on link use? Thanks again for any input to my stupid questions.
As per my response to the other poster, the priority command enables LLQ. LLQ will drop any traffic over the configured bandwidth.
If you want the prioritised servers to use available bandwidth over what's been reserved, then use the "bandwidth" statement in place of the "priority" statement. Be extra careful though. If the prioritised server pumps large amount of data, they WILL drown out the default class.
I don't think the prioritised hosts would starve the traffic. What you suggested above was LLQ. LLQ will NOT use anymore than what has been configured, thanks to its policing feature. Any traffic exceeding the configured bandwidth will be discarded.
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...