-
Getting Started with Citrix ADC
-
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
-
Deploy a Citrix ADC VPX instance
-
Install a Citrix ADC VPX instance on Microsoft Hyper-V servers
-
Install a Citrix ADC VPX instance on Linux-KVM platform
-
Prerequisites for Installing Citrix ADC VPX Virtual Appliances on Linux-KVM Platform
-
Provisioning the Citrix ADC Virtual Appliance by using OpenStack
-
Provisioning the Citrix ADC Virtual Appliance by using the Virtual Machine Manager
-
Configuring Citrix ADC Virtual Appliances to Use SR-IOV Network Interface
-
Configuring Citrix ADC Virtual Appliances to use PCI Passthrough Network Interface
-
Provisioning the Citrix ADC Virtual Appliance by using the virsh Program
-
Provisioning the Citrix ADC Virtual Appliance with SR-IOV, on OpenStack
-
Configuring a Citrix ADC VPX Instance on KVM to Use OVS DPDK-Based Host Interfaces
-
-
Deploy a Citrix ADC VPX instance on Microsoft Azure
-
Network architecture for Citrix ADC VPX instances on Microsoft Azure
-
Configure multiple IP addresses for a Citrix ADC 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
-
Configure a high-availability setup with a single IP address and a single NIC
-
Configure address pools (IIP) for a Citrix Gateway appliance
-
Configure multiple Azure VIPs for a standalone or high availability Citrix ADC instance
-
-
Authentication, authorization, and auditing application traffic
-
-
-
-
-
-
-
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 14: ShareFile wizard for load balancing Citrix ShareFile
-
-
-
-
-
Authentication and authorization
-
-
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 Citrix ADC Appliance and Cisco IOS Device
-
CloudBridge Connector Tunnel Diagnostics and Troubleshooting
-
-
Synchronizing Configuration Files in a High Availability Setup
-
Restricting High-Availability Synchronization Traffic to a VLAN
-
Understanding the High Availability Health Check Computation
-
Managing High Availability Heartbeat Messages on a Citrix ADC Appliance
-
Remove and Replace a Citrix ADC in a High Availability Setup
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)
此内容已动态机器翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
This content has been machine translated dynamically.
This content has been machine translated dynamically.
This content has been machine translated dynamically.
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.
这篇文章已经过机器翻译.放弃
Translation failed!
Upgrade a high availability pair
One of the requirements of Citrix ADC appliances in a high availability setup is to install the same Citrix ADC software release on both appliances of the setup. Therefore, when software on one appliance is upgraded, ensure that the software is upgraded on both the appliances.
You can follow the same procedure to upgrade a standalone appliance or each appliance in a high availability pair, although additional considerations apply to upgrading a high availability pair.
Before you start a Citrix ADC firmware upgrade on an HA pair, read the prerequisites mentioned in the Before you begin section. Also, you need to consider a few HA-specific points.
Points to note
-
First upgrade the secondary node, and then the primary node. Upgrading software on the secondary appliance before the primary appliance ensures that the upgrade process is completed without any issues.
- If the two nodes in an HA configuration are running different Citrix ADC software releases, the following information does not get synchronized on the primary and secondary nodes:
- Configuration propagation and synchronization
- States of the services
- Connection failover sessions
- Persistence sessions
- The above information might not get synchronized on the primary and secondary nodes if the two nodes are running different builds of the same release. Refer to the Known Issues section of the release notes to check if your Citrix ADC build has this issue.
- Synchronization of the files in the All mode of the Sync HA files command works successfully if the two nodes in an HA configuration are running different Citrix ADC software releases, or the two nodes are running different builds of the same release. For more information, see Synchronising Configuration Files in High Availability Setup.
Figure. Upgrade a high availability pair
You can upgrade using the Citrix ADC CLI or GUI.
Upgrade a high availability pair by using the CLI
The upgrade process includes the following steps:
- Upgrade software on the secondary appliance
- Upgrade software on the primary appliance
- Synchronize secondary appliance
Upgrade software on the secondary appliance
The following illustration depicts the procedure to upgrade software on the secondary appliance:
-
Log on to the secondary NetScaler appliance using an SSH utility, such as PuTTY and specifying the NetScaler IP (NSIP). Use the nsroot credentials to log on to the appliance.
-
From the command line interface of the appliance, type the following command to save the existing configuration: save config
-
Switch to the shell prompt.
login as: username Using keyboard-interactive authentication. Password: Last login: Wed Jun 24 14:59:16 2015 from 10.252.252.65 Done > shell Copyright (c) 1992-20
-
Run the following command to change to the default installation directory: # cd /var/nsinstall
-
Run the following command to create a temporary subdirectory of the nsinstall directory: # mkdir x_xnsinstall
Note: The text x_x is used to name the NetScaler version for future configurations. For example, the directory for the installation files of NetScaler 9.3 us called 9_3nsinstall. Do not use a period (.) in the folder name, it can cause failed upgrades.
-
Change to the x_xnsinstall directory.
-
Download the required installation package and documentation bundle, such as “ns-x.0-xx.x-doc.tgz,” to the temporary directory created in Step 4.
Notes:
- Some builds do not have a documentation bundle as it does not have to be installed.
- Click the Documentation tab from the GUI to access the documentation.
-
Before you run the install script, the files must be extracted and placed on the appliance. Use the following command to uncompress the bundle downloaded from Citrix website: tar -zxvf ns-x.0-xx.x-doc.tgz. The following is a quick explanation of the parameters used.
x: Extract files
v: Print the file names as they are extracted one by one
z: The file is a “gzipped” file
f: Use the following tar archive for the operation
-
Run the following command to install the downloaded software: # ./installns
Note: If the appliance does not have sufficient disk space to install the new kernel files, the installation process performs an automatic cleanup of the flash drive.
-
After the installation process is complete, the process prompts to restart the appliance. Press y to restart the appliance.
-
Log on to the appliance Command Line Interface using the nsroot credentials.
-
Run the following command from to display the state of the NetScaler appliance: show ha node The output of the preceding command should indicate that the appliance is a secondary node and synchronization is disabled.
-
Run the following command to disable synchronization on the appliance if synchronization is not disabled: set ha node -hasync disabled
-
Ensure that the configuration is complete and as expected.
-
Run the following command to perform a force failover and takeover as primary appliance: force failover
Here’s a sample configuration in the new primary node.
login: nsroot
Password: nsroot
Last login: Monday Apr 17 08:37:26 2017 from 10.102.29.9
Done
show ha node
2 nodes:
1) Node ID: 0
IP: 10.0.4.2
Node State: UP
Master State: Primary
...
Sync State: AUTO DISABLED
Propagation: AUTO DISABLED
...
Done
Upgrade software on the primary appliance
The following illustration depicts the procedure to upgrade software on the primary appliance:
Note: After completing the “Upgrade software on the secondary appliance” procedure, the original primary appliance is now a secondary appliance.
-
Log on to the secondary NetScaler appliance using an SSH utility, such as PuTTY. Use the nsroot credentials to log on to the appliance. Follow the same steps as mentioned in the above section to complete the installation process. We have to follow the same steps as mentioned in step 2 to step 9 in the previous section(Upgrade software of the secondary appliance)
-
After the installation process is complete, the process prompts to restart the appliance. Press y to restart the appliance.
-
Log on to the appliance Command Line Interface using the nsroot credentials.
-
Run the following command to display the state of the NetScaler appliance: show ha node. The output of the preceding command should indicate that the appliance is a primary node and the status of the node state is marked as UP.
-
Run the following command to perform a force failover to ensure that the appliance is a primary appliance: force failover
-
Verify that the appliance is a primary appliance.
Enable synchronization on the secondary appliance
To enable synchronization on the secondary appliance, complete the following procedure:
-
Run the following command to verify that the appliance is a secondary appliance: show node
-
Run the following command to enable synchronization on the appliance: set ha node -hasync enabled
-
Run the following command to verify that the configuration of the secondary appliance is synchronized with that of the primary appliance: show ns runningconfig
Here’s an example configuration of the new primary node and the new secondary node.
show ha node
Node ID: 0
IP: 10.0.4.11
Node State: UP
Master State: Primary
...
...
INC State: DISABLED
Sync State: ENABLED
Propagation: ENABLED
Enabled Interfaces : 1/1
Disabled Interfaces : None
HA MON ON Interfaces : 1/1
...
...
Local node information
Critical Interfaces: 1/1
Done
Show ha node
Node ID: 0
IP: 10.0.4.2
Node State: UP
Master State: Secondary
..
..
INC State: DISABLED
Sync State: SUCCESS
Propagation: ENABLED
Enabled Interfaces : 1/1
Disabled Interfaces : None
HA MON ON Interfaces : 1/1
. . .
. . .
Local node information:
Critical Interfaces: 1/1
Done
Upgrade a high availability pair by using the GUI
Follow these steps to upgrade a Citrix ADC pair in a high availability setup, by using the GUI:
-
Log on to the secondary node and perform the upgrade as described in the section “Upgrade a Citrix ADC standalone appliance by using the GUI” in Upgrade a Citrix ADC standalone appliance.
-
Log on to the primary node and perform the upgrade as described in the section “Upgrade a Citrix ADC standalone appliance by using the GUI” in Upgrade a Citrix ADC standalone appliance.
Upgrade a high availability pair
Share
Citrix Preview Documentation
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix 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 Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.