[j-nsp] Cisco to Juniper Question
Scott Morris
swm at emanon.com
Thu Jan 17 10:07:43 EST 2008
1. Laziness
2. Not seeing any problems, therefore thinking all is good
3. As you said the "it was like that when I got here and nobody asked me to
change it"
4. I saw a configuration on Google once that did this, and it seemed like a
good idea
Or some combination of the above. :)
Scott
-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Eric Van Tol
Sent: Thursday, January 17, 2008 9:06 AM
To: sthaug at nethelp.no; paul.carter at ehosting.com
Cc: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] Cisco to Juniper Question
> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of
> sthaug at nethelp.no
> Sent: Thursday, January 17, 2008 7:52 AM
> To: paul.carter at ehosting.com
> Cc: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] Cisco to Juniper Question
>
> (why do people do this, again and again? ...)
>
> Steinar Haug, Nethelp consulting, sthaug at nethelp.no
I ask this of myself all the time. For a point-to-point /30, I suppose it's
not really a problem. I imagine that the reason a lot of people do this is
because "it was like that when I got here". Either that, or some like the
benefit of a lower admin distance, as I believe that a static route to
next-hop has a distance of 1 in Cisco routers, whereas a static route to an
interface is 0. That said, I think it's the former.
:-)
-evt
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the juniper-nsp
mailing list