Why is FortiGate not sending probes to 4.2.2.2 and 4.2.2.1 servers?

Refer to the exhibit.

An administrator has configured a performance SLA on FortiGate, which failed to generate any traffic.

Why is FortiGate not sending probes to 4.2.2.2 and 4.2.2.1 servers? (Choose two.)

A. The Detection Mode setting is not set to Passive.

B. Administrator didn’t configure a gateway for the SD-WAN members, or configured gateway is not valid.

C. The configured participants are not SD-WAN members.

D. The Enable probe packets setting is not enabled.

Answer: B,D

Explanation:

The correct answers are:

B. Administrator didn’t configure a gateway for the SD-WAN members, or configured gateway is not valid.

D. The Enable probe packets setting is not enabled.

For option B, if the gateway for the SD-WAN members is not configured or is not valid, the FortiGate will not be able to send traffic through the SD-WAN members to reach the servers.

For option D, if the "Enable probe packets" setting is not enabled, the FortiGate will not send probe packets to the specified servers to check the health of the SD-WAN members.

A. The Detection Mode setting is not set to Passive.

NO – passive mode uses session information from the configured policy

C. The configured participants are not SD-WAN members.

NO – It is not possible to add participants that do not belong to the SW-WAN