ADC

Upgrade recommendations for GSLB deployment

August 1, 2023

Contributed by:

This section provides recommendations on the sequence in which GSLB nodes need to be upgraded in various GSLB setups. It also addresses a few FAQs.

Note: The NetScaler appliance from which the GSLB synchronization is started is referred to as the ‘main site’ and the GSLB sites on which the configuration is copied as the ‘subordinate sites’.

Before you start the upgrade process, read the prerequisites mentioned in the following topics:

Points to note when upgrading GSLB setups

In an HA setup, first upgrade the subordinate sites and then the main site.
In an HA setup, service states might not propagate from an older build primary node to a newer build secondary node. However, if the builds are of different versions, but have the same HA version, the service state might still propagate.
If GSLB is configured within a cluster, first upgrade the non-owner nodes, and then upgrade the owner node. If there is one site or multiple sites in a cluster, follow the same upgrade sequence in each of the site.
Enable new GSLB features only after you upgrade all nodes to a newer build.
Upgrade all GSLB nodes to the latest build. There is no functional impact on the available features when some of the GSLB nodes are using an older version and some of the GSLB nodes are upgraded to a newer version.

FAQs

Are GSLB service states propagated when instances run different software versions?

GSLB MEP is functional when instances run on different versions and GSLB service states are propagated across GSLB sites. There is no impact on the MEP communication when instances run different versions after an upgrade.
Is it recommended to do configuration changes during an upgrade?

In a GSLB setup, when a main site is being upgraded, it is not recommended to do configuration changes on any other GSLB nodes.

The following resources provide information about upgrading a NetScaler instance using NetScaler Console:

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Upgrade recommendations for GSLB deployment

August 1, 2023

Contributed by:

August 1, 2023

Contributed by:

Upgrade recommendations for GSLB deployment

Points to note when upgrading GSLB setups

FAQs

Related resources

In this article