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 sloooooooooow 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
Hosting    Assign Required

HOSTS

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

Network Interfaces

HOSTS     BOND      VLAN            NETWORK NAME    ADDRESS
MAC                       SPEED(Mbps)    RX(Mbps)       TX(Mbps)

eno1                                             * ovirtmgmt
192.168.0.63           00:17:a4:77:00:18     10000                 <
1           < 1

eno2                eno2.50 (50)              dmz
192.168.50.8          00:17:a4:77:00:1a     10000                  <
1           < 1

ens1f0             ens1f0.100 (100)        Hosting
192.168.100.7        00:17:a4:77:00:1c      10000                  <
1           < 1

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

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 192.168.100.7/28 brd 192.168.100.15 scope global Hosting
       valid_lft forever preferred_lft forever
    inet6 fe80::217:a4ff:fe77:1c/64 scope link
       valid_lft forever preferred_lft forever
21: ovirtmgmt: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP
    link/ether 00:17:a4:77:00:18 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.63/24 brd 192.168.0.255 scope global ovirtmgmt
       valid_lft forever preferred_lft forever
    inet6 fe80::217:a4ff:fe77:18/64 scope link
       valid_lft forever preferred_lft forever

2015-06-30 21:34 GMT-05:00 Julián Tete <danteconra...@gmail.com>:

> You can count on it :)
>
> 2015-06-30 21:23 GMT-05:00 Donny Davis <do...@cloudspin.me>:
>
>> Let us know how it works out, I am curious to see if having a untagged
>> and tagged interface on the same bridge was an issue.
>> On Jun 30, 2015 10:21 PM, "Julián Tete" <danteconra...@gmail.com> wrote:
>>
>>> Thanks Donny, Tomorrow I'm going to try this. :)
>>>
>>> 2015-06-30 21:12 GMT-05:00 Donny Davis <do...@cloudspin.me>:
>>>
>>>> That tells me that there is a tagging issue between the host and the
>>>> switch.
>>>> Untagged traffic flows without issue via the same interface as tagged
>>>> traffic.
>>>> As a personal best practice I separate access ports(untagged) and trunk
>>>> ports (tagged) traffic on different physical ports.
>>>> Can you setup a separate phys interface for the tagged traffic, or must
>>>> you be able to pass both on the same interface.
>>>> On Jun 30, 2015 10:05 PM, "Julián Tete" <danteconra...@gmail.com>
>>>> wrote:
>>>>
>>>>> My mgmt network works wonderfully, Virtual Machines created on the
>>>>> mgmt even can reach Internet. But my company wants the traffic separated.
>>>>>
>>>>> Thanks Donny, I'm a RHCSA from Colombia, but I'm learning about oVirt.
>>>>> (oVirt is a new thing in my country)
>>>>>
>>>>> P.S : I want to put VMware in the Trash Can too. ^_ ^
>>>>>
>>>>> 2015-06-30 20:59 GMT-05:00 Donny Davis <do...@cloudspin.me>:
>>>>>
>>>>>> There is a special place in my DC for vmware. TrashCan...lol
>>>>>> On Jun 30, 2015 9:50 PM, "Julián Tete" <danteconra...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> I'm going to check it out... but how the host can reach the Gateway
>>>>>>> and the Virtual Machine inside doesn't ?
>>>>>>>
>>>>>>> Donny you are very kind, this the last step to free my DataCenter
>>>>>>> from VMware.
>>>>>>>
>>>>>>> 2015-06-30 20:46 GMT-05:00 Donny Davis <do...@cloudspin.me>:
>>>>>>>
>>>>>>>> Does your switch have an IP on that vlan... I would step things out
>>>>>>>> VM>host>switch>rtr
>>>>>>>>
>>>>>>>> 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

Reply via email to