Re: [ovirt-users] Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway

2015-10-22 Thread Julián Tete
Good News Everyone :)

I Change from the CentOS 7 kernel to kernel-ml from elrepo in the Host

And oVirt 3.6 Release Candidate 3 works like a charm

Thank you pals :)

2015-10-21 19:36 GMT-05:00 Julián Tete :

> Hello Friends of oVirt
>
> I'm glad to get your help. I'm trying to build a community of oVirt in
> Colombia.
>
> This is the data requested:
>
> #HOST
>
> Software
>
> OS Version: RHEL - 7 - 1.1503.el7.centos.2.8
> Kernel Version: 3.10.0 - 229.14.1.el7.x86_64
> KVM Version: 3.10.0 - 229.14.1.el7.x86_64
> LIBVIRT Version: libvirt-1.2.8-16.el7_1.4
> VDSM Version: vdsm-4.17.9-0.el7.centos
> SPICE Version: 0.12.4 - 9.el7_1.3
> GlusterFS Version: glusterfs-3.7.5-1.el7
> CEPH Version: librbd1-0.80.7-2.el7
>
> Hardware
>
> Manufacturer: HP
> Family: ProLiant
> Product Name: ProLiant BL460c Gen8
> Version: [N/A]
> UUID: 2197C286-BC9C-4CF3-99CB-..
> Serial Number: VCX.
> CPU Model: Intel(R) Xeon(R) CPU E5-2667 v2 @ 3.30GHz
> CPU Type: Intel SandyBridge Family
> CPU Sockets: 2
> CPU Cores per Socket: 8
> CPU Threads per Core: 2 (SMT Enabled)
>
> Model name: QMH2572 - PCI-Express Dual Channel 8Gb Fibre Channel Mezzanine
> HBA, NFF
> Device type: FC
> Model name: QMH2572 - PCI-Express Dual Channel 8Gb Fibre Channel Mezzanine
> HBA, NFF
> Device type: FC
>
> The rest of the data is here:
>
> http://pastebin.com/Snc27Jgn
>
> Thank very much
>
> I love oVirt 3.6, so far so good.
>
> This is the last detail to dump VMware
>
> :)
>
>
>
> 2015-10-13 2:43 GMT-05:00 Ido Barkan :
>
>> Julian,
>> Lets try a more systematic approach (similar to what Donny suggests):
>>
>> Please disable your arp script, and reproduce the situation where your vm
>> cannot connect to the outside.
>> It will be also a good idea to have the failing machine be the only
>> powered on machine connected to the network (bridge).
>>
>> * from the machine os run a ping to a pingable destination outside of
>> your network (8.8.8.8?)
>> * run tcpdump on the hypervisor on several interfaces:
>>   * the vm tap device (vnet0? vnet1?)
>>   * the vm network bridge device (hosting?), where the tap device is
>> attached to. This should be visible via brctl.
>>   * the vlan device underneath the bridge (this one should have a name
>> like 'eno1.50' where eno1 is the physical nic and 50 is the vlan tag)
>>   * the physical device (the ethernet nic)
>>
>> The tcpdump command requires root privileges and looks like this: "sudo
>> tcpdump -n -i  icmp or arp"
>>
>> What I assume we will see are only icmp requests (pings) and no icmp
>> replies (pongs). There might be also be only arp requests and
>> no arp replies.
>> What I am interested at is the arp broadcasts, as the vm should broadcast
>> an arp request (who-is ).
>> My first guess is that is no response or there is one but the vm cannot
>> hear it. This is why I used the arp filter in the tcpdump command.
>>
>> This should shed some light on where the problem is and in which layer.
>> find out where the traffic is not forwarded.
>>
>> Also, when you locate the point of failure, try and wait for the traffic
>> to 'suddenly work' as you said and then figure out what was changed.
>>
>> We would love to see the dumps and coontinue to help.
>>
>> Thanks,
>> Ido
>>
>>
>> On Thu, Oct 8, 2015 at 7:29 PM, Julián Tete 
>> wrote:
>>
>>> I found the reason of my Problem: the virtual machines can't write the
>>> ARP table ¡¡¿?!!
>>>
>>> When I manually use the command:
>>>
>>> arp -s 192.168.XXX.XX 00:09:XX:XX:XX:XX
>>>
>>> I can reach the gateway
>>>
>>> I can't reach anything from my net segment but i can reach Internet
>>> (Double ¡¡¿?!!)
>>>
>>> For the moment I wrote a script, but is awful to do this.
>>>
>>> Any idea ?
>>>
>>> Thanks in advance :)
>>>
>>> 2015-07-10 11:26 GMT-05:00 Julián Tete :
>>>
 Perhaps us are affected by the following error :

 http://h20564.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c04267968

 I will keep you informed

 Thanks Friends

 2015-07-06 12:06 GMT-05:00 Julián Tete :

> Hi Friends of oVirt
>
> This the data required:
>
> I have a HP Enclosure with a HP SAN.
> I can't change the net settings in the switch because we have VMware
> Virtual Machines in production in the same enclosure.
> The switch is in Trunk Mode and all the traffic are in Tagged VLAN's
> with ID's: 1,50,90,91 and 100.
> I can play with 6 blades.
> I in the first Blade I installed oVirt in hosted engine mode.
> The only S.O is CentOS 7.1
>
> I used inxi to brig the data for you:
>
> My First Host is the only host until now (SPM) is the first data
> domain (NFS) and contains the hosted engine machine.
> I installed oVirt with ovirtmgmt in VLAN 1, over the interface eno1,
> without any VLAN Tagged configuration.
>
> This the data for my first 

Re: [ovirt-users] Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway

2015-10-21 Thread Julián Tete
Hello Friends of oVirt

I'm glad to get your help. I'm trying to build a community of oVirt in
Colombia.

This is the data requested:

#HOST

Software

OS Version: RHEL - 7 - 1.1503.el7.centos.2.8
Kernel Version: 3.10.0 - 229.14.1.el7.x86_64
KVM Version: 3.10.0 - 229.14.1.el7.x86_64
LIBVIRT Version: libvirt-1.2.8-16.el7_1.4
VDSM Version: vdsm-4.17.9-0.el7.centos
SPICE Version: 0.12.4 - 9.el7_1.3
GlusterFS Version: glusterfs-3.7.5-1.el7
CEPH Version: librbd1-0.80.7-2.el7

Hardware

Manufacturer: HP
Family: ProLiant
Product Name: ProLiant BL460c Gen8
Version: [N/A]
UUID: 2197C286-BC9C-4CF3-99CB-..
Serial Number: VCX.
CPU Model: Intel(R) Xeon(R) CPU E5-2667 v2 @ 3.30GHz
CPU Type: Intel SandyBridge Family
CPU Sockets: 2
CPU Cores per Socket: 8
CPU Threads per Core: 2 (SMT Enabled)

Model name: QMH2572 - PCI-Express Dual Channel 8Gb Fibre Channel Mezzanine
HBA, NFF
Device type: FC
Model name: QMH2572 - PCI-Express Dual Channel 8Gb Fibre Channel Mezzanine
HBA, NFF
Device type: FC

The rest of the data is here:

http://pastebin.com/Snc27Jgn

Thank very much

I love oVirt 3.6, so far so good.

This is the last detail to dump VMware

:)



2015-10-13 2:43 GMT-05:00 Ido Barkan :

