nanog mailing list archives
RE: Odd router brokenness
From: Leigh Porter <leigh.porter () ukbroadband com>
Date: Wed, 23 Nov 2011 17:00:39 +0000
-----Original Message----- From: Mark Radabaugh [mailto:mark () amplex net] Sent: 23 November 2011 16:53 To: NANOG list Subject: Re: Odd router brokenness On 11/23/11 11:33 AM, Saku Ytti wrote: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, causingpuntwhich is rate-limited by different policer than TTL exceeded policer.I was told the router was reloaded to resolve a CEF issue. Not sure what was wrong with 'clear cef linecard'.
Now *that* brings back memories! -- Leigh ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________
Current thread:
- Odd router brokenness Mark Radabaugh (Nov 23)
- Re: Odd router brokenness Saku Ytti (Nov 23)
- Re: Odd router brokenness Keegan Holley (Nov 23)
- Re: Odd router brokenness Mark Radabaugh (Nov 23)
- Re: Odd router brokenness Mark Radabaugh (Nov 23)
- RE: Odd router brokenness Leigh Porter (Nov 23)
- Re: Odd router brokenness Saku Ytti (Nov 23)
- Re: Odd router brokenness Keegan Holley (Nov 23)
- Re: Odd router brokenness Saku Ytti (Nov 23)