-
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)
此内容已动态机器翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
This content has been machine translated dynamically.
This content has been machine translated dynamically.
This content has been machine translated dynamically.
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.
这篇文章已经过机器翻译.放弃
Translation failed!
Support for heterogeneous cluster
NetScaler appliance now supports 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.
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 |
Note
If you run the “join cluster” command 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”.
Limitations of using heterogeneous cluster
- The number of packet engines present on all of the MPX hardware appliances should be same in the cluster deployment.
- The extra management CPU setting should be same on all the cluster nodes.
- The newly added node should 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 would agree upon a common cipher list.
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix 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 Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.