Im trying to find a way to protect BGP packets from high utilization outbound from my router. I have queue tree set up that is getting matches setting BGP to priority 1 with limit-at 500k bandwidth. However, doing a bandwidth test from the local router (upload), bgp drops. Doing a bandwidth test TOWARD the local router, BGP stays up. The connection is 10m down .5m up.
Ive also tried making a simple queue to match BGP (using the same packet mark that works on the queue tree), but I cant get that one to match any traffic on statistics “target upload”. It does match target download.
It appears something odd is going on or i am misunderstanding something. I tried setting up a simple queue this time, to match all packets targeting my tunnel interface, i set it to limit to 50k. Weird thing is when i look at the traffic page on the queue it shows “target download” is hitting 50k instead of upload. I’m running a 2m bandwidth test as “send”, My tunnel interface does show the 50kb as upload. So why does the queue say download?
The up/down of simple queues is reversed, kindof. Because simple queues are often used for limiting customers to some kind of speed package, the “download” represents the download from the customer’s perspective (which is actually upload from the router’s perspective) so that is normal.
Basically, what it is telling you is the customer at lsv-hub is downloading at a rate of 50k, which means that your router is uploading at that rate.
Based upon what you want, however (QoS on an interface egress), I think a queue tree is a better method.
Although they can be used for the same things, here is what they are usually used for:
Simple Queues - usually used to limit customers or IP ranges to some kind of speed package
Queue Trees - Placed on interface so that all traffic exiting interface passes through; usually used for prioritization of certain types of traffic, in case of congestion
Since BGP is really a type of data rather than a customer, a Queue Tree is closer to what you want