Re: [ovirt-users] creating a vlan-tagged network

2017-01-02 Thread Jim Kusznir
Actually, I finally was able to identify the issue and fix it...Turns out (as you probably expected), it wasn't ovirt... My upstream provider had some wierd security left over, it limited the MAC addresses permitted to exit the building, and my ovirt host made the list somehow while my VMs did

Re: [ovirt-users] creating a vlan-tagged network

2017-01-01 Thread Edward Haas
On Sun, Jan 1, 2017 at 7:16 PM, Jim Kusznir wrote: > I pinged both the router on the subnet and a host IP in-between the two > ip's. > > [root@ovirt3 ~]# ping -I 162.248.147.33 162.248.147.1 > PING 162.248.147.1 (162.248.147.1) from 162.248.147.33 : 56(84) bytes of > data.

Re: [ovirt-users] creating a vlan-tagged network

2017-01-01 Thread Jim Kusznir
I pinged both the router on the subnet and a host IP in-between the two ip's. [root@ovirt3 ~]# ping -I 162.248.147.33 162.248.147.1 PING 162.248.147.1 (162.248.147.1) from 162.248.147.33 : 56(84) bytes of data. 64 bytes from 162.248.147.1: icmp_seq=1 ttl=255 time=8.17 ms 64 bytes from

Re: [ovirt-users] creating a vlan-tagged network

2017-01-01 Thread Edward Haas
On Sun, Jan 1, 2017 at 10:50 AM, Jim Kusznir wrote: > I currently only have two IPs assigned to me...I can try and take another, > but that may not route out of the rack. I've got the VM on one of the IPs > and the host on the other currently. > > The switch is a

Re: [ovirt-users] creating a vlan-tagged network

2017-01-01 Thread Jim Kusznir
I currently only have two IPs assigned to me...I can try and take another, but that may not route out of the rack. I've got the VM on one of the IPs and the host on the other currently. The switch is a "web-managed" basic 8-port switch (thrown in for testing while the "real" switch is in

Re: [ovirt-users] creating a vlan-tagged network

2016-12-31 Thread Edward Haas
On Sun, Jan 1, 2017 at 9:01 AM, Jim Kusznir wrote: > Hi all: > > I've got my ovirt cluster up, but am facing an odd situation that I > haven't pinned down. I've also run into someone on the IRC channel with > the same bug, no solutions as of yet. Google also hasn't