[j-nsp] Redistribute Connected

[Mark Tinka]

On Tuesday 25 November 2008 15:55:12 Frans Legdeur wrote:

> You will loose valuable information, in case you use
> route reflectors and software like ARBOR, that collects
> traffic and routing information to understand where all
> your traffic is destined to. In your case you would only
> see the router as endpoint, not the real end-point that
> lays behind your router.

I'd like a flow collector that gives me the AS_PATH along 
with my flow data (which I believe Arbor does).

> I agree, all methods work, but without arguments I can't
> agree that it's a best practice ...

My fundamental belief is that you should build the network 
on sound principles, first, before getting to the advanced 
stuff.

I recall a conversation with a friend that was building a 
single-area IGP because routing code today doesn't support 
inter-area MPLS-TE (CSPF). In such a case, good, basic 
network design outweighs the limitations of a technology 
that you might not need (and would probably even cost you 
more money to support).

Setting the NEXT_HOP self attribute, I believe, is good 
practice, if your intentions aren't whether Arbor or some 
such software will work correctly or not.

Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20081125/c0d5bfc6/attachment.bin>