WLC 4402 Upgrade Failure

RVirdi · ‎07-22-2009

I cannot upgrade our WLC 4402 from version 5.0.148.0 to a higher version.

I have read all the relevant documentation and upgrades for other 4402s and 2100s have worked.

When I upgrade to 5.2.157.0, for example, the uplink port is disabled and I get the following error messages:

Message Log Severity Level ...................... ERROR

*May 13 17:22:33.504: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:305 Failed to read configuration file 'cliWebInitParms.cfg'

*May 13 17:22:33.354: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:305 Failed to read configuration file 'rfidInitParms.cfg'

*May 13 17:22:33.352: %WPS-3-TOKEN_MISSING_INVALID: sig_v1.c:266 Missing or invalid 'Preced' token in Version 1 sig

Previous message occurred 2 times.

*May 13 17:22:33.351: %WPS-3-TOKEN_MISSING_INVALID: sig_v1.c:266 Missing or invalid 'Preced' token in Version 1 sig

Previous message occurred 4 times.

*May 13 17:22:33.350: %WPS-3-TOKEN_MISSING_INVALID: sig_v1.c:266 Missing or invalid 'Preced' token in Version 1 sig

Previous message occurred 4 times.

*May 13 17:22:33.349: %WPS-3-TOKEN_MISSING_INVALID: sig_v1.c:266 Missing or invalid 'Preced' token in Version 1 sig

Previous message occurred 3 times.

*May 13 17:22:33.348: %WPS-3-TOKEN_MISSING_INVALID: sig_v1.c:266 Missing or invalid 'Preced' token in Version 1 sig

*May 13 17:22:33.286: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:305 Failed to read configuration file 'dhcpParms.cfg'

Would you like to display the next 15 entries? (y/n) y

*May 13 17:22:33.257: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:305 Failed to read configuration file 'bcastInitParms.cfg'

*May 13 17:22:33.119: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:305 Failed to read configuration file 'rrmInitParms.cfg'

*May 13 17:22:32.927: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:305 Failed to read configuration file 'apfInitParms.cfg'

*May 13 17:22:32.529: %DTL-3-DSNET_CONF_FAILED: dtl_ds.c:428 Unable to set symmetric mobility tunneling to enabled on Distribution Service interface.

*May 13 17:22:32.424: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:305 Failed to read configuration file 'mmInitParms.cfg'

*May 13 17:22:29.033: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:305 Failed to read configuration file 'aaaapiInitParms.cfg'

*May 13 17:22:29.031: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:305 Failed to read configuration file 'pemInitParms.cfg'

*May 13 17:22:29.012: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:305 Failed to read configuration file 'dot1xInitParms.cfg'

*May 13 17:22:16.031: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:305 Failed to read configuration file 'sshpmInitParms.cfg'

*May 13 17:22:15.992: %CNFGR-3-INV_COMP_ID: cnfgr.c:1940 Invalid Component Id : Unrecognized (36) in cfgConfiguratorInit.

*May 13 17:22:15.915: %SYSTEM-3-FILE_READ_FAIL: nvstore.c:305 Failed to read configuration file 'spamInitParms.cfg'

Can anyone please help?

ericgarnel · ‎07-22-2009

Per the Cisco Error & System Messages FAQ:

http://supportwiki.cisco.com/ViewWiki/index.php/Wireless_LAN_Controller_(WLC)_Error_and_System_Messages_FAQ

(copy & paste the whole line)

It states the following:

Q. These error messages appear on the Wireless LAN controller (WLC): * Jul 10 14:52:21.902 nvstore.c:304 SYSTEM-3-FILE_READ_FAIL: Failed to read configuration file 'cliWebInitParms.cfg' * Jul 10 14:52:21.624 nvstore.c:304 SYSTEM-3-FILE_READ_FAIL: Failed to read configuration file 'rfidInitParms.cfg' * Jul 10 14:52:21.610 nvstore.c:304 SYSTEM-3-FILE_READ_FAIL: Failed to read configuration file 'dhcpParms.cfg' * Jul 10 14:52:21.287 nvstore.c:304 SYSTEM-3-FILE_READ_FAIL: Failed to read configuration file 'bcastInitParms.cfg' What do these error message indicate?

A. These messages are information messages and are part of normal boot procedure, when particular configuration files are not found, the config sequence for each process sends out this message, for example, no DHCP server config, no tags (RF ID) config, and so forth. These messages do not interrupt the operation of the controller. "

If possible, can you reset the controller to factory defaults, reconfig and then try to upgrade it?

If that doesn't work, you may want to open a TAC case