Solved

Cisco Wireless Controller Unreachable after power outage (4402)

Posted on 2012-03-09
3
1,750 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 45

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

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

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

This subject  of securing wireless devices conjures up visions of your PC or mobile phone connecting to the Internet through some hotspot at Starbucks. But it is so much more than that. Let’s look at the facts: devices#sthash.eoFY7dic.
Concerto Cloud Services, a provider of fully managed private, public and hybrid cloud solutions, announced today it was named to the 20 Coolest Cloud Infrastructure Vendors Of The 2017 Cloud  (http://www.concertocloud.com/about/in-the-news/2017/02/0…
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…
As a trusted technology advisor to your customers you are likely getting the daily question of, ‘should I put this in the cloud?’ As customer demands for cloud services increases, companies will see a shift from traditional buying patterns to new…

809 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