Hyper-V Vlan - How to set up

[markwilfan]

I have the trunk to each hyper v server with all vlans tagged and the server vlan untagged. That means that each virtual nic is on server van by default unless you specify the vlan on the virtual nic

[newpersn]

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.

 

Yes. i would like to able to just to change the Vlan ID in the vm machine settings. Or am better off just using 1 link to the switch/server. (have all 3,4,5,6,8 vlans tagged so i can just pick a number)

[markwilfan]

Yes. i would like to able to just to change the Vlan ID in the vm machine settings. Or am better off just using 1 link to the switch/server. (have all 3,4,5,6,8 vlans tagged so i can just pick a number)

This is how I do it so it is possible. Think this is the way most people do it tbh

[LytchettNM]

Wow this is getting the Gary matter working which is not good this time of night!

I like simple and straightforward but this depends on the network overview and hardware capabilities.

I have a single subnet for our servers which terminate on the core switch as does all my client subnets basically a VLAN/subnet per building this keeps DNS clean and allows the core switch to do the networking routing and the server to just provide the services they are configured for.

[newpersn]

This is how I do it so it is possible. Think this is the way most people do it tbh

 

I will have a play tomorrow after i reboot and firmware update the switch. Do i try and do it on a trunk and leave out lcap?

 

Wow this is getting the Gary matter working which is not good this time of night!

I like simple and straightforward but this depends on the network overview and hardware capabilities.

I have a single subnet for our servers which terminate on the core switch as does all my client subnets basically a VLAN/subnet per building this keeps DNS clean and allows the core switch to do the networking routing and the server to just provide the services they are configured for.

 

Its been bugging me all day. And now im at home i can think and wonder about it. Trying different things at home via rdp.

[markwilfan]

Wow this is getting the Gary matter working which is not good this time of night!

I like simple and straightforward but this depends on the network overview and hardware capabilities.

I have a single subnet for our servers which terminate on the core switch as does all my client subnets basically a VLAN/subnet per building this keeps DNS clean and allows the core switch to do the networking routing and the server to just provide the services they are configured for.

Pretty simple from what I read. The vlans are set up on the switch the server is connected to. So as long as you can trunk the 4 ports you need to have 1 vlan as untagged and all the rest as tagged if you are sharing the trunk with management

[markwilfan]

I will have a play tomorrow after i reboot and firmware update the switch. Do i try and do it on a trunk and leave out lcap?

 

 

 

Its been bugging me all day. And now im at home i can think and wonder about it. Trying different things at home via rdp.

Honestly though, telnet to the switch, log in and type menu to get the cli menu. Much easier to configure most things compared to the gui

[Katy]

I've got one of these switches at the top of each comms rack, to trunk via the web interface I've set LACP Status: Disabled, Trunk Type: LACP, Trunk Group: Trk1... with LACP Status set to disabled it stops the dynamic group from appearing and just leaves you with a normal trunk group.

[newpersn]

Honestly though, telnet to the switch, log in and type menu to get the cli menu. Much easier to configure most things compared to the gui

 

I was playing around telnet and the switch and can't believe how easy and simple it was.

 

I've got one of these switches at the top of each comms rack, to trunk via the web interface I've set LACP Status: Disabled, Trunk Type: LACP, Trunk Group: Trk1... with LACP Status set to disabled it stops the dynamic group from appearing and just leaves you with a normal trunk group.

 

I will try this tomorrow. Thank you

[LytchettNM]

So 2 things to remember with LAG's you MUST configure both the server and switch ports to use the same protocol I would recommend LACP without a doubt.

The other thing to remember is that you won't be able to create a single transfer that exceeds the max speed of one port so with 4 x 1GB ports in a LAG the max bandwidth is still 1GB per transfer but you can now achieve 4 x transfers at a time, assuming the have the throughput from the client and servers storage.

Good luck with getting the LACP config sorted.

[newpersn]

So 2 things to remember with LAG's you MUST configure both the server and switch ports to use the same protocol I would recommend LACP without a doubt.

The other thing to remember is that you won't be able to create a single transfer that exceeds the max speed of one port so with 4 x 1GB ports in a LAG the max bandwidth is still 1GB per transfer but you can now achieve 4 x transfers at a time, assuming the have the throughput from the client and servers storage.

Good luck with getting the LACP config sorted.

 

Got it all working now. Thank you all for your help and thank you for bearing with me aswell

 

[markwilfan]

Got it all working now. Thank you all for your help and thank you for bearing with me aswell

 

[ATTACH=CONFIG]44823[/ATTACH]

Woo hoo

[LytchettNM]

Got it all working now. Thank you all for your help and thank you for bearing with me aswell

 

[ATTACH=CONFIG]44823[/ATTACH]

 

Congratulations