- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Virtual Connect Enterprise Manager and Virtual Con...
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-28-2010 06:49 AM
09-28-2010 06:49 AM
Virtual Connect Enterprise Manager and Virtual Connect firmware upgrade
David had a customer problem that was needing some attention:
**************************************
Here is a situation. Customer had VC 3.01 and ID 6.0 with VCEM 6.0 running fine.
They decided to update to ID 6.1 and VC fw 3.10 but they started by putting VC in maintenance mode at VCEM and updated vc fw to 3.10 (wrong starting point).Now, he can’t move VCEM from maintenance mode back to normal because VCEM 6.0 does not support this firmware.
He tried to upgrade to ID 6.1 but VCEM 6.1 module upgrade process failed because VCEM 6.0 was in maintenance mode.
So he gave up and tried to downgrade VC 3.10 to 3.01 but vcsu 1.5.0 comes with this message:
Internal Error: Downgrade from this version of Virtual Connect firmware to the
target version would result in destruction of domain. Please manually delete
the Virtual Connect domain and run Virtual Connect Support Utility again.
Is this really necessary? Any other way to turn this situation back to normal (with all components upgraded) without mayor disruption?
Thanks
**********************************
Dave had some good answers:
*****************************
You may want to try the VCSU v1.5.1:
Type: |
Utility - Tools |
Version: |
1.5.1 (17 Sep 2010) |
Operating System(s): |
Microsoft Windows Server 2003, Microsoft Windows Vista, Microsoft Windows XP Professional |
File name: |
vcsu-1.5.1-x86.msi (3.0 MB) |
» Description |
|
|
» Enhancements |
|
|
» Installation Instructions |
|
|
» Release Notes |
|
|
Fixes |
|
|
» Revision History |
|
|
|
|||
|
|
||
|
|||
********************************
Other suggestions or comments?