-
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 Active-Active Mode
On each NetScaler appliance that you want to deploy in active-active mode, you must add a virtual MAC and bind the virtual MAC to a VIP. The virtual MAC for a given VIP must be same on each appliance. For example, if VIP 10.102.29.5, is created on the appliances, a virtual router ID (VRID) must be created on each NetScaler and bound to VIP 10.102.29.5 on each NetScaler. When you bind a virtual MAC to a VIP, the appliance sends VRRP advertisements to each VLAN that is bound to that VIP. The virtual MAC can be shared by different VIPs configured on the same NetScaler.
Configuring IPv4 Active-Active Mode
Perform the following tasks on each of the NetScaler appliances to be included in the active-active configuration:
- Add a virtual MAC address. Add a virtual MAC address by adding a VRID. You can also specify a priority and enable or disable preemption and sharing on this VRID address.
- Add a VIP address and associate the virtual MAC’s VRID. Add a VIP address and set the VRID parameter to the newly created VRID. The attributes of the VRID (for example, priority and preemption) are bound to this VIP address. Note: The same VIP address must be added to all the other NetScaler appliances.
To add a virtual MAC address by using the CLI
At the command prompt, type:
- **add vrID** <id> [-**priority** <positive_integer>] [-**preemption** (**ENABLED**|**DISABLED**)][-**sharing** (**ENABLED**|**DISABLED**)] [-**tracking** <tracking>]
- show vrid
To add a VIP address by using the CLI:
At the command prompt, type:
- add ns ip <IPv4Address> -type VIP -vrid <value>
- show ns ip
To configure a virtual MAC by using the GUI:
- Navigate to System > Network > VMAC, on the VMAC tab, add a new virtual MAC, or edit an existing virtual MAC.
- Set the following parameters:
- Virtual Router ID
- Priority
- Tracking
- Preemption
- Sharing
To configure a VIP address and associate the VRID to it by using the GUI:
- Navigate to System > Network > IPs, on the IPV4s tab, add an IP address of type VIP.
- While adding the IP address, select the virtual router ID from the Virtual Router Id drop down box.
Sample Configuration:
The following sample configuration is for deploying NetScaler appliances NS1 and NS2 in IPv4 active-active mode. VIP address 203.0.113.10 is configured on both NS1 and NS2, with a different priority value on each appliance. On each appliance, this VIP address is bound to a virtual MAC address. 203.0.113.10 is master on NS2, because its priority (200) on NS2 is higher than on NS1 (100).
Settings on NS1
> add vrid 10 –Priority 100 –Preemption Enabled –sharing Enabled
Done
> add ns ip 203.0.113.10 –type VIP –vrid 10
Done
Settings on NS2
> add vrid 10 –Priority 200 –Preemption Enabled –sharing Enabled
Done
> add ns ip 203.0.113.10 –type VIP –vrid 10
Done
<!--NeedCopy-->
Configuring IPv6 Active-Active Mode
Perform the following tasks on each of the NetScaler appliances to be included in the active-active configuration:
- Add a virtual MAC6 address. Add a virtual MAC6 address by adding a VRID6. You can also specify a priority and enable or disable preemption and sharing on this VRID6 address.
- Add a VIP6 address. Add a VIP6 address. Set the VRID6 parameter to the VRID6 of the newly created virtual MAC6.The attributes of the virtual MAC6 (for example, priority and preemption) are bound to this VIP6 address. Note: The same VIP6 address must be added to all the other NetScaler appliances.
To add a virtual MAC6 address by using the CLI:
At the command prompt, type:
- **add vrID6** <id> [-**priority** <positive_integer>] [-**preemption** ( **ENABLED** | **DISABLED** )] [-**sharing** (**ENABLED** | **DISABLED** )]
- show vrID6
To add a VIP6 address by using the CLI:
At the command prompt, type:
- add ns ip6 <IPv6Address> -type VIP -vrid <value>
- show ns ip6
To configure a virtual MAC6 by using the GUI:
- Navigate to System > Network > VMAC, on the VMAC6 tab, add a new virtual MAC6, or edit an existing VMAC6.
- Set the following parameters:
- Virtual Router ID
- Priority
- Preemption
- Sharing
To configure a VIP6 address and associate the VRID to it by using the GUI:
- Navigate to System > Network > IPs, on the IPV6s tab, add an IPv6 address of type VIP.
- While adding the VIP6 address, select the VRID6 from the Virtual Router Id drop down box.
Sample Configuration:
The following sample configuration is for deploying NetScaler appliances NS1 and NS2 in IPv6 active-active mode. VIP6 address 2001:db8::5001 is configured on both NS1 and NS2, with a different priority value on each appliance. On each appliance, this VIP6 address is bound to a virtual MAC6 address. 2001:db8::5001 is master on NS2, because it’s priority (200) on NS2 is higher than on NS1 (100).
Settings on NS1
> add vrid6 10 –Priority 100 –Preemption Enable –sharing Enable
Done
> add ns ip6 2001:db8::5001 –type VIP –vrid6 10
Done
Settings on NS2
> add vrid6 10 –Priority 200 –Preemption Enable –sharing Enable
Done
> add ns ip6 2001:db8::5001 –type VIP –vrid6 10
Done
<!--NeedCopy-->
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.