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?!
that's a feature of ibgp. set the 2524 up as a route-reflector. make the
pm3 and the 7206 clients.
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:15 EDT