> Julian,
> Lets try a more systematic approach (similar to what Donny suggests):
>
> Please disable your arp script, and reproduce the situation where your vm
> cannot connect to the outside.
> It will be also a good idea to have the failing machine be the only
> powered on machine connected to the network (bridge).
>
> * from the machine os run a ping to a pingable destination outside of your
> network (8.8.8.8?)
> * run tcpdump on the hypervisor on several interfaces:
>   * the vm tap device (vnet0? vnet1?)
>   * the vm network bridge device (hosting?), where the tap device is
> attached to. This should be visible via brctl.
>   * the vlan device underneath the bridge (this one should have a name
> like 'eno1.50' where eno1 is the physical nic and 50 is the vlan tag)
>   * the physical device (the ethernet nic)
>
> The tcpdump command requires root privileges and looks like this: "sudo
> tcpdump -n -i  icmp or arp"
>
> What I assume we will see are only icmp requests (pings) and no icmp
> replies (pongs). There might be also be only arp requests and
> no arp replies.
> What I am interested at is the arp broadcasts, as the vm should broadcast
> an arp request (who-is ).
> My first guess is that is no response or there is one but the vm cannot
> hear it. This is why I used the arp filter in the tcpdump command.
>
> This should shed some light on where the problem is and in which layer.
> find out where the traffic is not forwarded.
>
> Also, when you locate the point of failure, try and wait for the traffic
> to 'suddenly work' as you said and then figure out what was changed.
>
> We would love to see the dumps and coontinue to help.
>
> Thanks,
> Ido
>
>
> On Thu, Oct 8, 2015 at 7:29 PM, Julián Tete 
> wrote:
>
>> I found the reason of my Problem: the virtual machines can't write the
>> ARP table ¡¡¿?!!
>>
>> When I manually use the command:
>>
>> arp -s 192.168.XXX.XX 00:09:XX:XX:XX:XX
>>
>> I can reach the gateway
>>
>> I can't reach anything from my net segment but i can reach Internet
>> (Double ¡¡¿?!!)
>>
>> For the moment I wrote a script, but is awful to do this.
>>
>> Any idea ?
>>
>> Thanks in advance :)
>>
>> 2015-07-10 11:26 GMT-05:00 Julián Tete :
>>
>>> Perhaps us are affected by the following error :
>>>
>>> http://h20564.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c04267968
>>>
>>> I will keep you informed
>>>
>>> Thanks Friends
>>>
>>> 2015-07-06 12:06 GMT-05:00 Julián Tete :
>>>
 Hi Friends of oVirt

 This the data required:

 I have a HP Enclosure with a HP SAN.
 I can't change the net settings in the switch because we have VMware
 Virtual Machines in production in the same enclosure.
 The switch is in Trunk Mode and all the traffic are in Tagged VLAN's
 with ID's: 1,50,90,91 and 100.
 I can play with 6 blades.
 I in the first Blade I installed oVirt in hosted engine mode.
 The only S.O is CentOS 7.1

 I used inxi to brig the data for you:

 My First Host is the only host until now (SPM) is the first data domain
 (NFS) and contains the hosted engine machine.
 I installed oVirt with ovirtmgmt in VLAN 1, over the interface eno1,
 without any VLAN Tagged configuration.

 This the data for my first host:

 http://pastebin.com/dfC0XTQM

 This the data for the Engine:

 http://pastebin.com/JdrMSbj0

 This the data for the Virtual Machine created in VLAN 50:

 S.O : CentOS 7.1
 SELinux: Permissive
 IP ADDRESS: 192.168.50.8
 PREFIX: 27
 GATEWAY: 192.168.50.1
 Interface: eth0

 The Virtual Machine hasn´t any VLAN configuration.

 In the 3 S.O, 

Re: [ovirt-users] Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway

2015-10-13 Thread Ido Barkan
Julian,
Lets try a more systematic approach (similar to what Donny suggests):

Please disable your arp script, and reproduce the situation where your vm
cannot connect to the outside.
It will be also a good idea to have the failing machine be the only powered
on machine connected to the network (bridge).

* from the machine os run a ping to a pingable destination outside of your
network (8.8.8.8?)
* run tcpdump on the hypervisor on several interfaces:
  * the vm tap device (vnet0? vnet1?)
  * the vm network bridge device (hosting?), where the tap device is
attached to. This should be visible via brctl.
  * the vlan device underneath the bridge (this one should have a name like
'eno1.50' where eno1 is the physical nic and 50 is the vlan tag)
  * the physical device (the ethernet nic)

The tcpdump command requires root privileges and looks like this: "sudo
tcpdump -n -i  icmp or arp"

What I assume we will see are only icmp requests (pings) and no icmp
replies (pongs). There might be also be only arp requests and
no arp replies.
What I am interested at is the arp broadcasts, as the vm should broadcast
an arp request (who-is ).
My first guess is that is no response or there is one but the vm cannot
hear it. This is why I used the arp filter in the tcpdump command.

This should shed some light on where the problem is and in which layer.
find out where the traffic is not forwarded.

Also, when you locate the point of failure, try and wait for the traffic to
'suddenly work' as you said and then figure out what was changed.

We would love to see the dumps and coontinue to help.

Thanks,
Ido


On Thu, Oct 8, 2015 at 7:29 PM, Julián Tete  wrote:

> I found the reason of my Problem: the virtual machines can't write the ARP
> table ¡¡¿?!!
>
> When I manually use the command:
>
> arp -s 192.168.XXX.XX 00:09:XX:XX:XX:XX
>
> I can reach the gateway
>
> I can't reach anything from my net segment but i can reach Internet
> (Double ¡¡¿?!!)
>
> For the moment I wrote a script, but is awful to do this.
>
> Any idea ?
>
> Thanks in advance :)
>
> 2015-07-10 11:26 GMT-05:00 Julián Tete :
>
>> Perhaps us are affected by the following error :
>>
>> http://h20564.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c04267968
>>
>> I will keep you informed
>>
>> Thanks Friends
>>
>> 2015-07-06 12:06 GMT-05:00 Julián Tete :
>>
>>> Hi Friends of oVirt
>>>
>>> This the data required:
>>>
>>> I have a HP Enclosure with a HP SAN.
>>> I can't change the net settings in the switch because we have VMware
>>> Virtual Machines in production in the same enclosure.
>>> The switch is in Trunk Mode and all the traffic are in Tagged VLAN's
>>> with ID's: 1,50,90,91 and 100.
>>> I can play with 6 blades.
>>> I in the first Blade I installed oVirt in hosted engine mode.
>>> The only S.O is CentOS 7.1
>>>
>>> I used inxi to brig the data for you:
>>>
>>> My First Host is the only host until now (SPM) is the first data domain
>>> (NFS) and contains the hosted engine machine.
>>> I installed oVirt with ovirtmgmt in VLAN 1, over the interface eno1,
>>> without any VLAN Tagged configuration.
>>>
>>> This the data for my first host:
>>>
>>> http://pastebin.com/dfC0XTQM
>>>
>>> This the data for the Engine:
>>>
>>> http://pastebin.com/JdrMSbj0
>>>
>>> This the data for the Virtual Machine created in VLAN 50:
>>>
>>> S.O : CentOS 7.1
>>> SELinux: Permissive
>>> IP ADDRESS: 192.168.50.8
>>> PREFIX: 27
>>> GATEWAY: 192.168.50.1
>>> Interface: eth0
>>>
>>> The Virtual Machine hasn´t any VLAN configuration.
>>>
>>> In the 3 S.O, Network Manager is stopped and disabled, connectivity is
>>> managed by the network daemon.
>>>
>>> This is the data for the Networking in the admin interface:
>>>
>>> http://postimg.org/image/lbypejxrh/
>>>
>>> http://postimg.org/image/jtkyhqs8f/
>>>
>>> http://postimg.org/image/7dwf1nb9f/
>>>
>>> http://postimg.org/image/6i9t75g33/
>>>
>>> http://postimg.org/image/sm8e6lecv/
>>>
>>> http://postimg.org/image/cvig7rjuv/
>>>
>>> http://postimg.org/image/fxcthsrtl/
>>>
>>> http://postimg.org/image/o6xjwwvyz/
>>>
>>> http://postimg.org/image/pv5ar5v3j/
>>>
>>> http://postimg.org/image/dx8br0gq7/
>>>
>>> http://postimg.org/image/baixp4b0j/
>>>
>>> This the case
>>>
>>> With No IP in the VLAN, and IP in the Virtual Machine, From the Virtual
>>> Machine can ping myself (192.168.50.8) but I can't reach the gateway, can't
>>> reach the host, can't reach Internet.
>>>
>>> Any help is appreciated
>>>
>>> Thanks Friends of oVirt
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> 2015-07-06 7:51 GMT-05:00 Soeren Malchow :
>>>
 Hi,

 To make it easier to understand what the situation is, it would help to
 see your bridging configuration and your interface configration.

 Something like:

 #> ip addr

 And

 #> brctl show

 Regards
 Soeren

 On 06/07/15 13:30, "users-boun...@ovirt.org on behalf of Dan

Re: [ovirt-users] Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway

2015-10-08 Thread Julián Tete
I found the reason of my Problem: the virtual machines can't write the ARP
table ¡¡¿?!!

When I manually use the command:

arp -s 192.168.XXX.XX 00:09:XX:XX:XX:XX

I can reach the gateway

I can't reach anything from my net segment but i can reach Internet (Double
¡¡¿?!!)

For the moment I wrote a script, but is awful to do this.

Any idea ?

Thanks in advance :)

2015-07-10 11:26 GMT-05:00 Julián Tete :

