Failed Software Upgrade

Unanswered Question
Jun 30th, 2009

Have a customer that reports a 4402 controller that has no console access after a software upgrade from 4.2.99 to 4.2.176.

They report they thought 4.2.176 went in ok but failed to read the configuration.

So they loaded ER.aes.

The controller powers up but no console access. Service port interface lights up but does not lease an address in DHCP.

From the look of the hyperterm log (before console was lost) both the primary and secondary were loaded with the same image version. But this failed it also appears the tftp load failed.

Is the controller bricked at this point?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Scott Fella Fri, 07/03/2009 - 10:40

Like Andrew mentioned, either use tftf32 or 3CDeamon which I use. Don't think it's bricked.

Mike Lydick Fri, 07/03/2009 - 11:51

Thanks, for the responses. I agree on the TFTP failing from server. But they rebooted the controller a few times with no console response. No DHCP lease on the service port. So is there a break sequence or something when the console does not come up?

There is no post at all on boot

andrewswanson Mon, 07/06/2009 - 05:40

Is there a dhcp scope setup for the vlan/subnet the service port connects to? Can't explain the lack of console access though. The service port interface can't be assigned a gateway so if you can get it to pick up an IP through DHCP, you should be able to access it from the same subnet.


Scott Fella Mon, 07/06/2009 - 06:41

Open a TAC case is my suggestion. They might have a work around for the corrupted image on the wlc. Upgrading the code should be done on the backup and not the primary image for emergency cases like yours.


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