[c-nsp] 2 full BGP feeds on 3750?...expanded

[Shakeel Ahmad]

I'll agree to this, UNTILL your upstream is a transite provider for your
prefix, you don't even need to run BGP.

If your provider is a transit provider for your publc prefixes, just recieve
a default router from their BGP process and do whatever you wan't (MED's,
weights or announce) with your own prefixes....


someone correct me if i am wrong.

shakeel


On 9/6/06, Mathias at telecityredbus.com <Mathias at telecityredbus.com> wrote:
>
> Hi Gert,
>
> You are right for end to end problems although static can still be used
> in which case a monitoring package should be used to help close the gap.
>
> Mathias,
>
>
> -----Original Message-----
> From: Gert Doering [mailto:gert at greenie.muc.de]
> Sent: 06 September 2006 12:45
> To: Mathias Kenfack-Tabakem (LON)
> Cc: Mark at u.tv; peter.salanki at bahnhof.net; cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] 2 full BGP feeds on 3750?...expanded
>
> Hi,
>
> On Wed, Sep 06, 2006 at 12:10:53PM +0100, Mathias at telecityredbus.com
> wrote:
> > I'll go a step further with that reasoning. Do we need BGP at all in
> > that environment? Unless I am missing something I'll argue no. Static
> > route and floating static route will do the trick here.
>
> I'd go for BGP "default route only" to make sure you notice if there are
> end-to-end problems, but the ethernet link is still "up" (otherwise
> you'll have black holes).
>
> gert
> --
> USENET is *not* the non-clickable part of WWW!
>
> //www.muc.de/~gert/
> Gert Doering - Munich, Germany
> gert at greenie.muc.de
> fax: +49-89-35655025
> gert at net.informatik.tu-muenchen.de
> This e-mail is intended only for the use of the addressees named above and
> may be confidential.
> If you are not an addressee you must not use any information contained in
> nor copy it nor inform any person other than the addressees of its existence
> or contents.
>
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>