> Perhaps us are affected by the following error :
>
> http://h20564.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c04267968
>
> I will keep you informed
>
> Thanks Friends
>
> 2015-07-06 12:06 GMT-05:00 Julián Tete :
>
>> Hi Friends of oVirt
>>
>> This the data required:
>>
>> I have a HP Enclosure with a HP SAN.
>> I can't change the net settings in the switch because we have VMware
>> Virtual Machines in production in the same enclosure.
>> The switch is in Trunk Mode and all the traffic are in Tagged VLAN's with
>> ID's: 1,50,90,91 and 100.
>> I can play with 6 blades.
>> I in the first Blade I installed oVirt in hosted engine mode.
>> The only S.O is CentOS 7.1
>>
>> I used inxi to brig the data for you:
>>
>> My First Host is the only host until now (SPM) is the first data domain
>> (NFS) and contains the hosted engine machine.
>> I installed oVirt with ovirtmgmt in VLAN 1, over the interface eno1,
>> without any VLAN Tagged configuration.
>>
>> This the data for my first host:
>>
>> http://pastebin.com/dfC0XTQM
>>
>> This the data for the Engine:
>>
>> http://pastebin.com/JdrMSbj0
>>
>> This the data for the Virtual Machine created in VLAN 50:
>>
>> S.O : CentOS 7.1
>> SELinux: Permissive
>> IP ADDRESS: 192.168.50.8
>> PREFIX: 27
>> GATEWAY: 192.168.50.1
>> Interface: eth0
>>
>> The Virtual Machine hasn´t any VLAN configuration.
>>
>> In the 3 S.O, Network Manager is stopped and disabled, connectivity is
>> managed by the network daemon.
>>
>> This is the data for the Networking in the admin interface:
>>
>> http://postimg.org/image/lbypejxrh/
>>
>> http://postimg.org/image/jtkyhqs8f/
>>
>> http://postimg.org/image/7dwf1nb9f/
>>
>> http://postimg.org/image/6i9t75g33/
>>
>> http://postimg.org/image/sm8e6lecv/
>>
>> http://postimg.org/image/cvig7rjuv/
>>
>> http://postimg.org/image/fxcthsrtl/
>>
>> http://postimg.org/image/o6xjwwvyz/
>>
>> http://postimg.org/image/pv5ar5v3j/
>>
>> http://postimg.org/image/dx8br0gq7/
>>
>> http://postimg.org/image/baixp4b0j/
>>
>> This the case
>>
>> With No IP in the VLAN, and IP in the Virtual Machine, From the Virtual
>> Machine can ping myself (192.168.50.8) but I can't reach the gateway, can't
>> reach the host, can't reach Internet.
>>
>> Any help is appreciated
>>
>> Thanks Friends of oVirt
>>
>>
>>
>>
>>
>>
>>
>>
>> 2015-07-06 7:51 GMT-05:00 Soeren Malchow :
>>
>>> Hi,
>>>
>>> To make it easier to understand what the situation is, it would help to
>>> see your bridging configuration and your interface configration.
>>>
>>> Something like:
>>>
>>> #> ip addr
>>>
>>> And
>>>
>>> #> brctl show
>>>
>>> Regards
>>> Soeren
>>>
>>> On 06/07/15 13:30, "users-boun...@ovirt.org on behalf of Dan Kenigsberg"
>>>  wrote:
>>>
>>> >On Tue, Jun 30, 2015 at 03:48:49PM -0500, Julián Tete wrote:
>>> >> Hi Friends of oVirt
>>> >>
>>> >> I'm trying to migrate my company from VMware to oVirt.
>>> >
>>> >We'd like to help you do this!
>>> >
>>> >> In my final tests, I set up 2 more VLANs in oVirt, (VM VLANs)
>>> >> The Virtual Machines in these VLANs, can be reached from the external
>>> >>IPs
>>> >> from the net range,
>>> >> but from the Virtual machines only can ping the Host with the Bridge
>>> and
>>> >> itself, can't reach the gateway. ¿?
>>> >>
>>> >> I configured a IP Forwarding in the Host with the virtual machine, and
>>> >> nothing changes...
>>> >>
>>> >> Any idea ? This is the last duty before embrace oVirt in the company.
>>> >>
>>> >> Look to the VLAN 100 configuration (My desired VM Network):
>>> >>
>>> >> http://postimg.org/image/7hrog0a2n/
>>> >>
>>> >> http://postimg.org/image/68b40i1vr/
>>> >>
>>> >> http://postimg.org/image/lu6mlshgp/
>>> >
>>> >I must admit that I don't understand your problem yet. When you ping
>>> >from inside your guest, where are your packets dropped?
>>> >
>>> >I'd like to point that your "Hosting" network, as most VM networks, is
>>> >better off left without an IP address. The benefit of this is better
>>> >security (host TCP stack is not accessible from VMs) and less chances of
>>> >routing collisions from the host.
>>> >
>>> >So unless you need to use the same network for something other than VM
>>> >communication, try to clear its address.
>>> >
>>> >Regards,
>>> >Dan.
>>> >___
>>> >Users mailing list
>>> >Users@ovirt.org
>>> >http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
>
___
Users mailing list

Re: [ovirt-users] Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway

2015-07-10 Thread Julián Tete
Perhaps us are affected by the following error :

http://h20564.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c04267968

I will keep you informed

Thanks Friends

2015-07-06 12:06 GMT-05:00 Julián Tete danteconra...@gmail.com:

 Hi Friends of oVirt

 This the data required:

 I have a HP Enclosure with a HP SAN.
 I can't change the net settings in the switch because we have VMware
 Virtual Machines in production in the same enclosure.
 The switch is in Trunk Mode and all the traffic are in Tagged VLAN's with
 ID's: 1,50,90,91 and 100.
 I can play with 6 blades.
 I in the first Blade I installed oVirt in hosted engine mode.
 The only S.O is CentOS 7.1

 I used inxi to brig the data for you:

 My First Host is the only host until now (SPM) is the first data domain
 (NFS) and contains the hosted engine machine.
 I installed oVirt with ovirtmgmt in VLAN 1, over the interface eno1,
 without any VLAN Tagged configuration.

 This the data for my first host:

 http://pastebin.com/dfC0XTQM

 This the data for the Engine:

 http://pastebin.com/JdrMSbj0

 This the data for the Virtual Machine created in VLAN 50:

 S.O : CentOS 7.1
 SELinux: Permissive
 IP ADDRESS: 192.168.50.8
 PREFIX: 27
 GATEWAY: 192.168.50.1
 Interface: eth0

 The Virtual Machine hasn´t any VLAN configuration.

 In the 3 S.O, Network Manager is stopped and disabled, connectivity is
 managed by the network daemon.

 This is the data for the Networking in the admin interface:

 http://postimg.org/image/lbypejxrh/

 http://postimg.org/image/jtkyhqs8f/

 http://postimg.org/image/7dwf1nb9f/

 http://postimg.org/image/6i9t75g33/

 http://postimg.org/image/sm8e6lecv/

 http://postimg.org/image/cvig7rjuv/

 http://postimg.org/image/fxcthsrtl/

 http://postimg.org/image/o6xjwwvyz/

 http://postimg.org/image/pv5ar5v3j/

 http://postimg.org/image/dx8br0gq7/

 http://postimg.org/image/baixp4b0j/

 This the case

 With No IP in the VLAN, and IP in the Virtual Machine, From the Virtual
 Machine can ping myself (192.168.50.8) but I can't reach the gateway, can't
 reach the host, can't reach Internet.

 Any help is appreciated

 Thanks Friends of oVirt








 2015-07-06 7:51 GMT-05:00 Soeren Malchow soeren.malc...@mcon.net:

 Hi,

 To make it easier to understand what the situation is, it would help to
 see your bridging configuration and your interface configration.

 Something like:

 # ip addr

 And

 # brctl show

 Regards
 Soeren

 On 06/07/15 13:30, users-boun...@ovirt.org on behalf of Dan Kenigsberg
 users-boun...@ovirt.org on behalf of dan...@redhat.com wrote:

 On Tue, Jun 30, 2015 at 03:48:49PM -0500, Julián Tete wrote:
  Hi Friends of oVirt
 
  I'm trying to migrate my company from VMware to oVirt.
 
 We'd like to help you do this!
 
  In my final tests, I set up 2 more VLANs in oVirt, (VM VLANs)
  The Virtual Machines in these VLANs, can be reached from the external
 IPs
  from the net range,
  but from the Virtual machines only can ping the Host with the Bridge
 and
  itself, can't reach the gateway. ¿?
 
  I configured a IP Forwarding in the Host with the virtual machine, and
  nothing changes...
 
  Any idea ? This is the last duty before embrace oVirt in the company.
 
  Look to the VLAN 100 configuration (My desired VM Network):
 
  http://postimg.org/image/7hrog0a2n/
 
  http://postimg.org/image/68b40i1vr/
 
  http://postimg.org/image/lu6mlshgp/
 
 I must admit that I don't understand your problem yet. When you ping
 from inside your guest, where are your packets dropped?
 
 I'd like to point that your Hosting network, as most VM networks, is
 better off left without an IP address. The benefit of this is better
 security (host TCP stack is not accessible from VMs) and less chances of
 routing collisions from the host.
 
 So unless you need to use the same network for something other than VM
 communication, try to clear its address.
 
 Regards,
 Dan.
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway

