Scenario details: Verifying that the policy is working

 

You need to use the monitor to verify that the policy is working as you configured.

  1. On the Quality of Service (QoS) configuration window, select Server > Monitor. The QoS Monitor window opens.

  2. Select the DiffServ policy type folder. This displays all the DiffServ policies. Select UCD from the list.

    The most interesting fields are the fields that obtain their data from your traffic. Make sure to check the total bits, bits in-profile, and packets in-profile fields. Bits out-of-profile indicate when traffic exceeds the configured policy values. In a differentiated service policy, the out-of-profile number (for UDP packets) indicates the number of bits being dropped. For TCP, the out-of-profile number indicates the number of bits that exceed the token bucket rate and are sent into the network. Bits are never dropped for TCP packets. The in-profile packets indicate the number of packets controlled by this policy (from the time the packet was started to the present monitor output).

    The value you assign to the Average Rate Limit field is also important. When packets exceed this limit, the system begins to drop them. As a result, the bits out-of-profile increases. This shows you that the policy is behaving as you configured it to work. See Monitoring QoS for a description of all the monitor fields.

    Remember that the results are only accurate when the policy is active. Verify the schedule you specified within the policy.

 

Parent topic:

Scenario: Limiting browser traffic
Previous topic: Scenario details: Starting or updating the QoS server