08-05-2013 10:24 AM - edited 03-04-2019 08:39 PM
We are deploying riverbed steelhead devices between our core switch and routers in each of our offices. These all connect to each other over an MPLS network.
Before the Steelheads, we had a simple policy on each router that identified several types of traffic we most cared about and set the DSCP marking right at the router,just before the traffic was handed off to mpls.
The steelhead will now be marking the traffic for us. This is because in the mode we've deployed, it changes the IP address and port numbers so that our router, with only a few exceptions (voice, video) can not recognize the traffic. So the Steelhead will mark it for us.
The question I have is, do I need ot issue any commands such as the MLS Qos Trust command on the router interface coming in from the Steelehead in order to retain those markings, or will the router just pass my steelhead markings through?
Haven't done much QoS, and the course has been soooooooo long ago...
Solved! Go to Solution.
08-05-2013 11:15 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Routers normally leave untouched ingress ToS, unless you configure a policy to something else.
Catalyst switches, if QoS disabled, also normally leave ToS alone. With QoS enabled, by default, they often will reset ToS unless you config them to do otherwise (e.g. a trust statement). (NB: Some of the newer Catalysts might follow "router" rules, e.g. 4500 sup7.)
08-05-2013 11:15 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Routers normally leave untouched ingress ToS, unless you configure a policy to something else.
Catalyst switches, if QoS disabled, also normally leave ToS alone. With QoS enabled, by default, they often will reset ToS unless you config them to do otherwise (e.g. a trust statement). (NB: Some of the newer Catalysts might follow "router" rules, e.g. 4500 sup7.)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide