[c-nsp] Setting "weight 255" as default for customer BGP with uRPF strict

Pete Templin petelists at templin.org
Sun Nov 21 14:31:03 EST 2004


Brian Feeny wrote:

> Is anyone setting "weight 255" for all customer neighbor sessions?  I 
> was looking at doing this for multi-homed
> customers, so that asymmetrical routing, split prefix announcements, etc 
> don't break uRPF (strict).  Then I just thought,
> well, why make a special case for multi-homed customers, what harm is 
> there on setting weight to all edge neighbor
> sessions.  I mean its only going to effect packets on that local router, 
> and if the packet has gotten so far as to actually
> end up on the router directly connected to the peer, it just seems the 
> best thing to do to hand it to the peer.

Why "255" as the value?  Are you simply looking for a non-zero value? 
Would a value larger than 32768 (default for locally originated routes) 
make any difference in any scenarios (hint: it did for me yesterday)?

I don't think weight will actually override any more specific 
announcements on the router, and therefore might not have the effect I 
think you're after.

pt


More information about the cisco-nsp mailing list