Phil Richards knows cyber security. He’s the Chief Information Security Officer for Ivanti—and he has great advice for anyone looking to build a career in cyber security.
How to configure etherchannel trunk between ESXi hosts and Cisco 2960 switch?
This is using 2 VMware ESXi 6.5 hosts. There are 5 VMs per host. We are intend to have 1 vlan for management, 1 for backup segment, and 1 for the production segment. we intend to configure a NIC teaming on 2 physical network (vmnic0 & 1) port per host. Respective port-group for each vlan id were created. 101 for production, 121 for mgmt, and 122 for backup. All 3 port groups joined to the same vswitch0. Load-balancing mode is, Route based on IP hash.
This ESXi Hosts are connected to Cisco Catalyst 2960-48-port switch. The Ethernet channels were configured as follows,
int port-channel 1
switchport trunk allowed vlan 101,121,122
switchport mode trunk
int gigabitethernet1/15
switchport trunk native vlan 101
switchport trunk encap dot1q
switchport trunk allowed vlan 101,121,122
switchport mode trunk
channel-group 1 mode on
int gigabitethernet1/16
switchport trunk native vlan 101
switchport trunk encap dot1q
switchport trunk allowed vlan 101,121,122
switchport mode trunk
channel-group 1 mode on
Do these configurations work?
Thank in advance.
This ESXi Hosts are connected to Cisco Catalyst 2960-48-port switch. The Ethernet channels were configured as follows,
int port-channel 1
switchport trunk allowed vlan 101,121,122
switchport mode trunk
int gigabitethernet1/15
switchport trunk native vlan 101
switchport trunk encap dot1q
switchport trunk allowed vlan 101,121,122
switchport mode trunk
channel-group 1 mode on
int gigabitethernet1/16
switchport trunk native vlan 101
switchport trunk encap dot1q
switchport trunk allowed vlan 101,121,122
switchport mode trunk
channel-group 1 mode on
Do these configurations work?
Thank in advance.
Asked:
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get this solution by purchasing an Individual license!
Start your 7-day free trial.
I wear a lot of hats...
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
Yes, at quick glance, that looks like the correct configuration.
Make sure you also set the vSwitch in ESXi to Route based on IP hash.
Also make sure you create the various Virtual Machine Portgroups with the correct VLAN Tag.
Make sure you also set the vSwitch in ESXi to Route based on IP hash.
Also make sure you create the various Virtual Machine Portgroups with the correct VLAN Tag.
Hi Sajid,
Found the difference.
It looks like you are configure vlan 1 to be the native vlan without tag. In switch, you configured "switchport trunk native vlan 1", and other vlans must be in "switchport trunk allowed ...". Then for the vlan 1 in ESXi, you configured vlan 1 with vlan id 0.
My question is, can I replace this vlan 1 with 101, and set the vlan 101 with vlan id 0 in ESXi?
Found the difference.
It looks like you are configure vlan 1 to be the native vlan without tag. In switch, you configured "switchport trunk native vlan 1", and other vlans must be in "switchport trunk allowed ...". Then for the vlan 1 in ESXi, you configured vlan 1 with vlan id 0.
My question is, can I replace this vlan 1 with 101, and set the vlan 101 with vlan id 0 in ESXi?
see the vlan 1 is the default vlan on the switch ... so when you trunk port to default then you have to go with only vlan 1
Do not use VLAN 1, VLAN 1 is a special VLAN and should not be used.
Tagged VLANs on the physical switch need to match the VLAN tags on your virtual machine portgroups.
So if you use 100, 101, then you need to use 100, 101 in ESXi.
I would not bother with a native VLAN for the trunk, because all this means is if you do not specify a VLAN Tag on a virtual machine portgroup, traffic will be tagged default with this VLAN
which may not be what you want!
Tagged VLANs on the physical switch need to match the VLAN tags on your virtual machine portgroups.
So if you use 100, 101, then you need to use 100, 101 in ESXi.
I would not bother with a native VLAN for the trunk, because all this means is if you do not specify a VLAN Tag on a virtual machine portgroup, traffic will be tagged default with this VLAN
which may not be what you want!
Experts Exchange Solution brought to you by
Your issues matter to us.
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trial
Hi Andrew,
Thanks for your comments on the native vlan on cisco switch, and matching with those set in ESXi port-group.
Thanks for your comments on the native vlan on cisco switch, and matching with those set in ESXi port-group.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Routers
From novice to tech pro — start learning today.
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get this solution by purchasing an Individual license!
Start your 7-day free trial.
https://www.experts-exchange.com/questions/29117210/Use-Switch-in-the-place-of-TRUNK-link-between-router-and-server.html
all the best