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

Router Error Message

Our Internet Firewall 2600 series router is producing the following error message:

"SYS-2-CHUNKBADMAGIC Bad magic number in chunk header, chunk 0 data 838AC610 chunkmagic 0 chunk_freemagic 82ED1F00"

I have looked up the error message at the CISCO site, see below:

Error Message

%SYS-2-CHUNKBADFREEMAGIC : Bad free magic number in chunk header, chunk [hex] data [hex] chunk_freemagic [hex]

Explanation An inconsistency was detected while the chunk memory pool was being managed. It is likely that this is a software error, but there could be a hardware memory problem.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac . With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl . If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl , or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Save any crashinfo or crashdump files. If the router has crashed and was not configured to automatically reload, the router will need to be reloaded manually.

I don't have sufficient rights to access the toolkit any advise on a way ahead would be greatly received. Should I be worried it seems to be working OK?

Cheers,

Richard Bailey

6 REPLIES

Re: Router Error Message

Richard,

What's the IOS version?

-Sundar

New Member

Re: Router Error Message

Hi,

Most probably, you're hitting the following bug:

CSCeg78036

Externally found severe defect: Resolved (R)

VFR/NAT: tracebacks in ip_vfr_delete_frag_state and ip_vfr_process

Release-note:

Symptoms: The following tracebacks may be generated when VFR handles

fragmented packets:

%SYS-2-CHUNKBADMAGIC: Bad magic number in chunk header, chunk 0 data 6472EE80

chunkmagic 0 chunk_freemagic 6484FA7C

Conditions: This symptom is observed on a Cisco 7200 series that runs Cisco

IOS interim Release 12.3(12.11)T1 and that is configured with a virtual

reassembly. The symptom may also occur on a Cisco 2651XM.

Workaround: Disable the virtual reassembly by entering the no ip

virtual-reassembly command.

This bug has been fixed in 12.3(14)T03. Therefore an upgrade to a more

recent release will fix that issue.

What is the IOS version of your router? Can you provide the "show tech"?

Regards,

Juan

New Member

Re: Router Error Message

Thanks for the reply IOS is c2600-advsecurityk9-mz.124-1a, would prefer not to post "sh tech".

Cheers,

Richard

Hall of Fame Super Silver

Re: Router Error Message

Richard

I had a set of routers (different platform and different IOS version) that reported the same error message. I opened a case with TAC about it. They did not provide a convincing explanation of the cause but they did recommend a code upgrade. I was frustrated to not know more about what caused the error, but I did upgrade the code. The problem went away.

Especially given that 12.4(1a) is pretty old code at this point, my suggestion to you is to upgrade the code to something pretty recent.

HTH

Rick

New Member

Re: Router Error Message

Cheers I'll give it ago.

Thanks

Richard

New Member

Re: Router Error Message

Hi Richard,

The current code has the bug I mentioned fixed but it?s actually a very old code, so I strongly agree with Rick that an IOS upgrade will be the best move in this case. You can try 12.4(7)x, 12.4(8)x or 12.4(10)x.

Regards,

Juan

397
Views
5
Helpful
6
Replies