-
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!
Using VRRP in a cluster setup
Virtual Router Redundancy Protocol (VRRP) is supported in a cluster setup for both IPv4 and IPv6. The two VRRP features supported in a cluster setup are Interface based VRRP and IP based VRRP.
IP based VRRP
In IP based VRRP, striped VIP addresses bound to the same VRID are configured on all nodes of a cluster setup. These VIP addresses are active on all the nodes
One of the cluster nodes acts as the VRID owner and sends out the VRRP advertisement to other nodes. If there is failure of the VRID owner node, another node in the cluster assumes the ownership of the VRID and starts sending VRRP advertisements. You can also assign a specific cluster node as the owner of the VRID.
Note
Citrix® recommends you to use IP based method for VRRP deployment in cluster.
Configuring IP based VRRP for IPv4
Perform the following tasks on a cluster setup for configuring IP based VRRP for IPv4:
- Add a VRID. A VRID is an integer used by the Cluster setup to form a virtual MAC address. The generic VMAC address is in the form of 00:00:5e:00:02:<VRID>.
-
(Optional) Assign a node as the owner of the virtual MAC address. You can set the owner node parameter (while adding or modifying VRID6) to the ID of the cluster node to assign it as the owner of the virtual MAC address. If the assigned owner node fails, one of the UP cluster nodes is dynamically elected as the owner of the virtual MAC address. You can set the owner node using the
set vrID <id> -ownerNode <positive_interger>command. - Bind the VRID to the VIP address of the nodes. Bind the created VRID to the striped VIP address.
To add a VRID by using the CLI
At the command prompt, type:
- add vrid <ID> [-ownerNode <positive_integer>]
- show vrid <ID>
To bind the VRID to VIP address by using the CLI
At the command prompt, type:
set ns ip <IPv4Address> -vrid <ID><!--NeedCopy-->show vrid <ID><!--NeedCopy-->
To add a VRID by using the GUI
- Navigate to System > Network > VMAC and, on the VMAC tab, click Add.
- On the Create VMAC page, specify a value in the Virtual Router ID field and then click Create.
To bind the VRID to a VIP address by using the GUI
- Navigate to System > Network > IPs, on the IPV4s tab, select a VIP address and click Edit.
-
Set the Virtual Router ID parameter while editing the VIP configuration.
> add vrid 90 Done > set ns ip 192.0.2.90 –vrid 90 Done
Configuring IP based VRRP for IPv6
Perform the following tasks on a cluster setup for configuring IP based VRRP for IPv6:
- Add a VRID6. A VRID6 is an integer used by the Cluster setup to form a virtual MAC6 address. The generic VMAC6 address is in the form of 00:00:5e:00:02:<VRID6>.
- (Optional) Assign a node as the owner of the virtual MAC6 address. You can set the owner node parameter (while adding or modifying VRID6) to the ID of the cluster node to assign it as the owner of the virtual MAC6 address. If the assigned owner node fails, one of the UP cluster nodes is dynamically elected as the owner of the virtual MAC6 address.
- Bind the VRID6 to the VIP6 address of the nodes. Bind the created VRID6 to the striped VIP6 address.
To add a VRID6 by using the CLI
At the command prompt, type:
add vrid6 <ID> [-ownerNode <positive_integer>]<!--NeedCopy-->show vrid6 <ID><!--NeedCopy-->
To bind the VRID6 to VIP6 address by using the CLI
At the command prompt, type:
set ns ip6 <IPv6Address> -vrid6 <ID><!--NeedCopy-->show vrid6 <ID><!--NeedCopy-->
To add a VRID6 by using the GUI
- Navigate to System > Network > VMAC and, on the VMAC6 tab, click Add.
- On the Create virtual MAC6 page, specify a value in the Virtual Router ID field and then click Create.
To bind the VRID6 to a VIP6 address by using the GUI
- Navigate to System > Network > IPs, on the IPV6s tab, select a VIP address and click Edit.
-
Set the Virtual Router ID parameter while editing the VIP6 configuration.
> add vrid6 90 Done > set ns ip6 2001:db8::5001 –vrid6 90 Done
Interface based VRRP
In the interface based VRRP feature, the same virtual MAC address is configured on both the nodes of the cluster. This virtual MAC address is used in GARP advertisements and ARP responses for the IP addresses configured on a node. This feature is useful in an active-spare two-node cluster setup that has external devices/routers that do not accept GARP advertisements.
Note
The interface based VRRP feature is applicable only to a two-node cluster with one node in active state and the other node serving as a spare.
With the same virtual MAC address on both cluster nodes, when the active node goes down and the spare node takes over as active, the MAC address for the IP addresses on the new active node remain unchanged and the ARP tables on the external devices/routers do not need to be updated.
Configuring interface based VRRP for IPv4
Perform the following tasks on a cluster setup to configure interface based VRRP for IPv4:
- Add a VRID. A VRID is an integer used by the Cluster setup to form a virtual MAC address.
- Bind the VRID to node interfaces. Bind the interfaces to the created VRID. The bound interfaces (in the current active node) use the virtual MAC address in GARP advertisements and ARP responses for its IPv4 addresses. You must associate the VRID to the interfaces of both nodes of the active-spare cluster setup. This is because unlike in a high availability setup, interface IDs differ in a cluster setup.
To add a VRID by using the CLI
At the command prompt, type:
- add vrid <ID>
- show vrid <ID>
To bind the VRID to an interface by using the CLI
At the command prompt, type:
- bind vrid <ID> -ifnum <interface_name>
- show vrid <ID>
To add a VRID and bind it to interfaces by using the GUI
- Navigate to System > Network > VMAC and, on the VMAC tab, click Add.
-
On the Create virtual MAC page, specify a value in the Virtual Router ID* field, bind interfaces in the Associate Interfaces section, and then click Create.
> add vrid 300 Done > bind vrid 300 -ifnum 1/1/2 2/1/3 Done
Configuring interface based VRRP for IPv6
Perform the following tasks on a cluster setup to configure interface based VRRP for IPv6:
- Add a VRID6. A VRID6 is an integer used by the Cluster setup to form a virtual MAC6 address. The generic VMAC6 address is in the form of 00:00:5e:00:01:<VRID6>.
- Bind the VRID6 to node interfaces. Bind the interfaces to the created VRID6. The bound interfaces (in the current active node) use the virtual MAC6 address in GARP advertisements and ARP responses for its IPv6 addresses. You must associate the VRID6 to the interfaces of both nodes of the active-spare cluster setup. This is because unlike in a high availability setup, interface IDs differ in a cluster setup.
To add a VRID6 by using the CLI
At the command prompt, type:
- add vrid6 <ID>
- show vrid6 <ID>
To bind the VRID6 to an interface by using the CLI
At the command prompt, type:
bind vrid6 <ID> -ifnum <interface_name><!--NeedCopy-->show vrid6 <ID><!--NeedCopy-->
To add a VRID6 and bind it to interfaces by using the GUI
- Navigate System > Network > VMAC and, on the VMAC6 tab, click Add.
-
On the Create virtual MAC6 page, specify a value in the Virtual Router ID field, bind interfaces in the Associate Interfaces section, and then click Create.
> add vrid6 100 Done > bind vrid6 100 -ifnum 0/1/1 1/1/2 2/1/3 Done
Share
Share
In this article
- IP based VRRP
- Configuring IP based VRRP for IPv4
- Configuring IP based VRRP for IPv6
- To add a VRID6 by using the CLI
- To bind the VRID6 to VIP6 address by using the CLI
- To add a VRID6 by using the GUI
- To bind the VRID6 to a VIP6 address by using the GUI
- Interface based VRRP
- Configuring interface based VRRP for IPv4
- Configuring interface based VRRP for IPv6
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.