[j-nsp] Strange ARP issue on M7i

Jonathan Lassoff jof at thejof.com
Wed Aug 15 03:21:26 EDT 2012


On Wed, Aug 15, 2012 at 12:13 AM, Saku Ytti <saku at ytti.fi> wrote:
> On (2012-08-14 13:09 -0700), Jonathan Lassoff wrote:
>
>> Moral of the story, as I see it: avoid static routing.
>
> This is bit circular. Vendor had software defect in ARP and you arrived to
> conclusion consequently we should not use static routing, but dynamic.
> However our choice of configuration does not affect quality of the code as
> implemented by vendor, so just as well we might have BGP defect doing
> something nasty, and someone might draw conclusion 'avoid bgp routing'.
>
> Moral of the story is, avoid broken software, which is easier said than
> done.

You make a very good point here.

My thing was more along the lines that routing (RIB) / next-hop path
information ought to be learned and/or monitored over protocols that
ride that same path, so that any path failures are detected and routed
around.


More information about the juniper-nsp mailing list