Castlewood
asked on
Potential issues for using trunk port connecting between a switch and a Hyper-V host ?
We use "Trunk" mode (instead of "Access") for connecting Hyper-V host to 4 ports of C3560 switch where 2 ports for VLAN2 and the other 2 ports for VLAN3. Both VLANs are for VMs. Can you see any potential risks/drawbacks for using trunk mode between a switch and a Hyper-V host? Pros and cons?
Here is partial config: (the complete config file attached.)
interface Port-channel1
description Trunk
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 2,3
switchport mode trunk
!
interface GigabitEthernet0/1
description vlan2
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 2,3
switchport mode trunk
mls qos trust cos
channel-group 1 mode active
!
interface GigabitEthernet0/2
description vlan2
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 2,3
switchport mode trunk
mls qos trust cos
channel-group 1 mode active
!
interface GigabitEthernet0/3
description vlan3
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 2,3
switchport mode trunk
mls qos trust cos
channel-group 1 mode active
!
interface GigabitEthernet0/4
description vlan3
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 2,3
switchport mode trunk
mls qos trust cos
channel-group 1 mode active
Here is partial config: (the complete config file attached.)
interface Port-channel1
description Trunk
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 2,3
switchport mode trunk
!
interface GigabitEthernet0/1
description vlan2
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 2,3
switchport mode trunk
mls qos trust cos
channel-group 1 mode active
!
interface GigabitEthernet0/2
description vlan2
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 2,3
switchport mode trunk
mls qos trust cos
channel-group 1 mode active
!
interface GigabitEthernet0/3
description vlan3
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 2,3
switchport mode trunk
mls qos trust cos
channel-group 1 mode active
!
interface GigabitEthernet0/4
description vlan3
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 2,3
switchport mode trunk
mls qos trust cos
channel-group 1 mode active
Only thing to be aware of is that if you have them set as trunk ports and you decide to rebuild you hypervisor at some point if they are not set as trunk port type edge then when the hypervisor has no OS the ports may flap and can cause slow performance through the switch for other servers/hosts when it continuously restarts the spanning tree stuff. Doesn't show up as 100% cpu on the switch... but can cause problems if not set
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
My EE Hyper-V articles may have additional information you can use:
Some Hyper-V Hardware and Software Best Practices
Practical Hyper-V Performance Expectations