Hyper-V Vlan - How to set up

[newpersn]

Hi all,

 

Just wondering on how i do this. Do i just setup the ports (eg: 22,23,24,25 as also like to team them as i got 4 spare nics on the server) on the switch to tagged (so VLAN 2,3,4,5,6,7,8 tagged)

 

Then within hyper-v network settings to untagged the NIC to the right vlan?

 

Am i right on thinking that should work?

[ADMaster]

If tagged is the same as trunked then yes.

I have cisco switches, the ports for the VMs trunked so multiple vlans can pass, the port for management is a standard access port with the vlan assigned on the switch.

 

In the VM settings I just tick the VMID box and enter the vlan number.

[LytchettNM]

Hi all,

 

Just wondering on how i do this. Do i just setup the ports (eg: 22,23,24,25 as also like to team them as i got 4 spare nics on the server) on the switch to tagged (so VLAN 2,3,4,5,6,7,8 tagged)

 

Then within hyper-v network settings to untagged the NIC to the right vlan?

 

Am i right on thinking that should work?

 

As you mention VLAN's I'm assuming your looking to connect this server to your core switch and use all 4 Ethernet ports together as a single connection?

You will have to setup both end of the connection by this I mean the server and the switch utilising LACP it's not hard to do a little googling, the terminology used by different switch manufacturers makes it difficult to offer exact advice without more of an overview the your networks topology and infrastructure.

If you have your VLAN's terminating within your core switch and it doing your routing then you should not need to touch your VLAN's as this most be working already again assuming this is a production network your looking to improve the bandwidth / performance of.

 

Darren

[Blue_Cookeh]

Using HP terminology...

 

We have 4 NICs in each Hyper-V host.

 

x1 NIC is a standard untagged port on our rack switch.

x3 NICs are LACP bonded on the switch and in Windows, the Hyper-V switch is then assigned to the Windows bonded interface. This bond is untagged on our data VLAN and tagged for all others.

 

This means if I need a VM on our data VLAN I just assign it's NIC as untagged, if I need it on another one I just VLAN tag it within the VM options in Hyper-V.

[newpersn]

So this is my main switch where i got the servers plugged in.... Just simple as this:

 

 

(Switch is a: HP-2530-48G-2SFPP)

[Blue_Cookeh]

So this is my main switch where i got the servers plugged in.... Just simple as this:

 

[ATTACH=CONFIG]40502[/ATTACH]

 

(Switch is a: HP-2530-48G-2SFPP)

 

Yes, that will put that physical interface into an LACP bond on whichever Trunk Group interface you choose (Trk1/2/3/4 etc). You want to put the same NICs from your server into the same Trunk Group to form the bond. You'll then need to untag/tag the VLANs on that Trunk Group and set the bond up in Windows using Server Manager.

Edited January 5, 2017 by Blue_Cookeh

[newpersn]

trying to get this to work and ive hit a dead wall....

 

 

Guessing im missing something somewhere....

[Blue_Cookeh]

trying to get this to work and ive hit a dead wall....

 

[ATTACH=CONFIG]44804[/ATTACH]

 

Guessing im missing something somewhere....

 

In what way isn't it working? Have you bonded the four ports in Server Manager in Windows, and set the bonding type to LACP?

[newpersn]

In what way isn't it working? Have you bonded the four ports in Server Manager in Windows, and set the bonding type to LACP?

 

Yep. 4 ports bonded together. And still doesn't pick the vlans up.

 

I've had a play with lacp and it won't let me add trunk and trunk group with lacp set. Take it off and I can set it. (Above screenshot)

 

I've looked up the vlan info on the ports and it won't let me add 3,4,5,6,8 tagged to the trunk. (1 is untagged and won't let me change it)

 

I'm guessing it something so simple that I haven't set.

[Blue_Cookeh]

I'll grab the configuration off our 2530 rack switch tomorrow for you

[newpersn]

I'll grab the configuration off our 2530 rack switch tomorrow for you

 

Thank you.

[LytchettNM]

Yep. 4 ports bonded together. And still doesn't pick the vlans up.

 

I've had a play with lacp and it won't let me add trunk and trunk group with lacp set. Take it off and I can set it. (Above screenshot)

 

I've looked up the vlan info on the ports and it won't let me add 3,4,5,6,8 tagged to the trunk. (1 is untagged and won't let me change it)

 

I'm guessing it something so simple that I haven't set.

 

You will need to setup both ends of the bonded link to LACP otherwise to will not be able to utilise the full speed of the bonded link, it looks like you have chosen trunk and not LACP from you screen shot.

When you creat the lag on the server make sure you set that bonded group to use LACP to.

 

If you have a router / layer 3 core switch doing your routing then you should not need to tag all you VLAN into your servers, the routing device should doing that work for you.

[newpersn]

Updated screen shots now. I've had a play since and still no luck.

 

[LytchettNM]

Server side looks good, but you have created a LACP link on the switch but not added it to a trunk group.

[LytchettNM]

And you only have one port assigned on the switch.

[newpersn]

It's ports 27,28,29,30. It wouldn't let me change them together.

 

It won't let me select a trunk group.

 

Off the top of my head it gives me an error about dynamic groups.

Edited August 2, 2017 by newpersn

[newpersn]

It's ports 27,28,29,30. It wouldn't let me change them together.

 

It won't let me select a trunk group.

 

Off the top of my head it gives me an error about dynamic groups.

 

Screen shot of the error:

 

[newpersn]

I get the same error when doing it though telnet aswell. I have noticed that "Dyn1" is untagged but wont let me tag the rest of the vlans on the same name.

[LytchettNM]

Sorry I don't know the switch so can't give you direct answers but is this switch in production or setup for testing?

If not in production then maybe do a factory reset and then look at setup of the LAG again I'm sure there will be guides on the manufacturer site for basic LAG configurations.

[LytchettNM]

Is the switch "Aruba 2530 48G PoE+ 2SFP+ Switch" if so this is a layer 2 switch, so where are you going to do the routing for the network?

[newpersn]

Sorry I don't know the switch so can't give you direct answers but is this switch in production or setup for testing?

If not in production then maybe do a factory reset and then look at setup of the LAG again I'm sure there will be guides on the manufacturer site for basic LAG configurations.

 

Production switch. I about to update the switch to latest firmware as its running firmware from 2016 and latest one is last month.

 

Is the switch "Aruba 2530 48G PoE+ 2SFP+ Switch" if so this is a layer 2 switch, so where are you going to do the routing for the network?

 

That is the switch. (well its a HPE not Aruba but same as) I'm sure its doing the routing already. (i didn't set this switch up. it was rushed in to production due to the old switch that failing, The config was mirrired across from the old one (setting by setting)

[markwilfan]

I always use the cli to trunk ports. Much easier

[LytchettNM]

Just found a guide on the HP site.

http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-c03594944-1.pdf#page121

Just a quick skim read it would seem if you enable LACP on the port the switch will dynamically create the trunk port I think.

[newpersn]

Just found a guide on the HP site.

http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-c03594944-1.pdf#page121

Just a quick skim read it would seem if you enable LACP on the port the switch will dynamically create the trunk port I think.

 

Must do. It wont let me change anything once i turn LACP to Active. Wont change anything else. I just cant get the vlans to pick up on Hyper-V

[LytchettNM]

Are you trying to configure the VLAN's to send down the trunk to the server?

We have our core switch stack setup to route everything in the switch so I only need one subnet from the switch to the server, if you are trying to terminate all of you VLAN's on the server I think you are going to have each VLAN on the server with an IP address in the subnet for each VLAN on your server, this could be a nightmare when it comes to DNS I would say.