SD-WAN - MX 16.16 - Little Help Needed...Best Practices/Tips/Advice

Solved
NJNetworkGuy100
Getting noticed

SD-WAN - MX 16.16 - Little Help Needed...Best Practices/Tips/Advice

So, we've upgraded all our MXs in NA to 16.16 and we've also migrated our phone system to MS Teams Voice.

 

So, with no internal phone system going over the site to site VPN and MS Teams is now a category for things like Traffic Shaping (finally!), we've decided to review and update our SD-WAN settings on the branch office MXs.

 

We operate the Auto VPN with all our branch office MXs as Spokes, and two datacenters as Hubs.  

 

Couple of questions and maybe some advice...

 

We noticed a few new categories that we could use for VPN Uplink Policy....does anyone know what network traffic the "Active Directory" category under "Productivity" covers?  

 

And does anyone have advice or tips for Traffic Shaping?  Is there traffic that you typically have bandwidth caps on it?  Like, background traffic on phones or video streaming.  

 

Any best practices docs, official or otherwise, that are available online?  Any good blog posts that you know of?  

 

Bring on the advice and tips and whatever!

1 Accepted Solution
PhilipDAth
Kind of a big deal
Kind of a big deal

It will be best to start by enabling QoS in Microsoft Teams:

https://docs.microsoft.com/en-us/microsoftteams/qos-in-teams-clients 

 

Then enabling the default traffic shaping rules is about all you need to do.  It will act on the QoS markers that Microsoft Teams applies to its packets.

 

PhilipDAth_0-1651693725762.png

 

View solution in original post

2 Replies 2
PhilipDAth
Kind of a big deal
Kind of a big deal

It will be best to start by enabling QoS in Microsoft Teams:

https://docs.microsoft.com/en-us/microsoftteams/qos-in-teams-clients 

 

Then enabling the default traffic shaping rules is about all you need to do.  It will act on the QoS markers that Microsoft Teams applies to its packets.

 

PhilipDAth_0-1651693725762.png

 

Oh, that's a great MS doc...thanks for that link.  Something to discuss with my company's O365 guys to see if they even knew about this for Teams.

Get notified when there are additional replies to this discussion.