[ovirt-users] Networking issues on Hosted Engine Appliance

Edward Haas ehaas at redhat.com
Mon Sep 5 04:08:54 EDT 2016


On Fri, Sep 2, 2016 at 10:49 AM, Simone Tiraboschi <stirabos at redhat.com>
wrote:

>
>
> On Thu, Sep 1, 2016 at 10:45 PM, Bryan Sockel <Bryan.Sockel at altn.com>
> wrote:
>
>> Having some issues with my Hosted Engine Appliance,  I am able to get it
>> up and running, and i can access it only from the server that is hosting
>> it.  The host server can ping the appliance, and the appliance can ping the
>> host server.  The host server can ping the rest of my network and get out
>> to the internet.
>>
>> This is a nested setup i am using for testing and poc and is running on a
>> vmware platform.
>>
>
> I'm not a VMWare expert but I suspect that you forgot enabling the
> Promiscuous Mode on the vSwitch where your virtual host is connected.
> vSwitch doesn't implement a MAC Learning algorithm and so only the frame
> addressed to a well known MAC address (such as the interfaces of host which
> is running as a VMWare virtual machine) will be sent over the right virtual
> port, other frames (the ones addressed to the hosted-engine nested VM for
> instance) will be lost.
> Promiscuous Mode mode will fix this behavior but of course it will also
> impact on the performance.
>
>
>
>> Server IP Config:
>>
>> eno16777984: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>>         ether 00:50:56:01:0d:48  txqueuelen 1000  (Ethernet)
>>         RX packets 572078  bytes 673729777 (642.5 MiB)
>>         RX errors 0  dropped 0  overruns 0  frame 0
>>         TX packets 342235  bytes 191490802 (182.6 MiB)
>>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>> lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
>>         inet 127.0.0.1  netmask 255.0.0.0
>>         loop  txqueuelen 0  (Local Loopback)
>>         RX packets 831524  bytes 6927010219 (6.4 GiB)
>>         RX errors 0  dropped 0  overruns 0  frame 0
>>         TX packets 831524  bytes 6927010219 (6.4 GiB)
>>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>> ovirtmgmt: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>>         inet 10.20.42.3  netmask 255.255.252.0  broadcast 10.20.43.255
>>         ether 00:50:56:01:0d:48  txqueuelen 0  (Ethernet)
>>         RX packets 957838  bytes 796793041 (759.8 MiB)
>>         RX errors 0  dropped 0  overruns 0  frame 0
>>         TX packets 795846  bytes 4627811240 (4.3 GiB)
>>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>> vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>>         ether fe:16:3e:20:fc:a2  txqueuelen 500  (Ethernet)
>>         RX packets 3434  bytes 11065518 (10.5 MiB)
>>         RX errors 0  dropped 0  overruns 0  frame 0
>>         TX packets 9008  bytes 2493747 (2.3 MiB)
>>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>
>> Kernel IP routing table
>> Destination     Gateway         Genmask         Flags Metric Ref    Use
>> Iface
>> default         gw-lab.colo.test 0.0.0.0         UG    0      0        0
>> ovirtmgmt
>> 10.20.40.0      0.0.0.0         255.255.252.0   U     0      0        0
>> ovirtmgmt
>> link-local      0.0.0.0         255.255.0.0     U     1004   0        0
>> ovirtmgmt
>>
>>
>> Appliance:
>> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>>         inet 10.20.42.17  netmask 255.255.252.0  broadcast 10.20.43.255
>>         ether 00:16:3e:20:fc:a2  txqueuelen 1000  (Ethernet)
>>         RX packets 9489  bytes 2674331 (2.5 MiB)
>>         RX errors 0  dropped 0  overruns 0  frame 0
>>         TX packets 3655  bytes 11370881 (10.8 MiB)
>>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>> lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
>>         inet 127.0.0.1  netmask 255.0.0.0
>>         loop  txqueuelen 0  (Local Loopback)
>>         RX packets 67298  bytes 36550074 (34.8 MiB)
>>         RX errors 0  dropped 0  overruns 0  frame 0
>>         TX packets 67298  bytes 36550074 (34.8 MiB)
>>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>
>> Kernel IP routing table
>> Destination     Gateway         Genmask         Flags Metric Ref    Use
>> Iface
>> default         ovirt1.test.lab 0.0.0.0         UG    100    0        0
>> eth0
>> 10.20.40.0      0.0.0.0         255.255.252.0   U     100    0        0
>> eth0
>>
>>
> Your server has a different gateway: gw-lab.colo.test
Your appliance has it set to ovirt1.test.lab.
Are these pointing to the same IP address?


>>
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20160905/ab0c5b1e/attachment.html>


More information about the Users mailing list