Policy problems
Before you begin, determine whether you are having problems with policies with RSVP scope. Policies with RSVP scope can be defined and made available by way of the Policy Agent.
If problems are encountered using such policies, check
the items listed in Table 1.
| Problem | Cause or action |
|---|---|
| RSVP policies not being applied to data flows | If the limits imposed by defined RSVP-scoped policies are not taking effect, check that the Policy Agent has been successfully started. The Policy Agent must be active in order for the RSVP Agent to retrieve these policies. Check that the policies are correctly defined. For example, do not specify both inbound and outbound interfaces in a single policy condition because such a policy never maps to any traffic on an end host node. Also, check both the RSVP Agent and Policy Agent log files for errors dealing with obtaining policies. |
| Policy values not being used or are incorrect | If the values being used in the policies
to limit Tspec and Rspec values do not appear to be correct, or do
not seem to be applied to RSVP data traffic, be aware that the service
policy and Tspec/Rspec units of measure are different. Specifically,
the following are different: If the Service Policy Unit is:
To arrive at the values to specify on the service policy, multiply the target Tspec/Rspec value by 8, then divide by 1000. For example, if the target Tspec b value is 6000, the corresponding MaxTokenBucketPerFlow value is 48 (6000 x 8 / 1000 = 48). See Diagnosing Policy Agent problems for more information about Policy Agent. |