-
Distributing traffic across cluster nodes
-
Managing the NetScaler cluster
-
Node groups for spotted and partially striped configurations
-
Removing a node from a cluster deployed using cluster link aggregation
-
Detecting jumbo probe on a cluster
-
Monitoring command propagation failures in a cluster deployment
-
Monitor Static Route (MSR) support for inactive nodes in a spotted cluster configuration
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!
Detecting jumbo probe on a cluster
If a jumbo frame is enabled on a cluster interface, the backplane interface must be large enough to support the all packets in the jumbo frame. It is achieved by setting the Maximum Transmission Unit (MTU) of the backplane.
The configured MTU value must be the same across all nodes in the cluster for the following:
- Server data plane (X)
- Client data plane (Y)
- Backplane: The configured MTU value must be set to 78 + a maximum of X and Y.
Note:
The MTU values for the server data plane (X) and client data plane (Y) need not be the same.
For example, if the MTU of a server data plane is 7500 and of the client data plane is 8922 across the cluster, then the MTU of a cluster backplane must be set to 78 + 8922 = 9000 across the cluster.
To verify the preceding configuration, you must send a jumbo probe (of the preceding computational size) to all the peer nodes of a cluster setup. If the probe does not succeed, the appliance displays a warning message in the output of the show cluster instance
command.
In the command interface mode, type the following command:
> show cluster instance
Cluster ID: 1
Dead Interval: 3 secs
Hello Interval: 200 msecs
Preemption: DISABLED
Propagation: ENABLED
Quorum Type: MAJORITY
INC State: DISABLED
Process Local: DISABLED
Cluster Status: ENABLED(admin), ENABLED(operational), UP
Warning:
The MTU for a backplane interface must be large enough to handle all packets in the frame. It must be equal to
<MTU\_VAL>
. If the recommended value is not user configurable, you must review the MTU value of jumbo interfaces.
Sl. no | Member Nodes | Health | Admin State | Operation State |
---|---|---|---|---|
1 | Node ID: 1; Node IP: 10.102.53.167 | UP | Active | ACTIVE (Configuration Coordinator) |
2 | Node ID: 2; Node IP: 10.102.53.168 | UP | Active | Active |
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.