cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Popup Hotspot Using ISR 1000 with WiFi/LTE for Teleworkers and Micro Branchesr

Ask Me Anything – How to Enable Network Connectivity to Remote Workers
3763
Views
10
Helpful
30
Replies
Highlighted
Beginner

WLC 2504 fails to load the latest image 8.3.120.0

Hi, 

I upgraded the image version on a WLC 2504 from 8.0.115.0 to 8.3.120.0 and it did perfectly but it fails to load it with no errors whatsoever.

Now the problem is, even though the bootloader and 'show boot' shows the primary image as "8.3.120.0" and the secondary as "8.0.115.0" it still loads the previous 8.0.115.0 version. I have tried "config boot primary" then saved and rebooted the WLC and the console shows that 8.3.120.0 is loading without any errors but eventually its the previous version that always loads. I'm stucked as i cant find any relative topic over the internet. Your response and help would be highly appreciated.

Below you can see that the bootloader loads the primary but eventually it loads the previous image.

WLCNG Boot Loader Version 1.0.20 (Built on Jan 14 2014 at 11:40:45 by cisco)
Board Revision 0.0 (SN: PSZ164309W9, Type: AIR-CT2504-K9) (P)

Verifying boot loader integrity... OK.

OCTEON CN5230C-SCP pass 2.0, Core clock: 750 MHz, DDR clock: 330 MHz (660 Mhz da ta rate)
CPU Cores: 4
DRAM: 1024 MB
Flash: 32 MB
Clearing DRAM........ done
Network: octeth0', octeth1, octeth2, octeth3
' - Active interface
E - Environment MAC address override
CF Bus 0 (IDE): OK
IDE device 0:
- Model: 1GB CompactFlash Card Firm: CF B612J Ser#: A191104296A1Wb5EBOtj
- Type: Hard Disk
- Capacity: 977.4 MB = 0.9 GB (2001888 x 512)


Press <ESC> now to access the Boot Menu...

Loading primary image (8.3.102.0)
100%

36878982 bytes read
Launching...
Launching images...
init started: BusyBox v1.6.0 (2010-05-13 17:50:10 EDT) multi-call binary
starting pid 688, tty '': '/etc/init.d/rcS'
Detecting Hardware ...
Installing ether-pow driver - 0x6008
starting pid 873, tty '/dev/ttyS0': '/usr/bin/gettyOrMwar'
Setting up ZVM
Exporting LD_LIBRARY_PATH
Decompressing...
Validating...... OK

Cryptographic library self-test....passed!
XML config selected
Validating XML configuration
octeon_device_init: found 1 DPs
/dev/fpga: No such device or address
readCPUConfigData: cardid 0x6060001
Cisco is a trademark of Cisco Systems, Inc.
Software Copyright Cisco Systems, Inc. All rights reserved.

Cisco AireOS Version 8.0.115.0
Firmware Version PIC 16.0


Initializing OS Services: ok
Initializing Serial Services: ok
Initializing Network Services: ok
Initializing Licensing Services: ok

License daemon start initialization.....

License daemon running.....
Starting Statistics Service: ok
Starting ARP Services: ok
Starting Trap Manager: ok
Starting Network Interface Management Services: ok
Starting System Services: ok
Starting FIPS Features: ok : Not enabled
Starting Fastpath Hardware Acceleration: ok
Starting Fastpath Console redirect : ok
Starting Fastpath DP Heartbeat : ok
Fastpath CPU0.00: Starting Fastpath Application. SDK-1.8.0, build 269. Flags-[DUTY CYCLE] : ok
Fastpath CPU0.00: Initializing last packet received queue. Num of cores(2)
Fastpath CPU0.00: Init MBUF size: 1856, Subsequent MBUF size: 2040
Fastpath CPU0.00: Core 0 Initialization: ok
Fastpath CPU0.00: Initializing Timer...
Fastpath CPU0.00: Initializing Timer...done.
Fastpath CPU0.00: Initializing Timer...
Fastpath CPU0.00: Initializing NBAR AGING Timer...done.
Fastpath CPU0.01: Core 1 Initialization: ok
Starting Switching Services: ok
Starting QoS Services: ok
Starting Policy Manager: ok
Starting Data Transport Link Layer: ok
Starting Access Control List Services: ok
Starting System Interfaces: ok
Starting Client Troubleshooting Service: ok
Starting Certificate Database: ok
Starting VPN Services: ok
Starting Management Frame Protection: ok
Starting DNS Services: ok
Starting Licensing Services: ok
Starting Redundancy: ok
Starting LWAPP: ok
Starting CAPWAP: ok
Starting LOCP: ok
Starting Security Services: ok
Starting Policy Manager: ok
Starting Authentication Engine: ok
Starting Mobility Management: ok
Starting Capwap Ping Component: ok
Starting AVC Services: ok
Starting Virtual AP Services: ok
Starting AireWave Director: ok
Starting Network Time Services: ok
Starting Cisco Discovery Protocol: ok
Starting Broadcast Services: ok
Starting Logging Services: ok
Starting DHCP Server: ok
Starting IDS Signature Manager: ok
Starting RFID Tag Tracking: ok
Starting RF Profiles: ok
Starting Power Supply and Fan Status Monitoring Service: ok
Starting Mesh Services: ok
Starting TSM: ok


(Cisco Controller) >show boot
Primary Boot Image............................... 8.3.102.0 (default)
Backup Boot Image................................ 8.0.115.0 (active)

30 REPLIES 30
Highlighted
Hall of Fame Community Legend

