Redundant OA firmware update, but without failures please

[ThomVis72]

The situation:
Multiple C7000 enclosures with redundant OA modules installed. Past firmware updates where hit/miss with the update bricking one of the OAs. Contacted support and they suggested rebooting the OAs before the update. Failure rate went down, but still existent. Support always replaced the bricked OAs, but we want to avoid this.

My plan:
- Reboot the OAs
- Pull the standby OA
- Firmware update the present OA.
- Pull the upgraded OA
- Reinsert the old-standby OA
- Firmware update the present OA
- Reinsert the first-upgraded OA

I know running an enclosure with no OA is not manageable, but the servers inside are running and connected.
Is this a good plan?

[Torsten.]

I updated hundreds of OAs and never had such problems.

I would continue to do the upgrade with both OA installed, reboot prior the update may not harm.

In case one does really fail, you may do the firmware recovery (see user guide).

Important:

For OAs with firmware version less than 3.50, first update to OA 3.50 and then continue updating to OA 4.50 or above.

[ThomVis72]

The flash recovery is known, and doesn't work all the time. That's why I mentoined the OA is bricked.

I need to go on-site twice if that happes, once to try the flash recovery, second time to replace the brick.

I would like a solution where I know the upgrade will succeed. If I need to be on-site for that, that's okay, saves me 1 trip and some headache.