FirePOWER update 5.4.0.3 inconveniences

[Ed Padilla Jr]

I updated to 5.4.0.3 FirePOWER "one sensor" so far, and by viewing the TASK STATUS, it displayed DISCONNECTED status.  Then I look at the Defense Center health status, and shows that the sensor is in "DISABLED" mode (technically according to Support, it is someplace inside doing something, and it can not communicate, and it doesnt tell you how long would it take to come back). Well, after 15 minutes of waiting in this LIMBO mode or FAR FAR AWAY galaxy status, I decided to manually hard bounce the sensor, and it finally it came up, saying that it completed the update.  Bingo!  I have 45 more sensors to go, and all them are INLINE NO BYPASS mode. 

Support wasn't helpful, because they say that "EVENTUALLY" will come back.....and if you feel a "reasonable time" the sensor does not come back, then call Support. 

Has anyone, experiencing this type of concern, on this particular update, and could share some thoughts on a workaround this "issue"?

Thanks,

[Marvin Rhoads]

They do take an inordinately long time. Then again, most products with databases built in do that.

Cisco does have the estimated upgrade time duration posted in the release notes.

If you want a more detailed blow-by-blow to see the progress in more granular detail, there are some log files that you can tail from the cli. That will give you every step of all the shell scripts that run as part of an upgrade.