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 |