Questions regarding 2006 Bootstrap and _ER Release...

Unanswered Question
Apr 17th, 2007

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 4.0.206.0; does this file apply only to 4.0.206.0? 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.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode