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 188.8.131.52 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?