SummaryIf a traffic is not hitting the correct policy, check the policy definitions and compare the associated object definitions to ensure they match.
Occasionally you may identify traffic that is not hitting the correct policy.
Typically this will either be noticed by reviewing the Real-Time Monitor with the View Policies checkbox enabled or by noticing unused policies in the Monitor > Control tab.
There are several places you can look for the cause of the issue.
1) Make sure policy exists in the optimizer tree under desired virtual circuit, Defining a policy (configuration > optimizer > policies > define parameters and click create new policy) does not means that traffic will be shaped according to it. Policy rules is only applied once that policy is included in the optimizer tree.
2) Ensure that there is not a more broad policy definition above the one you would like the traffic to fall into. It's important to remember that policy sets within a Virtual Circuit match in a Top-Down order. Traffic will remain in the first policy that it fits into.
For this reason it's important to ensure the policies are configured with the most specific at the top and least specific at the bottom, similarly to an Access Control List.
3) Ensure the traffic is hitting the correct application definition. This should be visible in the real time monitor. If you have defined a custom application and traffic is simply displaying as HTTP, you might need to modify your definition.
4) If their is a network object as part of the policy or application definition, ensure that the network object matches either the source or destination seen in the Real Time Monitor.
5) Ensure that the correct DSCP markings are selected inside the Policy if you're using a WAN link to pass the traffic that is configured to restrict the unmarked traffic.
If you are still seeing issues after checking the above, open a support case with the Exinda TAC Team.