-
Getting Started with NetScaler
-
Deploy a NetScaler VPX instance
-
Optimize NetScaler VPX performance on VMware ESX, Linux KVM, and Citrix Hypervisors
-
Apply NetScaler VPX configurations at the first boot of the NetScaler appliance in cloud
-
Configure simultaneous multithreading for NetScaler VPX on public clouds
-
Install a NetScaler VPX instance on Microsoft Hyper-V servers
-
Install a NetScaler VPX instance on Linux-KVM platform
-
Prerequisites for installing NetScaler VPX virtual appliances on Linux-KVM platform
-
Provisioning the NetScaler virtual appliance by using OpenStack
-
Provisioning the NetScaler virtual appliance by using the Virtual Machine Manager
-
Configuring NetScaler virtual appliances to use SR-IOV network interface
-
Configure a NetScaler VPX on KVM hypervisor to use Intel QAT for SSL acceleration in SR-IOV mode
-
Configuring NetScaler virtual appliances to use PCI Passthrough network interface
-
Provisioning the NetScaler virtual appliance by using the virsh Program
-
Provisioning the NetScaler virtual appliance with SR-IOV on OpenStack
-
Configuring a NetScaler VPX instance on KVM to use OVS DPDK-Based host interfaces
-
-
Deploy a NetScaler VPX instance on AWS
-
Deploy a VPX high-availability pair with elastic IP addresses across different AWS zones
-
Deploy a VPX high-availability pair with private IP addresses across different AWS zones
-
Protect AWS API Gateway using the NetScaler Web Application Firewall
-
Configure a NetScaler VPX instance to use SR-IOV network interface
-
Configure a NetScaler VPX instance to use Enhanced Networking with AWS ENA
-
Deploy a NetScaler VPX instance on Microsoft Azure
-
Network architecture for NetScaler VPX instances on Microsoft Azure
-
Configure multiple IP addresses for a NetScaler VPX standalone instance
-
Configure a high-availability setup with multiple IP addresses and NICs
-
Configure a high-availability setup with multiple IP addresses and NICs by using PowerShell commands
-
Deploy a NetScaler high-availability pair on Azure with ALB in the floating IP-disabled mode
-
Configure a NetScaler VPX instance to use Azure accelerated networking
-
Configure HA-INC nodes by using the NetScaler high availability template with Azure ILB
-
Configure a high-availability setup with Azure external and internal load balancers simultaneously
-
Configure a NetScaler VPX standalone instance on Azure VMware solution
-
Configure a NetScaler VPX high availability setup on Azure VMware solution
-
Configure address pools (IIP) for a NetScaler Gateway appliance
-
Deploy a NetScaler VPX instance on Google Cloud Platform
-
Deploy a VPX high-availability pair on Google Cloud Platform
-
Deploy a VPX high-availability pair with external static IP address on Google Cloud Platform
-
Deploy a single NIC VPX high-availability pair with private IP address on Google Cloud Platform
-
Deploy a VPX high-availability pair with private IP addresses on Google Cloud Platform
-
Install a NetScaler VPX instance on Google Cloud VMware Engine
-
-
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
-
-
-
-
-
-
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
-
-
-
Synchronize the configuration in a GSLB setup
-
Real-time synchronization between sites participating in GSLB
-
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
-
-
-
-
-
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!
Real-time synchronization between sites participating in GSLB
You can use the AutomaticConfigSync
parameter to automatically synchronize the real-time GSLB configuration of the main site to all the subordinate sites. You do not have to manually trigger the AutoSync option to synchronize the configuration.
You can automatically synchronize GSLB configuration of the main site to all the subordinate sites by using incremental synchronization or full synchronization. The GSLBSyncMode
parameter allows you to choose the synchronization mode.
Note:
Starting from NetScaler release 13.0 build 79.x, incremental synchronization of GSLB synchronization is supported. By default, the synchronization is performed using incremental synchronization. Incremental synchronization can be performed by enabling the
IncrementalSync
parameter. For details, see Incremental synchronization of GSLB configuration.
Best practices for using the real-time synchronization feature
- It is recommended that all the NetScaler appliances participating as sites have the sameNetScaler software version.
- To change the RPC node password, first change the password on the subordinate site and then on the main site.
- Configure local GSLB sites on each site participating in GSLB.
- Enable automaticConfigSync on one of the sites where the configuration is performed. This site eventually gets synchronized to other GSLB sites.
- If there is a new configuration or changes are made to the existing configuration, make sure to check the status using the
show gslb syncStatus
command to confirm if the changes are synchronized across all sites or if there was any error. - RSYNC port monitoring must be enabled.
To enable real-time synchronization by using the CLI
At the command prompt, type:
set gslb parameter [–automaticConfigSync (ENABLED | DISABLED)] [-MEPKeepAliveTimeout <secs>] [-GSLBSyncMode ( IncrementalSync | FullSync )] [-GSLBSyncLocFiles ( ENABLED | DISABLED)] [-GslbConfigSyncMonitor ( ENABLED | DISABLED )] [-GSLBSyncInterval <secs>] [-GSLBSyncSaveConfigCommand ( ENABLED | DISABLED )]
<!--NeedCopy-->
Example:
set gslb parameter –automaticConfigSync ENABLED
<!--NeedCopy-->
The real-time synchronization provides the following configurable parameters:
-
GSLBSyncMode-Mode in which configuration is synchronized from main site to remote sites.
- Possible values: IncrementalSync, FullSync
- Default value: IncrementalSync
-
GSLBSyncLocFiles—During GSLB config synchronization, by default, the changes in the location DB files are detected and automatically synchronized. Because the location DB directories do not change often, admins can disable automatically synchronizing the location DB files. Instead, admins must manually copy the location DB files to the GSLB subordinate sites. Synchronizing location DB files takes much time. Thus, avoiding it reduces the overall synchronization time.
Example to disable automatically synchronizing the location DB files:
set gslb parameter -GSLBSyncMode IncrementalSync -GSLBSyncLocFiles DISABLED <!--NeedCopy-->
-
GslbConfigSyncMonitor—Enable the GSLB Config Sync Monitor parameter to monitor the state of the subordinate sites’ RSYNC port which is the SSH port 22 on remote GSLB site IP address. If the monitor shows the subordinate site state as DOWN, the RSYNC operation to that site is skipped. This reduces the synchronization delays caused by attempting to connect to the remote sites that are DOWN.
Example to enable RSYNC port monitoring in CLI:
set gslb parameter -GSLBSyncMode IncrementalSync -GslbConfigSyncMonitor ENABLED <!--NeedCopy-->
-
GSLBSyncInterval—Set the time interval (in seconds) at which the GSLB configuration synchronization occurs. By default, the automatic GSLB configuration sync feature synchronizes the GSLB configuration automatically at every 10 seconds. You can change the time interval to any desired value. Refrain from setting this to a lower value, for example, not lesser than 5 seconds. Because synchronizing frequently might increase the management CPU consumption.
Note:
In an admin partition setup, the time interval can be set only in the default partition because it is a global parameter.
Example to set the sync interval:
set gslb parameter -AutomaticConfigSync ENABLED -GSLBSyncMode IncrementalSync -GSLBSyncInterval 7 <!--NeedCopy-->
-
GSLBSyncSaveConfigCommand—Enable this parameter to synchronize the
save ns config
command to subordinate sites, if theAutomaticConfigSync
option is enabled.Example to enable the synchronization of ‘Save Config’ Command:
set gslb parameter -AutomaticConfigSync ENABLED -GSLBSyncSaveConfigCommand ENABLED <!--NeedCopy-->
The
save ns config
command isn’t synchronized to subordinate sites in certain scenarios as follows:- Subordinate site is down or unreachable when config is saved on main site.
- Configuration has failed on a subordinate site.
To enable real-time synchronization by using the GUI
- Navigate to Configuration > Traffic Management > GSLB > Change GSLB Settings.
- In the Set GSLB Parameters page, you can perform the following:
- To automatically synchronize the real-time GSLB configuration, select Automatic ConfigSync.
Note: This option must be enabled only in the site where the configuration is performed.
- To set the Automatic GSLB config sync interval, enter the time in seconds in the GSLB Sync Interval field.
- To enable RSYNC port monitoring, select the GSLB Config Sync Monitor check box.
- To disable automatically synchronizing the location DB files, clear the GSLB Sync Loc Files check box.
- To enable synchronizing of the
save ns config
command to the subordinate sites, select Sync Save Config Command check box.
For information on the following topics, see Manual synchronization between sites participating in GSLB.
- Previewing GSLB synchronization
- Debugging the commands triggered during the synchronization process
Points to note
- The consolidated log file related to the real-time synchronization is stored in the /var/netscaler/gslb/periodic_sync.log directory.
- The default configuration file is stored in the /var/netscaler/gslb_sync/ directory.
- The main site uses the following directory structure:
- The main site stores all its files in the /var/netscaler/gslb_sync/master directory.
- The main site stores its configuration file that must be synced to the subordinate sites, in the /var/netscaler/gslb_sync/master/gslbconf/ directory.
- The status files pulled from all the subordinate sites are stored in the /var/netscaler/gslb_sync/master/slavestatus/ directory.
- The subordinate site uses the following directory structure:
- The subordinate site picks up the latest configuration file to be applied from the /var/netscaler/gslb_sync/slave/gslbconf directory.
- The subordinate site stores its status file in the /var/netscaler/gslb_sync/slave/gslbstatus directory.
- In an admin partition setup, the same directory structure is maintained in the location: /var/partitions/
partition name
/netscaler/gslb_sync. - The clocks on all the sites must be set accurately to a real-time standard like Coordinated Universal Time (UTC).
Incremental synchronization of GSLB configuration
The automatic GSLB configuration synchronization feature checks for the configuration changes on the main site at the interval of every 10 seconds, and performs a synchronization. This sync interval value is configurable.
In incremental synchronization, only the configurations that have changed on the main site between the last synchronization and the subsequent sync interval (10 secs) is synchronized across all the subordinate sites. Incremental synchronization is the default behavior. Pushing only the incremental configurations considerably reduces the configuration file size, and thus the synchronization time. If an incremental synchronization fails, the system automatically performs a full configuration synchronization.
Incremental synchronization is performed in the following manner:
- The main site pushes the configuration file comprising of only its latest changes to all the subordinate sites. The latest change refers to the configurations that has changed between the last synchronization and the subsequent sync interval (10 secs).
- Each subordinate site applies the latest change to its own site.
- Incremental synchronization in not attempted on the subordinate sites, which are in DOWN state. When the site comes back UP, again synchronization is performed.
- The subordinate site generates status logs at each step and copies them to a file at a specific location.
- The main site pulls the status log files from the specified location.
- The main site prepares a log file with logs combined from all the subordinate sites.
- This combined log file is stored in the “/var/netscaler/gslb/periodic_sync.log” file.
For more information on the directories where the configuration files are stored, see Points to note section.
To enable GSLB configuration incremental synchronization by using the CLI
set gslb parameter -AutomaticConfigSync (ENABLED | DISABLED) -GSLBSyncMode (IncrementalSync | FullSync) -GslbConfigSyncMonitor (ENABLED | DISABLED) -GSLBSyncInterval <secs> -GSLBSyncLocFiles (ENABLED | DISABLED)
<!--NeedCopy-->
Example:
set gslb parameter -AutomaticConfigSync ENABLED -GSLBSyncMode IncrementalSync
<!--NeedCopy-->
To enable GSLB incremental synchronization by using the GUI
- Navigate to Traffic Management > GSLB > Dashboard > Change GSLB settings.
- In the Set GSLB Parameters page, choose IncrementalSync from the GSLB Sync Mode drop-down menu.
Full synchronization of GSLB configuration
Whenever there is a configuration change in the main site, the complete GSLB running configuration on the main site is pushed to all the subordinate sites. Even if incremental synchronization is configured, a full synchronization is performed when the main site does not know the configuration status of the subordinate site. Some of such scenarios are as follows:
- Enable the automatic GSLB configuration synchronization feature for the first time.
- Reboot the NetScaler appliance.
- GSLB deployment has multiple main sites, and another main site becomes the active main site.
- Add a new subordinate site to the GSLB deployment.
GSLB configuration full synchronization is performed in the following manner:
- The main site pushes its latest configuration file to all the subordinate sites.
- Each subordinate site compares its own configuration with the latest configuration file sent by the main site. The subordinate site identifies the difference in configuration, and applies the delta configuration for its own site.
- The subordinate site generates status logs at each step and copies them to a file at a specific location.
- The main site pulls the status log files from the specified location.
- The main site prepares a log file with logs combined from all the subordinate sites.
- This combined log file is stored in the “/var/netscaler/gslb/periodic_sync.log” file.
If you attempt to manually synchronize (with the sync gslb config
command) a site while it is being autosynchronized, a “Sync in progress” error message appears. Autosynchronization cannot be triggered for a site that is in the process of being synchronized manually.
Note:
Starting with NetScaler 12.1 build 49.37, SNMP traps are generated when you synchronize the GSLB configuration. In real-time synchronization, the synchronization status in the first SNMP trap is captured as failure. You can ignore this status because a second SNMP trap is automatically generated immediately after the first trap with the actual synchronization status. However, if the synchronization failed in the second attempt also, SNMP trap is not generated because the synchronization status has not changed from the previous synchronization status.
For details on configuring NetScaler appliance to generate traps, see Configuring the NetScaler to generate SNMP traps.
To enable GSLB full synchronization by using the CLI
set gslb parameter -GSLBSyncMode (IncrementalSync | FullSync)
<!--NeedCopy-->
Example:
set gslb parameter -GSLBSyncMode FullSync
<!--NeedCopy-->
To enable GSLB incremental synchronization by using the GUI:
- Navigate to Traffic Management > GSLB > Dashboard > Change GSLB settings.
- In the Set GSLB Parameters page, choose FullSync from the GSLB Sync Mode drop-down menu.
Multiple main sites in a GSLB deployment
The NetScaler appliance supports multiple main sites in an active-passive deployment. It is recommended to have two main sites in a GSLB deployment to cope against GSLB main site failure. Having two main sites can avoid single point of failure of GSLB configuration synchronization. At any time, only one main site can actively process the GSLB configuration from the user. If the configuration changes are performed simultaneously in more than one main site, it might lead to configuration inconsistency or configuration losses. Hence, it is recommended to perform configuration changes from only one main site at a time, and use the other main site as a backup when the active main site fails.
Note:
When multiple main sites are used in a GSLB deployment, RSYNC monitoring must be enabled.
To make a GSLB node as one of the main sites for GSLB configuration synchronization, run the following command:
set gslb parameter -automaticConfigSync Enabled
<!--NeedCopy-->
Share
Share
In this article
- Best practices for using the real-time synchronization feature
- To enable real-time synchronization by using the CLI
- To enable real-time synchronization by using the GUI
- Points to note
- Incremental synchronization of GSLB configuration
- Full synchronization of GSLB configuration
- Multiple main sites in a GSLB deployment
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.