-
Distributing traffic across cluster nodes
-
Troubleshooting the NetScaler cluster
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
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 multiplenewnslog
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.
Share
Share
In this article
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.