[146847] in North American Network Operators' Group
Re: Odd router brokenness
daemon@ATHENA.MIT.EDU (Keegan Holley)
Wed Nov 23 11:43:29 2011
In-Reply-To: <20111123163323.GA19075@pob.ytti.fi>
From: Keegan Holley <keegan.holley@sungard.com>
Date: Wed, 23 Nov 2011 11:41:34 -0500
To: Saku Ytti <saku@ytti.fi>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
2011/11/23 Saku Ytti <saku@ytti.fi>
> On (2011-11-23 09:41 -0500), Mark Radabaugh wrote:
>
> > The question is: How does a router break in this manner? It
> > appears to unintentionally be doing something different with traffic
> > based on the source address, not the destination address. I
> > realize this can be done intentionally - but that is not the case
> > here (unless somebody isn't telling me something).
>
> I don't think we can determine that it has anything to do with source
> address based on data shown.
> 38.104.148.5 could very well be 6500 and somehow broken adjacency to
> 74.125.226.6, perhaps hardware adjacency having MTU of 0B, causing punt
> which is rate-limited by different policer than TTL exceeded policer.
>
>
> Agree. I've seen similar effects with a different ISP who had one side of
an ether-channel go south without the port showing down. Stuff hashed over
the good like was fine, stuff hashed over the bad like wasn't. Led to some
painful support calls from customers. I agree this list is a haven of
speculation and OT comments. In order to avoid making a bad problem worse
you should probably contact cogent.
