At some point or another, a number of my controllers ran firmware that potentially could corrupt the boot eeprom as described in 3.2.150 and 4.0.2xx release notes. Additionally not all controllers run 4.0 code; that subset runs 3.2.116.x.
Now, how do I remedy this situation for my 100+ 2006 controllers so that we eliminate the risk of boot failure in the event that we must default/clear these controllers?
All explanations on this matter lack a thorough treatment of addressing this matter. The only code with the _ER.aes suffix is 220.127.116.11; does this file apply only to 18.104.22.168? Or can it address any 3.2 or later release? What remedy exists for sites not ready yet to upgrade to the 'feature stream' ( >=4.0 )?
In the future, I hope Cisco gets away from these cryptic, meaningless or incomplete warnings and alerts that fails to fully address these type of issues.