Standalone scenario in NetScaler firmware 11.0 build 71.22, 11.1 build 55.13 and 11.1 build 56.19

When binding Servers to a Service Group, the Servers need to be bound in the order of creation. For example, abc1.com.au and then abc2.com.au.  When both Servers are bound, if we unbind abc1.com.au, it was not allowing us to bind the abc1.com.au back. NetScaler throws an error “resource already exists”.

Work-around: Re-create abc1.com.au with a different FQDN and then re-bind it to the service group.

High Availability Scenario in NetScaler firmware 11.0 build 71.22, 11.1 build 55.13, and 11.1 build 56.19

When you bind abc1.com.au and abc2.com.au to a Service Group, on the primary appliance these configurations are present. But when we add another node in HA, we see that only abc2.com.au is propagated to the secondary node service group.

We tried changing abc1.com.au to a different FQDN on the primary, re-add the newly created FQDN (i.e test.com.au) to the Service Group, and did a re-sync. However, abc2.com.au disappeared and we see only test.com.au.

We broke the HA pair, re-added the original servers (i.e abc1.com.au and abc2.com.au), and then added the appliances back into an HA pair. However, on the secondary appliance, we can see once again that abc1.com.au disappears.

Standalone and HA Scenario on NetScaler firmware 12.0 build 56.20

When we did the same two tests on the VPX devices running 12.0 build 56.20, we did not come across any issue that we noticed while testing on the older firmware versions.

The issue seems to have been fixed in 12.0 build 56.20.

This is a known issue and has been rectified in the 12.0 release. Upgrade the firmware to 12.0 build 56.20.