-
-
Advanced policy expressions: Working with dates, times, and numbers
-
Advanced policy expressions: Parsing HTTP, TCP, and UDP data
-
Advanced policy expressions: IP and MAC Addresses, Throughput, VLAN IDs
-
-
-
Bind a responder policy
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Bind a responder policy
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 integer.
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 more policies at any time without having to reassign the priority of an existing policy.
For additional information about binding policies on the NetScaler, see Policies and Expressions.
Note:
Responder policies are bound to TCP-based virtual servers.
To globally bind a responder policy by using the NetScaler command line:
At the command prompt, type the following command to globally bind a responder policy and verify the configuration:
bind responder global <policyName> <priority> [<gotoPriorityExpression> [-type <type>] [-invoke (<labelType> <labelName>)]
show responder global
Example:
> bind responder global poliError 100
Done
> show responder global
1) Global bindpoint: REQ_DEFAULT
Number of bound policies: 1
Done
<!--NeedCopy-->
To bind responder policy to a specific virtual server by using the NetScaler command line:
At the command prompt, type:
bind lb vserver <name> -policyname <policy_name> -priority <priority>
show lb vserver vs-loadbal <name>
Example:
> bind lb vserver vs-loadbal -policyName policyTwo -priority 100
Done
> show lb vserver
1) vs-loadbal (10.102.29.20:80) - HTTP Type: ADDRESS
State: OUT OF SERVICE
Last state change was at Wed Aug 19 09:05:47 2009 (+211 ms)
Time since last state change: 2 days, 00:58:03.260
Effective State: DOWN
Client Idle Timeout: 180 sec
Down state flush: ENABLED
Disable Primary Vserver On Down : DISABLED
Port Rewrite : DISABLED
No. of Bound Services : 0 (Total) 0 (Active)
Configured Method: LEASTCONNECTION
Mode: IP
Persistence: NONE
Vserver IP and Port insertion: OFF
Push: DISABLED Push VServer:
Push Multi Clients: NO
Push Label Rule: none
2) vs-cont-sw (0.0.0.0:0) - TCP Type: ADDRESS
State: DOWN
Last state change was at Wed Aug 19 10:03:46 2009 (+213 ms)
Time since last state change: 2 days, 00:00:04.260
Effective State: DOWN
Client Idle Timeout: 9000 sec
Down state flush: ENABLED
Disable Primary Vserver On Down : DISABLED
No. of Bound Services : 0 (Total) 0 (Active)
Configured Method: LEASTCONNECTION
Mode: IP
Persistence: NONE
Connection Failover: DISABLED
Done
<!--NeedCopy-->
To globally bind a responder policy by using the GUI:
- Navigate to AppExpert > Responder > Policies.
- On the Responder Policies page, select a responder policy, and then click Policy Manager.
- In the Responder Policy Manager dialog box Bind Points menu, select Default Global.
- Click Insert Policy to insert a new row and display a drop-down list of all unbound responder policies.
- Click one of the policies on the list. That policy is inserted into the list of globally bound responder policies.
- Click Apply Changes.
- Click Close. A message appears in the status bar, stating that the configuration has been successfully completed.
To bind a responder policy to a specific virtual server by using the GUI:
- Navigate to Traffic Management > Load Balancing > Virtual Servers.
- On the Load Balancing Virtual Servers page, select the virtual server to which you want to bind the responder policy, and then click Open.
- In the Configure Virtual Server (Load Balancing) dialog box, select the Policies tab, which displays a list of all policies configured on your NetScaler appliance.
- Select the check box next to the name of the policy you want to bind to this virtual server.
- Click OK. A message appears in the status bar, stating that the configuration has been successfully completed.
Share
Share
In this article
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.