- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Why VC for FC with ESX?
BladeSystem - General
1753448
Members
5135
Online
108794
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
тАО02-14-2009 05:49 PM
тАО02-14-2009 05:49 PM
Why VC for FC with ESX?
If my entire SAN supports NPIV, I'm not clear on the advantages of using HP VC for FC with VMware ESX VMs. Is there any advantage, or is it mostly for physical servers running a traditional OS that have SAN storage?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-15-2009 03:24 AM
тАО02-15-2009 03:24 AM
Why VC for FC with ESX?
If you move servers around inside enclosures it'd help
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2009 02:47 PM
тАО02-17-2009 02:47 PM
Why VC for FC with ESX?
Let's say you have a critical need to do maintenance on a blade. It's a member of a DRS group of 5 servers. You put it in maintenance mode which will evacuate all of the VMs to different hosts, but now you have split your VMs among only 4 servers (or N-1) and you're concerned about meeting the needs of the workloads. You could configure another blade, deploying VMware on it, configuring the LAN and presenting the shared LUN to the new WWN, and configuring it into the DRS group. But that sounds like a lot of hassle. Instead, with VC, as soon as the VMs are evacuated to the other hosts, you could shut down the blade, move the VC profile to another similar blade in the enclosure, and when it boots, it will look exactly to the outside world as if it were the blade that is now in maintenance! No hassling with a lot of configuration tasks. If you're using the Virtual Connect Enterprise Manager, the alternate blade could be in an entirely different enclosure! And with VCEM and Insight Control, you could do something that isn't possible with VMware alone: Let's say you have a blade that generates a pre-failure alert because it has had too many corrections in ECC memory, a condition that could cause an outright failure within a short time. Insight Control can receive that alert, interface with vCenter to put the blade into maintenance mode, and then automatically move the VC profile using VCEM to another blade and start it up!
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