|
When routes to the FortiGate are received from the BGP neighbor, the next hop shows as 0.0.0.0:
# get router info bgp neighbors 10.5.50.1 routes
VRF 0 BGP table version is 33, local router ID is 10.51.4.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight RouteTag Path
*>i10.5.10.128/25 0.0.0.0 0 100 0 0 i <-/1>
*>i10.5.10.64/26 0.0.0.0 0 100 0 0 65070 i <-/1>
*>i10.21.5.60/31 0.0.0.0 0 100 0 0 i <-/1>
*>i10.21.4.5/32 0.0.0.0 0 100 0 0 i <-/1>
BGP configuration:
# config router bgp
config neighbor-group
edit "Spoke-1"
set route-map-in "RMP-IN"
set route-map-out "RMP-OUT"
next
end
If there are route-maps configured for the BGP neighbor, check the config for route-map:
# config router route-map
edit "RMP-IN"
config rule
edit 1
set action deny
set match-ip-address "Transit_In"
set set-ip-nexthop 0.0.0.0
set set-ip6-nexthop ::
set set-ip6-nexthop-local ::
set set-originator-id 0.0.0.0
next
edit 20
set set-ip-nexthop 0.0.0.0
set set-ip6-nexthop ::
set set-ip6-nexthop-local ::
set set-originator-id 0.0.0.0
next
end
As shown above, 'set set-ip-nexthop 0.0.0.0' is configured on the route-map, replacing the next hop with 0.0.0.0.
This is a known issue 845656 with FortiManager 7.0.5. Read more here: https://docs.fortinet.com/document/fortimanager/7.0.5/release-notes/454729/known-issues
if possible, avoid upgrading FortiManager 7.0.4 to FortiManager 7.0.5 incase BGP with route maps is used.
|
