BGP routes being advertised by neighbour peer, relayed to local BGP peer,
Route shows up under received routes (with soft reconf ON) network 10.0.8.0/25 but is not being propagated into routers routing table
get router info bgp neighbors 172.16.0.9 received-routes
VRF 0 BGP table version is 2, local router ID is 172.16.0.10
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight RouteTag Path
*> 0.0.0.0/0 172.16.0.9 0 0 65535 3292 65108 44398 65168 ? <-/->
*> 10.0.0.0/25 172.16.0.10 0 0 0 65535 i <-/->
*> 10.0.1.0/25 172.16.0.10 0 0 65535 65500 ? <-/->
*> 10.0.2.0/25 172.16.0.10 0 0 65535 65500 ? <-/->
*> 10.0.3.0/25 172.16.0.10 0 0 65535 65500 ? <-/->
*> 10.0.8.0/25 172.16.0.9 0 0 65535 3292 65400 65500 ? <-/->
but not in rib:
get router info routing-table all
Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
V - BGP VPNv4
* - candidate default
Routing table for VRF=0
B* 0.0.0.0/0 [20/0] via 172.16.0.9 (recursive is directly connected, VLAN22-MPLS), 00:11:44, [1/0]
C 10.0.0.0/30 is directly connected, vlan9-control
C 10.0.1.0/25 is directly connected, VLAN11-Users
C 10.0.2.0/25 is directly connected, VLAN12-aux
C 10.0.3.0/25 is directly connected, VLAN13-Core
C 10.0.4.0/25 is directly connected, VLAN14-dmz
B 10.1.0.0/16 [20/0] via 172.16.0.9 (recursive is directly connected, VLAN22-MPLS), 00:11:44, [1/0]
B 10.15.0.0/16 [20/0] via 172.16.0.9 (recursive is directly connected, VLAN22-MPLS), 00:11:44, [1/0]
B 10.16.155.132/32 [20/0] via 172.16.0.9 (recursive is directly connected, VLAN22-MPLS), 00:11:44, [1/0]
B 10.37.1.24/29 [20/0] via 172.16.0.9 (recursive is directly connected, VLAN22-MPLS), 00:11:44, [1/0]
(ETC)
All other routes from BGP seems to be accepted, but not this one, i have similar issue with routes advertised in the opposite direction. All routing works via 0.0.0.0/0 but if i drop 0.0.0.0/0 via inbound routemap filtering then i cant route to 10.0.8.0/25.
Any ideas? i already talked to ISP (we have MPLS) and theyre blaming me.
hi,
i've answered your post in the other thread that was originally created.
please see there my remarks and suggestion.
| User | Count |
|---|---|
| 2728 | |
| 1417 | |
| 812 | |
| 739 | |
| 455 |
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 2025 Fortinet, Inc. All Rights Reserved.