You are designing a setup where the FortiGate device is connected to two upstream ISPs using BGP. Part of the requirement is that you must be able to refresh the route advertisements manually without disconnecting the BGP neighborships.
Which feature must you enable on the BGP neighbors to accomplish this goal?
To refresh route advertisements manually without disconnecting BGP neighborships on a FortiGate device, you must enable the soft-reconfiguration feature on the BGP neighbors. This feature allows BGP peers to update routing tables without tearing down and re-establishing the BGP session, ensuring continuous connectivity while applying new routing policies or filters.
https://community.fortinet.com/t5/FortiGate/Technical-Tip-BGP-soft-reset-to-refresh-BGP-routing-table/ta-p/190141
D Seems correct
The soft reconfigure is correct by elimination (FGTs all support BGP Refresh, so question is not worded correctly - to refresh routes in advertisements, there is no need to do manually anything, after the change is committed to config FGT will send BGP Refresh message to the peers to notify them of it. The same is true for Cisco and Juniper routers. The question should ask "when routing policy was changed" - then yes, reconfiguraiton is the way to notify BGP peers that BGP policy was changed. Anyway: Graceful restart - tells BGP neighbors to keep the routes advertised by peer even when peer GOES DOWN, i.e. it contradicts with the question condition that BGP session should not go down. Synchronization - unrelated at all, refers to the ancient rule that routes advertised/learned via BGP HAVE to be first learned via IGP (like OSPF/IS-IS/etc) to prevent loops in iBGP topology. No one uses it anymore, everyone either disables synchronization or it is disabled (as in FGTs) by default. Dterermenistic MED - is about route preference between EBGP peers, unrelated at all to the question.
correct is A
sorry D is correct set soft-reconfiguration
D Seems correct. When the BGP routing policy is changed (such as by changing the attributes or adding filters), it is necessary to reset the BGP session before the new policy takes effect. A soft reset is recommended to refresh the BGP routing table without disturbing existing BGP peering sessions. To do this, first enable soft-reconfiguration: # config router bgp # config neighbor edit 10.0.0.1 set soft-reconfiguration enable end end Use the following command to perform a soft reset: