-
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
-
-
-
-
-
-
-
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!
Configuring and Managing Virtual IP (VIP) Addresses
Configuration of a virtual server IP (VIP) address is not mandatory during initial configuration of the NetScaler. When you configure load balancing, you assign VIP addresses to virtual servers.
For more information about configuring a load balancing setup, see Load Balancing.
In some situations, you need to customize VIP attributes or enable or disable a VIP address. A VIP address is usually associated with a virtual server, and some of the VIP attributes are customized to meet the requirements of the virtual server. You can host the same virtual server on multiple NetScaler appliances residing on the same broadcast domain, by using ARP and ICMP attributes. After you add a VIP (or any IP address), the appliance sends, and then responds to, ARP requests. VIPs are the only NetScaler-owned IP addresses that can be disabled. When a VIP address is disabled, the virtual server using it goes down and does not respond to ARP, ICMP, or L4 service requests. As an alternative to creating VIP addresses one at a time, you can specify a consecutive range of VIP addresses.
To create a VIP address by using the CLI:
At the command prompt, type:
- add ns ip <IPAddress> <netmask> -type <type>
- show ns ip <IPAddress>
Example:
> add ns ip 10.102.29.59 255.255.255.0 -type VIP
Done
<!--NeedCopy-->
To create a range of VIP addresses by using the CLI:
At the command prompt, type:
- add ns ip <IPAddress> <netmask> -type <type>
- show ns ip <IPAddress>
Example:
> add ns ip 10.102.29.[60-64] 255.255.255.0 -type VIP
ip "10.102.29.60" added
ip "10.102.29.61" added
ip "10.102.29.62" added
ip "10.102.29.63" added
ip "10.102.29.64" added
Done
<!--NeedCopy-->
To enable or disable an IPv4 VIP address by using the CLI:
At the command prompt, type one of the following sets of commands to enable or disable a VIP and verify the configuration:
- enable ns ip <IPAddress>
- show ns ip <IPAddress>
- disable ns ip <IPAddress>
- show ns ip <IPAddress>
Example:
> enable ns ip 10.102.29.79
Done
> show ns ip 10.102.29.79
IP: 10.102.29.79
Netmask: 255.255.255.255
Type: VIP
state: Enabled
arp: Enabled
icmp: Enabled
vserver: Enabled
management access: Disabled
telnet: Disabled
ftp: Disabled
ssh: Disabled
gui: Disabled
snmp: Disabled
Restrict access: Disabled
dynamic routing: Disabled
hostroute: Disabled
Done
> disable ns ip 10.102.29.79
Done
> show ns ip 10.102.29.79
IP: 10.102.29.79
Netmask: 255.255.255.255
Type: VIP
state: Disabled
arp: Enabled
icmp: Enabled
vserver: Enabled
management access: Disabled
telnet: Disabled
ftp: Disabled
ssh: Disabled
gui: Disabled
snmp: Disabled
Restrict access: Disabled
dynamic routing: Disabled
hostroute: Disabled
Done
<!--NeedCopy-->
To configure a VIP address by using the GUI:
Navigate to System > Network > IPs > IPV4s, and add a new IP address or edit an existing address.
To create a range of VIP addresses by using the GUI:
- Navigate to System > Network > IPs > IPV4s.
- In the Action list, select Add Range.
To enable or disable a VIP address by using the GUI:
- Navigate to System > Network > IPs > IPV4s.
- Do one of the following:
- Select a VIP address.
- Hold down the Ctrl key and select multiple server address entries.
- Hold down the Shift key and select a range of server address entries.
- Select all the addresses by selecting the checkbox on the left side of the header row.
- From the Action list, select Disable or Enable.
Detecting a NetScaler Appliance in a UDP Load Balancing Setup through TTL Updates
The following table displays how a NetScaler appliance handles the TTL value of received packets in different functionalities.
| Functionality | TTL value |
|---|---|
| Virtual Server | TTL is set to 255 when forwarding the request to the backend servers. TTL is decremented by 1 when forwarding the response to the client. |
| L2 Mode | TTL is not changed. |
| L3 Mode | TTL is set to 255. |
| INAT | TTL is set to 255 when forwarding the request to the backend server. TTL is decremented by 1 when forwarding the response to the client. |
Some enterprises/scenarios running a monitoring application requires the NetScaler appliance of a load balancing setup to be detected as one of the hop in a traceroute. A NetScaler appliance of a load balancing setup is not detected in a traceroute because the appliance, by default, sets the TTL value to 255 instead of decrementing it when forwarding the request to a backend server.
To meet this requirement, Decrement TTL parameter of a VIP address can be used. This parameter applies to all UDP virtual servers using this VIP.
When you enable the Decrement TTL parameter of a VIP, the NetScaler appliance decrements the TTL value by 1 instead of setting it to 255 when forwarding requests, which are received on the UDP virtual servers that uses this VIP.
Monitoring applications using traceroute data can now detect the presence of a NetScaler appliance of a UDP load balancing setup.
Before You Begin
Before you begin configuring a NetScaler appliance to be detected in a traceroute of a load balancing setup, note the following points:
- Decrement TTL parameter is supported only for UDP load balancing virtual servers.
- Decrement TTL parameter is supported for IPv4 VIP as well as IPv6 VIP (VIP6) addresses.
- Decrement TTL parameter is supported for standalone NetScaler appliances as well as for high availability (HA) and cluster setups.
Configuration Steps
Configuring a NetScaler appliance to be detected in a traceroute of a UDP load balancing setup consists of the following tasks:
- Create a UDP load balancing configuration
- Enable the Decrement TTL parameter for the VIP address
CLI Procedures
To enable the decrement TTL option for a VIP address by using the CLI:
- To enable the decrement TTL option for a VIP address while adding the VIP address, at the command prompt, type:
- add ns ip <ip> <mask> -type VIP -decrementTTL ENABLED
- show ns ip <VIP address>
- To enable the decrement TTL option for an existing VIP address, at the command prompt, type:
- set ns ip <ip> <mask> -decrementTTL ENABLED
- show ns ip <VIP address>
To enable the decrement TTL option for a VIP6 address by using the CLI:
- To enable the decrement TTL option for a VIP6 address while adding the VIP6 address, at the command prompt, type:
- add ns ip6 <IP6/prefix> <mask> -type VIP -decrementTTL ENABLED
- show ns ip6 <VIP6/prefix>
- To enable the decrement TTL option for an existing VIP6 address, at the command prompt, type:
- set ns ip6 <ip6/prefix> <mask> -decrementTTL ENABLED
- show ns ip6 <VIP6 address>
> add ns ip 203.0.113.30 -type VIP -decrementTTL ENABLED
Done
> add ns ip6 2001:DB8:5001::30 -type VIP -decrementTTL ENABLED
Done
<!--NeedCopy-->
GUI Procedures
To enable the decrement TTL option for a VIP address by using the GUI:
Navigate to System > Network > IPs > IPv4s, and enable the Decrement TTL parameter while adding a new VIP address or editing an existing address.
To enable the decrement TTL option for a VIP6 address by using the GUI:
Navigate to System > Network > IPs > IPv6s, and enable the Decrement TTL parameter while adding a new VIP6 address or editing an existing address.
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.