Troubleshooting the NetScaler cluster

If a failure occurs in a NetScaler cluster, the first step in troubleshooting is to get information on the cluster instance. You can get the information by running the show cluster instance clId and show cluster node nodeId commands on the cluster nodes respectively.

If you are not able to find the issue by using the above two approaches, you can use one of the following:

  • Isolate the source of the failure. Try bypassing the cluster to reach the server. If the attempt is successful, the problem is probably with the cluster setup.

  • Check the commands recently executed. Run the history command to check the recent configurations performed on the cluster. You can also review the ns.conf file to verify the configurations that have been implemented.

  • Check the ns.log files. Use the log files, available in the /var/log/ directory of each node, to identify the commands run, the status of commands, and the state changes.

  • Check the newnslog files. Use the newnslog files, available in the /var/nslog/ directory of each node, to identify the events that have occurred on the cluster nodes. You can view multiple newnslog files as a single file, by copying the files to a single directory, and then running the following command:

     nsconmsg -K newnslog-node<id> -K     newnslog.node<id> -d current

If you still cannot resolve the issue, you can try tracing the packets on the cluster or use the show techsupport -scope cluster command. You can use the command to send the report to the technical support team.

Troubleshooting the NetScaler cluster

In this article