Nic Teaming on a CISCO switch stack.

[ikhantt]

 

 

Good Day All,

 

I have been experimenting with nic teaming on my new Server 2019 STD Hyper V install.

 

I have VMS in VMware hosts but I want to migrate them to Hyper V.

I have migrated some VM's to the new host but when I started them up not all can connect to the network.
they can ping internal between themselves but access outside.

 

I used this is a reference:

https://docs.microsoft.com/en-us/windows-server/networking/technologies/nic-teaming/nic-teaming-settings

 

my team is configured as in attachment. 

 

The ports are connected to 2 Cisco 3850's that are stacked.

All ports are on the same VM.

 

 

4 VM's that are on the Host are working fine, but when i start the 5th I don't get any network connectivity external to the Virtual switch. If i shut down the Hosts and restart no mater what i do i only get 4 hosts working.

 

i tried switching to load balancing mode: dynamic. but no VM's can connect other than the 1st VM I turn on.

 

Should i move to a switch dependent mode?

 

Any guidance will be appreciated.

 

Edited June 29, 2020 by ikhantt

[Jarsky]

If the VM's can communicate together, but not to anything else it doesn't sound like a teaming problem. If it was a teaming problem then you would have issues with the host. 

Make sure the Hyper-V Virtual Switch is bridged and not NAT. 

[The_Ellimist]

Okay so  I run stacked 3750G's. I use VMM to configure the teaming as I want to be able to see that config in the VMM interface and its all weird if you do it prior to importing the host in VMM. You see it as a team at all times and can't see the seperate adapters in VMM for the host for some reason.

 

You should be running LACP for teaming mode, Address hash for load balancing mode in your picture.

On your switch you need to have a port channel. The basics are below:

 

interface Port-Channel1

description LACP Hyper-V Group

switchport trunk encapsulation dot1q

switchport mode trunk

 

int gi1/0/1

description LACP Hyper-V Group - 1

switchport trunk encapsulation dot1q

switchport mode trunk

channel-group 1 mode active

 

int gi2/0/1

description LACP Hyper-V Group - 2

switchport trunk encapsulation dot1q

switchport mode trunk

channel-group 1 mode active

 

The descriptions are just how I keep track of ports on the switch and the groups they belong to. Adapt this to how you would like to do it.

 

In Hyper-V assign the VLAN ID by setting "Enable virtual LAN identification" and setting the ID to whatever VLAN you want the device on. Obviously in this case make sure that VLAN can talk to the internet.

 

If you want to trunk a network port on the vswitch you can only do that through powershell. Commands are below. Theres no way of doing this in the GUI that I know of as most people would just add more Vnics to the hosts and map them in the OS but its still handy to be able to do.

Get-VMNetworkAdapter -VMName VMNAME | Where-Object -Property MacAddress -eq "MACADDRESS" |
Set-VMNetworkAdapterVlan -Trunk -AllowedVlanIdList 100-110 -NativeVlanId 100