There isn't any signs that

There isn't any signs that the 8.3 firmware is corrupt. 

What happens if you tell the controller to boot the backup first, save the config, boot the primary first and then save the config?

Does this help?

Highlighted
Beginner

I havent tried that, do you

I havent tried that, do you thing that would help? 

Secondly, the 'esc' key doesnt let me get into the boot options during the startup. Is that information significant? 

Highlighted
Hall of Fame Community Legend

I havent tried that, do you

I havent tried that, do you thing that would help? 

I used to have issues booting secondary images in the past.  

Secondly, the 'esc' key doesnt let me get into the boot options during the startup.

There's a significant chance the console settings you're using is faulty.

Highlighted
Beginner

Ok so what you are saying is

Ok so what you are saying is that I should enter 'config boot backup' then 'save config' then 'config boot primary' then 'save config' then finally reboot it? Or do i need to reboot after 'config boot backup' and then again after 'config boot primary'? Please clarify.

Secondly, I am using the default console settings but I dont face any other issues while entering commands. What console settings shall i try?

Thank you in advance.

Highlighted
Hall of Fame Community Legend

1.  In CLI, configure to boot

1.  In CLI, configure to boot the secondary firmware.  Save the config.  And then change to boot the primary firmware.  Save the config.  Reload the controller. 

2.  If you can't interrupt using the "Esc" key then a setting is off.

Highlighted
Beginner

I tried that but it didnt

I tried that but it didnt work.

I arranged another 2504, ugraded it to similar version and this one is behaving exactly the same. So now i have two WLC2504 behaving likely.

Plus, none of the setting is allowing me to go into boot options in the startup.

Highlighted
Hall of Fame Community Legend

You may need to open a TAC

You may need to open a TAC case.  This could be a bug.

Highlighted
Beginner

Please note that I upgraded

Please note that I upgraded my secondary image to version 8.2 and now both 8.3 and 8.2 are not loading and the WLC stucks on amber during the image loadup.

I upgraded clean copies of both firmwares with proper cisco instructions facing no errors in the process so this cant be due to corrupt images.

Further, none of these two WLCs are under contract anymore so i can not open a TAC case i suppose.

Highlighted
Beginner

is there anyone to help me

is there anyone to help me out on this? i dont have a cisco contract over this device anymore so your suggestions or past experiences would be highly appreciable.

Highlighted
VIP Advocate

You might need to upgrade the

You might need to upgrade the FUS if it's not already on 1.9.0.0 or later. In 1.9.0.0 was a compactflash error fixed, besides a few other things. It would surprise me though, if that really is the reason for you issue.

Download:

https://software.cisco.com/download/release.html?mdfid=283848165&flowid=24841&softwareid=284364857&release=2.0.0.0&relind=AVAILABLE&rellifecycle=&reltype=latest

Highlighted
Beginner

the FUS version is currently

the FUS version is currently on PIC 16.0. I dont know what that is. Could that be a problem?

Highlighted
Beginner

PIC 16.0 is the firmware

PIC 16.0 is the firmware version. Cisco Wireless LAN Controller (WLC) Field Upgrade Software (FUS) is a special AES package that performs various system-related component upgrades. What was the version you came from when you first turned on the 2504? There is a critical FUS upgrade at 7.4 you have to apply before going higher. I have found with major jumps, you need to go back and check each upgrade document to see what they slipped in that is critical. So it looks like you missed 17.0, 18.0 and 19.0. I am sure those are NOT rolled up in the current FUS. Please read the link I have below as I think you will need to go back and grab those FUS files and apply them. Shouldn't have to downgrade the software though. 

This may help explain the process:

https://wirelessstew.wordpress.com/2014/01/26/new-fus-field-upgrade-software-release-1-9-0-0-for-cisco-wireless-lan/

This is the source of the release notes from old to new. In the notes, it will tell you what FUS is required. As I recall, I hit this very same issue moving past 7.4 a few years ago, which introduced me to FUS. 

http://www.cisco.com/c/en/us/support/wireless/2500-series-wireless-controllers/products-release-notes-list.html

(2504_1) >show sysinfo

Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 8.3.102.0
Bootloader Version............................... 1.0.20
Field Recovery Image Version..................... 7.6.101.1
Firmware Version................................. PIC 20.0

Highlighted
Beginner

Hello Peter!

Hello Peter!

Looking at your provided link, i think my FUS version is 1.9.0.0 because my Field Recovery Image Version is exactly the same as yours i.e 7.6.101.1. The website states

"When running FUS1.8.0.0 on WLC2504 and moving to 1.9.0.0
Field Recovery Image is upgraded from 7.4.1.30 to 7.6.101.1"

>show sysinfo

Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 8.0.115.0
Bootloader Version............................... 1.0.20
Field Recovery Image Version..................... 7.6.101.1
Firmware Version................................. PIC 16.0

>show boot
Primary Boot Image............................... 8.3.102.0 (default) 
Backup Boot Image................................ 8.0.115.0 (active)

The MD5 doesnt seem to be problematic as it matched the one provided by Cisco. There must be something we are missing here..

I am extremely thankful for your support and time Peter.

Highlighted
VIP Advocate

Maybe your CF card is broken

Maybe your CF card is broken and the image gets broken while it will be written on it.

Also, do you have a DTLS model? I'm not sure how they handle non-DTLS (encryption) images on this hardware if you bought it in one of the not allowed countries.

CreatePlease to create content
Content for Community-Ad

Cisco COVID-19 Survey