Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

wireless controller restarting

Hi,

Wireless controller 5500 is restarting with error

" ENVMON-0-KEEPALIVE: Wlcng_powerSupply.c:280 System is rebooting in seconds: lost heartbeat from environmental controller "

Did anyone came across this error. Couldn't even find it in cisco site.

Regards

venkat

4 REPLIES
Hall of Fame Super Silver

Re: wireless controller restarting

If your WLC keeps rebooting and isn't stable, then there must be something wrong. Has it ever been stable and just started to become unstable? How often does it reboot? What code are you running and is it in HA?

Anytime something brings down your production network it's really better to open a TAC case so in case it's a bad unit, you can get it replaced right away.

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***
Cisco Employee

wireless controller restarting

Hi Venkat,

This error has most commonly been attributed to an older FUS(1.3) with later version of software code(7.2 or higher) on your controller.  I would highly recommend to upgrade your FUS to the latest 1.7:

http://www.cisco.com/en/US/docs/wireless/controller/release/notes/fus_rn_1_7_0_0.html

Cheers,
Erwin

______________________________________

How helpful was I? Don't forget to rate me when you have the chance!

Cheers, Erwin ______________________________________ How helpful was I? Don't forget to rate me when you have the chance!
Cisco Employee

Re: wireless controller restarting

The caveat to back my statements

CSCtr39523

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

Symptom:
5508 controller may reboot without an output in the crash file.

Conditions:
Console :
fpga: Lost heartbeat from Environment controller, system will reboot in 5
seconds!!!

Syslog server if configured :
%ENVMON-0-KEEPALIVE: wlcng_powerSupply.c:280 System is rebooting in 5 seconds:
lost heartbeat from environmental controller

More information:
A WLC with the fixed firmware will show "FPGA 1.7" (or above.)

The fixed FUS image is now available on CCO (version 1.7.0.0-FUS.)

Cheers,
Erwin

______________________________________

How helpful was I? Don't forget to rate me when you have the chance!

Cheers, Erwin ______________________________________ How helpful was I? Don't forget to rate me when you have the chance!
Community Member

Re: wireless controller restarting

Hi,

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

Bug ID : CSCtr39523

Description

Symptom:

5508 controller may reboot without an output in the crash file.

Conditions:

Console :

fpga: Lost heartbeat from Environment controller, system will reboot in 5

seconds!!!

Syslog server if configured :

%ENVMON-0-KEEPALIVE: wlcng_powerSupply.c:280 System is rebooting in 5 seconds:

lost heartbeat from environmental controller

Workaround:

Downgrade to 6.0.220.0.

More information:

Although the release notes on CCO may state otherwise, this bug is not fixed,

and will not be fixed, in 7.0.230.0, 7.2.130.0, or any runtime image. It is

fixed only by applying a special FUS image, which updates the FPGA,

Environmental Controller, and USB firmware in the controller.

To find out whether your WLC needs to have the FUS image applied, issue the

command "show sysinfo". A WLC with the fixed firmware will show "FPGA 1.7" (or

above.)

The fixed FUS image is now available on CCO (version 1.7.0.0-FUS.)

Description:

Configuration consists of a 5508 controller with no APs/Clients  attached. It was noticed that at 12-24 hour intervals that it would  reboot on it's own due to "fpga: Lost heartbeat from Environment  controller". This was originally seen with 7.0.119.10 and later with  7.0.119.18. The controller was migrated to a different room with no  connections at all except the console and it still failed. Version  6.0.202.0 was loaded onto it and it ran without failure for 5+ days so  there is some interaction between the 7.0.119.x code branch and this  particular hardware.

This failure was origionally found at a customer site and has been seen in the SJ01-AW lab as well.

685
Views
0
Helpful
4
Replies
CreatePlease to create content