Created on
‎07-07-2024
10:42 PM
Edited on
‎03-14-2025
07:50 AM
By
Jean-Philippe_P
Description | This article explains an issue with ADVPN with BGP as a routing protocol when redistributing connected routes is enabled. |
Scope |
An issue with some of the BGP neighbors will not establish or stay on the Active status when redistributing connected routes is enabled on ADVPN with BGP as the routing protocol setup.
Network Topology:
This issue occur because of a shortcut path created between Spoke1 and Spoke2. The tunnel IP of Spoke2 is seen as a connected route from Spoke1.
Since the redistribute connected routes is enabled, Spoke1 will go to advertise the route on the BGP because of this the HUB FortiGate will see the remote IP 10.10.10.4 route being received on the Spoke1.
This is the reason why BGP neighborship between HUB FortiGate and Spoke2 FortiGate is failing due to routing issue. |
Solution |
Note: To create a filter, open an advanced routing feature under System -> Feature Visibility and enable advanced routing.
If the connected route is enabled there will be two options (All or Filter):
Sample Prefix list:
Select the prefix list created on the Route Map Rules 'Match IP address' and then Apply.
Select the Route Map created on the Redistribute Connected Route filter.
Note: Create a Redistribute Connected Filter as well on the other spoke blocking the other Tunnel IP to be advertised.
Once All the tunnel IP addresses were blocked to be advertised via BGP, the routing table on the Hub FortiGate should look like this. All of the tunnel IPs are being advertised on the correct peering devices.
The BGP peer on all of the neighbors will now be Established:
|