Based on best practices, if an SSID is configured for a primary and secondary gateway cluster with cluster preemption enabled, which will decide if the APs move to the secondary gateway cluster if…

Question

Options

• ATunnel orchestrator for LAN tunnel service in HPE Aruba Networking Central
• BCluster leader in the primary gateway cluster
• CEvery AP individually
• DCluster leader in the secondary gateway cluster

• A
  59% (24)
• B
  24% (10)
• C
  12% (5)
• D
  5% (2)

Explanation

In HPE Aruba Networking, when all nodes in the primary gateway cluster are down, the Tunnel Orchestrator (part of the LAN tunnel service in HPE Aruba Central) is the control-plane component responsible for detecting that failure and directing APs to move to the secondary gateway cluster - making A correct. The Tunnel Orchestrator maintains visibility across both clusters and enforces the preemption policy centrally.

Why the distractors are wrong:

• B (Cluster leader in the primary cluster): If all primary nodes are down, the cluster leader is also down - it cannot make any decisions.
• C (Every AP individually): APs don't independently decide to switch clusters; that would produce inconsistent, uncoordinated behavior across the network.
• D (Cluster leader in the secondary cluster): The secondary cluster leader handles APs after they've been redirected, but it doesn't trigger or decide the failover itself.

Memory tip: Think of the Tunnel Orchestrator as the "air traffic controller" - it sits above both clusters and directs traffic (APs) where to go when a runway (primary cluster) is closed. The clusters themselves are just the runways; they can't reroute planes if they're offline.

No community discussion yet for this question.