This section covers the steps to enable suspended mode.

In the suspended mode, configuration changes are prohibited only on the active follower sites participating in the upgrade or maintenance activity. The other sites (the leader sites and the remaining active follower sites) still participate in the GSLB process.

In suspended mode, the GSLB leader sites accept the configuration. The configuration changes are synchronized to all the follower sites except the one on which the suspended mode is enabled. If an error or incorrect configuration occurs, it is localized to the specific site only. The errors or crash issues do not get propagated to the other sites, and do not affect the application hosted through GSLB. The application is accessible while the upgrade or maintenance work continues on one of the active follower sites.

In suspended mode, configuration on the GSLB leader is not prohibited and it can have all the create, read, update, and delete (CRUD) operations. After the upgrade, once the follower site is set to no suspended mode, the follower will receive all the configuration from the leader site.

Note:

  • It is applicable to the follower site only. It cannot be applied to the leader site.

  • All configuration sync is performed once the site exits the suspended mode.

  • After the upgrade, the one-time configuration synchronization is performed between the follower sites and the leader site.

Enabling Suspend Mode

Login to the Avi Load Balancer CLI and follow the step mentioned below:

[admin-controller]: configure gslb default
[admin-controller]: gslb> site index 1
[admin-controller]: gslb> suspended_mode

Post the upgrade of the follower site, the no suspended mode is enabled on the follower, and it syncs the information available on the leader site.

[admin-controller]: configure gslb gs1
[admin-controller]: gslb> site index 1
[admin-controller]: gslb> no suspended_mode
Note:

Disable the DNS virtual services on the active follower site when enabling the suspended mode on a specific site. Once the planned activity is over, re-enable the DNS virtual services.