If the appliance does not work as expected after you complete the installation, upgrade, or downgrade process, the first thing to do is to check for the most common causes of the problem.
The NetScaler appliance is not accessible after the software downgrade
During the software downgrade process, if the configuration file of the existing release and build does not match the configuration file of the earlier release and build, the appliance cannot load the configuration, and the default IP address is assigned to the appliance.
Configuration of the appliance is lost after you upgrade the software across multiple releases.
Some migration commands are built in for upgrading to the next release. Such commands might not be available across releases.
During an upgrade, if I run the command for synchronizing, the following message appears:
Command failed on the secondary node but succeeded on the primary node.
Do not run any dependent commands (set /unset /bind /unbind) when High Availability (HA) synchronization is in progress.
During an upgrade process, traffic does not pass through the new primary node when you run the force failover command.
In an HA pair, after you run the force HA failover command the devices keep rebooting. The secondary device does not come up after an upgrade.
Check to see if the /var directory is full. If so, remove the old installation files. Run the df –h command to show the available disk space.
After upgrading an HA pair, one of the nodes is listed as state UNKNOWN.
After you upgrade the NetScaler appliance, the interface shows most of the load balancing virtual servers and services are DOWN.
Verify that the SNIP address is active on the secondary appliance. Also, type the show service command to see if the service is running.
After performing an upgrade, all virtual servers are down on the secondary appliance.
After performing a downgrade, the NetScaler appliance does not boot up properly.
Check to see if the correct license has been installed.
In an HA pair, some features do not get synchronized after an upgrade is performed.
Run the sync ha file misc command to synchronize the configurations files from the primary node to secondary node.
During reboot, the following error message appears:
One or more commands in ns.conf failedWhat should I do?
Make sure that no command in the ns.conf file exceeds the 255 byte limit. In commands that create policies that are too long for the 255-byte limit, you can use pattern sets to shorten the policies.
add cs policy p11 -rule 'HTTP.REQ.URL.ENDSWITH_ANY("ctx_file_extensions")' Donectx_file_extensions is a default patset that covers a large number of extensions. In addition to the default pattern sets, you can create user-defined pattern sets. Add a patset by running the following command:
add patset <name>
When upgrading a NetScaler VPX appliance, I am told to free up space in /var. What files do I remove?
Remove the old installation files from /var/tmp/ directory. Also remove unwanted files from /flash.
There is no connectivity to the graphical user interface (GUI) when you run the force HA failover command on the secondary appliance.
Log on to the secondary appliance using the command line interface and enable the access to GUI by running the set ns ip <IP> -gui enabled command.
After performing an upgrade, and when I click on any link on the GUI that has to load a java applet (Upgrade Wizard or license Wizard), the following error message appears: GUI version does not match with the kernel version. Please close this instance, clear java plug-in cache and reopen.
These troubleshooting steps also apply to issues with configuration loss when downgrading the software across multiple releases.
For any other issue, see the release notes, Knowledge Center articles, and FAQs.