topic Bootloader Version........... in Wireless

Problem with Field image recovery software

Kamran Mustafayev — Mon, 05 Jul 2021 09:27:22 GMT

Dears,

I updated cisco wlc 5508 FUS image, but field recovery image stayed the same, does this mean that fus is not upgraded, what can i do?

Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 8.0.110.0
Bootloader Version............................... 1.0.20
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.7, Env 1.8, USB console 2.2
Build Type....................................... DATA + WPS + LDPE

System Name...................................... NW2-WLC01
System Location.................................. Level 11 Server Room
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. SSO
IP Address....................................... 10.10.12.8
IPv6 Address..................................... ::
Last Reset....................................... Software reset
System Up Time................................... 0 days 21 hrs 29 mins 51 secs
System Timezone Location......................... (GMT +4:00) Muscat, Abu Dhabi
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180

Bootloader Version...........

Leo Laohoo — Fri, 06 Feb 2015 08:24:52 GMT

Bootloader Version............................... 1.0.20

FUS upgrade was successful. Your Bootloader version is reflecting the newest version.

But what about Field recovery

Kamran Mustafayev — Fri, 06 Feb 2015 08:34:12 GMT

But what about Field recovery image? it is not upgraded, i have HA between two WLC 5508, one of them has the newest field recovery image and the second has the 6.0.182.0

After 2 weeks of normal work wlc suddenly crashes, before the first crash i initiated debug capwap errors enable command, and AP begin disconnecting randomly, so i dont know if the cause is field recovery image different or problem is debug command, im using 8.0.110.0 version of code on both of WLC

what can be the problem, i need you advice

I think there is a firewall

Kamran Mustafayev — Sun, 08 Feb 2015 08:53:04 GMT

I think there is a firewall blocking capwap ports 5246 5247, or it is bug of 8.0.110.0 image

This is what you should see:

Scott Fella — Sun, 08 Feb 2015 14:43:47 GMT

This is what you should see:

Cisco 5500 Series Wireless LAN Controllers

•Field Recovery Image is upgraded from 7.0.112.21 to 7.6.101.1

•Bootloader is upgraded to 1.0.20

•Offline Field Diagnostics is upgraded from 0.9.28 to 0.9.35

•FPGA Revision version is upgraded to 1.7

•Environment Controller (MCU) Image version is upgraded to 1.8

•USB Console Revision version is upgraded to 2.2

The issue is if you were upgrading the FUS to 1.9.0.0, you should of had console access to see what was going on. Typically the primary will download the image and write to flash and then the secondary would upload the image from the primary and write to flash. The secondary would need to be rebooted first then the primary. If the sysinfo didn't match between the two, then you need to upload the FUS 1.9.0.0 and do it again. This is if your have AP SSO enabled. If it's an N+1 configuration, then you need to upload the FUS 1.9.0.0 to the WLC that hasn't had everything upgraded and perform the upgrade again. From the console you can choose what you want upgraded by skipping the upgraded that is up to date.

-Scott

So, i will upload FUS image

Kamran Mustafayev — Mon, 09 Feb 2015 09:42:27 GMT

So, i will upload FUS image again to my wlc with 1.0.20 bootloader, but with older Field recovery image

I will tell the results

thank you

the problem is :CSCus81385 -

Kamran Mustafayev — Fri, 13 Feb 2015 07:38:25 GMT

the problem is :

CSCus81385 - msglog flooded with Validation of SPAM_VENDOR_SPECIFIC_PAYLOADand40;185&#41

11 february. 2015, they showed this bug only 2 days ago for 8.0.110.0 code

Re: This is what you should see:

shelagh.m — Sun, 15 Oct 2017 19:33:26 GMT

Hi Scott, I am having the same issue as described here. It seems to go fine until reboot.

here is the console output:-

====================
Checking for Field recovery image upgrade

Field Recovery Image upgrade ...

Upgrade Field Recovery Image from version 6.0.182.0 to 7.6.101.1

Upgrade will start in 30 sec, press (y) to start immediately else press any key to ABORT !!.

====================
Checking for usb console firmware upgrade

USB upgrade ...

Upgrading USB from rev 1.27 to rev 2.2

