FCSS_SDW_AR-7.4 · Question #50
An SD-WAN member is no longer used to steer SD-WAN traffic. The administrator updated the SD-WAN configuration and deleted the unused member. After the configuration update, users report that some…
The correct answer is B. FortiGate can remove some static routes associated with an interface when the member is. When an SD-WAN member is deleted, FortiGate can also remove static routes that were tied to that interface. If those routes are needed for destinations not covered by SD-WAN rules, traffic to those networks becomes unreachable. This explains why flows not matching SD-WAN rules…
Question
An SD-WAN member is no longer used to steer SD-WAN traffic. The administrator updated the SD-WAN configuration and deleted the unused member. After the configuration update, users report that some destinations are unreachable. You confirm that the affected flow does not match an SD-WAN rule. What could be a possible cause of the traffic interruption?
Options
- AFortiGate, with SD-WAN enabled, cannot route traffic through interfaces that are not SD-WAN
- BFortiGate can remove some static routes associated with an interface when the member is
- CFortiGate removes the layer 3 settings for interfaces that are removed from the SD-WAN
- DFortiGate administratively brings down interfaces when they are removed from the SD-WAN
How the community answered
(62 responses)- A13% (8)
- B77% (48)
- C6% (4)
- D3% (2)
Explanation
When an SD-WAN member is deleted, FortiGate can also remove static routes that were tied to that interface. If those routes are needed for destinations not covered by SD-WAN rules, traffic to those networks becomes unreachable. This explains why flows not matching SD-WAN rules are interrupted after the member was removed.
Topics
Community Discussion
No community discussion yet for this question.