From: john matijevic (matijevi@bellsouth.net)
Date: Wed Sep 15 2004 - 00:56:34 GMT-3
Hello Joseph,
The answer key has on R4, for network 2.2.2.0/29 next hop 10.1.1.1, that
is what I also came up with when I did this lab also. You need to make
sure that the best route for 2.2.2.0/29 is next hop 10.1.1.1 *>.
Sincerely,
John Matijevic, CCIE #13254, MCSE, CNE, CCEA
CEO
IgorTek Inc.
151 Crandon Blvd. #402
Key Biscayne, FL 33149
Hablo Espanol
305-321-6232
http://home.bellsouth.net/p/PWP-CCIE
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Joseph Rothstein
Sent: Tuesday, September 14, 2004 11:19 PM
To: ccielab@groupstudy.com
Subject: BGP reachability issues Lab 2 Cisco Press
Greetings to all.
Has anyone else had reachability issues with the BGP part of Lab 2 int
eh new Cisco Press book? I ahve a strange situation on R4 which prevents
pinging the loopback 2.2.2.2 on R2:
R4#sipb
BGP table version is 5, local router ID is 10.4.4.4
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 2.2.2.0/29 10.6.6.6 0 61555 62555
i
* 10.1.1.1 0 61555 62555
i
*> 4.4.4.0/24 0.0.0.0 0 32768 i
*> 5.5.5.0/27 10.6.6.6 0 61555 64555
i
* 10.1.1.1 0 61555 64555
i
*> 8.8.8.0/28 10.6.6.6 0 61555 63555
i
* 10.1.1.1 0 61555 63555
i
This basically causes packets to bounce back and forth between R6 and R4
since R6's BGP table uses 10.90.90.1 as it's next hop for 2.2.2.2, which
goes through R4. So once the packet gets to R4 on its way to 10.90.90.1,
it just goes right back to R6.
This seems like a pretty big problem, although the text does not state
that IP addresses under BGP have to be reachable.
Did anyone else run into this little problem?
Joe
There is more to life than increasing its speed. - Mahatma Ghandi
This archive was generated by hypermail 2.1.4 : Fri Oct 01 2004 - 15:00:42 GMT-3