-
Getting Started with NetScaler
-
Solutions for Telecom Service Providers
-
Load Balance Control-Plane Traffic that is based on Diameter, SIP, and SMPP Protocols
-
Provide Subscriber Load Distribution Using GSLB Across Core-Networks of a Telecom Service Provider
-
Authentication, authorization, and auditing application traffic
-
Basic components of authentication, authorization, and auditing configuration
-
Web Application Firewall protection for VPN virtual servers and authentication virtual servers
-
On-premises NetScaler Gateway as an identity provider to Citrix Cloud™
-
Authentication, authorization, and auditing configuration for commonly used protocols
-
Troubleshoot authentication and authorization related issues
-
Troubleshoot authentication, authorization and auditing issues
-
Configure EULA as an authentication factor in NetScaler nFactor system
-
Configure periodic Endpoint Analysis scan as a factor in nFactor authentication
-
Configure post-authentication Endpoint Analysis scan as a factor in NetScaler nFactor authentication
-
Configure pre-authentication Endpoint Analysis scan as a factor in nFactor authentication
-
Configure pre-auth and post-auth EPA scan as a factor in nFactor authentication
-
Configure prefill user name from certificate in NetScaler nFactor authentication
-
Localize error messages generated by NetScaler nFactor system
-
Configure NetScaler Gateway preauthentication EPA scan for the domain check
-
-
-
-
-
-
Persistence and persistent connections
-
Advanced load balancing settings
-
Gradually stepping up the load on a new service with virtual server–level slow start
-
Protect applications on protected servers against traffic surges
-
Retrieve location details from user IP address using geolocation database
-
Use source IP address of the client when connecting to the server
-
Use client source IP address for backend communication in a v4-v6 load balancing configuration
-
Set a limit on number of requests per connection to the server
-
Configure automatic state transition based on percentage health of bound services
-
-
Use case 2: Configure rule based persistence based on a name-value pair in a TCP byte stream
-
Use case 3: Configure load balancing in direct server return mode
-
Use case 6: Configure load balancing in DSR mode for IPv6 networks by using the TOS field
-
Use case 7: Configure load balancing in DSR mode by using IP Over IP
-
Use case 10: Load balancing of intrusion detection system servers
-
Use case 11: Isolating network traffic using listen policies
-
Use case 12: Configure Citrix Virtual Desktops for load balancing
-
Use case 13: Configure Citrix Virtual Apps and Desktops for load balancing
-
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
Use case 15: Configure layer 4 load balancing on the NetScaler appliance
-
-
-
-
Create a certificate signing request and use SSL certificates on a NetScaler appliance
-
Configure SSL acceleration with HTTP on the front end and SSL on the back end
-
Export certificates used on a NetScaler appliance as PFX file
-
Configure SSL monitoring when client authentication is enabled on the back-end service
-
Configure SSL action to forward client traffic if a cipher is not supported on the ADC
-
Configure synchronization of files in a high availability setup
-
-
-
Authentication and authorization for System Users
-
-
Configuring a CloudBridge Connector Tunnel between two Datacenters
-
Configuring CloudBridge Connector between Datacenter and AWS Cloud
-
Configuring a CloudBridge Connector Tunnel Between a Datacenter and Azure Cloud
-
Configuring CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
-
Configuring a CloudBridge Connector Tunnel Between a NetScaler Appliance and Cisco IOS Device
-
CloudBridge Connector Tunnel Diagnostics and Troubleshooting
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!
Unbind a policy
If you want to re-assign a policy or delete it, you must first remove its binding.
Unbind an integrated caching, rewrite, or compression advanced policy globally by using the CLI
At the command prompt, type the following commands to unbind an integrated caching, rewrite, or compression Advanced policy globally and verify the configuration:
- unbind cache|rewrite|cmp global <policyName> [-type req_override|req_default|res_override|res_default] [-priority <positiveInteger>]
- show cache|rewrite|cmp global
<!--NeedCopy-->
Example:
> unbind cache global_nonPostReq
Done
> show cache global
1) Global bindpoint: REQ_DEFAULT
Number of bound policies: 1
2) Global bindpoint: RES_DEFAULT
Number of bound policies: 1
Done
<!--NeedCopy-->
The priority is required only for the “dummy” policy named NOPOLICY.
Unbind a responder policy globally by using the CLI
At the command prompt, type the following commands to unbind a responder policy globally and verify the configuration:
- unbind responder global <policyName> [-type override|default] [-priority <positiveInteger>]
- show responder global
<!--NeedCopy-->
Example:
> unbind responder global pol404Error
Done
> show responder global
1) Global bindpoint: REQ_DEFAULT
Number of bound policies: 1
Done
<!--NeedCopy-->
The priority is required only for the “dummy” policy named NOPOLICY.
Unbind a DNS policy globally by using the CLI
At the command prompt, type the following commands to unbind a DNS policy globally and verify the configuration:
- unbind responder global <policyName>
- unbind responder global
<!--NeedCopy-->
Example:
unbind dns global dfgdfg
Done
show dns global
Policy name : dfgdfggfhg
Priority : 100
Goto expression : END
Done
<!--NeedCopy-->
Unbind an advanced policy from a virtual server by using the CLI
At the command prompt, type the following commands to unbind an Advanced policy from a virtual server and verify the configuration:
- unbind cs vserver <name> -policyName <policyName> [-priority <positiveInteger>] [-type REQUEST|RESPONSE]
- show lb vserver <name>
<!--NeedCopy-->
Example:
unbind cs vserver vs-cont-switch -policyName pol1
Done
> show cs vserver vs-cont-switch
vs-cont-switch (10.102.29.10:80) - HTTP Type: CONTENT
State: UP
Last state change was at Wed Aug 19 08:56:55 2009 (+18 ms)
Time since last state change: 0 days, 02:47:55.750
Client Idle Timeout: 180 sec
Down state flush: ENABLED
Disable Primary Vserver On Down : DISABLED
Port Rewrite : DISABLED
State Update: DISABLED
Default: Content Precedence: RULE
Vserver IP and Port insertion: OFF
Case Sensitivity: ON
Push: DISABLED Push VServer:
Push Label Rule: none
Done
<!--NeedCopy-->
The priority is required only for the “dummy” policy named NOPOLICY.
Unbind an integrated caching, responder, rewrite, or compression Advanced policy globally by using the GUI
- In the navigation pane, click the feature with the policy that you want to unbind (for example, Integrated Caching).
- In the details pane, click
<Feature Name>policy manager. - In the Policy Manager dialog box, select the bind point with the policy that you want to unbind, for example, Advanced Global.
- Click the policy name that you want to unbind, and then click Unbind Policy.
- Click Apply Changes.
- Click Close. A message in the status bar indicates that the policy is unbound successfully.
Unbind 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, select policy and click unbind policy.
- Click OK. A message in the status bar indicates that the policy is unbinded successfully.
Unbind an advanced policy from a load balancing or content switching virtual server by using the GUI
- Navigate to Traffic Management, and expand Load Balancing or Content Switching, and then click Virtual Servers.
- In the details pane, double-click the virtual server from which you want to unbind the policy.
- On the Policies tab, in the Active column, clear the check box next to the policy that you want to unbind.
- Click OK. A message in the status bar indicates that the policy is unbinded successfully.
Share
Share
In this article
- Unbind an integrated caching, rewrite, or compression advanced policy globally by using the CLI
- Unbind a responder policy globally by using the CLI
- Unbind a DNS policy globally by using the CLI
- Unbind an advanced policy from a virtual server by using the CLI
- Unbind an integrated caching, responder, rewrite, or compression Advanced policy globally by using the GUI
- Unbind a DNS policy globally by using the GUI
- Unbind an advanced policy from a load balancing or content switching virtual server 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.