2015-07-06 Thread Dan Kenigsberg
On Tue, Jun 30, 2015 at 03:48:49PM -0500, Julián Tete wrote:
 Hi Friends of oVirt
 
 I'm trying to migrate my company from VMware to oVirt.

We'd like to help you do this!

 In my final tests, I set up 2 more VLANs in oVirt, (VM VLANs)
 The Virtual Machines in these VLANs, can be reached from the external IPs
 from the net range,
 but from the Virtual machines only can ping the Host with the Bridge and
 itself, can't reach the gateway. ¿?
 
 I configured a IP Forwarding in the Host with the virtual machine, and
 nothing changes...
 
 Any idea ? This is the last duty before embrace oVirt in the company.
 
 Look to the VLAN 100 configuration (My desired VM Network):
 
 http://postimg.org/image/7hrog0a2n/
 
 http://postimg.org/image/68b40i1vr/
 
 http://postimg.org/image/lu6mlshgp/

I must admit that I don't understand your problem yet. When you ping
from inside your guest, where are your packets dropped?

I'd like to point that your Hosting network, as most VM networks, is
better off left without an IP address. The benefit of this is better
security (host TCP stack is not accessible from VMs) and less chances of
routing collisions from the host.

So unless you need to use the same network for something other than VM
communication, try to clear its address.

Regards,
Dan.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway

2015-07-06 Thread Soeren Malchow
Hi,

To make it easier to understand what the situation is, it would help to
see your bridging configuration and your interface configration.

Something like:

# ip addr

And

# brctl show

Regards
Soeren

On 06/07/15 13:30, users-boun...@ovirt.org on behalf of Dan Kenigsberg
users-boun...@ovirt.org on behalf of dan...@redhat.com wrote:

On Tue, Jun 30, 2015 at 03:48:49PM -0500, Julián Tete wrote:
 Hi Friends of oVirt
 
 I'm trying to migrate my company from VMware to oVirt.

We'd like to help you do this!

 In my final tests, I set up 2 more VLANs in oVirt, (VM VLANs)
 The Virtual Machines in these VLANs, can be reached from the external
IPs
 from the net range,
 but from the Virtual machines only can ping the Host with the Bridge and
 itself, can't reach the gateway. ¿?
 
 I configured a IP Forwarding in the Host with the virtual machine, and
 nothing changes...
 
 Any idea ? This is the last duty before embrace oVirt in the company.
 
 Look to the VLAN 100 configuration (My desired VM Network):
 
 http://postimg.org/image/7hrog0a2n/
 
 http://postimg.org/image/68b40i1vr/
 
 http://postimg.org/image/lu6mlshgp/

I must admit that I don't understand your problem yet. When you ping
from inside your guest, where are your packets dropped?

I'd like to point that your Hosting network, as most VM networks, is
better off left without an IP address. The benefit of this is better
security (host TCP stack is not accessible from VMs) and less chances of
routing collisions from the host.

So unless you need to use the same network for something other than VM
communication, try to clear its address.

Regards,
Dan.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway

2015-07-06 Thread Julián Tete
Hi Friends of oVirt

This the data required:

I have a HP Enclosure with a HP SAN.
I can't change the net settings in the switch because we have VMware
Virtual Machines in production in the same enclosure.
The switch is in Trunk Mode and all the traffic are in Tagged VLAN's with
ID's: 1,50,90,91 and 100.
I can play with 6 blades.
I in the first Blade I installed oVirt in hosted engine mode.
The only S.O is CentOS 7.1

I used inxi to brig the data for you:

My First Host is the only host until now (SPM) is the first data domain
(NFS) and contains the hosted engine machine.
I installed oVirt with ovirtmgmt in VLAN 1, over the interface eno1,
without any VLAN Tagged configuration.

This the data for my first host:

http://pastebin.com/dfC0XTQM

This the data for the Engine:

http://pastebin.com/JdrMSbj0

This the data for the Virtual Machine created in VLAN 50:

S.O : CentOS 7.1
SELinux: Permissive
IP ADDRESS: 192.168.50.8
PREFIX: 27
GATEWAY: 192.168.50.1
Interface: eth0

The Virtual Machine hasn´t any VLAN configuration.

In the 3 S.O, Network Manager is stopped and disabled, connectivity is
managed by the network daemon.

This is the data for the Networking in the admin interface:

http://postimg.org/image/lbypejxrh/

http://postimg.org/image/jtkyhqs8f/

http://postimg.org/image/7dwf1nb9f/

http://postimg.org/image/6i9t75g33/

http://postimg.org/image/sm8e6lecv/

http://postimg.org/image/cvig7rjuv/

http://postimg.org/image/fxcthsrtl/

http://postimg.org/image/o6xjwwvyz/

http://postimg.org/image/pv5ar5v3j/

http://postimg.org/image/dx8br0gq7/

http://postimg.org/image/baixp4b0j/

This the case

With No IP in the VLAN, and IP in the Virtual Machine, From the Virtual
Machine can ping myself (192.168.50.8) but I can't reach the gateway, can't
reach the host, can't reach Internet.

Any help is appreciated

Thanks Friends of oVirt








2015-07-06 7:51 GMT-05:00 Soeren Malchow soeren.malc...@mcon.net:

 Hi,

 To make it easier to understand what the situation is, it would help to
 see your bridging configuration and your interface configration.

 Something like:

 # ip addr

 And

 # brctl show

 Regards
 Soeren

 On 06/07/15 13:30, users-boun...@ovirt.org on behalf of Dan Kenigsberg
 users-boun...@ovirt.org on behalf of dan...@redhat.com wrote:

 On Tue, Jun 30, 2015 at 03:48:49PM -0500, Julián Tete wrote:
  Hi Friends of oVirt
 
  I'm trying to migrate my company from VMware to oVirt.
 
 We'd like to help you do this!
 
  In my final tests, I set up 2 more VLANs in oVirt, (VM VLANs)
  The Virtual Machines in these VLANs, can be reached from the external
 IPs
  from the net range,
  but from the Virtual machines only can ping the Host with the Bridge and
  itself, can't reach the gateway. ¿?
 
  I configured a IP Forwarding in the Host with the virtual machine, and
  nothing changes...
 
  Any idea ? This is the last duty before embrace oVirt in the company.
 
  Look to the VLAN 100 configuration (My desired VM Network):
 
  http://postimg.org/image/7hrog0a2n/
 
  http://postimg.org/image/68b40i1vr/
 
  http://postimg.org/image/lu6mlshgp/
 
 I must admit that I don't understand your problem yet. When you ping
 from inside your guest, where are your packets dropped?
 
 I'd like to point that your Hosting network, as most VM networks, is
 better off left without an IP address. The benefit of this is better
 security (host TCP stack is not accessible from VMs) and less chances of
 routing collisions from the host.
 
 So unless you need to use the same network for something other than VM
 communication, try to clear its address.
 
 Regards,
 Dan.
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway

2015-07-06 Thread Jeff Bailey
I see the tap interface on the ovirtmgmt bridge which is in the 
192.168.0.0/24 subnet but your vm has a 192.168.50.0/27 address.  I 
don't know why it's attached to that bridge though since it looks like 
you've placed it on the dmz network.  What happens if you change the IP 
address in your test vm to something in 192.168.0.0/24 and then ping 
your 192.168.0.1 gateway?


On 7/6/2015 1:06 PM, Julián Tete wrote:

Hi Friends of oVirt

This the data required:

I have a HP Enclosure with a HP SAN.
I can't change the net settings in the switch because we have VMware 
Virtual Machines in production in the same enclosure.
The switch is in Trunk Mode and all the traffic are in Tagged VLAN's 
with ID's: 1,50,90,91 and 100.

I can play with 6 blades.
I in the first Blade I installed oVirt in hosted engine mode.
The only S.O is CentOS 7.1

I used inxi to brig the data for you:

My First Host is the only host until now (SPM) is the first data 
domain (NFS) and contains the hosted engine machine.
I installed oVirt with ovirtmgmt in VLAN 1, over the interface eno1, 
without any VLAN Tagged configuration.


This the data for my first host:

http://pastebin.com/dfC0XTQM

This the data for the Engine:

http://pastebin.com/JdrMSbj0

This the data for the Virtual Machine created in VLAN 50:

S.O : CentOS 7.1
SELinux: Permissive
IP ADDRESS: 192.168.50.8
PREFIX: 27
GATEWAY: 192.168.50.1
Interface: eth0

The Virtual Machine hasn´t any VLAN configuration.

In the 3 S.O, Network Manager is stopped and disabled, connectivity is 
managed by the network daemon.


This is the data for the Networking in the admin interface:

http://postimg.org/image/lbypejxrh/

http://postimg.org/image/jtkyhqs8f/

http://postimg.org/image/7dwf1nb9f/

http://postimg.org/image/6i9t75g33/

http://postimg.org/image/sm8e6lecv/

http://postimg.org/image/cvig7rjuv/

