From: shiran guez (shiranp3@gmail.com)
Date: Sun Jan 27 2008 - 13:54:52 ARST
Well if they do not want to remove the EIGRP it do not prevent to do some
filtering on the prefix you receive back from the provider.
the EIGRP is only for the 2 connected routers and 2 connected 6500 and all 4
are directly connected?
can you describe the Internal network layout a little bit?
On Jan 26, 2008 11:44 PM, David <david@gotimmons.com> wrote:
> hi,
>
> BGP question.
>
> I have been fighting with a BGP issue for a while and my customer does
> not
> want to make the changes I recommend. The main change is a prefix filter
> to
> prevent asymmetric routing. In addition to that I have many others. For
> one, I wanted to replace EIGRP between the two BGP routers with an IBGP
> relationship; however, I am getting push back on making any changes to
> their
> environment. Besides the fact that I have always created IBGP relationship
> between routers in the same AS, I was having problems thinking about major
> issues or design constraints created by the use of EIGRP.
>
>
>
> Current Design Facts:
>
>
> Facts)
> 1. We have two BGP routers, AS 64646 (notice 666 in there?) That peers to
> two distinct AT&T routers: Basic Multi-home single provider.
> 2) They run EIGRP between the two (64646) routers on a directly connected
> interface on each router
>
> 3) they run EIGRP between another interface on each router and two
> distinct
> 6500s.
>
> 4) They each form EBGP relationship with provider on an ATM interface.
> Very
> ugly because provider strips private AS and advertise our own network back
> to us with a public AS. This fact sets the scene for the asymmetric
> routing.
> IE, IGP routes disappear and EBGP is the best path to get to local
> resources,
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
-- Shiran Guez MCSE CCNP NCE1 http://cciep3.blogspot.com http://www.linkedin.com/in/cciep3
This archive was generated by hypermail 2.1.4 : Fri Feb 01 2008 - 10:38:01 ARST