Cisco VTP and Native VLAN on Hyper-V

[dazza007]

Hello!

I understand that the native vlan on a trunk is used to share VTP information. If setting up a Hyper-V server should the native vlan on the switchport be the management vlan of Hyper-V or should it be the same vlan as the management vlan for the switches.

 

A couple of years ago we upgraded our servers to Hyper-Converged Servers and the install was done with a guru from the Netherlands and mentioned that the native port should be the management vlan, looking at the connected interface (as a trunk) sends but does not receive vtp information.

 

Is it relevant though, as it is cisco proprietary method?

 

As you see this is bugging me! Google cannot help

 

Cheers

Dazza

[FN-GM]

The native VLAN sends other data as well. Technically speaking it doesn’t matter what the native VLAN is, as long as it’s the same on both the server and switch.

 

Personally I wouldn’t use VTP. You’re asking for trouble!

[nicholab]

From Cisco: VLAN Trunk Protocol (VTP) reduces administration in a switched network. When you configure a new VLAN on one VTP server, the VLAN is distributed through all switches in the domain. This reduces the need to configure the same VLAN everywhere. VTP is a Cisco-proprietary protocol that is available on most of the Cisco Catalyst series products.

 

So if it Cisco server kit it might support VTP but no the hyper-v network will not understand VTP. VLAN ID’s should be the same across the site.

[Davit2005]

I would not bother using VTP either to be honest. We have 700+ switches on site and get on without it. There are things you need be wary of revision numbers, etc. to name a few. It does not matter what is the native vlan is for a server connecting to a switch as long as it matches. It is also better not to have any client vlans untagged on uplinks, in actual fact it is best to have all the vlans for clients, servers, management, etc tagged on uplinks if possible then leave vlan 1 untagged as it is best not to use for client traffic anyway. Edited November 23, 2022 by Davit2005

[dazza007]

Thank you all!

I can see the wood for the trees now! Indeed sending VLAN information from a CISCO switch to a Hyper-V switch is a non-starter indeed.

Having learned cisco by being thrown in at the deep end, i reviewed some of the fundamentals and I am surprised that I have not wiped the VLAN database in 4 years, a refresh is overdue so an ideal time to drop VTP!

Many many thanks for your comments, they are always much appreciated!