Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Help interpreting crashinfo contents

Hello all,

Does the presence of the crashinfo file below indicate that my PIX has experienced an error it could not recover from (and so it reloaded itself to restore service) ? Or is it possible that the PIX lost power ?

If a PIX loses power does it generate the crashinfo file ?

Piaras Walsh, Ireland

pix_device# show crashinfo

: Saved_Crash

Thread Name: Dispatch Unit (Old pc 0x001fe7c6 ebp 0x014d7b44)

Traceback:

0: 0010b2ce

1: 0010d6a5

2: 0010e281

3: 0066b772

4: 00580721

5: 00580755

6: 00580a9f

7: 00580ba9

8: 005deea9

9: 00651408

10: 006510de

11: 00553022

12: 001fe694

13: 001113d9

4 REPLIES
Bronze

Re: Help interpreting crashinfo contents

I have come across this crash trace back with a scenario involving H.225 traffic going through the PIX. Do you have a lot of H.225 traffic on this PIX? Also, if you do not need inspect h225, would you be able to disable it and see if the problem is seen again?.

But up to my knowledge, I would suggest you to consider upgrading to a interim release with bug-fixes and monitor.

New Member

Re: Help interpreting crashinfo contents

I upgraded from 704 to 712. After the upgrade the PIX crashed every 10mins. Many 7.1 syslogs of these types wer observed:

%PIX-4-313005: No matching connection for ICMP

error message: icmp src Outside:internet_ip dst

Inside:inside_ip (type 3, code 3) on Outside interface.

Original IP payload: udp src 134.226.190.217/0 dst 88.105.72.1/1026.

%PIX-4-419002: Duplicate TCP SYN from

Inside_interface:inside_host/4239 to Outside_interface:internet_host/12775 with different

initial sequence number

The crashinfo traceback is:

Thread Name: Dispatch Unit (Old pc 0x00212b72 ebp 0x018499c4)

Traceback:

0: 0010b3ee

1: 0010d839

2: 0010e421

3: 00b18f75

4: 00b19771

5: 0068c2f0

6: 006934ce

7: 00692aa6

8: 0058c47e

9: 00212a08

10: 001116f9

vector 0x0000000e (page fault)

I had to re-install 704. Has anyone experienced similar problems ? Any help appreciated. Thanks.

New Member

Re: Help interpreting crashinfo contents

I just had the same problem. After upgrade the both PIXes crashed in 1-2 min after rebooting every time. We're tried to fix bug when PIX crash after failing failover interface. It was necessary to downgrade back to 7.0(4). Now I think version 7.0(5) is the best choice in my case. Am I right?

Thanks!

New Member

Re: Help interpreting crashinfo contents

I have been advised by TAC that the problem which causes the traceback shown above is resolved in 7.0.5 and 7.1.2.4. Alternatively I have been told that switching off HTTP inspection if running 7.1.2 will prevent the PIX from crashing. I am upgrading the production PIX this week. I will update this thread with the results.

288
Views
4
Helpful
4
Replies