<div dir="ltr"><div><div><div>Hi Tom,<br><br></div>It turns out that the issue was setting a default aka native VLAN on the switch port. The switch is an Arista. After I'd tried re-creating the networks on the oVirt side, I thought I'd just try removing the default VLAN, and it worked. For whatever reason, our VMWare cluster (that I'm trying to migrate away from) has this setting, as do our blade centres, and they have no problem. I'm not sure why you'd want a default Anyway, thanks for the reply - all sorted now!<br><br></div>Cheers,<br><br></div>Cam<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 15, 2016 at 1:07 PM, Tom Gamull <span dir="ltr"><<a href="mailto:tgamull@redhat.com" target="_blank">tgamull@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Can you eliminate the switch or port config as the issue? I’m a little unclear as to how you configured the nodes I have basically use a single NIC (some are LACP bonds) with a GENERAL link type (not TRUNK or ACCESS) where there is a default VLAN (which I don’t tag) and the rest of the VLANs are tagged. On my switch (TP-LINK) I have to go to the VLANs and say TAG on all of them except the DEFAULT one. I couldn’t get TRUNK working even with one untagged and the rest tagged. For me, using GENERAL was the way I did it.<div><br></div><div>I’m not a networking except on hardware but this discussion may clarify. I have no idea why TRUNK didn’t work over GENERAL and didn’t spend much more time than that but here’s a discussion on the topic <a href="https://supportforums.cisco.com/discussion/11897946/general-vs-trunk-mode" target="_blank">https://supportforums.<wbr>cisco.com/discussion/11897946/<wbr>general-vs-trunk-mode</a></div><div><br></div><div>Tom<br>
<br><div><blockquote type="cite"><div><div class="h5"><div>On Sep 14, 2016, at 3:08 PM, cmc <<a href="mailto:iucounu@gmail.com" target="_blank">iucounu@gmail.com</a>> wrote:</div><br></div></div><div><div><div class="h5"><div dir="ltr"><div><div><div><div><div>Hi,<br><br></div>I have modified my VM network to have multiple tagged networks. It used to be an untagged network and it worked fine, but I needed to add more networks on the host. The switch it is connected to has the port configured as a trunk port with these VLANs. When a VM sends traffic out (to get a DHCP address for instance), it reaches the server but does not get the DHCP offer that the server sends. I did a tcpdump on the node that hosts the VM and the packets going out do not have a VLAN tag. I assume the VM host interface would should not have the tag present, but that the p2p1.91 interface should put the VLAN tag on.<br><br>The relevant interface configuration on the node that the VM host is on looks like:<br><br>27: sohonet_DMZ: <BROADCAST,MULTICAST,UP,LOWER_<wbr>UP> mtu 1500 qdisc noqueue state UP <br> link/ether a0:36:9f:2a:63:20 brd ff:ff:ff:ff:ff:ff<br>29: p2p1.91@p2p1: <BROADCAST,MULTICAST,UP,LOWER_<wbr>UP> mtu 1500 qdisc noqueue master vmnet state UP <br> link/ether a0:36:9f:2a:63:20 brd ff:ff:ff:ff:ff:ff<br>30: vmnet: <BROADCAST,MULTICAST,UP,LOWER_<wbr>UP> mtu 1500 qdisc noqueue state UP <br> link/ether a0:36:9f:2a:63:20 brd ff:ff:ff:ff:ff:ff<br> inet6 fe80::a236:9fff:fe2a:6320/64 scope link <br> valid_lft forever preferred_lft forever<br>31: vnet0: <BROADCAST,MULTICAST,UP,LOWER_<wbr>UP> mtu 1500 qdisc pfifo_fast master vmnet state UNKNOWN qlen 500<br> link/ether fe:1a:4a:16:01:58 brd ff:ff:ff:ff:ff:ff<br> inet6 fe80::fc1a:4aff:fe16:158/64 scope link <br> valid_lft forever preferred_lft forever<br>32: vnet1: <BROADCAST,MULTICAST,UP,LOWER_<wbr>UP> mtu 1500 qdisc pfifo_fast master vmnet state UNKNOWN qlen 500<br> link/ether fe:1a:4a:16:01:5c brd ff:ff:ff:ff:ff:ff<br> inet6 fe80::fc1a:4aff:fe16:15c/64 scope link <br> valid_lft forever preferred_lft forever<br><br></div>where vnet1 is the VM interface, and p2p1.91 is the VLAN'd interface for the network. The network the VM nic is on is vmnet, and the physical interface is p2p1<br><br></div>Configuring an address manually does not help, nor does dropping the firewall on the host.<br></div><div>I've run the vmnet interface in promiscuous mode to see if I can see anything coming back, but the return traffic does not appear.<br></div><div><br>Any ideas as to why the network is not working?<br><br></div>Thanks for any help.<br><br></div>-Cam<br><div><div><div><br><br></div></div></div></div></div></div>
______________________________<wbr>_________________<br>Users mailing list<br><a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br><a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br></div></blockquote></div><br></div></div></blockquote></div><br></div>