Some servers lost connectivity on the same server as others

Running a HYPER-V host (Windows Server 2012 R2 Data Center), with 11 vm's connected via NIC Teaming connected to an Aruba 2920-48G Switch, 3 of the vm's are suddenly not able to connect (yellow explanation sign reads 'no Internet connection'). NIC cards shows no issues and NIC Teaming has all green up arrows. No issues in the event logs.

I removed the static IP's from the servers but they still won't connect to DHCP (with error 'unidentified'
I deleted the virtual NICs and recreated (same issue)
I checked DNS and there are no issues jumping out at me
I replaced all of the Ethernet cables on all NIC's on the server
I logged into the switch and didn't see any issues

I have never seen anything like this. Is there another area that I should be looking at? My fear is that more servers will lose connection and I am at a loss as to why.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Make sure the network driver is up to date.

Is the VM's vNIC getting a VLAN tag? Is the VLAN set up correctly in the switch?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bizzie247Author Commented:
Thank you, yes, drivers are up to date. Yes, vlan tag. That is the strange part, other servers are in the same vlan, on the same server and (for now), running without issue.
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Check the VLAN tag/trunk setup on the switch. Since a team is involved, the switch may be blocking the tag on a port the VMs currently reside on in the team.
bizzie247Author Commented:
I contacted HP to report the issue an they suggested changing the setting in NIC Teaming from 'Switch Independent' to 'LACP' and create associated LACP Trunk on the switch. This worked. Thanks
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.