Description | This article describes why a default route or redundant route that is learned via eBGP is not installed in the FortiGate routing-table. |
Scope | FortiGate. |
Solution |
When FortiGate has two ISP BGP peering that are advertising the default route or the same route, FortiGate may not install the routes in the routing-table. This would be an expected behavior of BGP protocol to install one route only as its best route.
In this example, BGP peering is with 10.193.4.152 and 10.201.4.152 which both are advertising a default route and 172.21.0.0/20 subnet.
juara-kvm89 # get router info bgp summary VRF 0 BGP router identifier 10.1.1.1, local AS number 65510 Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
juara-kvm89 # get router info bgp neighbors 10.193.4.152 received-routes Network Next Hop Metric LocPrf Weight RouteTag Path Total number of prefixes 2
Network Next Hop Metric LocPrf Weight RouteTag Path
juara-kvm89 # get router info routing-table bgp B 172.21.0.0/20 [20/0] via 10.193.4.152 (recursive is directly connected, port9), 00:03:49, [1/0]
From the output of the routing-table, BGP is only installed from one peer only. To install both routes from both peers, the 'ebgp-multipath' would need to be enabled.
config router bgp
Below is the updated routing-table showing both routes from both peers.
juara-kvm89 # get router info routing-table bgp |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.