- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: Firmware Update Process and Behaviour in Multi...
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
06-06-2011 12:36 PM
06-06-2011 12:36 PM
Firmware Update Process and Behaviour in Multi stacked enclosures
Kanwar had a firmware update question:
***********************
Hi Team,
Just wondering what will be the process and behavior of upgrading the firmware in stacked enclosures ? According to “Virtual Connect Multi-Enclosure Stacking Reference Guide”
"VCSU will upgrade all the module at same time (page 17 of the doc.)."
However I don’t want all the modules to be updated at same time so how should I go about this ?
**************************
Lee replied:
The Virtual Connect Support Utility (VCSU) will allow you to set serial activation and place pause timers in the Interactive mode of the tool. I suggest reading the Admin Guide for the VCSU tool. VCSU doesn’t allow granular updates for Multi-Enclosure Domains(MED), I.E. update one chassis at a time. You have to do it all at once. The only flexibility is with module activation and timings.
Mark also had some advice:
Upgrade and Activate are two distinct operations in a firmware upgrade.
“Upgrade” is defined as a transfer of the firmware image to the alternate flash bank on the VC module.
“Activate” is defined as a reset of the module to boot the new firmware image.
Upgrades (i.e transfer) are done in parallel. This cannot be modified and there is no reason to modify this.
Activates (i.e resets) are done Odd/Even by default but can be modified to “Serial”.
A serial activate would only reset one module at a timer per domain, so no two modules would ever be rebooting at the same time.
I would follow Lee’s instructions on reading the Admin Guide for the VCSU.
**********************
Any other comments or suggestions?
- Tags:
- firmware update
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2012 10:15 AM
05-04-2012 10:15 AM
Re: Firmware Update Process and Behaviour in Multi stacked enclosures
I have a similar issues here. there are multiple enclosures stacked. The command to update VC firmware in a VCSU helps to update firmware on all the enclosures in the stack. According to Lee's reply does it mean that, since VSCU will not allow updating firmware individually will VCEM help doing this.