- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE 3PAR StoreServ Storage
- >
- 3PAR Virtual Service Processor VSP fails after Mig...
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
01-19-2016 07:35 AM
01-19-2016 07:35 AM
Hi,
I recently setup VSP V4.4.0 GA-22 on a Hyper-V Standalone Host. We configured the VSP accordingly, running fine.
This VSP needs to be moved to a different Hyper-V Host. I stopped the VM, did a "Shared-Nothing" Livemigration to the destination Hyper-V Host. This step processed successfully.
After I started the VM, the network-configuration in the VM failed. Error in console log:
>>Device eth0 does not seem to be present, delaying initialization.
>>Device eth1 does not seem to be present, delaying initialization.
The VSP is not accessible through network at all.
Even when migrating the VM back to the origin Hyper-V Host, the VSP fails with same error.
Restored the VSP from backup to this host, success.
Checked VSP Best practise, but content is confusing:
Page 8:
Protecting your VSP using VMware HA or Microsoft Failover Clustering
Users should consider running the VSP on a VMware HA cluster or Microsoft Failover Cluster as applicable.....
Page 9:
VSP and Hypervisor VM mobility
At the time of the writing of this paper and with the release of HP 3PAR SP 4.2, the VMware VMotion or Microsoft Live Migration are not supported. It is recommended that users do not attempt to use such features with the current VSP release
How should I supply a VSP in Hyper-V with high-availibility, when HA Features like migrations are not supported?And why is the VSP so picky against (Live-) Migrations?
For reply thanks in advance,
Markus
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2016 04:14 AM