Today I had an issue loading my WLC software on my SRE module sitting on a 3925. Just a quick note on one of the errors I incurred.
It is important to note that this error was caused by the environment I was in, specifically the routes, so you may or may not have as much mileage with this.
XXX-GW1#service-module sm1/0 install url ftp://***:***@10.30.0.28/AS_SMWLC$
Proceed with installation? [no]: yes
Loading AS_SMWLC_7_3_112_0.aes.install.sre !
[OK – 2819/4096 bytes]
Welcome to WLC installation checking resource requirements now
Resource check complete proceeding with installation
000081: Feb 12 2014 14:28:12.095 GMT: %SM_INSTALL-6-INST_RESET: SM1/0 is reset for software installation.
000082: Feb 12 2014 14:29:36.003 GMT: %SM_INSTALL-6-INST_RBIP: SM1/0 received msg: RBIP Registration Request
000083: Feb 12 2014 14:29:36.007 GMT: %SM_INSTALL-6-INST_RBIP: SM1/0 received msg: RBIP File Request
000084: Feb 12 2014 14:29:37.447 GMT: %SM_INSTALL-6-INST_RBIP: SM1/0 received msg: RBIP File Request
000085: Feb 12 2014 14:29:44.467 GMT: %SM_INSTALL-6-INST_RBIP: SM1/0 received msg: RBIP File Request
000086: Feb 12 2014 14:29:44.503 GMT: %SM_INSTALL-6-INST_RBIP: SM1/0 received msg: RBIP File Request
000087: Feb 12 2014 14:30:10.663 GMT: %SRE_SM-6-STATE_CHANGE: SM1/0 changing state from SERVICE_MODULE_STATE_ERRQ to SERVICE_MODULE_STATE_STDY
000088: Feb 12 2014 14:30:32.067 GMT: %SM_INSTALL-6-INST_PROG: SM1/0 PROGRESSING: Partitioning-HardDrive.
000089: Feb 12 2014 14:30:32.071 GMT: %SM_INSTALL-6-INST_PROG: SM1/0 PROGRESSING: Upgrading-Boot-Loader.
SM1/0 is reset due to BootLoader-Download-failed.
000090: Feb 12 2014 14:33:41.663 GMT: %SM_INSTALL-6-INST_FAIL: SM1/0 is reset due to BootLoader-Download-failed.
000091: Feb 12 2014 14:33:41.667 GMT: %SRE_SM-6-STATE_CHANGE: SM1/0 changing state from SERVICE_MODULE_STATE_STDY to SERVICE_MODULE_STATE_ERRQ
When viewing the log files of my FTP server I could see that the router was logging in and pulling my AS_SMWLC_7_3_112_0.aes files but it would always fail to get the bootloader package. For my SRE the bootloader sits inside of sm_bl and I could see that that file never got requested. After a quick forum glance to https://supportforums.cisco.com/thread/2038484 told me what I was missing.
My new 3925 had a gig0/0 IP inside of 10.30.0.0/24 which was the same as my laptop, however my SM interface that I had configured was on a different subnet 10.184.0.0/24. I had realised that it was the SM trying to pull the bootloader file so the source address would have been 10.184 and not from 10.30 like you would presume from the IOS. In my environment my laptop’s GW did not have a route to the 10.184 network, so simply adding this route resolved my issues.