- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Virtual Connect Update Path from F/W 2.34 to 3.18
BladeSystem - General
1748051
Members
4881
Online
108758
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
тАО06-09-2011 06:34 AM
тАО06-09-2011 06:34 AM
Virtual Connect Update Path from F/W 2.34 to 3.18
Good day
Just want confirmation that the below is the correct path when upgrading virtual connect firmware.
1) Only do one virtual connect at a time
2) Do not skip more that two versions so:
a - first upgrade from 2.34 to 3.10
b - second upgrade from 3.10 to 3.18 (current latest)
Cheers!
Just want confirmation that the below is the correct path when upgrading virtual connect firmware.
1) Only do one virtual connect at a time
2) Do not skip more that two versions so:
a - first upgrade from 2.34 to 3.10
b - second upgrade from 3.10 to 3.18 (current latest)
Cheers!
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2011 09:43 AM
тАО06-09-2011 09:43 AM
Re: Virtual Connect Update Path from F/W 2.34 to 3.18
Personally, I would use VCSU, and let the utility decide whether the upgrade path is OK. Also let VCSU do all modules in one pass, it is smart enought to know the correct order in which to do them.
Dave.
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-10-2011 02:23 AM
тАО06-10-2011 02:23 AM
Re: Virtual Connect Update Path from F/W 2.34 to 3.18
Got it confirmed by HP twice. The entry in the question is a supported path.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-10-2011 02:24 AM
тАО06-10-2011 02:24 AM
Re: Virtual Connect Update Path from F/W 2.34 to 3.18
As stated in question.
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