- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Virtual Connect move question
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
Forums
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
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
10-18-2010 06:09 AM
10-18-2010 06:09 AM
Virtual Connect move question
Brad had a customer Virtual Connect question:
********************
They have the original virtual connects in bays 1 and 2. They have already installed the new flex 10 VCs in 3 and 4. They did all of this prior to the new firmware that was just released. Now they just need to remove the legacy VC’s from Bays 1 and 2 to repurpose them. They just want to make sure when they pull them out that they will not lose the configuration and connectivity to the blades. They have already disabled all the LOM nics and are strictly running off of the Mezz cards. Because this is production and there are 16 blades in the Chassis they have also backed up the config just in case. I think they will be fine but I wanted to make sure.
**********************
Lionel replied:
****************************
Unfortunately this is not allowed today and this repurpose function does not exist, the only choice you have is to delete the domain!
Even if we had the possibility to move the VCM Primary/backup function to the other modules in Bay 3 and 4, the rule that applies here for you is “Replacing a primary or backup VC Module with a different VC module type is not allowed without first deleting the domain. “
**************************
Other comments or suggestions?