******************************************************************
* Upgrade may take several minutes to complete. *
* Please make sure POWER SUPPLY is always ON during this period. *
* Loss of POWER will completely kill this unit and make it *
* unrecoverable *
******************************************************************

Upgrade will start in 30 sec, press (y) to start immediately else press any key to ABORT !!.

Timeout, starting upgrade.
Starting USB Console Programming
..................
Programming Complete!

All upgrades done. System reboot ...
Restarting system.

WLCNG Boot Loader Version 1.0.20 (Built on Jan 14 2014 at 11:40:45 by cisco)
Board Revision 1.3 (SN: FCW1648L09K, Type: AIR-CT5508-K9) (G)

Verifying boot loader integrity... OK.

OCTEON CN5645-NSP pass 2.1, Core clock: 600 MHz, DDR clock: 330 MHz (660 Mhz data rate)
FPGA Revision 1.7
Env FW Revision 1.8
USB Console Revision 2.2
CPU Cores: 10
DRAM: 1024 MB
Flash: 32 MB
Clearing DRAM........ done
Network: octeth0', octeth1
' - Active interface
E - Environment MAC address override
CF Bus 0 (IDE): OK
IDE device 0:
- Model: STEC M2T CF 1.0.0 Firm: K1367MIX Ser#: STIM2M3512248014207
- 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.0.140.0)
100%

38294942 bytes read
Launching...
init started: BusyBox v1.6.0 (2010-05-13 17:50:10 EDT) multi-call binary
starting pid 845, tty '': '/etc/init.d/rcS'
/etc/init.d/rcS: line 5: cannot create /proc/sys/net/ipv4/ip_no_pmtu_disc: nonexistent directory
Set PLX switch MPS settings .............!!!!!!!
Detecting Hardware ...
set smp_affinity for irq 48
003f
DP from CGE5.0 ...
starting pid 1120, 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
readCPUConfigData: cardid 0x6070001
Cisco is a trademark of Cisco Systems, Inc.
Software Copyright Cisco Systems, Inc. All rights reserved.

Cisco AireOS Version 8.0.140.0
Firmware Version FPGA 1.7, Env 1.8, USB console 2.2
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 Licensing Services: 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(10)
Fastpath CPU0.00: Init MBUF size: 1856, Subsequent MBUF size: 2040
Fastpath CPU0.00: Core 0 Initialization and FIPS self-test: 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 and FIPS self-test: ok
Fastpath CPU0.02: Core 2 Initialization and FIPS self-test: ok
Fastpath CPU0.03: Core 3 Initialization and FIPS self-test: ok
Fastpath CPU0.03: Received instruction to get link status
Fastpath CPU0.04: Core 4 Initialization and FIPS self-test: ok
Fastpath CPU0.05: Core 5 Initialization and FIPS self-test: ok
Fastpath CPU0.06: Core 6 Initialization and FIPS self-test: ok
Fastpath CPU0.07: Core 7 Initialization and FIPS self-test: ok
Fastpath CPU0.08: Core 8 Initialization and FIPS self-test: ok
Fastpath CPU0.09: Core 9 Initialization and FIPS self-test: 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 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
Starting CIDS Services: ok
Starting Ethernet-over-IP: ok
Starting DTLS server: enabled in CAPWAP
Starting CleanAir: ok
Starting WIPS: ok
Starting SSHPM LSC PROV LIST: ok
Starting RRC Services: ok
Starting SXP Services: ok
Starting Alarm Services: ok
Starting FMC HS: ok
Starting IPv6 Services: ok
Starting Config Sync Manager : ok
Starting Hotspot Services: ok
Starting PMIP Services: ok
Starting Portal Server Services: ok
Starting mDNS Services: ok
Starting Management Services:
Web Server: CLI: Secure Web: ok

(Cisco Controller)

Enter User Name (or 'Recover-Config' this one-time only to reset configuration to factory defaults)

User: admin
Password:************
(Cisco Controller) >
(Cisco Controller) >
(Cisco Controller) >show sysinfo

Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 8.0.140.0
Bootloader Version............................... 1.0.20
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.7, Env 1.8, USB console 2.2
Build Type....................................... DATA + WPS