BGP - not adding BGP route into routing-table

Forum|Forum|8 years ago
February 20, 2018
6 replies
21682 views

Hi all,

I hope you can assist, I have an issue where the iBGP route that is advertised from the ISP is not being added into the Forti routing-table.

The neighbor relationship is working and I can see the routes - please see below output from my config - I must be missing something - our help is appreciated !!

Config:

config router prefix-list     edit "DFLT-BGP-IN"         config rule             edit 1                 set prefix 0.0.0.0 0.0.0.0                 unset ge                 unset le             next             edit 10                 set action deny                 set prefix any                 unset ge                 unset le             next         end     next     edit "RAIN-OUT"         config rule             edit 10                 set prefix 1.2.3.4 255.255.255.240                 unset ge                 unset le             next             edit 20                 set action deny                 set prefix any                 unset ge                 unset le             next
[ul]
config router route-map[/ul]
    edit "only_default_route"         config rule             edit 10                 set match-ip-address "DFLT-BGP-IN"             next         end     next     edit "BGP-RTMP-1-IN-ISP1"         config rule             edit 10                 set match-ip-address "DFLT-BGP-IN"                 set set-local-preference 200             next         end     next     edit "BGP-RTMP-2-IN-ISP2"         config rule             edit 10                 set match-ip-address "DFLT-BGP-IN"                 set set-local-preference 150             next         end     next     edit "BGP-RTMP-1-OUT-ISP-1"         config rule             edit 10                 set match-ip-address "RAIN-OUT"                 set set-metric 100             next         end     next     edit "BGP-RTMP-2-OUT-ISP-2"         config rule             edit 10                 set match-ip-address "RAIN-OUT"                 set set-metric 150
[ul]
config router static[/ul]
   edit 19         set dst 1.2.3.4 255.255.255.240 (fake public addresses we use)         set blackhole enable     next     edit 17         set dst 2.2.2.2 255.255.255.255 (loopback)         set blackhole enable     next end
[ul]
config router bgp[/ul]
    set as 37101     set router-id 2.2.2.2     config neighbor         edit "10.1.24.1"             set description "ISP-1"             set remote-as 37105             set route-map-in "BGP-RTMP-1-IN-ISP1"             set route-map-out "BGP-RTMP-1-OUT-ISP-1"             set send-community6 disable         next     end     config network         edit 10             set prefix 1.2.3.4 255.255.255.240

Here is the output from the tshoot:

BGP router identifier 2.2.2.2, local AS number 37105 BGP table version is 7 2 BGP AS-PATH entries 0 BGP community entries Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 10.1.24.1 4 37105 1171 1143 7 0 0 15:57:11 1

# get router info bgp network BGP table version is 7, local router ID is 2.2.2.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 Path *>i0.0.0.0/0 10.1.24.1 0 200 0 37662 i *> 1.2.3.4/28 0.0.0.0 100 32768 i Total number of prefixes 2

# get router info bgp neighbors 10.1.24.1 received-routes % Inbound soft reconfiguration not enabled

# get router info routing-table bgp

So the route that the neighbor advertises, is seen by BGP, but not added to the BGP routing table ?

please help

thanks

stanislav_timofeev

New Member

Hi. Could you check the #get router info routing-table database output? Does it have default route received from BGP neighbor?

If yes, it seems that you don't have any issue. As you can see from your debug soft-reconfiguration feature is not enabled for your neighbor. it means that prefixes rejected by the inbound policy are not kept in memory and therefore "get router info bgp neighbors 10.1.24.1 received-routes" is unable to show these rejected prefixes. You accept only default and reject all, so it seems to be a root cause.