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. And see here for current known issues.

New Member

Catalyst 6509 - IOS - CPU High and eventually crashed

Hi,

  Recently one of our Cat 6509 started giving the below mentioned error message and eventually crashed.

"No memory availale for asychronous request"

Could some one throw some light and I am happy to give any additional info. on this.

Thanks in advance,

S4U

6 REPLIES

Re: Catalyst 6509 - IOS - CPU High and eventually crashed

Can you provide crash file from both SP and RP if they are available?

If SUP run out of memory, it could cause the crash as well. In general, shortage of memory could be a memory leaking issue.

So, reviewing crash file to see what caused the crash. If it was memory, you can monitor the memory usage to see if you can find a process which kept using more and more memory. You can open a TAC case to let tac engineer to help you .

New Member

Re: Catalyst 6509 - IOS - CPU High and eventually crashed

Hi

Can you provide blow mentioned logs

show tech

regards

krishna kumar

New Member

Re: Catalyst 6509 - IOS - CPU High and eventually crashed

Hi Guys,

Sorry for the delay. Got stuck with other issues.

Cheers

S4U

New Member

Re: Catalyst 6509 - IOS - CPU High and eventually crashed

Hi

The Current running IOS is defered release kindly upgrade the image to latest version

Hope this will resolve the issue

latest Image

s222-ipservicesk9_wan-mz.122-18.SXF17.bin

regards

krishna kumar

New Member

Re: Catalyst 6509 - IOS - CPU High and eventually crashed

Thanks for the Input.

Will try doing the upgrade but I am wondering why the problem started after 2 years in production.

Thanks in advance

S4U

Re: Catalyst 6509 - IOS - CPU High and eventually crashed

SUP crashed after error message "pm failed to send port admin change notification", there were some traceback in the log as well.

There was only 400K memory left and they were fragmented as wel when the issue happened.

-SP-2-MALLOCFAIL: Memory allocation of 65536 bytes failed from 0x40298EFC, alignment 8
Pool: Processor  Free: 431936  Cause: Memory fragmentation   <<<<<<<<
Alternate Pool: None  Free: 0  Cause: No Alternate pool

-Process= "LTL MGR cc", ipl= 0, pid= 226
-Traceback= 40280AB4 402866EC 40298F04 405C8000 405C84D8 405C85F8 405CDEA0 405CE770 405CCA4C

It could be a bug. If you would like to find out what the bug might be, you can open a TAC case for help.

555
Views
0
Helpful
6
Replies