- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dual Homed ADVPN with BGP
I need some help figuring out why my ADVPN lab isn't working as it should. I currently have 2 hubs and 2 branches in the topology. I am able to communicate branch to branch via the primary ADVPN tunnel just fine, but when I fail one of the WAN links at either of the branches, the BGP next-hop does not populate correctly causing traffic to halt.
BRANCH1 # get router info bgp network BGP table version is 37, local router ID is 10.255.255.2 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.10.10.0/30 10.255.255.1 0 100 0 0 i * i 10.255.255.1 0 90 0 0 i *>i11.11.11.0/30 10.255.255.4 0 100 0 0 i * i 10.255.254.1 0 90 0 0 i *> 12.12.12.0/30 0.0.0.0 100 32768 0 i *>i13.13.13.0/30 10.255.255.3 0 100 0 0 i * i 10.255.255.3 0 90 0 0 i Total number of prefixes 4
BRANCH2 # get router info bgp network BGP table version is 25, local router ID is 10.255.255.3 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.10.10.0/30 10.255.255.1 0 100 0 0 i * i 10.255.255.1 0 90 0 0 i *>i11.11.11.0/30 10.255.255.4 0 100 0 0 i * i 10.255.254.1 0 90 0 0 i *>i12.12.12.0/30 10.255.255.2 0 100 0 0 i * i 10.255.254.2 0 90 0 0 i *> 13.13.13.0/30 0.0.0.0 100 32768 0 i Total number of prefixes 4
I have Hub2 BGP local-pref set to 90 to serve as a backup hub, but as you can see, 10.255.254.x only shows up for a few select networks and not all of them. Both hubs have route-reflector-client enabled in their BGP settings.
For reference, I have followed the ADVPN setup located here: https://kb.fortinet.com/kb/viewAttachment.do?attachID=FortiOS_ADVPN_version_2018-11-22.pdf&documentI...
Attached is a screenshot of my GNS3 topology.
Any help is appreciated! Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, did you ever get this working as expected?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Eugene.milon wrote:I have not. I am going to wait until Fortinet releases its next 6.x firmware that should fix this specific issue.Hi, did you ever get this working as expected?
