I'm getting that impression too. Maybe I should just run OSPF on the
2524! That should work, right?! Then the core should see the
advertisments from both guys, or am I shooting blanks here?! :)
On Wed, 18 Mar 1998, Danny McPherson wrote:
:
:Since the three iBGP speakers you listed are currently fully-meshed, 2524 will
:tell 7206 and PM3 about head office, but 7206 and PM3 can't tell one another
:.. else there is a potential for loops to occur. Remember the BGP rule that
:one iBGP speaker can't advertise a route to another iBGP speaker that was
:learned from a third iBGP speaker.
:
:Since "head office" is a local route, I'd think it being in your IGP would
:make the most sense. I'd also guess that running BGP on your 2524 is
:overkill, and that sourcing the BGP advertisement(s) from the core, then
:allowing an IGP (or static routers) to do the internal stuff would be a good
:idea..
:
:-danny
:
:
:> The 7206 is the core BGP speaker. I don't want to risk tearing down the
:> rest of the network by making the 7206 a RR client. Maybe I'll just do
:> OSPF between them. I don't understand why that doesn't work. Even though
:> it is internal, I thought it should still work. What if I give the 2524
:> a different AS number?!
:>
:> On Tue, 17 Mar 1998, Eric Kozowski wrote:
:>
:> :At 02:11 PM 3/17/98 , you wrote:
:> :>I got a 2524, a PM3 and a 7206 all talking BGP to one another. The 2524
:> :>is advertising our head office network to our Core Cisco via a T1. The
:> :>2524 is advertising that same network to the PM3 over an ISDN line. I
:> :>have the Core Cisco seeing the advertisment from the 2524 over the T1 and
:> :>I have the PM3 seeing the advertisment from the 2524 over the ISDN. What
:> :>I do NOT have, however is the Core Cisco seeing the advertisment over the
:> :>ethernet from the PM3.
:> :>
:> :>Here is sh bgp peers on the PM3:
:> :>liv3> sh bgp peer
:> :> Remote IP AS Flg DH Up Accept Inject Advertise
:> :>-------------------------------------------------------------------
:> :>207.136.64.69 7271 -- Up all all
:> :>207.136.80.33 7271 -- Up all all all
:> :>
:> :>64.69 is the 2524
:> :>80.33 is the Core network
:> :>
:> :>For you Livingston gurus, I even added a summarization for that network.
:> :>I doubt you need it because if you need to add a summarization for each
:> :>network you learn from BGP in order for it to be advertised back out, that
:> :>is a pretty lame implementation of BGP.
:> :>
:> :>Finally, here is the config for the PM3 neighbor on the Core Cisco:
:> :>
:> :> neighbor 207.136.80.119 remote-as 7271
:> :> neighbor 207.136.80.119 soft-reconfiguration inbound
:> :> neighbor 207.136.80.119 filter-list 1 out
:> :>
:> :>It's not stopping anything from being advertised.
:> :>
:> :>BGP: filter-list 1 is an as-path access-list permit .*
:> :>
:> :>Anyone have any ideas?!
:
:
-- Regards,Jason A. Lixfeld jlixfeld@idirect.ca System Administrator [L5] jlixfeld@torontointernetxchange.net
--------------------------------------------------------------------- TUCOWS Interactive Ltd. o/a | "A Different Kind of Internet Company" Internet Direct Canada Inc. | "FREE BANDWIDTH for Toronto Area IAPs" 5415 Dundas Street West | http://www.torontointernetxchange.net Suite 301, Toronto Ontario | (416) 236-5806 ext 18 (T) M9B-1B5 CANADA | (416) 236-5804 (F) ---------------------------------------------------------------------
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:15 EDT