http://postimg.org/image/fxcthsrtl/

http://postimg.org/image/o6xjwwvyz/

http://postimg.org/image/pv5ar5v3j/

http://postimg.org/image/dx8br0gq7/

http://postimg.org/image/baixp4b0j/

This the case

With No IP in the VLAN, and IP in the Virtual Machine, From the 
Virtual Machine can ping myself (192.168.50.8) but I can't reach the 
gateway, can't reach the host, can't reach Internet.


Any help is appreciated

Thanks Friends of oVirt








2015-07-06 7:51 GMT-05:00 Soeren Malchow soeren.malc...@mcon.net 
mailto:soeren.malc...@mcon.net:


Hi,

To make it easier to understand what the situation is, it would
help to
see your bridging configuration and your interface configration.

Something like:

# ip addr

And

# brctl show

Regards
Soeren

On 06/07/15 13:30, users-boun...@ovirt.org
mailto:users-boun...@ovirt.org on behalf of Dan Kenigsberg
users-boun...@ovirt.org mailto:users-boun...@ovirt.org on
behalf of dan...@redhat.com mailto:dan...@redhat.com wrote:

On Tue, Jun 30, 2015 at 03:48:49PM -0500, Julián Tete wrote:
 Hi Friends of oVirt

 I'm trying to migrate my company from VMware to oVirt.

We'd like to help you do this!

 In my final tests, I set up 2 more VLANs in oVirt, (VM VLANs)
 The Virtual Machines in these VLANs, can be reached from the
external
IPs
 from the net range,
 but from the Virtual machines only can ping the Host with the
Bridge and
 itself, can't reach the gateway. ¿?

 I configured a IP Forwarding in the Host with the virtual
machine, and
 nothing changes...

 Any idea ? This is the last duty before embrace oVirt in the
company.

 Look to the VLAN 100 configuration (My desired VM Network):

 http://postimg.org/image/7hrog0a2n/

 http://postimg.org/image/68b40i1vr/

 http://postimg.org/image/lu6mlshgp/

I must admit that I don't understand your problem yet. When you ping
from inside your guest, where are your packets dropped?

I'd like to point that your Hosting network, as most VM
networks, is
better off left without an IP address. The benefit of this is better
security (host TCP stack is not accessible from VMs) and less
chances of
routing collisions from the host.

So unless you need to use the same network for something other
than VM
communication, try to clear its address.

Regards,
Dan.
___
Users mailing list
Users@ovirt.org mailto:Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway

2015-07-02 Thread Julián Tete
I tried a different Aproach:

One VLAN for each NIC

I tried but not works I left the Virtual Machine pinging the Gateway
after 10 minutes I left my Worstation alone and I went back to my home.
Today i see the ping working (¿?) Maybe I rush too much...or maybe not.

I reboot the Virtual Machine, same problem: after 15 minutes the Machine
can't reach the Gateway, we need HA and 10+ minutes it's not considerated.

After a I mess my oVirt LAB, after trying everything.

This my last working setup with sloow reaching of Gateway:

DATA CENTERS

Logical Networks:
---
Name: ovirtmgmt
Description: Management Network
Network Label: 1
MTU: Default
---
Name: dmz
Description: VLAN 50
Network Label: 50
Enable VLAN tagging: 50
VM network
MTU: Default
---
Name: Hosting
Description: VLAN 100
Network Label: 100
Enable VLAN tagging: 100
VM network
MTU: Default


CLUSTERS

Logical Networks

ovirtmgmt Assign Required Display Network Migration Network
dmz Assign
HostingAssign Required

HOSTS

Name: srvovirt02.cnsc.net
Hostname/IP: 192.168.0.63

Network Interfaces

HOSTS BOND  VLANNETWORK NAMEADDRESS
MAC   SPEED(Mbps)RX(Mbps)   TX(Mbps)

eno1 * ovirtmgmt
192.168.0.63   00:17:a4:77:00:18 1 
11

eno2eno2.50 (50)  dmz
192.168.50.8  00:17:a4:77:00:1a 1  
11

ens1f0 ens1f0.100 (100)Hosting
192.168.100.700:17:a4:77:00:1c  1  
11

ens1f1
00:17:a4:77:00:1e 0  11

Setup Hosts Networks

Network: ovirtmgmt
Static
IP: 192.168.0.63
Subnet Mask: 255.255.255.0
Gateway: 192.168.0.1
Custom Properties: No available keys
Sync network: Yes

Network: dmz
Static
IP: 192.168.50.8
Subnet Mask: 255.255.255.224
Gateway: 192.168.50.1
Custom Properties: Please select a key...

Network: Hosting
Static
IP: 192.168.100.7
Subnet Mask: 255.255.255.240
Gateway: 192.168.100.1
Custom Properties: Please select a key...

Virtual Machines

Name: PruebaVLAN
Host: srvovirt02.cnsc.net

Edit Network Interface

Name: nic1
Profile: dmz/dmz
Type: VirtIO
Custom MAC address: 00:00:1a:4a:3e:00
Link State: Up
Card Status: Plugged

Network Interfaces in the Host srvovirt02.cnsc.net:

1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: eno1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq master
ovirtmgmt state UP qlen 1000
link/ether 00:17:a4:77:00:18 brd ff:ff:ff:ff:ff:ff
inet6 fe80::217:a4ff:fe77:18/64 scope link
   valid_lft forever preferred_lft forever
3: eno2: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP qlen
1000
link/ether 00:17:a4:77:00:1a brd ff:ff:ff:ff:ff:ff
inet6 fe80::217:a4ff:fe77:1a/64 scope link
   valid_lft forever preferred_lft forever
4: ens1f0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP
qlen 1000
link/ether 00:17:a4:77:00:1c brd ff:ff:ff:ff:ff:ff
inet6 fe80::217:a4ff:fe77:1c/64 scope link
   valid_lft forever preferred_lft forever
5: ens1f1: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:17:a4:77:00:1e brd ff:ff:ff:ff:ff:ff
6: bond0: BROADCAST,MULTICAST,MASTER mtu 1500 qdisc noop state DOWN
link/ether 72:f8:9c:75:e3:86 brd ff:ff:ff:ff:ff:ff
7: ;vdsmdummy;: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
10: vnet0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast
master dmz state UNKNOWN qlen 500
link/ether fe:00:1a:4a:3e:00 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc00:1aff:fe4a:3e00/64 scope link
   valid_lft forever preferred_lft forever
17: eno2.50@eno2: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue
master dmz state UP
link/ether 00:17:a4:77:00:1a brd ff:ff:ff:ff:ff:ff
inet6 fe80::217:a4ff:fe77:1a/64 scope link
   valid_lft forever preferred_lft forever
18: dmz: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UP
link/ether 00:17:a4:77:00:1a brd ff:ff:ff:ff:ff:ff
inet 192.168.50.8/27 brd 192.168.50.31 scope global dmz
   valid_lft forever preferred_lft forever
inet6 fe80::217:a4ff:fe77:1a/64 scope link
   valid_lft forever preferred_lft forever
19: ens1f0.100@ens1f0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc
noqueue master Hosting state UP
link/ether 00:17:a4:77:00:1c brd ff:ff:ff:ff:ff:ff
inet6 fe80::217:a4ff:fe77:1c/64 scope link
   valid_lft forever preferred_lft forever
20: Hosting: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state
UP
link/ether 00:17:a4:77:00:1c brd ff:ff:ff:ff:ff:ff
inet 

Re: [ovirt-users] Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway

2015-07-02 Thread Donny Davis
Something isn't right. Are you using centos 7 for hosts or the node ISO. I
just setup Vlans and it works just fine on my end.

Try setting the switch ports to access mode with your Vlans, remove the
tagging from ovirt and see if it works.

