-
-
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 policy globally
The following binding procedures are typical. However, refer to the documentation for the feature of interest to you for complete instructions.
Bind an integrated caching policy globally by using the CLI
At the command prompt, type the following commands to bind an Integrated Caching policy and verify the configuration:
- bind cache global <policy> -priority <positiveInteger> [-type REQ_OVERRIDE | REQ_DEFAULT | RES_OVERRIDE | RES_DEFAULT]
- show cache global
<!--NeedCopy-->
Example:
> bind cache global _nonPostReq -priority 100 -type req_default
Done
> show cache global
1) Global bindpoint: REQ_DEFAULT
Number of bound policies: 2
2) Global bindpoint: RES_DEFAULT
Number of bound policies: 1
Done
<!--NeedCopy-->
The type argument is optional to maintain backward compatibility. If you omit the type, the policy is bound to REQ_DEFAULT or RES_DEFAULT, depending on whether the policy rule is a response-time or a request-time expression.
Bind a rewrite policy globally by using the CLI
At the command prompt, type the following commands to bind a Rewrite policy and verify the configuration:
- bind rewrite global <policyName> <priority> [-type REQ_OVERRIDE | REQ_DEFAULT | RES_OVERRIDE | RES_DEFAULT]
- show rewrite global
<!--NeedCopy-->
Example:
bind rewrite global pol_remove-pdf 100
Done
> show rewrite global
1) Global bindpoint: REQ_DEFAULT
Number of bound policies: 1
2) Global bindpoint: REQ_OVERRIDE
Number of bound policies: 1
Done
<!--NeedCopy-->
The type argument is optional for globally bound policies, to maintain backward compatibility. If you omit the type, the policy is bound to REQ_DEFAULT or RES_DEFAULT, depending on whether the policy rule is a response-time or a request-time expression.
Bind a compression policy globally by using the CLI
At the command prompt, type the following commands to bind a compression policy and verify the configuration:
- bind cmp global <policyName> -priority <positiveInteger> [-type REQ_OVERRIDE | REQ_DEFAULT | RES_OVERRIDE | RES_DEFAULT]
- show cmp global
<!--NeedCopy-->
Example:
> bind cmp global cmp_pol_1 -priority 100
Done
> show cmp policy cmp_pol_1
Name: cmp_pol_1
Rule: HTTP.REQ.URL.SUFFIX.EQ("BMP")
Response Action: COMPRESS
Hits: 0
Policy is bound to following entities
1) GLOBAL REQ_DEFAULT
Priority: 100
GotoPriorityExpression: END
Done
<!--NeedCopy-->
Bind a responder policy globally by using the CLI
At the command prompt, type the following commands to bind a Responder policy and verify the configuration:
- bind responder global <policyName> <priority> [-type OVERRIDE | DEFAULT ]
- show responder global
<!--NeedCopy-->
Example:
bind responder global pol404Error1 200
Done
> show responder global
1) Global bindpoint: REQ_DEFAULT
Number of bound policies: 1
Done
<!--NeedCopy-->
Bind a DNS policy globally by using the CLI
At the command prompt, type the following commands to bind a DNS policy and verify the configuration:
- bind dns global <policyName> <priority>
- show dns global
<!--NeedCopy-->
Example:
> bind dns global pol_ddos_drop1 150
Done
> show dns global
Policy name : pol_ddos_drop
Priority : 100
Goto expression : END
Policy name : pol_ddos_drop1
Priority : 150
Done
<!--NeedCopy-->
Bind an integrated caching, responder, rewrite, or compression policy globally by using the GUI
- In the navigation pane, click the name of the feature for which you want to bind the policy.
- In the details pane, click <Feature Name> policy manager.
- In the Policy Manager dialog box, select the bind point to which you want to bind the policy (for example, for Integrated Caching, Rewrite, or Compression, you could select Request and Default Global). The Responder does not differentiate between request-time and response-time policies.
- Click Insert Policy and, from the Policy Name pop-up menu, select the policy name. A priority is assigned automatically to the policy, but you can click the cell in the Priority column and drag it anywhere within the dialog box if you want the policy to be evaluated after other policies in this bank. The priority is automatically reset. Note that priority values within a policy bank must be unique.
- Click Apply Changes.
- Click Close. A message in the status bar indicates that the policy is bound successfully.
Bind a DNS policy globally by using the GUI
- Navigate to Traffic Management > DNS > Policies.
- In the details pane, click Global Bindings.
- In the global bindings dialog box, click Insert Policy, and select the policy that you want to bind globally.
- Click in the Priority field and enter the priority level.
- Click OK. A message in the status bar indicates that the policy is bound successfully.
Share
Share
In this article
- Bind an integrated caching policy globally by using the CLI
- Bind a rewrite policy globally by using the CLI
- Bind a compression policy globally by using the CLI
- Bind a responder policy globally by using the CLI
- Bind a DNS policy globally by using the CLI
- Bind an integrated caching, responder, rewrite, or compression policy globally by using the GUI
- Bind a DNS policy globally 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.