I have been trying to use Virtual SANs/FC Adapters in my 2012 Hyper-v failover clusters. I have run into a couple problems which have led me to remove failover clustering and go with stand-alone hosts, which seems more stable. If anyone has experienced similar issues and has better fixes, that would be fantastic.
SAN Details:
- HP EVA4000
- OpenIndiana ZFS storage server
- HP Brocade 4 and 8 Gb FC switches
Host details:
- HP BL465c G7 blade servers
- HP LPe1105 HBAs
- Latest HP MPIO DSM for EVA, Microsoft DSM for OI LUNs
- Latest HP SPP (firmware and drivers)
Issues:
- If a node is reset or crashes, a VM using virtual FC adapters will not start on any nodes in the cluster--I receive "an unknown NPIV error occurred”. In order to start the VM, I have to swap the WWPNs on the A and B ports on each virtual FC adapter. The VM will not Live Migrate (since I can't use the second WWPN) until all nodes in the cluster have been rebooted.
- After removing a node from the failover cluster, the previously working vSANs stop working. If I remove the vSANs, I cannot add them back because Hyper-v decides that the HBA driver no longer supports NPIV. The only fix I have found is a rebuild...which is hardly a fix. Haven't been able to get deep enough into HP's support to find someone who knows what "NPIV" means
- This seems like it may be on my storage side, but a couple time my clusters started failing roles back and forth until they locked up and had to be totally rebooted to restore them.
Matthew