- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- VCSU - Previous firmware update was not completed
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
08-19-2011 04:30 AM
08-19-2011 04:30 AM
Hi
So I ran into this problem when attempting to update the Virtual Connect FlexFabric 10Gb/24-port modules on my new c7000 from 3.15 to 3.18. Disabling DNS on the interconnect bays resolved the error and restored functionality as described in the advisory, but now when I attempt to retry the update, VCSU returns the following result:
The following modules will NOT be updated:
==============================================================================
Enclosure Bay Module Current Version Status
==============================================================================
SGH120X5AJ 1 HP VC 3.15 Previous firmware
FlexFabric 2010-10-09T08:13:18Z update was not
10Gb/24-Port completed
Module
------------------------------------------------------------------------------
SGH120X5AJ 2 HP VC 3.15 Previous firmware
FlexFabric 2010-10-09T08:13:18Z update was not
10Gb/24-Port completed
Module
------------------------------------------------------------------------------
The log file shows the following information:
[Fri Aug 19 20:37:06 2011] (8668)[VcsuCore.cpp:2448] : Checking state of any incompleted firmware updates.
[Fri Aug 19 20:37:06 2011] (8668)[VcsuCore.cpp:2465] :
Previous firmware update process on the module in bay 1 did not complete
[Fri Aug 19 20:37:06 2011] (8668)[VcsuCore.cpp:2466] : The module should be reset to activate the firmware.
[Fri Aug 19 20:37:06 2011] (8668)[VcsuCore.cpp:2590] : Incomplete firmware update operation on module : enc_serial- SGH120X5AJ, bay- 1
[Fri Aug 19 20:37:06 2011] (8668)[VcsuCore.cpp:1955] : Primary VCM found in enclosure SGH120X5AJ, bay 1
[Fri Aug 19 20:37:13 2011] (8668)[OaWrap.cpp:783] : User successfully deleted
I already reset the Virtual Connect Manager as part of the "checkpoint error" fix, how do I reset the module?
Do I need to download and reinstall 3.15 with the -f option?
Thanks
Adam
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-19-2011 06:37 AM
08-19-2011 06:37 AM
SolutionIt looks like you have a pending firmware update that still needs to be committed on those devices. "Rebooting" the Virtual Connect Modules themselves should remove them from this state.
Easiest way to do it is from the Onboard Administrator of the chassis where the VC Module resides. Go to Interconnect Bays -> VC Module you want to reboot -> Virtual Buttons Tab. From there, you should be able to power off the VC Module, then power it back on. Conversely, if you're nearby, you can physically pull the VC Module from the chassis and plug it back in. That should do the trick as well...
Of course, since you're rebooting the modules, you will force a VC Failover, so be aware that you could potentially affect network traffic out of the chassis. Good luck!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2011 06:07 PM
08-21-2011 06:07 PM
Re: VCSU - Previous firmware update was not completed
Hi Jonathan
That fixed it. After performing the reboot both modules showed 3.18 without additional intervention required. I had already done the "Virtual Connect Manager reset" through the VCM web interface but obviously that wasn't sufficient and a full power cycle was required.
Thanks