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
So you're saying the Websense proxy is dropping the markings? If so, the ideal solution would be for the Websense proxy to stop doing that.
Otherwise, assuming there are multiple markings you need to preserve, you need a policy, on some downstream (from the Websense) transit device, to analyze and remark traffic with their appropriate QoS markings. Depending on the complexity of the analysis, the ingress port, from the Websense attached to your 4507, would be the most logical place for such a policy.
Do know, that Catalyst switches, by default, when QoS is enabled, will erase QoS markings. I assume this isn't the issue on the 4507. If it is, just trust (or trust and verify) traffic entering the 4507.
Also know, QoS changes much on the latest 4500 sups, i.e. sup7 QoS is different from sup V QoS.
