Which settings should be checked first when troubleshooting an HPE switch stack with inter- switch latency?

Question

Options

• AStack cable connections
• BSpanning tree configuration
• CMTU configuration
• DStack firmware versions

• A
  75% (38)
• B
  25% (13)

Explanation

When troubleshooting inter-switch latency in an HPE stack, physical stack cable connections (A) are checked first because a degraded or faulty cable is the most common cause of latency and performance degradation in stacked environments. MTU mismatches (C) cause packet fragmentation or drops between stack members, directly introducing latency and retransmissions. Firmware version mismatches (D) between stack members are a known source of instability and latency because members may handle packets differently or fall back to slower compatibility modes.

Spanning tree (B) is the distractor - while STP can cause forwarding delays, it operates at Layer 2 and its timers affect convergence, not ongoing inter-switch latency in a properly converged stack. In a stack, members typically share a single STP instance, making STP configuration less relevant than the physical and firmware layer.

Memory tip: Think CAF - Cables first (physical), then Adjust MTU (logical), then Firmware sync (software). Spanning tree is a red herring because stacks abstract away most inter-switch STP concerns.

No community discussion yet for this question.