Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Cisco Wireless Controller Unreachable after power outage (4402)

Posted on 2012-03-09
3
Medium Priority
?
1,893 Views
Last Modified: 2012-06-21
I am unable to reach one of my controllers following a power outage via the WCS software.  I can reach the web UI of the controller from one server in the building.  I have tried reloading the firmware (Code AIR-WLC4400-K9-6-0-188-0.aes) via TFTP and it worked.  After the reboot I received the following errors in the log:

*Mar 09 21:52:54.542: %WEB-3-INVALID_TFTP_DNLDCODE: file_download.c:893 TFTP download failed with unknown failure code.
*Mar 09 21:52:52.479: %RRM-3-RRM_LOGMSG: rrmChanUtils.c:292 RRM LOG: Airewave Director: Could not find valid channel lists for 802.11bg
*Mar 09 21:52:51.610: %USMDB-3-MSGTAG030: usmdb_apf.c:262 For information regarding Emergency image Version,Please refer Controller documents.
*Mar 09 21:52:47.643: %ETHOIP-3-PKT_RECV_ERROR: ethoip.c:337 ethoipSocketTask: ethoipRecvPkt returned error
*Mar 09 21:52:47.643: %ETHOIP-3-PING_RESPONSE_TX_FAILED: ethoip_ping.c:312 Failed to tx a ping response to 10.0.0.12, rc=5
*Mar 09 21:52:37.643: %ETHOIP-3-PKT_RECV_ERROR: ethoip.c:337 ethoipSocketTask: ethoipRecvPkt returned error
*Mar 09 21:52:37.642: %ETHOIP-3-PING_RESPONSE_TX_FAILED: ethoip_ping.c:312 Failed to tx a ping response to 10.0.0.12, rc=5
*Mar 09 21:52:35.008: %SIM-3-PORT_UP: sim.c:9547 Physical port 1 is up!.
*Mar 09 21:52:29.328: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'cliWebInitParms.cfg'
*Mar 09 21:52:29.271: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'rrcEngineInitParms.cfg'
*Mar 09 21:52:29.271: %CNFGR-3-INV_COMP_ID: cnfgr.c:2105 Invalid Component Id : Unrecognized (82) in cfgConfiguratorInit.
*Mar 09 21:52:29.204: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'rfidInitParms.cfg'
*Mar 09 21:52:29.194: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'dhcpParms.cfg'
*Mar 09 21:52:29.166: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'bcastInitParms.cfg'
*Mar 09 21:52:28.963: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'rrmInitParms.cfg'
*Mar 09 21:52:28.787: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'apfInitParms.cfg'
*Mar 09 21:52:28.676: %MM-3-MEMBER_ADD_FAILED: mm_dir.c:903 Could not add Mobility Member. Reason: IP already assigned, Member-Count:1,MAC: 00:00:00:00:00:00, IP: 0.0.0.0
*Mar 09 21:52:28.474: %DTL-3-DSNET_CONF_FAILED: dtl_ds.c:424 Unable to set symmetric mobility tunneling to disabled on Distribution Service interface.
*Mar 09 21:52:28.473: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'mmInitParms.cfg'
*Mar 09 21:52:25.313: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'aaaapiInitParms.cfg'
*Mar 09 21:52:25.309: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'pemInitParms.cfg'
*Mar 09 21:52:25.175: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'dot1xInitParms.cfg'
*Mar 09 21:52:25.153: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'capwapInitParms.cfg'
*Mar 09 21:52:24.982: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'spamInitParms.cfg'
*Mar 09 21:52:24.980: %SSHPM-3-FREAD_FAILED: sshpmlscscep.c:1395 Error reading file /mnt/application/lscca_pem.crt
*Mar 09 21:52:12.800: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:422 Failed to read configuration file 'sshpmInitParms.cfg'
*Mar 09 21:52:12.787: %CNFGR-3-INV_COMP_ID: cnfgr.c:2105 Invalid Component Id : Unrecognized (36) in cfgConfiguratorInit.

I am still only able to reach it via one server.

Anyone seen this before?
0
Comment
Question by:bryan-emerson
  • 2
3 Comments
 
LVL 47

Expert Comment

by:Craig Beck
ID: 37704790
Restore a backup of the configuration to rule out any changes after the code upgrade.  I understand you installed the same version, but you should restore the configuration afterwards.
0
 

Accepted Solution

by:
bryan-emerson earned 0 total points
ID: 37758979
Figured it out, it was upstream in the Router config!
0
 

Author Closing Comment

by:bryan-emerson
ID: 37775754
This solved the issue.
0

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

You deserve ‘straight talk’ from your cloud provider about your risk, your costs, security, uptime and the processes that are in place to protect your mission-critical applications.
As managed cloud service providers, we often get asked to intervene when cloud deployments go awry. Attracted by apparent ease-of-use, flexibility and low computing costs, companies quickly adopt leading public cloud platforms such as Amazon Web Ser…
Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually. After setting up a router, find the network security…
Both in life and business – not all partnerships are created equal. Spend 30 short minutes with us to learn:   • Key questions to ask when considering a partnership to accelerate your business into the cloud • Pitfalls and mistakes other partners…

877 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question