I know that isn't how you want to set things up, but we need to start
isolating things... Is it just the gateway Can you ping other machines
on different subnets... What about pinging google
On Jul 2, 2015 5:51 PM, Julián Tete danteconra...@gmail.com wrote:

 Don't work :'(

 I'm going to try this:




 *https://bugzilla.redhat.com/show_bug.cgi?id=1072027
 https://bugzilla.redhat.com/show_bug.cgi?id=1072027https://bugzilla.redhat.com/show_bug.cgi?id=1072027
 https://bugzilla.redhat.com/show_bug.cgi?id=1072027*

 2015-07-02 11:40 GMT-05:00 Julián Tete danteconra...@gmail.com:

 I'm going to erase everything and the try this:

 http://www.ovirt.org/QA:TestCase_Hosted_Engine_Tagged_VLAN_Support

 2015-07-02 10:41 GMT-05:00 Julián Tete danteconra...@gmail.com:

 I tried a different Aproach:

 One VLAN for each NIC

 I tried but not works I left the Virtual Machine pinging the Gateway
 after 10 minutes I left my Worstation alone and I went back to my home.
 Today i see the ping working (¿?) Maybe I rush too much...or maybe not.

 I reboot the Virtual Machine, same problem: after 15 minutes the Machine
 can't reach the Gateway, we need HA and 10+ minutes it's not considerated.

 After a I mess my oVirt LAB, after trying everything.

 This my last working setup with sloow reaching of Gateway:

 DATA CENTERS

 Logical Networks:
 ---
 Name: ovirtmgmt
 Description: Management Network
 Network Label: 1
 MTU: Default
 ---
 Name: dmz
 Description: VLAN 50
 Network Label: 50
 Enable VLAN tagging: 50
 VM network
 MTU: Default
 ---
 Name: Hosting
 Description: VLAN 100
 Network Label: 100
 Enable VLAN tagging: 100
 VM network
 MTU: Default
 

 CLUSTERS

 Logical Networks

 ovirtmgmt Assign Required Display Network Migration Network
 dmz Assign
 HostingAssign Required

 HOSTS

 Name: srvovirt02.cnsc.net
 Hostname/IP: 192.168.0.63

 Network Interfaces

 HOSTS BOND  VLANNETWORK NAMEADDRESS
 MAC   SPEED(Mbps)RX(Mbps)   TX(Mbps)

 eno1 * ovirtmgmt
 192.168.0.63   00:17:a4:77:00:18 1 
 11

 eno2eno2.50 (50)  dmz
 192.168.50.8  00:17:a4:77:00:1a 1  
 11

 ens1f0 ens1f0.100 (100)Hosting
 192.168.100.700:17:a4:77:00:1c  1  
 11

 ens1f1
 00:17:a4:77:00:1e 0  11

 Setup Hosts Networks

 Network: ovirtmgmt
 Static
 IP: 192.168.0.63
 Subnet Mask: 255.255.255.0
 Gateway: 192.168.0.1
 Custom Properties: No available keys
 Sync network: Yes

 Network: dmz
 Static
 IP: 192.168.50.8
 Subnet Mask: 255.255.255.224
 Gateway: 192.168.50.1
 Custom Properties: Please select a key...

 Network: Hosting
 Static
 IP: 192.168.100.7
 Subnet Mask: 255.255.255.240
 Gateway: 192.168.100.1
 Custom Properties: Please select a key...

 Virtual Machines

 Name: PruebaVLAN
 Host: srvovirt02.cnsc.net

 Edit Network Interface

 Name: nic1
 Profile: dmz/dmz
 Type: VirtIO
 Custom MAC address: 00:00:1a:4a:3e:00
 Link State: Up
 Card Status: Plugged

 Network Interfaces in the Host srvovirt02.cnsc.net:

 1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN
 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
 inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
 inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
 2: eno1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq master
 ovirtmgmt state UP qlen 1000
 link/ether 00:17:a4:77:00:18 brd ff:ff:ff:ff:ff:ff
 inet6 fe80::217:a4ff:fe77:18/64 scope link
valid_lft forever preferred_lft forever
 3: eno2: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP
 qlen 1000
 link/ether 00:17:a4:77:00:1a brd ff:ff:ff:ff:ff:ff
 inet6 fe80::217:a4ff:fe77:1a/64 scope link
valid_lft forever preferred_lft forever
 4: ens1f0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP
 qlen 1000
 link/ether 00:17:a4:77:00:1c brd ff:ff:ff:ff:ff:ff
 inet6 fe80::217:a4ff:fe77:1c/64 scope link
valid_lft forever preferred_lft forever
 5: ens1f1: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN qlen 1000
 link/ether 00:17:a4:77:00:1e brd ff:ff:ff:ff:ff:ff
 6: bond0: BROADCAST,MULTICAST,MASTER mtu 1500 qdisc noop state DOWN
 link/ether 72:f8:9c:75:e3:86 brd ff:ff:ff:ff:ff:ff
 7: ;vdsmdummy;: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN
 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
 10: vnet0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast
 master dmz state 

Re: [ovirt-users] Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway

2015-07-02 Thread Julián Tete
I'm going to erase everything and the try this:

http://www.ovirt.org/QA:TestCase_Hosted_Engine_Tagged_VLAN_Support

2015-07-02 10:41 GMT-05:00 Julián Tete danteconra...@gmail.com:

 I tried a different Aproach:

 One VLAN for each NIC

 I tried but not works I left the Virtual Machine pinging the Gateway
 after 10 minutes I left my Worstation alone and I went back to my home.
 Today i see the ping working (¿?) Maybe I rush too much...or maybe not.

 I reboot the Virtual Machine, same problem: after 15 minutes the Machine
 can't reach the Gateway, we need HA and 10+ minutes it's not considerated.

 After a I mess my oVirt LAB, after trying everything.

 This my last working setup with sloow reaching of Gateway:

 DATA CENTERS

 Logical Networks:
 ---
 Name: ovirtmgmt
 Description: Management Network
 Network Label: 1
 MTU: Default
 ---
 Name: dmz
 Description: VLAN 50
 Network Label: 50
 Enable VLAN tagging: 50
 VM network
 MTU: Default
 ---
 Name: Hosting
 Description: VLAN 100
 Network Label: 100
 Enable VLAN tagging: 100
 VM network
 MTU: Default
 

 CLUSTERS

 Logical Networks

 ovirtmgmt Assign Required Display Network Migration Network
 dmz Assign
 HostingAssign Required

 HOSTS

 Name: srvovirt02.cnsc.net
 Hostname/IP: 192.168.0.63

 Network Interfaces

 HOSTS BOND  VLANNETWORK NAMEADDRESS
 MAC   SPEED(Mbps)RX(Mbps)   TX(Mbps)

 eno1 * ovirtmgmt
 192.168.0.63   00:17:a4:77:00:18 1 
 11

 eno2eno2.50 (50)  dmz
 192.168.50.8  00:17:a4:77:00:1a 1  
 11

 ens1f0 ens1f0.100 (100)Hosting
 192.168.100.700:17:a4:77:00:1c  1  
 11

 ens1f1
 00:17:a4:77:00:1e 0  11

 Setup Hosts Networks

 Network: ovirtmgmt
 Static
 IP: 192.168.0.63
 Subnet Mask: 255.255.255.0
 Gateway: 192.168.0.1
 Custom Properties: No available keys
 Sync network: Yes

 Network: dmz
 Static
 IP: 192.168.50.8
 Subnet Mask: 255.255.255.224
 Gateway: 192.168.50.1
 Custom Properties: Please select a key...

 Network: Hosting
 Static
 IP: 192.168.100.7
 Subnet Mask: 255.255.255.240
 Gateway: 192.168.100.1
 Custom Properties: Please select a key...

 Virtual Machines

 Name: PruebaVLAN
 Host: srvovirt02.cnsc.net

 Edit Network Interface

 Name: nic1
 Profile: dmz/dmz
 Type: VirtIO
 Custom MAC address: 00:00:1a:4a:3e:00
 Link State: Up
 Card Status: Plugged

 Network Interfaces in the Host srvovirt02.cnsc.net:

 1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN
 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
 inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
 inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
 2: eno1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq master
 ovirtmgmt state UP qlen 1000
 link/ether 00:17:a4:77:00:18 brd ff:ff:ff:ff:ff:ff
 inet6 fe80::217:a4ff:fe77:18/64 scope link
valid_lft forever preferred_lft forever
 3: eno2: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP qlen
 1000
 link/ether 00:17:a4:77:00:1a brd ff:ff:ff:ff:ff:ff
 inet6 fe80::217:a4ff:fe77:1a/64 scope link
valid_lft forever preferred_lft forever
 4: ens1f0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP
 qlen 1000
 link/ether 00:17:a4:77:00:1c brd ff:ff:ff:ff:ff:ff
 inet6 fe80::217:a4ff:fe77:1c/64 scope link
valid_lft forever preferred_lft forever
 5: ens1f1: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN qlen 1000
 link/ether 00:17:a4:77:00:1e brd ff:ff:ff:ff:ff:ff
 6: bond0: BROADCAST,MULTICAST,MASTER mtu 1500 qdisc noop state DOWN
 link/ether 72:f8:9c:75:e3:86 brd ff:ff:ff:ff:ff:ff
 7: ;vdsmdummy;: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN
 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
 10: vnet0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast
 master dmz state UNKNOWN qlen 500
 link/ether fe:00:1a:4a:3e:00 brd ff:ff:ff:ff:ff:ff
 inet6 fe80::fc00:1aff:fe4a:3e00/64 scope link
valid_lft forever preferred_lft forever
 17: eno2.50@eno2: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc
 noqueue master dmz state UP
 link/ether 00:17:a4:77:00:1a brd ff:ff:ff:ff:ff:ff
 inet6 fe80::217:a4ff:fe77:1a/64 scope link
valid_lft forever preferred_lft forever
 18: dmz: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UP
 link/ether 00:17:a4:77:00:1a brd ff:ff:ff:ff:ff:ff
 inet 192.168.50.8/27 brd 192.168.50.31 scope global dmz
valid_lft forever preferred_lft forever
 inet6 fe80::217:a4ff:fe77:1a/64 scope link
valid_lft forever preferred_lft forever
 19: ens1f0.100@ens1f0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc
 noqueue master 

Re: [ovirt-users] Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway

2015-07-02 Thread Julián Tete
Don't work :'(

I'm going to try this:




*https://bugzilla.redhat.com/show_bug.cgi?id=1072027
https://bugzilla.redhat.com/show_bug.cgi?id=1072027https://bugzilla.redhat.com/show_bug.cgi?id=1072027
https://bugzilla.redhat.com/show_bug.cgi?id=1072027*

2015-07-02 11:40 GMT-05:00 Julián Tete danteconra...@gmail.com:

 I'm going to erase everything and the try this:

 http://www.ovirt.org/QA:TestCase_Hosted_Engine_Tagged_VLAN_Support

 2015-07-02 10:41 GMT-05:00 Julián Tete danteconra...@gmail.com:

 I tried a different Aproach:

 One VLAN for each NIC

 I tried but not works I left the Virtual Machine pinging the Gateway
 after 10 minutes I left my Worstation alone and I went back to my home.
 Today i see the ping working (¿?) Maybe I rush too much...or maybe not.

 I reboot the Virtual Machine, same problem: after 15 minutes the Machine
 can't reach the Gateway, we need HA and 10+ minutes it's not considerated.

 After a I mess my oVirt LAB, after trying everything.

 This my last working setup with sloow reaching of Gateway:

 DATA CENTERS

 Logical Networks:
 ---
 Name: ovirtmgmt
 Description: Management Network
 Network Label: 1
 MTU: Default
 ---
 Name: dmz
 Description: VLAN 50
 Network Label: 50
 Enable VLAN tagging: 50
 VM network
 MTU: Default
 ---
 Name: Hosting
 Description: VLAN 100
 Network Label: 100
 Enable VLAN tagging: 100
 VM network
 MTU: Default
 

 CLUSTERS

 Logical Networks

 ovirtmgmt Assign Required Display Network Migration Network
 dmz Assign
 HostingAssign Required

 HOSTS

 Name: srvovirt02.cnsc.net
 Hostname/IP: 192.168.0.63

 Network Interfaces

 HOSTS BOND  VLANNETWORK NAMEADDRESS
 MAC   SPEED(Mbps)RX(Mbps)   TX(Mbps)

 eno1 * ovirtmgmt
 192.168.0.63   00:17:a4:77:00:18 1 
 11

 eno2eno2.50 (50)  dmz
 192.168.50.8  00:17:a4:77:00:1a 1  
 11

 ens1f0 ens1f0.100 (100)Hosting
 192.168.100.700:17:a4:77:00:1c  1  
 11

 ens1f1
 00:17:a4:77:00:1e 0  11

 Setup Hosts Networks

 Network: ovirtmgmt
 Static
 IP: 192.168.0.63
 Subnet Mask: 255.255.255.0
 Gateway: 192.168.0.1
 Custom Properties: No available keys
 Sync network: Yes

 Network: dmz
 Static
 IP: 192.168.50.8
 Subnet Mask: 255.255.255.224
 Gateway: 192.168.50.1
 Custom Properties: Please select a key...

 Network: Hosting
 Static
 IP: 192.168.100.7
 Subnet Mask: 255.255.255.240
 Gateway: 192.168.100.1
 Custom Properties: Please select a key...

 Virtual Machines

 Name: PruebaVLAN
 Host: srvovirt02.cnsc.net

 Edit Network Interface

 Name: nic1
 Profile: dmz/dmz
 Type: VirtIO
 Custom MAC address: 00:00:1a:4a:3e:00
 Link State: Up
 Card Status: Plugged

 Network Interfaces in the Host srvovirt02.cnsc.net:

 1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN
 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
 inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
 inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
 2: eno1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq master
 ovirtmgmt state UP qlen 1000
 link/ether 00:17:a4:77:00:18 brd ff:ff:ff:ff:ff:ff
 inet6 fe80::217:a4ff:fe77:18/64 scope link
valid_lft forever preferred_lft forever
 3: eno2: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP
 qlen 1000
 link/ether 00:17:a4:77:00:1a brd ff:ff:ff:ff:ff:ff
 inet6 fe80::217:a4ff:fe77:1a/64 scope link
valid_lft forever preferred_lft forever
 4: ens1f0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP
 qlen 1000
 link/ether 00:17:a4:77:00:1c brd ff:ff:ff:ff:ff:ff
 inet6 fe80::217:a4ff:fe77:1c/64 scope link
valid_lft forever preferred_lft forever
 5: ens1f1: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN qlen 1000
 link/ether 00:17:a4:77:00:1e brd ff:ff:ff:ff:ff:ff
 6: bond0: BROADCAST,MULTICAST,MASTER mtu 1500 qdisc noop state DOWN
 link/ether 72:f8:9c:75:e3:86 brd ff:ff:ff:ff:ff:ff
 7: ;vdsmdummy;: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN
 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
 10: vnet0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast
 master dmz state UNKNOWN qlen 500
 link/ether fe:00:1a:4a:3e:00 brd ff:ff:ff:ff:ff:ff
 inet6 fe80::fc00:1aff:fe4a:3e00/64 scope link
valid_lft forever preferred_lft forever
 17: eno2.50@eno2: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc
 noqueue master dmz state UP
 link/ether 00:17:a4:77:00:1a brd ff:ff:ff:ff:ff:ff
 inet6 fe80::217:a4ff:fe77:1a/64 scope link
valid_lft forever preferred_lft forever
 18: dmz: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UP
 link/ether 

Re: [ovirt-users] Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway

2015-06-30 Thread Donny Davis
Are you configuring the vms interface with the vlan or tagging at the host.
On Jun 30, 2015 7:28 PM, Julián Tete danteconra...@gmail.com wrote:

 Hi Donny

 We have HP Switches (HP 5406zl) and they are configurated on trunk mode.
 (VMware is configurated to use that).

 Any suggestion ?

 Thanks for your response.

 :)

 2015-06-30 17:51 GMT-05:00 Donny Davis do...@cloudspin.me:

 Vlans are layer 2, sounds like a tagging problem. Cisco switches? The tag
 sticks to the host bridge, but is being stripped off when it leaves the
 host Is your switch in access mode or trunk?
 Hi Friends of oVirt

 I'm trying to migrate my company from VMware to oVirt.
 In my final tests, I set up 2 more VLANs in oVirt, (VM VLANs)
 The Virtual Machines in these VLANs, can be reached from the external IPs
 from the net range,
 but from the Virtual machines only can ping the Host with the Bridge and
 itself, can't reach the gateway. ¿?

 I configured a IP Forwarding in the Host with the virtual machine, and
 nothing changes...

 Any idea ? This is the last duty before embrace oVirt in the company.

 Look to the VLAN 100 configuration (My desired VM Network):

 http://postimg.org/image/7hrog0a2n/

 http://postimg.org/image/68b40i1vr/

 http://postimg.org/image/lu6mlshgp/

 http://postimg.org/image/540o1qc0t/

 http://postimg.org/image/4kyg787bt/

 http://postimg.org/image/v7ralh7zb/

 http://postimg.org/image/kn903cl03/

 For any idea, thanks in advance

 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway

2015-06-30 Thread Donny Davis
Does your switch have an IP on that vlan... I would step things out
VMhostswitchrtr

You have already confirmed VM to host.

I'm going to look at your screens again to make sure I didn't miss anything
On Jun 30, 2015 9:42 PM, Julián Tete danteconra...@gmail.com wrote:

 Thanks for the explanation :)

 I set everything of the VLANs at oVirt, After I put a IP on the Virtual
 Machine. But the Virtual Machine can't reach the gateway, The host can do.
 The Virtual Machine only can reach the host. All the machines of the range
 of net can reach the Virtual Machine.

 2015-06-30 20:36 GMT-05:00 Donny Davis do...@cloudspin.me:

 I'm asking if your setting the vlan on the VM or at ovirt.

 More than likely if you are coming from VMware you have the Vlans set at
 the hypervisor. This does work in ovirt, I am doing it right now
 On Jun 30, 2015 9:31 PM, Julián Tete danteconra...@gmail.com wrote:

 Mmmm I'm new in oVirt :(

 VMs Interface is Virtual MachineS Interface or VM Network Interface in
 the host ?

 I configured the IP of the VLAN in the host.

 I double check: the NIC of the Host has the VLAN assigned.

 Can you help me ?

 2015-06-30 20:11 GMT-05:00 Donny Davis do...@cloudspin.me:

 Are you configuring the vms interface with the vlan or tagging at the
 host.
 On Jun 30, 2015 7:28 PM, Julián Tete danteconra...@gmail.com wrote:

 Hi Donny

 We have HP Switches (HP 5406zl) and they are configurated on trunk
 mode. (VMware is configurated to use that).

 Any suggestion ?

 Thanks for your response.

 :)

 2015-06-30 17:51 GMT-05:00 Donny Davis do...@cloudspin.me:

 Vlans are layer 2, sounds like a tagging problem. Cisco switches? The
 tag sticks to the host bridge, but is being stripped off when it leaves 
 the
 host Is your switch in access mode or trunk?
 Hi Friends of oVirt

 I'm trying to migrate my company from VMware to oVirt.
 In my final tests, I set up 2 more VLANs in oVirt, (VM VLANs)
 The Virtual Machines in these VLANs, can be reached from the external
 IPs from the net range,
 but from the Virtual machines only can ping the Host with the Bridge
 and itself, can't reach the gateway. ¿?

 I configured a IP Forwarding in the Host with the virtual machine,
 and nothing changes...

 Any idea ? This is the last duty before embrace oVirt in the company.

 Look to the VLAN 100 configuration (My desired VM Network):

 http://postimg.org/image/7hrog0a2n/

 http://postimg.org/image/68b40i1vr/

 http://postimg.org/image/lu6mlshgp/

 http://postimg.org/image/540o1qc0t/

 http://postimg.org/image/4kyg787bt/

 http://postimg.org/image/v7ralh7zb/

 http://postimg.org/image/kn903cl03/

 For any idea, thanks in advance

 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users





