[c-nsp] Late night BGP puzzler

[Peter Kranz]

Unfortunately, MED comes too late in the process for this example (equal as
path length routes from 2 different AS#, one IGP and one EGP).. The only
option is local_pref (or weight, but that could lead to trouble)

Step 5: Prefer the path with the lowest origin type.
Note: IGP is lower than Exterior Gateway Protocol (EGP), and EGP is lower
than INCOMPLETE.

Step 6: Prefer the path with the lowest multi-exit discriminator (MED).

Peter Kranz
Founder/CEO - Unwired Ltd
www.UnwiredLtd.com
Desk: 510-868-1614 x100
Mobile: 510-207-0000
pkranz at unwiredltd.com


-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Gert Doering
Sent: Wednesday, August 01, 2007 11:26 PM
To: Gunjan GANDHI (BR/EPA)
Cc: Collins, Richard (EXT); cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Late night BGP puzzler

Hi,

On Thu, Aug 02, 2007 at 12:00:50PM +1000, Gunjan GANDHI (BR/EPA) wrote:
> MED should not be used under this scenario as both the upstream routes
> are from different providers. Unless both providers have agreed upon a
> MED benchmark value, it is not wise to use MED for route selection. It
> is like comparing oranges with apples.

I strongly disagree here - this is purely a matter of local policy.

MED is a much better tool for careful traffic adjustment than local-pref.

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
_______________________________________________
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/