07-06-2013 09:48 PM - edited 03-04-2019 08:23 PM
Hello,
I am unable to see routes in the routing when distributing EIGRP routes into BGP. When doing a show ip bgp.. I do see the route listed, but not from the routing table. Attached is my network topology. How my lab is setup is that from DENTST Router to Cadiz-Rtr it is setup for BGP. From Cadiz-Rtr to CadizPlant-Rtr is setup for EIGRP. Cadiz-Rtr will be the one redistributing eigrp into bgp and bgp into eigrp. Here is the sh ip route output:
Cadiz-Rtr#sh ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, 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, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
+ - replicated route, % - next hop override
Gateway of last resort is not set
1.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C 1.1.1.0/30 is directly connected, Serial2/1.200
L 1.1.1.2/32 is directly connected, Serial2/1.200
10.0.0.0/8 is variably subnetted, 4 subnets, 3 masks
D 10.168.192.0/24
[90/409600] via 192.168.203.2, 09:26:43, Ethernet0/2.300
C 10.168.236.0/24 is directly connected, Ethernet0/0.2
L 10.168.236.254/32 is directly connected, Ethernet0/0.2
B 10.168.250.192/26 [200/0] via 1.1.1.1, 05:32:00
172.16.0.0/24 is subnetted, 1 subnets
D 172.16.192.0 [90/409600] via 192.168.203.2, 09:26:43, Ethernet0/2.300
192.168.203.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.203.0/30 is directly connected, Ethernet0/2.300
L 192.168.203.1/32 is directly connected, Ethernet0/2.300
CadizPlant-Rtr
CadizPlant-Rtr#sh ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, 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, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
+ - replicated route, % - next hop override
Gateway of last resort is not set
1.0.0.0/30 is subnetted, 1 subnets
D EX 1.1.1.0 [170/281856] via 192.168.203.1, 00:47:45, Ethernet0/0.300
10.0.0.0/8 is variably subnetted, 4 subnets, 3 masks
C 10.168.192.0/24 is directly connected, Loopback2
L 10.168.192.254/32 is directly connected, Loopback2
D EX 10.168.236.0/24
[170/281856] via 192.168.203.1, 00:47:45, Ethernet0/0.300
D EX 10.168.250.192/26
[170/281856] via 192.168.203.1, 00:47:45, Ethernet0/0.300
172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks
C 172.16.192.0/24 is directly connected, Loopback200
L 172.16.192.254/32 is directly connected, Loopback200
192.168.203.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.203.0/30 is directly connected, Ethernet0/0.300
L 192.168.203.2/32 is directly connected, Ethernet0/0.300
DENTST-Rtr
DenverTest-Rtr#sh ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, 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, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
+ - replicated route, % - next hop override
Gateway of last resort is not set
1.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C 1.1.1.0/30 is directly connected, Serial2/0.100
L 1.1.1.1/32 is directly connected, Serial2/0.100
10.0.0.0/8 is variably subnetted, 3 subnets, 3 masks
B 10.168.236.0/24 [200/0] via 1.1.1.2, 00:58:28
C 10.168.250.192/26 is directly connected, Ethernet0/0.2
L 10.168.250.254/32 is directly connected, Ethernet0/0.2
DenverTest-Rtr#sh ip bgp
BGP table version is 13, local router ID is 10.168.250.254
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter,
x best-external, a additional-path, c RIB-compressed,
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found
Network Next Hop Metric LocPrf Weight Path
* i 1.1.1.0/30 1.1.1.2 0 100 0 i
*> 0.0.0.0 0 32768 i
* i 10.168.192.0/24 192.168.203.2 409600 100 0 ?
*>i 10.168.236.0/24 1.1.1.2 0 100 0 i
*> 10.168.250.192/26
0.0.0.0 0 32768 i
* i 172.16.192.0/24 192.168.203.2 409600 100 0 ?
Solved! Go to Solution.
07-06-2013 10:02 PM
Hello Quoc Le,
Here is the thing:
DenverTest-Rtr#sh ip bgp
* i 172.16.192.0/24 192.168.203.2 409600 100 0 ?
* i 10.168.192.0/24 192.168.203.2 409600 100 0 ?
The problem is that Denver router does not know how to get to 192.168.203.2 so it will not install the routes on it's routing table (they are not valid... Missing the > on the BGP table)
How to fix it:
make sure you know how to get to 192.168.203.2 (Static route)
add the command bgp neig X.X.X.X next-hop-self on Router Cadiz-Rtr
Regards
Remember to rate all of the helpful posts.
For this community that's as important as a thanks.
07-06-2013 10:02 PM
Hello Quoc Le,
Here is the thing:
DenverTest-Rtr#sh ip bgp
* i 172.16.192.0/24 192.168.203.2 409600 100 0 ?
* i 10.168.192.0/24 192.168.203.2 409600 100 0 ?
The problem is that Denver router does not know how to get to 192.168.203.2 so it will not install the routes on it's routing table (they are not valid... Missing the > on the BGP table)
How to fix it:
make sure you know how to get to 192.168.203.2 (Static route)
add the command bgp neig X.X.X.X next-hop-self on Router Cadiz-Rtr
Regards
Remember to rate all of the helpful posts.
For this community that's as important as a thanks.
07-06-2013 10:23 PM
Thanks! I was able to fix it, I was not advertising 192.168.203.2 network into BGP. Once I added that network, I was able to see 10.168.192.X network in the routing table. Thanks for the help.
07-06-2013 10:49 PM
Hello Quoc,
Exactly, that was the problem as I mentioned: We must have a route to the device that publishes the route
Regards
Remember to rate all of the helpful posts.
For this community that's as important as a thanks.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: