From: ccie2be (ccie2be@nyc.rr.com)
Date: Fri Jan 14 2005 - 16:11:35 GMT-3
Hi guys,
I figured it out.
Stupidly, I forgot to clear the bgp session between R4 and R5.
After cleraing the sesson, all was well in bgp land. See below:
Rack1R4#sh ip bgp nei 150.1.5.5
BGP neighbor is 150.1.5.5, remote AS 200, internal link
BGP version 4, remote router ID 150.1.5.5
BGP state = Established, up for 00:01:03
Last read 00:01:03, hold time is 0, keepalive interval is 0 seconds <--
Yea, finally I got bgp to shut-up
Configured hold time is 0, keepalive interval is 0 seconds
Neighbor capabilities:
Route refresh: advertised and received(old & new)
Address family IPv4 Unicast: advertised and received
#################################################
In case any of you are wondering why I was trying so hard to get BGP
to shut up, it was because I'm running bgp over an isdn link and wanted
to prevent bgp from bringing up the link.
I also discovered that I can control which side of bgp peering initiate the
peering.
(Yeah, I know this isn't real world, but then, again, neither is the lab.)
Anyway, I used an inbound acl on one side of the isdn link which filters on
port 179.
Now, only this side with the acl can initiate the bgp peering.
OK, I hope my pain and frustration helps those of you beefing up on BGP.
Thanks, Tim
This archive was generated by hypermail 2.1.4 : Wed Feb 02 2005 - 22:10:22 GMT-3