___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway

2015-06-30 Thread Donny Davis
How is your mgmt network working... You have no vlan tag on it If your
switch port is setup for trunk mode?

I have a Cisco switch that when in trunk mode will not pass untagged
traffic.
The mgmt network and hosting network are on the same interface.
One tagged one not

I would try putting a machine on the mgmt network and see if traffic flows
as it should. This is not outside ovirt capability set, we just have to
narrow down where traffic is not flowing
:)

Up until about 3 months ago I used ovirt to host a public IaaS, included in
my setup was several vlan tagged networks. The community is for help,
welcome to open source.

Donny D
On Jun 30, 2015 9:46 PM, Donny Davis do...@cloudspin.me wrote:

 Does your switch have an IP on that vlan... I would step things out
 VMhostswitchrtr

 You have already confirmed VM to host.

 I'm going to look at your screens again to make sure I didn't miss anything
 On Jun 30, 2015 9:42 PM, Julián Tete danteconra...@gmail.com wrote:

 Thanks for the explanation :)

 I set everything of the VLANs at oVirt, After I put a IP on the Virtual
 Machine. But the Virtual Machine can't reach the gateway, The host can do.
 The Virtual Machine only can reach the host. All the machines of the range
 of net can reach the Virtual Machine.

 2015-06-30 20:36 GMT-05:00 Donny Davis do...@cloudspin.me:

 I'm asking if your setting the vlan on the VM or at ovirt.

 More than likely if you are coming from VMware you have the Vlans set at
 the hypervisor. This does work in ovirt, I am doing it right now
 On Jun 30, 2015 9:31 PM, Julián Tete danteconra...@gmail.com wrote:

 Mmmm I'm new in oVirt :(

 VMs Interface is Virtual MachineS Interface or VM Network Interface in
 the host ?

 I configured the IP of the VLAN in the host.

 I double check: the NIC of the Host has the VLAN assigned.

 Can you help me ?

 2015-06-30 20:11 GMT-05:00 Donny Davis do...@cloudspin.me:

 Are you configuring the vms interface with the vlan or tagging at the
 host.
 On Jun 30, 2015 7:28 PM, Julián Tete danteconra...@gmail.com
 wrote:

 Hi Donny

 We have HP Switches (HP 5406zl) and they are configurated on trunk
 mode. (VMware is configurated to use that).

 Any suggestion ?

 Thanks for your response.

 :)

 2015-06-30 17:51 GMT-05:00 Donny Davis do...@cloudspin.me:

 Vlans are layer 2, sounds like a tagging problem. Cisco switches?
 The tag sticks to the host bridge, but is being stripped off when it 
 leaves
 the host Is your switch in access mode or trunk?
 Hi Friends of oVirt

 I'm trying to migrate my company from VMware to oVirt.
 In my final tests, I set up 2 more VLANs in oVirt, (VM VLANs)
 The Virtual Machines in these VLANs, can be reached from the
 external IPs from the net range,
 but from the Virtual machines only can ping the Host with the Bridge
 and itself, can't reach the gateway. ¿?

 I configured a IP Forwarding in the Host with the virtual machine,
 and nothing changes...

 Any idea ? This is the last duty before embrace oVirt in the company.

 Look to the VLAN 100 configuration (My desired VM Network):

 http://postimg.org/image/7hrog0a2n/

 http://postimg.org/image/68b40i1vr/

 http://postimg.org/image/lu6mlshgp/

 http://postimg.org/image/540o1qc0t/

 http://postimg.org/image/4kyg787bt/

 http://postimg.org/image/v7ralh7zb/

 http://postimg.org/image/kn903cl03/

 For any idea, thanks in advance

 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users





