Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Servers and Operating Systems
- >
- BladeSystem
- >
- BladeSystem - General
- >
- Updating Virtual Connect Modules
BladeSystem - General
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
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
- Email to a Friend
- 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
- Email to a Friend
- 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
- Email to a Friend
- 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.
End of content
United States
Hewlett Packard Enterprise International
Communities
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP