Below are the few General FAQ's with regards to App QOS from various customers.
- If Torrent application is assigned to Forwarding Class 12 and YouTube to 13, will torrent have more priority than YouTube?
- No. both are given equal weights in TC3. You need to define weights to define how much more important fc12 is over fc13.
- If we enable a scheduler for BE Traffic, will that scheduler be applicable for both torrent and YouTube traffic?
- Yes. Please refer to the class of service documentation on the knowledge base.
- If Torrent application is assigned to Forwarding Class 12 and YouTube to 13, will torrent hit queue 0 and YouTube hit queue 1 respectively for BE? When we were testing, and running YouTube, Q1 count not increasing and Q0 count was increasing.
- Yes. Please verify if the app-qos-policy is hitting the rule (show orgs org-services <org-name> class-of-services app-qos-policy). If the rule is not hitting, then there is an issue with the configuration.
- If I’m enabling policing for YouTube in scenario-1, torrent won’t be policed at all as it is a different App QoS Profile?
- Yes.
- If we enable flow anchoring, it is based on L3/L4? Can we specify the particular zones or IP Addresses to follow the prioritization? Since we are enabling flow anchoring, there won’t be any DPI, so if a particular LAN zone has phones connected to it and we have prioritized that zone, and also given a SIP, RTP and RTCP rule for APP QoS, the APP QoS rule will never be hit at all and will be prioritized from the LAN zone itself?
- Flow anchoring is only valid for qos-policies and not app-qos-policies.
- App-qos-policy will supersede the qos-policy.
- However, if you have flow-anchoring on L3-L4, the flow will be anchored according to the designated priority, but the result from app-qos-policy will be used to designate the qos-profile (fc/loss priority).
- Since FTP and torrent has both upload and download substantial amount, what would be the best practice with the Voice prioritization, that we can police both upload and download and enable scheduler with low guaranteed rate and about 50% of transmit rate for FTP and torrent and keep voice unpoliced?
- FTP/torrent traffic is typically given a queue in TC3 and is not policed. If the idea is to support voice prioritization, without limiting the bandwidth that is being allocated for voice, then do not put any schedulers on EF (where the voice should be going). This should suffice in most cases.