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):
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). 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?