Why are you classifying SQL traffic as low priority traffic? In the vast majority of environments you would be giving SQL a higher priority over other traffic, not setting it as low priority traffic. With how you have things configured, your QoS is performing exactly what you are telling it to. Traffic starts queuing, WRED kicks in and will start dropping packets from lower priority queues to preserve high priority traffic.
You need to look at how you've actually configured QoS and what your organizations actual goal is with this traffic. From the look of things and how you have it configured at the moment, it appears like you want to treat SQL traffic as low priority. If that's the case and it meets your business use-case that's all fine and well, but you will run into DB replication issues.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!