Showing results for 
Search instead for 
Did you mean: 

Cisco 5760 WLC unresponsive to show run then to telnet

Omar Hegazy

I have 2 WLC 5760 stacked. Everything was working fine. We faced some issues regarding authentication for an SSID that use radius authentication. We noticed on (show radius statistics) that we have a high timeout number of request. So we changed the default radius-server timeout from 5 to 20 sec. After that with some times we noticed that when we use show run, no output never shows and show tech shows only few lines and becomes unresponsive, other shows all fine and ok. At this instance we could show start-up config. Then we reverted back the radius timeout to 10 sec and while saving the configuration, it never shows it saved and become unresponsive too. Then we couldn't make show start-up as previously and it showed this message 

Cisco-WLC-5760#show startup-config 
Using 0 out of 2097152 bytes, uncompressed size = 7809 bytes
%Error opening nvram:/startup-config (Device or resource busy)

After that we noticed the below log message using terminal monitor on telnet:

%PARSER-6-WMLRETRY: Write memory lock currently held by pid '404', automatic retry. -Process= "Virtual Exec", ipl= 0, pid= 406

Then after a while, we couldn't initiate any telnet sessions to the WLC however it is pinging normally (The remote system refused the connection). The WLC runs IOS version 3.3.4SE


Notice, all wifi services working fine however this issue appeared. Any suggestions? 

3 Replies 3



I had a similar behaviour with Cat4500E. TAC told me to upgrade the IOS because it looked like a bug. Usually, a reboot would help as an immediate remedy. We checked the memory, the processes, the lines and all looked ok. 

My advice is therefore, upgrade the firmware. 



Please rate useful answers. 

I have rebooted and it was ok and after that i upgraded to 3.3.5SE. It looks fine now but we never knew what is the trigger of this bug to happen. Was it increasing the radius timeout to 20 second or not, we didn't know that.


This is a bug has been found across multiple devices.

Console and SSH sessions lockup and become unresponsive after using any "show" command. The switch freezes and logs message below every few seconds.


%PARSER-6-WMLRETRY: Write memory lock currently held by pid '415',

The switch may not recover without a reboot. After the reboot the switch may start working as before with no issues.

The proposed solution by TAC was to do a code upgrade. As I'm am currently in the beginning of a "Lan Refresh" project I will just be replacing these devices first.

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:

Recognize Your Peers