Issue:
The VM's is losing network connectivity to the external network over the virtual switch when creating a third or fourth VM. Sometimes even local connectivity is missing, but not always.
Scenario:
- HP ProLiant ML350p Gen8
- Windows Server 2012 R2 Standard with Hyper-V
- 1 NIC for management, 1 NIC for VM's (HP Ethernet 1G 4-port 331i adapter, driver version 16.6.0.4.)
- LAB environment on separate subnet for 'proof or concept' with no user load - yet!
Things I've tried:
- Update NIC to the latest available official driver on HPs webpage. No change.
- Alternating settings for 'Virtual Machines Queue' in NIC driver settings. No change
- Replaced physical firewall. No change.
- Firmware update using HP intelligent Provisioning (sufficient?). No change.
- Replaced physical switch. VM can now connect to external network (!?)
Workaround:
I've found out that changing physical switch will restore connectivity. However, loss of connectivity will occur again after creating another VM - until the switch is replaced once again.
I alternate between two switches; Dell PowerConnection 2816 and D-Link DGS-1008G. I know the D-link is a consumer switch (HP enterprise switches awaiting, but doubt it will matter) but it should work for now.
Question:
I'm not completely comfortable with putting this hypervisor in production with this irrational behavior and my question is if anybody else has encountered similar problems and if so how did you resolve it permanently?
Essen