[181907] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: Possible Sudden Uptick in ASA DOS?

daemon@ATHENA.MIT.EDU (Klimakhin, Kirill)
Thu Jul 9 03:24:00 2015

X-Original-To: nanog@nanog.org
From: "Klimakhin, Kirill" <Kirill.Klimakhin@COREBTS.com>
To: Mark Mayfield <Mark.Mayfield@cityofroseville.com>, "nanog@nanog.org"
 <nanog@nanog.org>
Date: Wed, 8 Jul 2015 17:45:55 +0000
In-Reply-To: <ffc0dc8068ba47c2bdc35184b8301df5@MIEXMBVM1.metro-inet.us>
Errors-To: nanog-bounces@nanog.org

This is pretty scary when you take into account that the NYSE is still down=
.



Kirill Klimakhin
Principal Consultant
120 Seventh Street
Suite 202
Garden City, NY 11530
(C) 631-707-3303
(F) 631-982-0174
Kirill.Klimakhin@corebts.com
www.corebts.com

-----Original Message-----
From: NANOG [mailto:nanog-bounces+kirill.klimakhin=3Dcorebts.com@nanog.org]=
 On Behalf Of Mark Mayfield
Sent: Wednesday, July 08, 2015 12:58 PM
To: nanog@nanog.org
Subject: Possible Sudden Uptick in ASA DOS?

Come in this morning to find one failover pair of ASA's had the primary cra=
sh and failover, then a couple hours later, the secondary crash and failove=
r, back to the primary.

Another pair running the same code had the primary crash and fail in the sa=
me time window.

So, three crashes in 4 hours in our environment.

Open a TAC case on one of these for post-mortem analysis, and they interpre=
ted the crash dump to point at a DOS bug first published in Oct.

The very interesting thing; on the phone the TAC engineer said this was "th=
e 10th one of these I've dealt with this morning".

Here's the bug they reference:
https://tools.cisco.com/bugsearch/bug/CSCul36176/?reffering_site=3Ddumpcr

Anyone else have observations to add on this?

Mark Mayfield
City of Roseville - AS 54371
Network Systems Engineer

2660 Civic Center Drive
Roseville, MN 55113
651-792-7098      Office


________________________________
Important Notice: This email message and any files transmitted with it are =
confidential and intended solely for the use of the individual or entity to=
 whom they are addressed. If you are not the named addressee, you should no=
t disseminate, distribute or copy this e-mail. Please notify the sender imm=
ediately by e-mail if you have received this e-mail by mistake and delete t=
his e-mail from your system. Please note that any views or opinions present=
ed in this email are solely those of the author and do not necessarily repr=
esent those of Core BTS. Core BTS specifically disclaims liability for any =
damage caused by any virus transmitted by this email.


home help back first fref pref prev next nref lref last post