Tagged VLANs on ESXi Guests Not Working

I run my CloudStack lab environment on 2 Mac Minis running on ESXi 5.5. For a long time, I had faced the issue where tagged VLAN traffic between my CentOS/Ubuntu guest VMs simply refused to work.

Changing the network adapter type from vmxnet to e1000 seems to fix the issue.

Screen Shot 2013-11-21 at 2.29.16 pm

# Guest #1
[root@csman1-1 ~]# vconfig add eth0 22
Added VLAN with VID == 22 to IF -:eth0:-
[root@csman1-1 ~]# ifconfig eth0.22 192.168.22.21 netmask 255.255.255.0 up
[root@csman1-1 ~]# ping 192.168.22.22
PING 192.168.22.22 (192.168.22.22) 56(84) bytes of data.
From 192.168.22.21 icmp_seq=2 Destination Host Unreachable
From 192.168.22.21 icmp_seq=3 Destination Host Unreachable
From 192.168.22.21 icmp_seq=4 Destination Host Unreachable
# Guest # 2
[root@kvm1-1 ~]# vconfig add eth0 22
Added VLAN with VID == 22 to IF -:eth0:-
[root@kvm1-1 ~]# ifconfig eth0.22 192.168.22.22 netmask 255.255.255.0 up
[root@kvm1-1 ~]# ping 192.168.22.21
PING 192.168.22.21 (192.168.22.21) 56(84) bytes of data.
From 192.168.22.22 icmp_seq=2 Destination Host Unreachable
From 192.168.22.22 icmp_seq=3 Destination Host Unreachable
From 192.168.22.22 icmp_seq=4 Destination Host Unreachable

And after the switching to the e1000 network adapter:

# Guest #1
[root@csman1-1 ~]# vconfig add eth0 22
Added VLAN with VID == 22 to IF -:eth0:-
[root@csman1-1 ~]# ifconfig eth0.22 192.168.22.21 netmask 255.255.255.0 up
[root@csman1-1 ~]# ping 192.168.22.22
PING 192.168.22.22 (192.168.22.22) 56(84) bytes of data.
64 bytes from 192.168.22.22: icmp_seq=1 ttl=64 time=0.763 ms
64 bytes from 192.168.22.22: icmp_seq=2 ttl=64 time=0.436 ms
64 bytes from 192.168.22.22: icmp_seq=3 ttl=64 time=0.449 ms
--- 192.168.22.22 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2405ms
rtt min/avg/max/mdev = 0.436/0.549/0.763/0.152 ms
# Guest #2
[root@kvm1-1 ~]# vconfig add eth0 22
Added VLAN with VID == 22 to IF -:eth0:-
[root@kvm1-1 ~]# ifconfig eth0.22 192.168.22.22 netmask 255.255.255.0 up
[root@kvm1-1 ~]# ping 192.168.22.21
PING 192.168.22.21 (192.168.22.21) 56(84) bytes of data.
64 bytes from 192.168.22.21: icmp_seq=1 ttl=64 time=0.858 ms
--- 192.168.22.21 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 929ms
rtt min/avg/max/mdev = 0.858/0.858/0.858/0.000 ms

Shanker Balan

Shanker Balan is a devops and infrastructure freelancer with over 14 years of industry experience in large scale Internet systems. He is available for both short term and long term projects on contract. Please use the Contact Form for any enquiry.

More Posts - Website

Follow Me:
TwitterLinkedIn

Published by

Shanker Balan

Shanker Balan is a devops and infrastructure freelancer with over 14 years of industry experience in large scale Internet systems. He is available for both short term and long term projects on contract. Please use the Contact Form for any enquiry.

One thought on “Tagged VLANs on ESXi Guests Not Working”

  1. You may also be wondering how non-IP traffic would be put through this calculation since there wouldn’t be an IP header and thus it wouldn’t have a 32-bit source and destination IP address for this calculation. As per the definition from the networking guide: “For non-IP packets, whatever is at those offsets is used to compute the hash”. This essentially means that two 32 bit binary values will be taken from the frame/packet from where the IP addresses would usually be located if it was an IP packet. It really doesn’t matter if these two 32-bit values are not actually IP addresses. So long as there is binary data in these locations, the calculation can still be applied to balance this traffic out across the adapters in the team.

Leave a Reply