[c-nsp] Loopback Advertise in OSPF

[Mark Tinka]

On Wednesday 27 February 2008, Phil Mayers wrote:

> I think that's probably a bit dramatic (no offence
> intended). We've used "redis connected / static" for
> "customer" routes (edge networks) for quite a while now
> here with no problesm; initially in a VRF-lite model:

If you read further on in my post, you will see I said 
redistribution is bad with the exception of MPLS/VPN's 
and/or VRF's.

> * "redistribution is bad" - which is certainly true 
> *between* the  
> dynamic protocols, but no-one has ever convinced me that's 
> true for 
> connected or static routes

Well, I wouldn't be keen on having flapping customer links 
keeping my OSPF process busy. Keeping OSPF light by using 
it for Loopback and core interfaces only is how I'd deploy 
it.

Using iBGP to originate customer routes means you don't need 
to redistribute any connected prefixes into routing 
protocols.

Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 832 bytes
Desc: This is a digitally signed message part.
Url : https://puck.nether.net/pipermail/cisco-nsp/attachments/20080228/a9b1b1f0/attachment.bin