nerdexam
Fortinet

NSE8_812 · Question #28

Refer to the exhibit showing FortiGate configurations. ************************ FMG-A CONFIG ********************* config system ha set failover-mode vrrp set mode primary config monitored-ips edit…

The correct answer is A. Change the FortiManager IP address on the managed FortiGate to 10.3.106.65. See the full explanation below for the reasoning.

Question

Refer to the exhibit showing FortiGate configurations.
  • FMG-A CONFIG *

config system ha set failover-mode vrrp set mode primary config monitored-ips edit 1 set interface "port2" set ip "192.168.48.63" next end config peer edit 1 set ip 10.3.106.64 set serial-number "FMG-VM0A17001234" next end set priority 50 set vip "10.3.106.65" set vrrp-interface "port1" end
  • FMG-B CONFIG *

config system central-management set type fortimanager set serial-number "FMG-VM0A17001234" set fmg "10.3.106.63" end FortiManager VM high availability (HA) is not functioning as expected after being added to an existing deployment. The administrator finds that VRRP HA mode is selected, but primary and secondary roles are greyed out in the GUI. The managed devices never show online when FMG-B becomes primary, but they will show online whenever the FMG-A becomes primary. What change will correct HA functionality in this scenario?

Options

  • AChange the FortiManager IP address on the managed FortiGate to 10.3.106.65.
  • BMove the monitored IP to match on both FortiManager devices.
  • CUnset the primary and secondary roles in the FortiManager CLI configuration so VRRP will decide who is primary.
  • DChange the priority of FMG-A to be numerically lower for higher preference.

How the community answered

(48 responses)
  • A
    81% (39)
  • B
    2% (1)
  • C
    6% (3)
  • D
    10% (5)

Community Discussion

No community discussion yet for this question.

Full NSE8_812 Practice