___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway

2015-06-30 Thread Julián Tete
Hi Friends of oVirt

I'm trying to migrate my company from VMware to oVirt.
In my final tests, I set up 2 more VLANs in oVirt, (VM VLANs)
The Virtual Machines in these VLANs, can be reached from the external IPs
from the net range,
but from the Virtual machines only can ping the Host with the Bridge and
itself, can't reach the gateway. ¿?

I configured a IP Forwarding in the Host with the virtual machine, and
nothing changes...

Any idea ? This is the last duty before embrace oVirt in the company.

Look to the VLAN 100 configuration (My desired VM Network):

http://postimg.org/image/7hrog0a2n/

http://postimg.org/image/68b40i1vr/

http://postimg.org/image/lu6mlshgp/

http://postimg.org/image/540o1qc0t/

http://postimg.org/image/4kyg787bt/

http://postimg.org/image/v7ralh7zb/

http://postimg.org/image/kn903cl03/

For any idea, thanks in advance
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway

2015-06-30 Thread Julián Tete
Hi Donny

We have HP Switches (HP 5406zl) and they are configurated on trunk mode.
(VMware is configurated to use that).

Any suggestion ?

Thanks for your response.

:)

2015-06-30 17:51 GMT-05:00 Donny Davis do...@cloudspin.me:

 Vlans are layer 2, sounds like a tagging problem. Cisco switches? The tag
 sticks to the host bridge, but is being stripped off when it leaves the
 host Is your switch in access mode or trunk?
 Hi Friends of oVirt

 I'm trying to migrate my company from VMware to oVirt.
 In my final tests, I set up 2 more VLANs in oVirt, (VM VLANs)
 The Virtual Machines in these VLANs, can be reached from the external IPs
 from the net range,
 but from the Virtual machines only can ping the Host with the Bridge and
 itself, can't reach the gateway. ¿?

 I configured a IP Forwarding in the Host with the virtual machine, and
 nothing changes...

 Any idea ? This is the last duty before embrace oVirt in the company.

 Look to the VLAN 100 configuration (My desired VM Network):

 http://postimg.org/image/7hrog0a2n/

 http://postimg.org/image/68b40i1vr/

 http://postimg.org/image/lu6mlshgp/

 http://postimg.org/image/540o1qc0t/

 http://postimg.org/image/4kyg787bt/

 http://postimg.org/image/v7ralh7zb/

 http://postimg.org/image/kn903cl03/

 For any idea, thanks in advance

 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway

2015-06-30 Thread Donny Davis
Vlans are layer 2, sounds like a tagging problem. Cisco switches? The tag
sticks to the host bridge, but is being stripped off when it leaves the
host Is your switch in access mode or trunk?
Hi Friends of oVirt

I'm trying to migrate my company from VMware to oVirt.
In my final tests, I set up 2 more VLANs in oVirt, (VM VLANs)
The Virtual Machines in these VLANs, can be reached from the external IPs
from the net range,
but from the Virtual machines only can ping the Host with the Bridge and
itself, can't reach the gateway. ¿?

I configured a IP Forwarding in the Host with the virtual machine, and
nothing changes...

Any idea ? This is the last duty before embrace oVirt in the company.

Look to the VLAN 100 configuration (My desired VM Network):

http://postimg.org/image/7hrog0a2n/

http://postimg.org/image/68b40i1vr/

http://postimg.org/image/lu6mlshgp/

http://postimg.org/image/540o1qc0t/

http://postimg.org/image/4kyg787bt/

http://postimg.org/image/v7ralh7zb/

http://postimg.org/image/kn903cl03/

For any idea, thanks in advance

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users