Instruction manual

Chapter 3: High Availability
3-14 NetScaler 9000 Series Installation and Configuration Guide - Volume 1
NSICG60_JAN05
For example, on primary NetScaler 9000 system NS1 type the following CLI
command
add lb vserver Server1 http 10.102.1.1 80
z To verify if the new server Server1 is added in NS1, type the following
command at the CLI prompt on NS1:
show lb vserver
This lists all the Load Balancing virtual servers present in NetScaler 9000
system NS1. Check that the new server
Server1 is displayed in this list.
z To verify the configuration propagation, on the secondary NetScaler 9000
system NS2, type the following command at the CLI prompt on NS2:
show lb vserver
Check that the new server Server1 that was added in NetScaler 9000
system NS1 is displayed in the existing Load Balancing virtual server list
in NS2.
3.5.1 Command Propagation Failure
The following are some of the command propagation failures and their work
arounds:
If a command propagation fails, the network connectivity between primary
and secondary NetScaler devices should be checked.
If a command execution succeeds on the primary NetScaler device but fails to
propagate on the secondary NetScaler device, run the command again on
secondary NetScaler device to see the exact error message. The error may
have occurred because the resources required by the command are present on
primary NetScaler device and are not available on the secondary NetScaler
device.
If the authentication failure error is displayed, verify if the user
nsroot exists
on both primary and secondary NetScaler devices and if the password for the
user is the same on both the primary and the secondary NetScaler devices.
3.6 Forced Synchronization
In addition to the automatic synchronization, the NetScaler system allows for
a forced synchronization between two nodes in an HA setup. To force