-
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 proxy support for outbound calls to IDP or third party endpoints
-
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
-
Configure protected user as an authentication factor in NetScaler nFactor authentication
-
Localize error messages generated by NetScaler nFactor system
-
Configure NetScaler Gateway preauthentication EPA scan for the domain check
-
-
-
-
-
Administer a cache redirection virtual server
-
Manage client connections for a virtual server
-
Translate destination IP address of a request to origin IP address
-
-
-
-
Configure DNS resource records
-
Configure NetScaler as a non-validating security aware stub-resolver
-
Jumbo frames support for DNS to handle responses of large sizes
-
Caching of EDNS0 client subnet data when the NetScaler appliance is in proxy mode
-
Use case - configure the automatic DNSSEC key management feature
-
Use Case - configure the automatic DNSSEC key management on GSLB deployment
-
-
-
Source IP address whitelisting for GSLB communication channels
-
Use case: Deployment of domain name based autoscale service group
-
Use case: Deployment of IP address based autoscale service group
-
-
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
-
-
-
-
Support for hybrid Post Quantum cryptography on the frontend
-
-
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!
Manage client connections for a virtual server
You can configure timeouts on a cache redirection virtual server so that client connections are not kept open indefinitely. You can also insert Via headers in requests. To possibly reduce network congestion, you can reuse open TCP connections. You can enable or disable delayed cleanup of cache redirection virtual server connections.
You can configure the appliance to send ICMP responses to PING requests according to your settings. On the IP address corresponding to the virtual server, set the ICMP RESPONSE to VSVR_CNTRLD, and on the virtual server, set the ICMP VSERVER RESPONSE.
The following settings can be made on a virtual server:
- When you set ICMP VSERVER RESPONSE to PASSIVE on all virtual servers, appliance always responds.
- When you set ICMP VSERVER RESPONSE to ACTIVE on all virtual servers, appliance responds even if one virtual server is UP.
- When you set ICMP VSERVER RESPONSE to ACTIVE on some and PASSIVE on others, appliance responds even if one virtual server set to ACTIVE is UP.
This document includes the following information:
-
Configure client timeout
-
Insert Via headers in the requests
-
Reuse TCP connections
-
Configure delayed connection cleanup
Configure client timeout
You can specify expiration of client requests by setting a timeout value for the cache redirection virtual server. The timeout value is the number of seconds for which the cache redirection virtual server waits to receive a response for the client request.
To configure a time-out value, use the cltTimeout parameter, which specifies the time, in seconds, after which the NetScaler appliance closes any idle client connections. The default value is 180sec for HTTP/SSL-based services and 9000sec for TCP-based services.
Configure client timeout by using the CLI
At the command prompt, type the following commands to configure client timeout and verify the configuration:
- set cr vserver <name> [-cltTimeout <secs>]
- show cr vserver <name>
<!--NeedCopy-->
Example:
> set cr vserver Vserver-CRD-1 -cltTimeout 6000
Done
> show cr vserver Vserver-CRD-1
Vserver-CRD-1 (*:80) - HTTP Type: CONTENT
State: UP ARP:DISABLED
Client Idle Timeout: 6000 sec
Down state flush: ENABLED
Disable Primary Vserver On Down : DISABLED
Default: Content Precedence: URL Cache: TRANSPARENT
On Policy Match: CACHE L2Conn: OFF OriginUSIP: OFF
Redirect: POLICY Reuse: ON Via: ON ARP: OFF
Backup: Vserver-CRD-2
1) Cache bypass Policy: bypass-cache-control
2) Cache bypass Policy: Policy-CRD
Done
<!--NeedCopy-->
Configure client timeout by using the GUI
- Navigate to Traffic Management > Cache Redirection > Virtual Servers.
- In the details pane, select the virtual server for which you want to configure client timeout, (for example, Vserver-CRD-1), and then click Open.
- In Configure Virtual Server (Cache Redirection) dialog box, select the Advanced tab.
- In the Client Time-out(secs) text box, enter the time-out value in seconds.
- Click OK.
Insert Via headers in the requests
A Via header lists the protocols and recipients between the start and end points for a request or a response and informs the server of proxies through which the request was sent. You can configure the cache redirection virtual server to insert a Via header in each HTTP request. The via parameter is enabled by default when you create a cache redirection virtual server.
To enable or disable Via-header insertion in client requests, use the via parameter, which specifies the state of the system in inserting a Via header in the HTTP requests.
Possible values: ON, OFF
Default value: ON
Enable or disable Via-header insertion in client requests by using the CLI
At the command prompt, type:
- set cr vserver <name> [-via (ON|OFF)]
- show cr vserver <name>
<!--NeedCopy-->
Example:
> set cr vserver Vserver-CRD-1 -via ON
Done
> show cr vserver Vserver-CRD-1
Vserver-CRD-1 (*:80) - HTTP Type: CONTENT
State: UP ARP:DISABLED
Client Idle Timeout: 6000 sec
Down state flush: ENABLED
Disable Primary Vserver On Down : DISABLED
Default: Content Precedence: URL Cache: TRANSPARENT
On Policy Match: CACHE L2Conn: OFF OriginUSIP: OFF
Redirect: POLICY Reuse: ON Via: ON ARP: OFF
Backup: Vserver-CRD-2
1) Cache bypass Policy: bypass-cache-control
2) Cache bypass Policy: Policy-CRD
Done
>
<!--NeedCopy-->
Enable or disable Via-header insertion in client requests by using the GUI
- Navigate to Traffic Management > Cache Redirection > Virtual Servers.
- In the details pane, select the virtual server for which you want to configure client timeout, (for example, Vserver-CRD-1), and then click Open.
- In Configure Virtual Server (Cache Redirection) dialog box, select the Advanced tab.
- Select the Via check box.
- Click OK.
Reuse TCP connections
You can configure the NetScaler appliance to reuse TCP connections to the cache and origin servers across client connections. This can improve performance by saving the time required to establish a session between the server and the appliance. The reuse option is enabled by default when you create a cache redirection virtual server.
To enable or disable the reuse of TCP connections, use the reuse parameter, which specifies the state of reuse of TCP connections to the cache or origin servers across client connections.
Possible values: ON, OFF
Default value: ON
Enable or disable the reuse of TCP connections by using the CLI
At the command prompt, type:
- set cr vserver <name> [-reuse (ON|OFF)]
- show cr vserver <name>
<!--NeedCopy-->
Example:
> set cr vserver Vserver-CRD-1 -reuse ON
Done
> show cr vserver Vserver-CRD-1
Vserver-CRD-1 (*:80) - HTTP Type: CONTENT
State: UP ARP:DISABLED
Client Idle Timeout: 6000 sec
Down state flush: ENABLED
Disable Primary Vserver On Down : DISABLED
Default: Content Precedence: URL Cache: TRANSPARENT
On Policy Match: CACHE L2Conn: OFF OriginUSIP: OFF
Redirect: POLICY Reuse: ON Via: ON ARP: OFF
Backup: Vserver-CRD-2
1) Cache bypass Policy: bypass-cache-control
2) Cache bypass Policy: Policy-CRD
Done
<!--NeedCopy-->
Enable or disable the reuse of TCP connections by using the GUI
- Navigate to Traffic Management > Cache Redirection > Virtual Servers.
- In the details pane, select the virtual server for which you want to configure client timeout, (for example, Vserver-CRD-1), and then click Open.
- In Configure Virtual Server (Cache Redirection) dialog box, select the Advanced tab.
- Select the Reuse check box.
- Click OK.
Configure delayed connection cleanup
The down state flush option performs delayed cleanup of connections on a cache redirection virtual server. The down state flush option is enabled by default when you create a cache redirection virtual server.
To enable or disable the down state flush option, set the downStateFlush parameter.
Possible values: ENABLED, DISABLED
Default value: ENABLED
Enable of disable the down state flush option by using the CLI
At the command prompt, type the following commands to configure delayed connection clean up and verify the configuration:
- set cr vserver <name> [-downStateFlush (ENABLED | DISABLED)]
- show cr vserver <name>
<!--NeedCopy-->
Example:
> set cr vserver Vserver-CRD-1 -downStateFlush ENABLED
Done
> show cr vserver Vserver-CRD-1
Vserver-CRD-1 (*:80) - HTTP Type: CONTENT
State: UP ARP:DISABLED
Client Idle Timeout: 6000 sec
Down state flush: ENABLED
Disable Primary Vserver On Down : DISABLED
Default: Content Precedence: URL Cache: TRANSPARENT
On Policy Match: CACHE L2Conn: OFF OriginUSIP: OFF
Redirect: POLICY Reuse: ON Via: ON ARP: OFF
Backup: Vserver-CRD-2
1) Cache bypass Policy: bypass-cache-control
2) Cache bypass Policy: Policy-CRD
Done
<!--NeedCopy-->
Enable or disable the reuse of TCP connections by using the GUI
- Navigate to Traffic Management > Cache Redirection > Virtual Servers.
- In the details pane, select the virtual server for which you want to configure client timeout, (for example, Vserver-CRD-1), and then click Open.
- In Configure Virtual Server (Cache Redirection) dialog box, click Advanced tab.
- Select the Down state flush check box.
- 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.