The configuration is the same, but if you have poor RF, this will add only a cosmetic benefit. You need to ensure that clients in class are not dropping more than 2/10 pings to their default gateway to be conservative. If that is happening, the RF of your environment needs to be fixed first. The configuration above is to further prioritize traffic, not solve RF problems.
------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
------------------------------
Original Message:
Sent: Nov 19, 2020 12:10 PM
From: Yogendran Parthasarathy
Subject: Zoom call woes
This configuration can be applied in 6.x controller?
------------------------------
Yogendran Parthasarathy
Original Message:
Sent: Oct 12, 2020 07:11 PM
From: Colin Joseph
Subject: Zoom call woes
This is a sample of what I have:
config tnetdestination zoom description "Zoom" name *.zoom.usip access-list session zoom any alias zoom any permit disable-scanning queue high tos 46 dot1p-priority 7 alias zoom any any permit disable-scanning queue high tos 46 dot1p-priority 7 user-role Production access-list session global-sacl access-list session zoom access-list session allowall
This would only mark the QOS from the AP to the client. If you have other problems going on with your wireless, this is not a silver bullet.
You can type "show firewall dns-names" on the MD to see if it is indeed learning all of the zoom URLs ip addresses to mark the traffic properly.
You could also choose a client and type "show datapath session table <ip address of client>" on the MD to see if any traffic is being marked with the dscp markings above.