- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: Redundant OA firmware update, but without fail...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2020 06:38 AM
09-03-2020 06:38 AM
Redundant OA firmware update, but without failures please
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2020 07:28 AM - edited 09-03-2020 07:43 AM
09-03-2020 07:28 AM - edited 09-03-2020 07:43 AM
Re: Redundant OA firmware update, but without failures please
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.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2020 07:07 AM
09-10-2020 07:07 AM
Re: Redundant OA firmware update, but without failures please
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.