On 06/02/2014 21:21, Charles Spurgeon wrote:
On Thu, Feb 06, 2014 at 11:32:25AM +0000, Phil Mayers wrote:
On 05/02/14 20:23, Charles Spurgeon wrote:
FYI. We recently encountered an inline packet crash bug that took out
Can you clarify what "inline packet crash bug" means? It's not a term
I'm familiar with.
You're right, the usage is unclear. As far as we can tell, packet
traffic through the router triggered the crash. This does not appear
to have been caused by punt packets to the CPU. However, we have no
details. All that we know for sure is that both routers crashed at the
same time.
It couldn't have been a routing update e.g. BGP advertisment that both
routers got and contained weird/large/etc. values? Wouldn't be the first
time that happened.
Assuming you got a crashinfo, and assuming the stack wasn't totally
trashed, the traceback might be informative, to TAC if nothing else.
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
