# VLAN Tagging not recognized by VMWare vSwitch **URL:** \ **Category:** SLES Configure-Administer\ **Created:** [October 25, 2016, 10:33am UTC](https://forums.suse.com/t/vlan-tagging-not-recognized-by-vmware-vswitch/28840 "2016-10-25T10:33:01Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![bwiesnet](https://avatars.discourse-cdn.com/v4/letter/b/e0b2c6/32.png) [@bwiesnet](https://forums.suse.com/u/bwiesnet)\ **Post date:** [October 25, 2016, 10:33am UTC](https://forums.suse.com/t/vlan-tagging-not-recognized-by-vmware-vswitch/28840/1 "2016-10-25T10:33:01Z")
Dear Community, I recently configured a vlan with parent device eth2 in yast and set the desired vlan-id. The vlan is showing up when I type ifconfig (this server is running as VM on an esxi): ```auto eth2 Link encap:Ethernet HWaddr 00:50:56:91:38:4E inet6 addr: fe80::250:56ff:fe91:384e/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:101465816 errors:0 dropped:1442325 overruns:0 frame:0 TX packets:44 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:55164023743 (52608.5 Mb) TX bytes:2472 (2.4 Kb) vlan945 Link encap:Ethernet HWaddr 00:50:56:91:38:4E inet addr:10.10.68.10 Bcast:10.10.68.31 Mask:255.255.255.224 inet6 addr: fe80::250:56ff:fe91:384e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:36 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:1824 (1.7 Kb) ``` A second VM on the same esxi server with the configuration above and ip-address ending with .11 CAN PING .10 and vice versa. Now I add another VM on a different esxi server (so the packets have to go up to the router). It has the IP-Address ending with .12. BUT IT CAN NOT PING .11 and .10 and vice versa. At the router no ARP Addresses are in the table. The vswitch on the two vmware switches are configured as trunk (see: [https://kb.vmware.com/selfservice/microsites/search.do?language=en\_US&cmd=displayKC&externalId=1004252](https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004252)). None of the VMS above can ping the Gateway .1!! NOW to proove the infrastructure I set up an ubuntu server on the same esxi server that runs .12 and I give the ubuntu server the IP-Address ending with .13 AAAANNNDD IT CAN PING THE DEFAULT GATEWAY AAAND THERE ARE ARP ENTRIES AT THE ROUTER. So whats the matter with my suse configs on .10, .11 and .12? ---
**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\ **Post date:** [October 25, 2016, 6:55pm UTC](https://forums.suse.com/t/vlan-tagging-not-recognized-by-vmware-vswitch/28840/2 "2016-10-25T18:55:38Z")
Hi bwiesnet, > Now I add another VM on a different esxi server (so the packets have to go up to the router). It has the IP-Address ending with .12. BUT IT CAN NOT PING from an IP point of view, if it needs a router, it needs different subnets. Routers (per definition) are the connecting points between subnets… > None of the VMS above can ping the Gateway .1 Is the router’s gw interface member of VLAN 945? I bet it’s not. > The vswitch on the two vmware switches are configured as trunk how are these VMware servers (or rather the links you try to use from these VMs) connected - directly or via an Ethernet switch? In the latter case, how are the switch parts defined, have you enabled these for VLAN tagging (i.e. 802.1q mode) and permitted VLAN 945 on the Ethernet switch ports? Regards, Jens ---
**Author:** ![bwiesnet](https://avatars.discourse-cdn.com/v4/letter/b/e0b2c6/32.png) [@bwiesnet](https://forums.suse.com/u/bwiesnet)\ **Post date:** [October 27, 2016, 3:22pm UTC](https://forums.suse.com/t/vlan-tagging-not-recognized-by-vmware-vswitch/28840/3 "2016-10-27T15:22:02Z")
Ok I am really sorry for this post, we just detected, the network interfaces were in the wrong order so the vlan was at the wrong adapter… shame on me… Now everything works fine… ---
**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\ **Post date:** [October 28, 2016, 12:34pm UTC](https://forums.suse.com/t/vlan-tagging-not-recognized-by-vmware-vswitch/28840/4 "2016-10-28T12:34:04Z")
Hi, > [@bwiesnet;34946](#): > > Ok I am really sorry for this post, we just detected, the network interfaces were in the wrong order so the vlan was at the wrong adapter… shame on me… Now everything works fine… so I lost my bet 😉 Thank you for reporting back and I’m happy you were able to resolve the issue! Regards, J