FCSS_EFW_AD-7.6 · Question #77
Refer to the exhibits. Network topology Output from the command config system ha A network diagram and the output from the command config system ha are shown. The administrator has configured the…
The correct answer is D. The administrator must reconfigure the heartbeat interface. Option D is correct because FortiGate HA cluster formation depends on the heartbeat interfaces being correctly configured and matching between both cluster members - if the wrong interface is specified (or the designated heartbeat port isn't physically connected between the…
Question
Refer to the exhibits. Network topology Output from the command config system ha A network diagram and the output from the command config system ha are shown. The administrator has configured the cluster with the commands shown in the exhibit. Why is the HA cluster not forming?
Exhibits
Options
- AThe administrator must reconfigure the monitor interface.
- BThe administrator must reconfigure the cluster in active-active mode.
- CThe administrator must reconfigure the cluster in FGSP mode.
- DThe administrator must reconfigure the heartbeat interface.
How the community answered
(65 responses)- A6% (4)
- B12% (8)
- C34% (22)
- D48% (31)
Explanation
Option D is correct because FortiGate HA cluster formation depends on the heartbeat interfaces being correctly configured and matching between both cluster members - if the wrong interface is specified (or the designated heartbeat port isn't physically connected between the units), the devices cannot discover each other and the cluster will never form. The exhibits likely show a mismatch between the configured hbdev (heartbeat device) and the actual interface being used, or the heartbeat interface is assigned to a port that isn't directly interconnecting the two FortiGates.
Why the distractors are wrong:
- A (monitor interface): Monitor interfaces track link state for failover triggering, but their misconfiguration causes failover issues, not cluster formation failure.
- B (active-active mode): Both active-passive and active-active modes form clusters the same way; mode selection doesn't block cluster discovery.
- C (FGSP mode): FGSP (FortiGate Session Life Support Protocol) is an alternative clustering method for devices that can't use traditional HA heartbeat links - choosing it isn't a fix unless the topology truly requires it, and nothing in the scenario suggests that.
Memory tip: Think of the heartbeat interface as a "handshake" - if the two FortiGates can't shake hands (wrong port or wrong cable), they'll never agree they're in a cluster. Always verify hbdev in config system ha matches the physically connected interface on both units.
Topics
Community Discussion
No community discussion yet for this question.