cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
16624
Views
6
Helpful
96
Replies

WLC 5508 automatically restarting twice in a week

meiyappan
Level 1
Level 1

Hi,

 

I have very strange issue with my wireless Lan controller. It reboots automatically.

Atleast in week, it restarts once or twice.

If i want to check any historical logs , i can not check since after restarting WLC , all logs will be cleared,

I get the logs from the time it restarts , starting with

COLD STARTS :

I am predicting the issue with temperature setting

right now the Internal temperature is +41 C

How do i check , what is the threshold set for temperature.

can anybody  suggest me anything about this ?

  Cisco Controller  Product Version: 8.0.110.0

 

Kindly suggest how to resolve this issue 

96 Replies 96

As what Abraham has pointed out, not only is "7.6.130.37" is not only old but it's a special engineering release.  Unless there is an operation reason why there's the need to use this particular version, I'd recommend upgrading to a version that can support all the different APs in your network. 

Can you CLI into the controller and post the complete output to the command "sh coredump summary".

The command isn't showing anything. I have this code on another controller and there are no problems with reboots. I can make time to upgrade code though. I will just go that route and can update if the problem comes back. Thanks guys.

The command isn't showing anything.

Can you post the complete output to the command "sh sysinfo"?

(LMC-WLC-1) >show sysinfo

Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.6.130.37
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS

System Name...................................... LMC-WLC-1
System Location.................................. Lexington Medical Center
System Contact................................... Sean Coogle
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. Disabled
IP Address....................................... 10.199.215.251
Last Reset....................................... Power on reset
System Up Time................................... 7 days 13 hrs 55 mins 51 secs
System Timezone Location.........................
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180

Configured Country............................... US  - United States
Operating Environment............................ Commercial (0 to 40 C)

--More or (q)uit current module or <ctrl-z> to abort
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +35 C
External Temperature............................. +18 C
Fan Status....................................... OK

State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 11
Number of Active Clients......................... 391

Burned-in MAC Address............................ 00:06:F6:61:D4:00
Power Supply 1................................... Absent
Power Supply 2................................... Present, OK
Maximum number of APs supported.................. 250

We installed a second power supply a few months ago and ran this to a different power outlet that feeds from another source. It did not fix the issue. So, I removed the primary power supply to see if it is causing an issue, so it is currently running off of the second power supply only.

Hi Sean,

In addition to the old version you have, you are also using 11 WLANs which is not a Cisco recommended practice. Actually, they suggest as much 5 (we have had a lot of conversations with the Cisco BU expert and Engineers). See below my output which is similar to your. I replaced some information by X.X.X.X for confidentiality reasons.

(Cisco Controller) >show sysinfo

Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 8.0.132.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS

System Name...................................... DC-CiscoWLC
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. Disabled
IP Address....................................... X.X.X.X
IPv6 Address..................................... ::
Last Reset....................................... Software reset
System Up Time................................... 44 days 5 hrs 29 mins 10 secs
System Timezone Location......................... (GMT -5:00) Eastern Time (US and Canada)
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180

Configured Country............................... CA  - Canada

--More-- or (q)uit
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +41 C
External Temperature............................. +22 C
Fan Status....................................... OK

State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 5
Number of Active Clients......................... 880

Burned-in MAC Address............................ 30:E4:XX:XX:XX:XX
Power Supply 1................................... Present, OK
Power Supply 2................................... Absent
Maximum number of APs supported.................. 500
System Nas-Id.................................... DC-CiscoWLC
WLC MIC Certificate Types........................ SHA1

BTW from the following link looks like there is something else regarding FUS that could be affecting you. Not sure about this as I am not having this "reboot" issue on 8.0 version

http://thewifiguy.net/2014/06/15/whats-all-the-fus-about/

There are recommendations for FUS image components that should be installed on the 5508. FUS version 1.7 was released to fix a critical issue that could cause the 5508 to crash during normal operations:

CSCtr39523 – AW: 5508 Controller sporadically reboots due to lost heartbeat to EnvCnt

FUS 1.7 is required to ensure this issue is resolved on the 5508 Wireless LAN Controller.

FUS version 1.9 has been released and includes a partial fix for a compact flash driver issue that can possibly be seen at the bootloader level of the WLC, and thus requires a FUS upgrade to resolve.

CSCul68057 – CF driver change for 5508/WiSM2

This defect mostly affects AireOS and is fixed in WLC 7.4.121.0 (MR2). However, there are some conditions where the WLC recovery image needs to utilize flash. Therefore in order to ensure all possible conditions for CSCul68057 are resolved, FUS version 1.9 is required.

Both of these defects are classified Severity 1.

FUS 1.9 will be installed on all new Wireless LAN Controllers from manufacturing and cannot be downgraded (nor is recommended). Note that the FUS is NOT running code at WLC operating system level. It does not directly affect runtime of AireOS. The FUS includes only firmware changes.

FUS 1.9 is the recommended FUS version at this time. For WLCs with FUS lower than 1.7, it is recommended to upgrade to 1.9. For WLCs already running 1.7, at this time there is less urgency to upgrade to 1.9, as the scenarios for the use of the WLC recovery image and compact flash are less common. However, it is recommended that these WLCs at be upgraded to FUS 1.9 to ensure full fix of CSCul68057.

As mentioned, there is no requirement for any specific version of the FUS components to be compatible with a 6.0 and higher AireOS version or hardware platform to operate. Always refer to the release notes of specific FUS / AireOS code versions to verify if a specific software version or hardware has a compatibility requirement.

Last Reset....................................... Power on reset

This tells me it's not a crash but a power-related issue.  

Bootloader Version............................... 1.0.1

FUS is also very old.  

Review Cisco Networking for a $25 gift card