- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Updating Virtual Connect Modules
BladeSystem - General
1752773
Members
4851
Online
108789
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО03-28-2010 02:29 PM
тАО03-28-2010 02:29 PM
Updating Virtual Connect Modules
We have 4 ethernet Virtual Connect modules in a c7000 chassis they were running 2.01 and I was upgrading to 2.32.
I have managed to update 3 of them but the active VCM failed.
I now have a mismatch.
The error in vcutil says "Previous firmware update process on the module in bay 2 did not complete
The module should be reset to activate the firmware.
Any ideas?
Thanks
I have managed to update 3 of them but the active VCM failed.
I now have a mismatch.
The error in vcutil says "Previous firmware update process on the module in bay 2 did not complete
The module should be reset to activate the firmware.
Any ideas?
Thanks
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-30-2010 03:10 AM
тАО03-30-2010 03:10 AM
Re: Updating Virtual Connect Modules
The answer to this is in the question, "Reset" the modules.
Note:: A software reset is often insufficient. It is usually necessary to physically "Pull" the module and reinsert it.
When you do this, the module will disappear from the OA "Interconnect" display, and will reappear after ~2-3 minutes, at which point it should display the correct FW. Second Note, you may find that the FW is not displayed in the VCM.
IF YOU ARE CYCLING THE "ACTIVE" VC MODULE, THIS MIGHT BE A DISRUPTIVE ACTION, DEPENDING ON YOUR CONFIGURATION.
If you have your servers correctly teamed, then there should be no problem. However if you dont, it can take 25-30 seconds for the vcm to failover to the other module, which can cause problems for servers which are not teamed.
If you are doing multiple modules, I would recommend that you wait a minimum of 5 minutes between each module.
HTH
Dave.
Note:: A software reset is often insufficient. It is usually necessary to physically "Pull" the module and reinsert it.
When you do this, the module will disappear from the OA "Interconnect" display, and will reappear after ~2-3 minutes, at which point it should display the correct FW. Second Note, you may find that the FW is not displayed in the VCM.
IF YOU ARE CYCLING THE "ACTIVE" VC MODULE, THIS MIGHT BE A DISRUPTIVE ACTION, DEPENDING ON YOUR CONFIGURATION.
If you have your servers correctly teamed, then there should be no problem. However if you dont, it can take 25-30 seconds for the vcm to failover to the other module, which can cause problems for servers which are not teamed.
If you are doing multiple modules, I would recommend that you wait a minimum of 5 minutes between each module.
HTH
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-30-2010 03:57 AM
тАО03-30-2010 03:57 AM
Re: Updating Virtual Connect Modules
Hi thanks for the reply.
Yeah I tried that but it didnt work for me. The way I got it working was upload the update bin via the VCM web management then just upgraded from there. 20 minutes later it upgraded fine.
Yeah I tried that but it didnt work for me. The way I got it working was upload the update bin via the VCM web management then just upgraded from there. 20 minutes later it upgraded fine.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP