Instruction manual

Chapter 3: High Availability
3-18 NetScaler 9000 Series Installation and Configuration Guide - Volume 1
NSICG60_JAN05
The set ns node command will not be propagated or synchronized, and
affects only the node on which the command is executed.
To ensure that the unit is put back as an active HA unit, use the following
command:
set ns node –hastatus ENABLE
3.9 Troubleshooting HA Issues
This section provides troubleshooting information for some of the existing
High Availability feature issues.
1. Improper synchronization of VLAN Configuration in High Availability
NetScaler 9000 systems
Ensure that the VLAN configuration is done after configuring the
NetScaler 9000 system with the High Availability setup.
For NetScaler 9000 systems in High Availability setup, synchronization
does not work properly when only one NetScaler 9000 system has a
VLAN configuration.
2. Retrieving lost configuration
If the primary NetScaler 9000 system is unable to send the configuration
to the secondary NetScaler 9000 system because of any network error
then the secondary NetScaler 9000 system may not have an accurate
configuration and may not behave correctly if failover occurs.
In this situation, you can retrieve the original primary NetScaler 9000
system’s configuration from a back-up copy present in the NetScaler
9000 systems disk. The NetScaler 9000 system saves the last four copies
of the ns.conf file in the /nsconfig directory. These are named
ns.conf.0, ns.conf.1, and so on. The ns.conf.0 file contains
the latest configuration.
To retrieve the NetScaler 9000 system’s configuration, proceed as
follows:
a. Exit from the CLI to FreeBSD by entering this CLI command:
>shell
b. Enter the following FreeBSD commands to determine the name of the
latest backup copy (based on the timestamp of the file):
#ls -lt /nsconfig/ns.conf.? | head -1