From: Brian Dennis (brian@labforge.com)
Date: Fri May 09 2003 - 03:21:38 GMT-3
Just because the next hop is pingable it does not mean it's a valid next
hop. Next hop addresses that are reachable only via a default route
aren't valid. Also next hop addresses that are reachable only via
another BGP route are also not valid.
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
Director of CCIE Training and Development - IPexpert, Inc.
Mailto: brian@ipexpert.net
Toll Free: 866.225.8064
Outside U.S. & Canada: 312.321.6924
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Pierrre-Alex GUANEL
Sent: Thursday, May 08, 2003 10:24 PM
To: ccielab@groupstudy.com
Cc: Cisco
Subject: BGP route not synchronized -- WEIRED!
I have a problem with a router not advertising internal bgp routes to
its
peers (exhibit1)
The route (188.1.2.0/24) is synchronized (exhibit 2) and the next hop is
reacheable (exhibit 3) but the router still does not accept the route as
synchronized (exhibit 4)
The router is running IOS c2500-js-l.121-5.T.bin. I am puzzled. Any
ideas ?
R1#show ip bgp
BGP table version is 1, local router ID is 1.1.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal
Origin codes: i - IGP, e - EGP, ? - incomplete
-------------------- exhibit 1
Network Next Hop Metric LocPrf Weight Path
* i188.1.2.0/24 10.0.70.1 0 100 0 1 i
-------------------- exhibit 2
R1#show ip route ospf | i 188.1.2.0
O E1 188.1.2.0 [110/106] via 10.0.0.7, 00:21:23, TokenRing0
-------------------- exhibit 3
R1#ping 10.0.70.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.70.1, timeout is 2 seconds:
!!!!!
--------------------------- exhibit 4
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/8/8 ms
R1#show ip bgp 188.1.2.0
BGP routing table entry for 188.1.2.0/24, version 0
Paths: (1 available, no best path)
Not advertised to any peer
1
10.0.70.1 (metric 7) from 10.0.70.1 (10.0.70.1)
Origin IGP, metric 0, localpref 100, valid, internal, not
synchronized
Thanks,
Pierre-Alex
This archive was generated by hypermail 2.1.4 : Mon Jun 02 2003 - 15:13:39 GMT-3