-
Distributing traffic across cluster nodes
-
Upgrading or downgrading the NetScaler cluster
-
Test the traffic on a single node during cluster upgrade
-
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!
Test the traffic on a single node during cluster upgrade
Testing traffic on a specific node during a cluster upgrade is crucial to ensure system stability and traffic integrity. When upgrading a cluster, it is recommended to upgrade nodes one at a time during the maintenance window. You can’t test the traffic on partially upgraded clusters because traffic can go through nodes that are not upgraded.
If traffic fails after completing the upgrade, a full downgrade might be required, which is time-consuming and depends on the number of nodes in the cluster.
Starting from NetScaler 14.1 Build 43.x, a new command is available to help test traffic on a single node during upgrade by using the policy-based backplane steering (PBS) mechanism with the nodeid parameter.
Important:
Use this feature only during the upgrade process. You must remove the ACL after the upgrade is completed. Do not use this feature in normal cluster operations.
Before upgrading a specific node, run the following command on the CLIP:
add ns acl <name_of_ACL> ALLOW -srcIP = <source_IP> -destIP = <destination_ip> -type DFD -nodeid <node_id>
apply acls -type DFD
Example:
add ns acl Sample_ACL ALLOW -srcIP = 10.1.1.150 -destIP = 24.1.1.1 -type DFD -nodeid 2
apply acls -type DFD
The general upgrade process includes the following steps:
- Identify the maintenance window.
-
Apply the ACL on CLIP. Use the following command on CLIP before upgrading a node. Save the configuration.
add ns acl <name_of_ACL> ALLOW -srcIP = <source_IP> -destIP = <destination_ip> -type DFD -nodeid <node_id> apply acls -type DFD - Upgrade and reboot the node for which you applied the ACL.
- Test the traffic that matches the attributes mentioned in the ACL. It must be steered to the specific node id.
- Verify if the traffic is functioning properly.
- If the traffic works as expected, proceed with upgrading the remaining nodes.
-
After completing the upgrade, remove the ACL from CLIP using:
rm ns acl <name_of_ACL> apply acls -type DFD
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.