From: Steve McNutt (lpd@xxxxxxxxxxxxxxxx)
Date: Tue Oct 24 2000 - 00:54:06 GMT-3
If your doing the CCbootcamp labs you'll have BGP down in no time flat.
belive it!
with the information you have given the only thing I can think of is maybe
you made a change to your bgp config on r2, r3, or r4 at some point and
forgot to reset your bgp sessions.
-steve
-----Original Message-----
From: Derek Buelna [mailto:dameon@aracnet.com]
Sent: Monday, October 23, 2000 11:20 PM
To: 'Steve McNutt'
Subject: RE: bootcamp lab 3: bgp
Thank you. I'm not great at BGP.
Now it is working for some reason. Yes, r3 and r4 have an adjacency. When I
did a sh ip bgp on r3, he had 137.20.10,20,30 and 40 but r4 didn't get the
20 one although he had the others.
I was confused that it wasn't working earlier so I started messing with sync
and next hop self within as 1 primarily.
My understanding is that the routes r3 sends to r4 should use 137.20.103.3
(r3) for the next hop, which is reachable to r4.
I was rather confused that r3 was sending 10 and 30 but not 20.
Thanks for your assistance. I probably have a few stupid questions about
BGP, although I have attended the Mentor workshop and ecp1. I'm going to go
through the examples in Halabi's book.
-Derek
-----Original Message-----
From: Steve McNutt [mailto:lpd@jacksonville.net]
Sent: Monday, October 23, 2000 7:44 PM
To: Derek Buelna; ccielab@groupstudy.com
Subject: RE: bootcamp lab 3: bgp
These are dumb questions and I hope you're not insulted, but have you
verified that R3 and R4 have established adjacencies? have you checked to
see whether R3 has sent any prefixes to R4?
BTW, next-hop reachability and IGP synchronization would not be a relevant
in this situation because R3 and R4 are talking EBGP.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Derek Buelna
Sent: Monday, October 23, 2000 8:55 PM
To: ccielab@groupstudy.com
Subject: bootcamp lab 3: bgp
Hi,
I'm apparently having some next hop reachability problems.
I'm doing lab 3 and can't get r2's 137.20.20.0 route into the bgp table on
r4.
R3 see's it.
Note that my configs are almost identical to the solution although I have
experimented with next-hop self.
R4 has all of the routes in his routing table. He can reach 100.1, 100.2 and
101.1.
I'm confused. R3 has the route in his bgp table but he apparently isn't
advertising the route to r4.
I tried putting next-hop-self on the neighbor relationship between r3 and r4
so that there should be any next hop reach issues but he won't advertise it?
I'll send the configs if someone wants to look..
-Derek
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:29 GMT-3