-
AppExpert Applications and Templates
-
Configure application authentication, authorization, and auditing
-
-
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
-
-
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 classic policy
Depending on the policy type, you can bind a classic policy either globally or to a virtual server. Policy bind points are described in the table, “Policy Type and Bind Points for Policies in Features That Use Classic Policies.”
Note: You can bind a classic policy to multiple bind points.
Bind a classic policy globally by using the CLI
At the command prompt, type the following commands to set the parameters and verify the configuration:
- bind cmp global <policyName> [-priority <positive_integer>]
- show cmp global
<!--NeedCopy-->
Example
> bind cmp global cmp-pol-compress -priority 2
Done
> show cmp global
1) Policy Name: cmp-pol-compress Priority: 2
2) Policy Name: ns_nocmp_xml_ie Priority: 8700
3) Policy Name: ns_nocmp_mozilla_47 Priority: 8800
4) Policy Name: ns_cmp_mscss Priority: 8900
5) Policy Name: ns_cmp_msapp Priority: 9000
6) Policy Name: ns_cmp_content_type Priority: 10000
Done
>
<!--NeedCopy-->
Bind a classic policy to a virtual server by using the CLI
At the command prompt, type the following commands to set the parameters and verify the configuration:
- bind lb vserver <name> [<targetVserver>] [-policyName <string> [-priority <positive_integer>]
- show lb vserver<name>
<!--NeedCopy-->
Example
> bind lb vserver lbtemp -policyName cmp-pol-compress -priority 1
Done
> show lb vserver lbtemp
lbtemp (10.102.29.101:80) - HTTP Type: ADDRESS
State: UP
Last state change was at Tue Oct 27 06:40:38 2009 (+557 ms)
Time since last state change: 0 days, 02:00:40.330
Effective State: UP
Client Idle Timeout: 180 sec
Down state flush: ENABLED
Disable Primary Vserver On Down : DISABLED
Port Rewrite : DISABLED
No. of Bound Services : 1 (Total) 1 (Active)
Configured Method: LEASTCONNECTION
Current Method: Round Robin, Reason: Bound service's state changed to UP
Group: vserver-grp
Mode: IP
Persistence: COOKIEINSERT (version 0) Persistence Backup: SOURCEIP Persistence Mask: 255.255.255.255
Persistence Timeout: 2 min Backup Persistence Timeout: 2 min
Vserver IP and Port insertion: OFF
Push: DISABLED Push VServer:
Push Multi Clients: NO
Push Label Rule: none
1) http-one (10.102.29.252: 80) - HTTP State: UP Weight: 1
Persistence Cookie Value : NSC_wtfswfs-hsq=ffffffff096e03ed45525d5f4f58455e445a4a423660
1) Policy : cmp-pol-compress Priority:1
Done
>
<!--NeedCopy-->
Bind a classic policy globally by using the GUI
Note: This procedure documents the Global Bindings dialog box. Depending on the feature for which you want to globally bind a policy, the route by which you arrive at this dialog box may be different.
-
In the navigation pane, expand the feature for which you want to globally bind a classic policy, and then locate the policy that you want to bind globally.
Note: You cannot globally bind policies for Content Switching, Cache Redirection, SureConnect, Priority Queuing, or Citrix Gateway Authorization.
-
In the details pane, click Global Bindings.
-
In the Bind/Unbind <feature name> Policy(s) to Global dialog box, click Insert Policy.
-
In the Policy Name column, click the name of an existing policy that you want to globally bind, or click New Policy to open the Create <feature name> Policy dialog box.
-
After you have selected the policy or created a new policy, in the Priority column, type the priority value.
The lower the number, the sooner this policy is applied relative to other policies. For example, a policy assigned a priority of 10 is applied before a policy with a priority of 100. You can use the same priority for different policies. All features that use classic policies implement only the first policy that a connection matches, so policy priority is important for getting the results you intend.
As a best practice, leave room to add policies by setting priorities with intervals of 50 (or 100) between each policy.
-
Click OK.
Bind a classic policy to a virtual server by using the GUI
-
In the navigation pane, expand the feature that contains the virtual server to which you want to bind a classic policy (for example, if you want to bind a classic policy to a content switching virtual server, expand Traffic Management > Content Switching), and then click Virtual Servers.
-
In the details pane, select the virtual server, and then click Open.
-
In the Configure <Feature> Virtual Server dialog box, on the Policies tab, click the feature icon for the type policy that you want, and then click Insert Policy.
-
In the Policy Name column, click the name of an existing policy that you want to bind to a virtual server, or click A to open the Create <feature name> Policy dialog box.
-
After you have selected the policy or created a new policy, in the Priority column, set the priority.
If you are binding a policy to a content switching virtual server, in the Target column, select a load balancing virtual server to which traffic that matches the policy should be sent.
-
Click OK.
Share
Share
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.