ASA 5520 is caught in a rebooting cycle.

w-schultz · ‎09-16-2009

Version 8.2(1) and ASDM 6.2(1)

%ASA-1-199010: Signal 11 caught in process/fiber (Unicorn Proxy Thread)/(unicorn-proxy) at address 0x3ed, corrective action at 0x9ff2340

Yesterday I made a DNS change to move my VPN clients over from our vpn3k machines to these Asa5520 boxes. These boxes have been in firewall production for more than 6 months and light VPN duty since then, today is the first day of heavier VPN load.

At this point we've got about 20 users on the Asa's and I am now seeing the secondary unit caught in a reboot cycle, the above error was the cause of the first reboot. My syslog leads me to belive that the VPN sessions and cookies were being transferred when this happened, and now watching the failover the secondary unit will reload after the 'Bulk Sync' step of the failover process.

The primary unit is okay at this point, if someone has some advice it would be more than welcome.

JORGE RODRIGUEZ · ‎09-16-2009

Being the first time you have noticed this I would collect any crash info and open a TAC case, have them follow up.

show crashdump

http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/admin_trouble.html#wp1042821

Syslog ID 199010

Error Message %ASA-1-199010: Signal 11 caught in process/fiber(rtcli async executor

process)/(rtcli async executor) at address 0xf132e03b, corrective action at

0xca1961a0

http://www.cisco.com/en/US/docs/security/asa/asa80/system/message/logmsgs.html#wp5364753

Jorge Rodriguez