I'm not sure why you'd still show the 4.2 boot loader. What order did you install them in? Did you do a second reboot to confirm that it was still showing 4.2.61? When you loaded both ER and AES did you disable both radio networks and all wlans? What do you show if you do a "show run-config" ?
I upgraded the 3750 first - uploaded both images, disabled the WLANs and rebooted the box. Checked the sysinfo and saw the discrepancy - tried downloding the ER file again and rebooted but no difference.
With the 4402 I rebooted after downloading the s/w then repeated with the boot image - Same result - bootloader still previous version. This time I forgot to disable the WLANs though.
The run-config output reports the 4.2 bootloader.
I did notice that when I was upgrading the 4402 via it's own GUI it was referring to the "emergency bootloader", could this be significant?
That is a known issue regarding the bootloader. Even though you load the bootloader, it will still show the original. This info was from TAC... no date when this would be fixed since the boot loader file isn't always an upgrade to the boot loader, but to the partition. TAC also mentioned that when opening a case that this be noted... if the boot loader was installed or not, or which bootloader was loaded last. Hope this clarifies things.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...