When looking at the QoS statistics under an interface, there is a section of bypass traffic. Could someone tell me what this bypass traffic is related to?
Bypass traffic means traffic that we cannot apply QoS on it as we don't know the app yet. E.g. insufficient data and tcp incomplete traffic will be classified as bypass traffic.
Wouldn't any traffic that is not mapped to a class automatically fall into class 4, including applications that have not yet been identified? I wonder (just a guess) if bypass traffic is related to traffic destined for the firewall, such as routing protocols, ARP, etc. Or would such traffic also fall within class 4?
Be reminded that QoS apply on egress interface, and so is the report. So it doesn't apply on traffic arriving on that interface. I didn't check if ARP traffic will be in class 4 as well previously, but the ARP traffic volume should be small- and remember we only work on egress traffic.
Few firewall inbound and outbound traffic does not fall in the Qos Profile configured. There is a built-in “bypass” queue. Management traffic and protocol specific traffic (ARP, OSPF, BGP, etc.) is mapped to this internal “bypass” queue. This queue is not configurable by the user.
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 Live Community as a whole!
The Live Community thanks you for your participation!