Hey, Everyone!
I've been reading around this forum looking for some questions related to QoS and I've found quite a few answers but not everything I'm looking for. If I repeat something that is explained elsewhere and I didn't see it, feel free to beat me over the head with a stick. I know how much people hate it when someone asks a question that has already been answered. =)
Okay, first off, let's say I am trying to apply a QoS policy to my WAN interface, both upstream and downstream traffic. Since most QoS policies can only be applied to the out direction of an interface, you would need to apply the policy to both your LAN and WAN interface like so:
set interfaces ethernet eth1 traffic-policy out wan_downstream set interfaces ethernet eth0 traffic-policy out wan_upstream
with the eth0 interface being your WAN interface and the eth1 interface being your LAN interface. My question is, wouldn't this also apply said policy to some inter-vlan traffic?
Okay, my second question relates a bit more to my specific application. I would like to implement a priority-based QoS policy, meaning I would like to prioritize some packets over others rather than simply limiting bandwidth based matches. For example, I would like my setup to look something like this:
Super time-sensitive stuff like NTP, routing protocols, etc. no matter the source > VoIP traffic tagged with specific dcsp values, both signaling and RTP but only from VLAN 2 (my VoIP VLAN) > traffic from VLAN 3 (important traffic VLAN, endpoints, iPhones, etc.) > traffic from VLAN 5 (not so important traffic VLAN) > VLAN 6 (guest VLAN) > Everything else including non-VoIP traffic from VLAN 2, traffic from unlisted VLANs, traffic from management VLAN, etc.
I have started to try to implement something like this with a priority-queue but, priority-queue only seems to allow 7 different levels of traffic separation. All I have done thus far is prioritized VoIP traffic over everything else using the below configuration (it was applied to the respective interfaces using the code above).
traffic-policy { priority-queue wan_downstream { class 5 { description "VOIP (RTP and Signal)" match VOIP-RTP { ip { dscp 46 } } match VOIP-SIG { ip { dscp 26 } } queue-type drop-tail } default { queue-type drop-tail } description "WAN downstream qos policy" } priority-queue wan_upstream { class 5 { description "VOIP (RTP and Signal)" match VOIP-RTP { ip { dscp 46 } } match VOIP-SIG { ip { dscp 26 } } queue-type drop-tail } default { queue-type drop-tail } description "WAN upstream qos policy" } }
I am kinda at a loss as to where to go from here. Sure I could set up the other levels of the priority-queue and match traffic to them but I don't really want to do all that work only to find out there is a different type of policy that allows for more than 7 classifications. Is there such a policy type? Something I can expand on easily later if I need to?
Also, being a bit of a Newb at this, I need some best practice tips. I have looked at several different documents from vendors all over about what traffic should come before other traffic but I would really like to get everyone's opinion here. What do you prioritize over all else? What does your prioritization hierarchy look like?
Also, I have several IPSec site-to-site tunnels on this same router that all go over the same WAN link I am trying to apply a QoS policy to. How would those factor into my QoS policy? Would the QoS policy apply before the tunnel or would the tunnel apply before the QoS policy?
Some of these questions may be common knowledge and I just haven't progressed enough in studying networking to know that. I'm still working on the basics but my goal with all of these questions, having a homelab, etc. is to learn. After this, I am going to start working on learning the basics of internal QoS.
Thanks ahead of time.
Oh! What's the difference between traffic-policy and traffic-control?