-
AppExpert Applications and Templates
-
Configure application authentication, authorization, and auditing
-
-
Configuring Advanced Policy Infrastructure
-
Invoking or Removing a Policy Label or Virtual Server Policy Bank
-
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!
Invoke or remove a policy label or virtual server policy bank
Unlike a policy, which can only be bound once, you can use a policy label or a virtual server’s policy bank any number of times by invoking it. Invocation can be performed from two places:
- From the binding for a named policy in a policy bank.
- From the binding for a NOPOLICY “dummy” entry in a policy bank.
Typically, the policy label must be of the same type as the policy from which it is invoked. For example, you would invoke a responder policy label from a responder policy.
Note: When binding or unbinding a global NOPOLICY entry in a policy bank at the command line, you specify a priority to distinguish one NOPOLICY entry from another.
Invoke a rewrite or integrated caching policy label by using the CLI
At the command prompt, type the one of the following commands to invoke a rewrite or integrated caching policy label and verify the configuration:
- bind cache global <policy> -priority <positive_integer> [-gotoPriorityExpression <expression>] -type REQ_OVERRIDE|REQ_DEFAULT|RES_OVERRIDE|RES_DEFAULT] -invoke reqvserver|resvserver|policylabel <label_name>
- bind rewrite global<policy> -priority <positive_integer> [-gotoPriorityExpression <expression>] -type REQ_OVERRIDE|REQ_DEFAULT|RES_OVERRIDE|RES_DEFAULT] -invoke reqvserver|resvserver|policylabel <label_name>
- show cache global|show rewrite global
<!--NeedCopy-->
Example:
> bind cache global _nonPostReq2 -priority 100 -type req_override -invoke
policylabel lbl-cache-pol
Done
> show cache global
1) Global bindpoint: REQ_DEFAULT
Number of bound policies: 2
2) Global bindpoint: RES_DEFAULT
Number of bound policies: 1
3) Global bindpoint: REQ_OVERRIDE
Number of bound policies: 1
Done
<!--NeedCopy-->
Invoke a responder policy label by using the CLI
At the command prompt, type the following commands to invoke a responder policy label and verify the configuration:
- bind responder global <policy_Name> <priority_as_positive_integer> [<gotoPriorityExpression>] -type REQ_OVERRIDE|REQ_DEFAULT|OVERRIDE|DEFAULT -invoke vserver|policylabel <label_name>
- show responder global
<!--NeedCopy-->
Example:
> bind responder global pol404Error1 300 -invoke policylabel lbl-respndr-pol
Done
> show responder global
1) Global bindpoint: REQ_DEFAULT
Number of bound policies: 2
Done
<!--NeedCopy-->
Invoke a virtual server policy bank by using the CLI
At the command prompt, type the following commands to invoke a Virtual Server Policy Bank and verify the configuration:
- bind lb vserver <vserver_name> -policyName <policy_Name> -priority <positive_integer> [-gotoPriorityExpression <expression>] -type REQUEST|RESPONSE -invoke reqvserver|resvserver|policylabel <policy_Label_Name>
- bind lb vserver <vserver_name>
<!--NeedCopy-->
Example:
> bind lb vserver lbvip -policyName ns_cmp_msapp -priority 100
Done
> show lb vserver lbvip
lbvip (8.7.6.6:80) - HTTP Type: ADDRESS
State: DOWN
Last state change was at Wed Jul 15 05:54:24 2009 (+166 ms)
Time since last state change: 28 days, 06:37:49.250
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
1) CSPolicy: pol-cont-sw CSVserver: vs-cont-sw Priority: 100 Hits: 0
2) Policy : pol-ssl Priority:0
3) Policy : ns_cmp_msapp Priority:100
4) Policy : cf-pol Priority:1 Inherited
Done
<!--NeedCopy-->
Remove a rewrite or integrated caching policy label by using the CLI
At the command prompt, type one of the following commands to remove a rewrite or integrated caching policy label and verify the configuration:
- unbind rewrite global <policyName> -priority <positiveInteger> -type REQ_OVERRIDE|REQ_DEFAULT|RES_OVERRIDE|RES_DEFAULT
- unbind cache global <policyName> -priority <positiveInteger> -type REQ_OVERRIDE|REQ_DEFAULT|RES_OVERRIDE|RES_DEFAULT
- show rewrite global|show cache global
<!--NeedCopy-->
Example:
> unbind rewrite global NOPOLICY -priority 100 -type REQ_OVERRIDE
> show rewrite global
Done
1) Global bindpoint: REQ_DEFAULT
Number of bound policies: 1
Done
<!--NeedCopy-->
Remove a responder policy label by using the CLI
At the command prompt, type the following commands to remove a responder policy label and verify the configuration:
- unbind responder global <policyName> -priority <positiveInteger> -type OVERRIDE|DEFAULT
- show responder global
<!--NeedCopy-->
Example:
> unbind responder global NOPOLICY -priority 100 -type REQ_DEFAULT
Done
> show responder global
1) Global bindpoint: REQ_DEFAULT
Number of bound policies: 1
Done
<!--NeedCopy-->
Remove a virtual server policy label by using the CLI
At the command prompt, type one of the following commands to remove a Virtual Server policy label and verify the configuration:
- unbind lb vserver <virtualServerName> -policyName NOPOLICY-REWRITE|NOPOLICY-RESPONDER|NOPOLICY-CACHE -type REQUEST|RESPONSE -priority <positiveInteger>
- unbind cs vserver <virtualServerName> -policyName NOPOLICY-REWRITE|NOPOLICY-RESPONDER|NOPOLICY-CACHE -type REQUEST|RESPONSE -priority <positiveInteger>
- show lb vserver|show cs vserver
<!--NeedCopy-->
Example:
> unbind lb vserver lbvip -policyName ns_cmp_msapp -priority 200
Done
> show lb vserver lbvip
lbvip (8.7.6.6:80) - HTTP Type: ADDRESS
State: DOWN
Last state change was at Wed Jul 15 05:54:24 2009 (+161 ms)
Time since last state change: 28 days, 06:47:54.600
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
1) CSPolicy: pol-cont-sw CSVserver: vs-cont-sw Priority: 100 Hits: 0
1) Policy : pol-ssl Priority:0
2) Policy : cf-pol Priority:1 Inherited
Done
<!--NeedCopy-->
Invoke a policy label or virtual server policy bank by using the GUI
- Bind a policy, as described in Bind a policy globally, Bind a policy to a virtual server, or Bind a policy to a policy label. Alternatively, you can enter a NOPOLICY “dummy” entry instead of a policy name. You do this if you do not want to evaluate a policy before evaluating the policy bank.
- In the Invoke field, select the name of the policy label or virtual server policy bank that you want to evaluate if traffic matches the bound policy. A message in the status bar indicates that the policy label or virtual server policy bank is invoked successfully.
Remove a policy label invocation by using the GUI
- Open the policy and clear the Invoke field. Unbinding the policy also removes the invocation of the label. A message in the status bar indicates that the policy label is removed successfully.
Share
Share
In this article
- Invoke a rewrite or integrated caching policy label by using the CLI
- Invoke a responder policy label by using the CLI
- Invoke a virtual server policy bank by using the CLI
- Remove a rewrite or integrated caching policy label by using the CLI
- Remove a responder policy label by using the CLI
- Remove a virtual server policy label by using the CLI
- Invoke a policy label or virtual server policy bank by using the GUI
- Remove a policy label invocation by using the GUI
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.