-
Distributing traffic across cluster nodes
-
Support for heterogeneous 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!
Support for heterogeneous cluster
NetScaler supports a heterogeneous cluster in a cluster deployment. A heterogeneous cluster spans nodes of different NetScaler hardware and you can have a combination of different platforms in the same cluster.
Important:
The formation or supportability of a heterogeneous cluster is possible and limited only to MPX hardware platforms.
The supportability and formation of the heterogeneous cluster depend on certain NetScaler models. The following table lists the platforms that are supported in the formation of a heterogeneous cluster, with an equal number of packet engines.
| Number of Packet Engines | MPX Hardware Platforms | Supported MPX Hardware Platforms to form Heterogeneous Cluster |
|---|---|---|
| 5 | MPX 11500 | MPX 14020 |
| 7 | MPX 11515 | MPX 14040 |
| 9 | MPX 11530 | MPX 14060 |
For more information on how to form a heterogeneous cluster deployment of NetScaler MPX appliances with the different number of packet engines across different SSL chipsets, see the Heterogeneous cluster deployments section in SSL offloading configuration.
Note:
Before release 13.0 build 47.x, if you run the
join clustercommand from the node that has an unequal number of packet engines, the following error message appears: “Mismatch in the number of active PPEs between CCO and local node”.
Points to note
- The extra management CPU setting must be the same on all the cluster nodes.
- The newly added node must have the same capacity on the data planes and backplane, as that of existing cluster nodes.
- If there are mixed platform devices supporting different ciphers, then the cluster agrees upon a common cipher list.
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.