cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
606
Views
0
Helpful
3
Replies

CHUNKBADMAGIC???

riju
Level 1
Level 1

My IOS is 12.3(14)T1. I did a ping with large size packets(20000-35000). Ping result is good, but got some messages:

000413: Apr 25 14:29:50.951 XXX: %SYS-2-CHUNKBADMAGIC: Bad magic

number in chu

nk header, chunk 0 data 443E49B0 chunkmagic 0 chunk_freemagic

43CCD478

-Process= "<interrupt level>", ipl= 4

-Traceback= 0x40AA598C 0x400BA458 0x402F8D44 0x40042968 0x40042C4C

0x4001031C 0x

400116BC

000414: Apr 25 14:30:01.047 XXX: %SYS-2-CHUNKBADMAGIC: Bad magic

number in chu

nk header, chunk 0 data 443E4898 chunkmagic 0 chunk_freemagic

43CD1A28

-Process= "<interrupt level>", ipl= 4

-Traceback= 0x40AA598C 0x400BA458 0x402F8D44 0x40042968 0x40042C4C

0x4001031C 0x

400116BC

000415: Apr 25 14:30:14.247 XXX: %SYS-2-CHUNKBADMAGIC: Bad magic

number in chu

nk header, chunk 0 data 443E4898 chunkmagic 43CCF3D4

chunk_freemagic 43CCECDC

-Process= "<interrupt level>", ipl= 4, pid= 74

-Traceback= 0x40AA598C 0x400BA458 0x402F8D44 0x40042968 0x40042C4C

0x4001031C 0x

400116BC

000416: Apr 25 14:30:27.807 XXX: %SYS-2-CHUNKBADMAGIC: Bad magic

number in chu

nk header, chunk 0 data 443E4898 chunkmagic 43CD2818

chunk_freemagic 43CCF058

-Process= "<interrupt level>", ipl= 4, pid= 74

-Traceback= 0x40AA598C 0x400BA458 0x402F8D44 0x40042968 0x40042C4C

0x4001031C 0x

400116BC

What does this means?

3 Replies 3

Richard Burts
Hall of Fame
Hall of Fame

I had an issue which included error messages about CHUNKBADMAGIC on a router running the T train of 12.3 code. I opened a case with TAC. They agreed that it was some kind of bug in IOS. We never were quite sure what triggered it. They advised that I change IOS release levels. I suspect that it is a similar issue in your case.

HTH

Rick

HTH

Rick

Can you please give your case number, so I can refer to that also. My IOS is 12.3(14)T1. Which was the IOS you had repoerted to TAC?

My TAC case was 600459735. The TAC engineer gave me two bug IDs that he thought were related: CSCee65576 and CSCee57895.

For us the problem stopped when we upgraded to 12.3(8)T4

HTH

Rick

HTH

Rick