|
1) By default, the 'capability-route-refresh' is enabled under the BGP neighbor.
# config router bgp
config neighbor
edit <BGP-NEIGHBOR-IP>
set capability-route-refresh enable
next
end
end
2) Route refresh capability must have been negotiated in BGP OPEN message when the BGP session establishes.
vdom2 # get router info bgp neighbors 10.200.2.2 | grep refresh
Route refresh: advertised and received (old and new)
Route refresh request: received 0, sent 3
3) Command to perform the route refresh.
Fortigate# execute router clear bgp ip <neighbor_ip> [in|out]
out: Resend all routes to the neighbor in the BGP UPDATE message without resetting the connection. Recommended when changing outbound policy. FortiGate does not send the ROUTE-REFRESH request message to the BGP neighbor.
in : Sends a ROUTE-REFRESH request message to the BGP neighbor so that neighbor re-sends all BGP routes in the BGP UPDATE message. Recommended when changing inbound policy.
4) Ensure that 'soft-reconfiguration' should be disabled, else 'soft-reconfiguration' will take precedence over the by default enabled 'capability-route-refresh' and the FortiGate will store a separate unmodified database of all routes from a BGP neighbor in addition to the RIB which unnecessarily consumes more memory.
# config router bgp
config neighbor
edit <BGP-NEIGHBOR-IP>
set capability-route-refresh enable
set soft-reconfiguration disable
next
end
end
5) As of now FortiGate does not support the BGP capability code 70 'Enhanced route refresh capability' [RFC7313]. If the BGP neighbor (another vendor device) supports that capability, BGP negotiation will still succeed with the FortiGate as the 'ignore-optional-capability' command is by default enabled under BGP.
# config router bgp
set ignore-optional-capability enable
end
|
