cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1647
Views
4
Helpful
4
Replies

asa 5540 8.2.3 arbitrarily reload

Igor Mordiuk
Level 1
Level 1

Hi.

I have two ASA 5540 working in Active/Standby mode. After I've upgraded them to 8.2.3 ver. I have the following issue: once a day presently active device arbitary reload.

I have no err in show version and in syslogs:

11:15:50 ASA : %ASA-6-302020: Built inbound ICMP connection for faddr 10.10.0.36/512 gaddr 10.0.0.16/0 laddr 10

11:15:58 ASA : %ASA-1-104001: (Primary) Switching to ACTIVE - HELLO not heard from mate.

The config of failover is the following:

failover

failover lan unit primary

failover lan interface FAILINT Management0/0

failover polltime unit 3 holdtime 9

failover polltime interface 4 holdtime 20

failover key *****

failover replication http

failover link FAILINT Management0/0

failover interface ip FAILINT 192.168.255.1 255.255.255.252 standby 192.168.255.2

Also, CPU utilization during this period is about 5-10%

Any thoughts?

4 Replies 4

Igor Mordiuk
Level 1
Level 1

guys, any ideas?

Hello Igor,

It is completely expected that if an ASA on a failover cluster does not receive a hello packet will become active, you will need to check the cable between them just to avoid a layer 1 issue.  the extrange behavior is with the Active being reloaded.

So the Active gets reloaded once a day, can you provide the show crash of the device because seems to be crashing.

Regards,

Please rate helpful posts.

Julio

Julio Carvajal
Senior Network Security and Core Specialist
CCIE #42930, 2xCCNP, JNCIP-SEC

Hi, Julio.

Thanks for your reply.

Crash-log from primary device:

Cisco Adaptive Security Appliance Software Version 8.2(3)

Compiled on Fri 06-Aug-10 07:51 by builders

Hardware:   ASA5540

Crashinfo collected on 18:44:50.667 EEST Sat Dec 17 2011

Message #148 :

core0: An internal error occurred.  Specifically, a programming assertion was

violated.  Copy the error message exactly as it appears, and get the

Message #149 : output of the show version command and the contents of the configuration

file.  Then call your technical support representative.

Message #150 : assertion "(next_pinuse(p))" failed: file "malloc.c", line 2815

: End_Crash

Crash-log from secondary device:

Cisco Adaptive Security Appliance Software Version 8.2(3)

Compiled on Fri 06-Aug-10 07:51 by builders

Hardware:   ASA5540

Crashinfo collected on 20:15:50.976 EEST Mon Dec 19 2011

Message #145 :

core0: An internal error occurred.  Specifically, a programming assertion was

violated.  Copy the error message exactly as it appears, and get the

Message #146 : output of the show version command and the contents of the configuration

file.  Then call your technical support representative.

Message #147 : assertion "0" failed: file "malloc.c", line 3056

: End_Crash

Hello Igor,

That is not what we are looking for.

What I want you to do is to go to the device that has been reloading and get the following output:

-Show crash

Please rate helpful posts.

Julio

Julio Carvajal
Senior Network Security and Core Specialist
CCIE #42930, 2xCCNP, JNCIP-SEC
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: