- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Network dropout for VM after vMotion
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
12-18-2013 11:42 PM
12-18-2013 11:42 PM
Network dropout for VM after vMotion
I have two C7000 enclosures, each with two VC FlexFabric modules with a single Virtual Connect domain. There are three BL645c blades in each enclosure running VMware ESXi 5.0. There are 20-30 VLANs defined in Virtual Connect and vSphere.
I have a problem when I vMotion a virtual machine from one host to another that the VM will lose network connectivity. I have checked the configuration and am confident it is correct.
Connectivity is restored if I disconnect and reconnect the vNIC with the vSphere Client, which confirms the configuration is correct. This issue only seems to affect one or two VLANs.
The vSwitch is configured to notify switches of the move, but it is as if this update is not sent. This issue can occur when migrating a VM within the same enclosure or over to a separate enclosure. The issue doesn't occur on other VLANs. There is no consistency.
Has anyone else experienced this issue?