Citrix Systems Network Router 9.2 User Manual
208
Citrix NetScaler Policy Configuration and Reference Guide
policy that a connection matches. So policy priority is important to get the
results you intended.
results you intended.
As a best practice, leave room to add policies by setting priorities with
intervals of 50 (or 100) between each policy.
intervals of 50 (or 100) between each policy.
4.
Click OK.
To bind a classic policy globally using the NetScaler command line
At the command line, type:
bind feature global policy_name priority
•
For feature, for Application Firewall policies, you substitute appfw. For
Access Gateway policies, you substitute accessgw. For SSL policies, you
substitute ssl.
Access Gateway policies, you substitute accessgw. For SSL policies, you
substitute ssl.
•
For policy_name, substitute the name of the policy you just created.
•
For priority, substitute a positive integer that represents the priority you
want to assign to that policy.
want to assign to that policy.
In the NetScaler OS, 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. All features except the Rewrite feature on
the NetScaler appliance implement only the first policy that a connection
matches, not any additional policies that it might also match.
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. All features except the Rewrite feature on
the NetScaler appliance implement only the first policy that a connection
matches, not any additional policies that it might also match.
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, better, 100) between each policy when you globally bind
your policies. If you do this, you can add additional policies at any time
without having to reassign the priority of an existing policy. You simply
look at the priorities assigned to the preceding and following policies, and
assign a new policy a priority between that of those two numbers.
and still set them to evaluate in the order you want, by setting priorities with
intervals of 50 (or, better, 100) between each policy when you globally bind
your policies. If you do this, you can add additional policies at any time
without having to reassign the priority of an existing policy. You simply
look at the priorities assigned to the preceding and following policies, and
assign a new policy a priority between that of those two numbers.
To bind a classic policy to a virtual server using the configuration utility
1.
Expand the feature that contains the virtual server, for example, expand
Content Switching or Load Balancing, and then click Virtual Servers.
Content Switching or Load Balancing, and then click Virtual Servers.
2.
Select the virtual server to which you want to bind a policy and then click
Open.
Open.
3.
In the Configure Virtual Server dialog box, click the Policies tab.
4.
Click the icon for the type policy that you want, click Insert Policy, and
then click the name of the policy that you want to bind.
then click the name of the policy that you want to bind.