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
What is "best" is whatever best accomplishes your service requirements. Ideally, if possible, keeping to "best practices" and other recommendations.
There are RFC and Cisco recommendations for marking traffic. I suggest one of those should be used. Personally, I would recommend using RFC recommendations.
There are also some Cisco recommendations for processing marked traffic, but those are really up to your needs.
If your real-time data traffic really needs the best possible treatment, it, as is usually the case for VoIP bearer traffic, could also be placed into a 2960's PQ. It doesn't need to be, and probably shouldn't be, marked the same as VoIP bearer traffic.
If your real-time data traffic needs treatment similar to PQ, but doesn't really need PQ, you can, on a 2960, provide it a very high weight relative to other traffic.
If you fear both traffic types in the same queue, especially if that queue is PQ, you could set both egress queues to same high priority relative to other traffic, and weigh them, relative to each other, as desired. E.g. weights such as 255 255 10 1.
