You are deploying a pair of PA-5250 firewalls in active/passive HA mode for a large enterprise. The firewalls are configured with multiple virtual routers (VRs) to segment traffic: VR-A for internal corporate network, VR-B for DMZ, and VR-C for Internet edge. Each VR is associated with a separate Vsys. The HA pair uses IPsec tunnel monitoring to determine failover. The customer reports that after a recent configuration change, failover does not occur when the primary firewall's Internet-facing interface (ethernet1/1) goes down. You verify that the primary firewall detects the interface failure, but the secondary does not take over. The HA configuration shows: 'monitor failure only' set to 'link-status', 'monitor hold time' 1000ms, 'promotion hold time' 2000ms, and 'monitor failure condition' is 'any'. The IPsec tunnel monitoring is configured for tunnel to a remote site. The path monitoring includes the Internet-facing interface under VR-C. What is the most likely reason for the failover failure?
Trap 1: The use of multiple virtual routers prevents HA from monitoring…
HA monitoring is per-Vsys and can monitor interfaces in different VRs within the same Vsys.
Trap 2: The 'monitor hold time' is too short, causing flapping to be…
1000ms is a standard value and would not prevent failover detection.
Trap 3: The 'monitor failure only' is set to 'link-status' instead of…
While path monitoring is more comprehensive, link-status should still trigger failover for a direct interface failure.
- A
The use of multiple virtual routers prevents HA from monitoring interfaces across VRs.
Why wrong: HA monitoring is per-Vsys and can monitor interfaces in different VRs within the same Vsys.
- B
The IPsec tunnel monitoring is configured, but it is not a valid HA monitoring method; only path, interface, and route monitoring are supported.
IPsec tunnel monitoring is not an HA monitoring method; the firewall may not consider it for failover decisions.
- C
The 'monitor hold time' is too short, causing flapping to be ignored.
Why wrong: 1000ms is a standard value and would not prevent failover detection.
- D
The 'monitor failure only' is set to 'link-status' instead of 'path-monitoring'.
Why wrong: While path monitoring is more comprehensive, link-status should still trigger failover for a direct interface failure.