Select the DiffServ policy type. This will display all the DiffServ
policies. Similar to example 1, the most interesting fields
are the fields that obtain their data from your traffic. These fields include
the bits total, bits in-profile, and packets out-of-profile fields. Bits out-of-profile
indicate when traffic exceeds the configured policy values. The in-profile
packets indicate the number of packets controlled by this policy. What values
you assign the average rate limit field is very important. When TCP packets
exceed this limit, they are sent into the network, until the TCP congestion
window can be reduced to queue out-of-profile packets. As a result, the bits
out-of-profile will increase. The difference between this policy and the Limit
browser traffic scenario is that the packets here are protected using the
VPN protocol. As you can see, QoS does work with a VPN connection. See the Monitor QoS for a description of all the monitor fields.
Note: Remember
that the results will only be accurate when the policy is active. Verify the
schedule you specified within the policy.