Unable to set up HA in GUI after upgrading to 14.1

Unable to set up HA in GUI after upgrading to 14.1

book

Article ID: CTX575058

calendar_today

Updated On:

Description

After upgrading to 14.1 4.42, when trying to add HA node from GUI, the following error will be thrown even RPC password is correct.

image.png

Changing RPC password from GUI will not help to resolve this issue.

image.png

Resolution

* Please test and verify the change before implementation.

1) In  ADC #1 's CLI, add the opposite node ADC#2, just ignore the warning(node ID 0 is for the local ADC, ID 1 is for the remote ADC).

> add HA node 1 <ADC#2 IP>
Warning: One or more RPC nodes are configured with default passwords. For enhanced security, you must change the default RPC node password.
 Done

On ADC#1, the ADC#2 's status shows as unknown at this time.
image.png

On ADC#2, the ADC#1 can not be seen at this time.

image.png 

2) In  ADC #2 's CLI, add the opposite node ADC#1, the same warning displays, ignore it.

> add HA node 1 <ADC#1 IP>
Warning: One or more RPC nodes are configured with default passwords. For enhanced security, you must change the default RPC node password.
 Done

The opposite node's status displays as UP, and sysnchronization state becomes success.

image.png

image.png


3) (Notes) Don't try to change RPC password before set up HA.
If you change the self-node's RPC password before adding opposite node in CLI as below,

> set ns rpcnode <ADC#1/ADC#2> -password ****
 Done
> add HA node 1 <ADC#2/ADC#1>
Warning: One or more RPC nodes are configured with default passwords. For enhanced security, you must change the default RPC node password.
 Done

The follwing error will display:

image.png

For a solution, reset RPC password on self-node both on the two nodes from GUI, the synchronization state will become success.

image.png
 

Problem Cause

After upgrading to 14.1, "RPC Node Password" is a required parameter in GUI, but there is not a related parameter in CLI command "add HA node". Adding opposite node separatedly on the two nodes' CLI is a workaround for this issue.

Additional Information

https://docs.netscaler.com/en-us/citrix-gateway/current-release/high-availability/ng-ha-config-for-ha-tsk/ng-ha-add-rpc-node-tsk.html

https://support.citrix.com/article/CTX116748/how-to-set-up-a-high-availability-pair-on-adc ​​​​​​​