-
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!
Setting up GSLB in a cluster
Note
Supported from NetScaler 10.5 Build 52.11 onwards.
To set up GSLB in a cluster you must bind the different GSLB entities to a node group. The node group must have a single member node.
Notes
- If you have configured the static proximity GSLB method, make sure that the static proximity database is present on all the cluster nodes. It happens by default if the database file is available at the default location. However, if the database file is maintained in a directory other than /var/netscaler/locdb/, you must manually sync the file to all the cluster nodes.
- The
show gslb domaincommand is not supported in a cluster setup.
To set up GSLB in a cluster by using the CLI:
Log on to the cluster IP address and perform the following operations at the command prompt:
-
Configure the different GSLB entities. For information, see GSLB Configuration Entities.
Note
When creating the GSLB site, make sure that you specify the cluster IP address and public cluster IP address. The public cluster IP address is needed only when the cluster is deployed behind a NAT device. While configuring a GSLB site, you must use the cluster IP address of the same site. These parameters are required to ensure the availability of the GSLB auto-sync functionality.
add gslb site <siteName> <siteType> <siteIPAddress> -publicIP <ip_addr> -clip <ip_addr> <publicCLIP><!--NeedCopy--> -
Create a cluster node group.
add cluster nodegroup <name> <name>@ [-strict ( YES | NO )] [-sticky ( YES | NO )] [-state <state>] [-priority <positive_integer>]<!--NeedCopy-->Note
Enable the sticky option if you want to set up GSLB based for VPN users.
-
Bind a single cluster node to the node group.
bind cluster nodegroup <name> -node <nodeId><!--NeedCopy--> -
Bind the local GSLB site to the node group.
bind cluster nodegroup <name> -gslbSite <string><!--NeedCopy-->Note
Make sure that the IP address of the local GSLB site IP address is striped (available across all cluster nodes).
-
Bind the ADNS (or ADNS-TCP) service or the DNS (or DNS-TCP) load balancing virtual server to the node group.
To bind the ADNS service:
```bind cluster nodegroup
-service **To bind the DNS load balancing virtual server:** ```bind cluster nodegroup <name> -vServer <string><!--NeedCopy--> -
Bind the GSLB virtual server to the node group.
bind cluster nodegroup <name> -vServer <string><!--NeedCopy--> -
[Optional] To set up GSLB based on VPN users, bind the VPN virtual server to the GSLB node group.
bind cluster nodegroup <name> -vServer <string><!--NeedCopy--> -
Verify the configurations.
show gslb runningConfig<!--NeedCopy-->
To set up GSLB in a cluster by using the GUI:
Log on to the cluster IP address and perform the following operations in the Configuration tab:
-
Configure the GSLB entities.
Navigate to Traffic Management > GSLB to perform the required configurations.
-
Create a node group and perform other node group related configurations.
Navigate to System > Cluster > Node Groups to perform the required configurations.
For the detailed configurations to be performed, see the description provided in the preceding CLI procedure.
Support for GSLB parent-child topology in a cluster
Starting with NetScaler 12.1 build 49.xx, GSLB parent-child topology is supported in cluster.
For more information about the parent-child topology, see Parent-child topology deployment using the MEP protocol.
To set up GSLB parent-child topology in a cluster by using the CLI
Parent site
Perform the following configuration:
-
Create a cluster node group.
add cluster nodegroup <name>Example:
add cluster nodegroup parentng -
Bind a single cluster node to the node group.
bind cluster nodegroup <name> -node <nodeId>Example:
bind cluster nodegroup parentng -node n2 -
Bind the local GSLB site to the node group.
bind cluster nodegroup <name> -gslbSite <string>Example:
bind cluster nodegroup parentng -gslbSite site1 -
Bind the ADNS (or ADNS-TCP) service or the DNS (or DNS-TCP) load balancing virtual server to the node group.
bind cluster nodegroup <name> -service <string>Example:
bind cluster nodegroup parentng – service ADNS -
Bind the GSLB virtual server to the node group.
bind cluster nodegroup <name> -vServer <string>Example:
bind cluster nodegroup parentng -vServce gslbvs1
Child site
Perform the following configuration:
-
Create a cluster node group.
add cluster nodegroup <name>Example:
add cluster nodegroup childng -
Bind a single cluster node to the node group.
bind cluster nodegroup <name> -node <nodeId>Example:
bind cluster nodegroup childng -node -n3 -
Bind the local GSLB site to the node group.
bind cluster nodegroup <name> -gslbSite <string>Example:
bind cluster nodegroup childng -gslbSite site1
Note
For parent and child sites to exchange aggregated statistics in metric-based load balancing methods, you must add local GSLB services on the child site. The metric-based load balancing methods are least connection, least bandwidth, and least packets.
To set up GSLB parent-child topology in a cluster by using the GUI
-
Configure the GSLB entities.
Navigate to Traffic Management > GSLB to perform the required configurations.
-
Create a node group.
Navigate to System > Cluster > Node Groups to perform the required configurations.
-
In the Node Group page, select the node group to which you want to bind a node, click Edit, and perform the following tasks. You can also perform these tasks when adding a node group.
-
Bind a node to the node group.
In Advance Settings, click Cluster Nodes and perform the following tasks:
- In Cluster Nodes section, click No Cluster Node.
- In Select Cluster Node, click > and select the node that you want to bind to the node group. You can also add a cluster node.
-
Bind the local GSLB site to the node group.
In Advance Settings, click GSLB Sites and perform the following tasks:
- In the GSLB Sites section, click No GSLB Site.
- In the Select GSLB Site, click > and select the GSLB site that you want to bind to the node group. You can also add a GSLB site.
-
Bind the GSLB virtual server to the node group.
In Advance Settings, click Virtual Servers and perform the following task:
- In the Virtual Servers pane, click +.
- In Choose Virtual Server, select the server that you want to bind to the node group.
-
Bind the ADNS (or ADNS-TCP) service or the DNS (or DNS-TCP) load balancing virtual server to the node group.
In Advance Settings, click Services and perform the following tasks:
- In Services section, click No Service.
- In Select Service, select the service that you want to bind to the node group. You can also add a service.
-
Note
For child sites, you only have to bind the cluster node and local GSLB site to the node group.
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.