To put a policy
into effect, you must bind it either globally, so that it applies to all
traffic that flows through the NetScaler, or to a specific virtual server, so
that the policy applies only to requests whose destination IP address is the
VIP of that virtual server.
When you bind a
policy, you assign a priority to it. The priority determines the order in which
the policies you define are evaluated. You can set the priority to any positive
In the NetScaler
operating system, policy priorities work in reverse order—the higher the
number, the lower the priority. For example, if you have three policies with
priorities of 10, 100, and 1000, the policy assigned a priority of 10 is
performed first, then the policy assigned a priority of 100, and finally the
policy assigned an order of 1000. The responder feature implements only the
first policy that a request matches, not any additional policies that it might
also match, so policy priority is important for getting the results you intend.
You can leave
yourself plenty of room to add other policies in any order, and still set them
to evaluate in the order you want, by setting priorities with intervals of 50
or 100 between each policy when you globally bind it. You can then add
additional policies at any time without having to reassign the priority of an
For additional information about binding policies on the
NetScaler, see "Policies and
policies cannot be bound to TCP-based virtual servers.