HI
I thought Its promiscuous mode issue ,after reboot of engine unable to
reach again ? is there anyways to resolve ?
Thanks,
Nagaraju
On Fri, Apr 22, 2016 at 11:45 AM, Budur Nagaraju <nbudoor(a)gmail.com> wrote:
I found the solution ,promiscuous mode was rejecting the packets this
was
causing the issue ,enabled and now able to ping without any issues.
Thanks for the support !
On Fri, Apr 22, 2016 at 8:39 AM, Budur Nagaraju <nbudoor(a)gmail.com> wrote:
> HI
>
> Any updates issue is blocking ?
>
> Thanks,
> Nagaraju
>
>
> On Thu, Apr 21, 2016 at 7:20 PM, Budur Nagaraju <nbudoor(a)gmail.com>
> wrote:
>
>> Below are the details, unable to ping the gateway from the ovirt engine
>> ,able to ping the ovirt engine from host as both are there in the same
>> network.
>>
>>
>> [root@oe ~]# ip addr
>> 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
>> inet6 ::1/128 scope host
>> valid_lft forever preferred_lft forever
>> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
>> state UP qlen 1000
>> link/ether 00:16:3e:33:38:e5 brd ff:ff:ff:ff:ff:ff
>> inet 10.206.66.9/23 brd 10.206.67.255 scope global eth0
>> inet6 fe80::216:3eff:fe33:38e5/64 scope link
>> valid_lft forever preferred_lft forever
>> [root@oe ~]#
>> [root@oe ~]#
>> [root@oe ~]#
>> [root@oe ~]# ip route
>> 10.206.66.0/23 dev eth0 proto kernel scope link src 10.206.66.9
>> 169.254.0.0/16 dev eth0 scope link metric 1002
>> default via 10.206.67.254 dev eth0
>> [root@oe ~]#
>> [root@oe ~]#
>> [root@oe ~]#
>> [root@oe ~]# brctl show
>> bridge name bridge id STP enabled interfaces
>> [root@oe ~]#
>>
>>
>>
>>
>>
>>
>> On Thu, Apr 21, 2016 at 4:51 PM, Yedidyah Bar David <didi(a)redhat.com>
>> wrote:
>>
>>> On Thu, Apr 21, 2016 at 1:39 PM, Budur Nagaraju <nbudoor(a)gmail.com>
>>> wrote:
>>> > HI
>>> >
>>> > Installed hosted engine and after configuring IP to ovirt engine
>>> unable to
>>> > ping the gateway and found that there is no issue with the Network .
>>>
>>> You mean that from inside the engine machine, you cannot ping the
>>> gateway?
>>>
>>> Can you ping it from the host?
>>>
>>> Please share output of these commands, from both the host and the
>>> engine vm:
>>>
>>> ip addr
>>> ip route
>>> brctl show
>>>
>>> Thanks,
>>>
>>> >
>>> > Is there any thing am missing while installing Hosted engine ? below
>>> is
>>> > output details,
>>> >
>>> >
>>> > --== CONFIGURATION PREVIEW ==--
>>> >
>>> > Engine FQDN :
oe.bnglab.psecure.net
>>> > Bridge name : ovirtmgmt
>>> > SSH daemon port : 22
>>> > Gateway address : 10.206.67.254
>>> > Host name for web application : hosted_engine_1
>>> > Host ID : 1
>>> > Image alias : hosted_engine
>>> > Image size GB : 25
>>> > Storage connection : 10.204.207.152:
>>> /home/heoe
>>> > Console type : vnc
>>> > Memory size MB : 4096
>>> > MAC address : 00:16:3e:2f:5c:40
>>> > Boot type : cdrom
>>> > Number of CPUs : 2
>>> > ISO image (for cdrom boot) :
>>> > /ovirt/CentOS-6.7-x86_64-minimal.iso
>>> > CPU Type : model_SandyBridge
>>> >
>>> > Please confirm installation settings (Yes, No)[Yes]: yes
>>> > [ INFO ] Stage: Transaction setup
>>> > [ INFO ] Stage: Misc configuration
>>> > [ INFO ] Stage: Package installation
>>> > [ INFO ] Stage: Misc configuration
>>> > [ INFO ] Configuring libvirt
>>> > [ INFO ] Configuring VDSM
>>> > [ INFO ] Starting vdsmd
>>> > [ INFO ] Waiting for VDSM hardware info
>>> > [ INFO ] Waiting for VDSM hardware info
>>> > [ INFO ] Creating Storage Domain
>>> > [ INFO ] Creating Storage Pool
>>> > [ INFO ] Connecting Storage Pool
>>> > [ INFO ] Verifying sanlock lockspace initialization
>>> > [ INFO ] Creating VM Image
>>> > [ INFO ] Disconnecting Storage Pool
>>> > [ INFO ] Start monitoring domain
>>> > [ INFO ] Configuring VM
>>> > [ INFO ] Updating hosted-engine configuration
>>> > [ INFO ] Stage: Transaction commit
>>> > [ INFO ] Stage: Closing up
>>> > The following network ports should be opened:
>>> > tcp:5900
>>> > tcp:5901
>>> > udp:5900
>>> > udp:5901
>>> > An example of the required configuration for iptables can
>>> be found
>>> > at:
>>> > /etc/ovirt-hosted-engine/iptables.example
>>> > In order to configure firewalld, copy the files from
>>> > /etc/ovirt-hosted-engine/firewalld to
>>> /etc/firewalld/services
>>> > and execute the following commands:
>>> > firewall-cmd -service hosted-console
>>> > [ INFO ] Creating VM
>>> > You can now connect to the VM with the following command:
>>> > /usr/bin/remote-viewer vnc://localhost:5900
>>> > Use temporary password "2049ZfXr" to connect to vnc
console.
>>> > Please note that in order to use remote-viewer you need to
>>> be able
>>> > to run graphical applications.
>>> > This means that if you are using ssh you have to supply the
>>> -Y
>>> > flag (enables trusted X11 forwarding).
>>> > Otherwise you can run the command from a terminal in your
>>> > preferred desktop environment.
>>> > If you cannot run graphical applications you can connect to
>>> the
>>> > graphic console from another host or connect to the console using the
>>> > following command:
>>> > virsh -c qemu+tls://Test/system console HostedEngine
>>> > If you need to reboot the VM you will need to start it
>>> manually
>>> > using the command:
>>> > hosted-engine --vm-start
>>> > You can then set a temporary password using the command:
>>> > hosted-engine --add-console-password
>>> > The VM has been started. Install the OS and shut down or
>>> reboot
>>> > it. To continue please make a selection:
>>> >
>>> > (1) Continue setup - VM installation is complete
>>> > (2) Reboot the VM and restart installation
>>> > (3) Abort setup
>>> > (4) Destroy VM and abort setup
>>> >
>>> > _______________________________________________
>>> > Users mailing list
>>> > Users(a)ovirt.org
>>> >
http://lists.ovirt.org/mailman/listinfo/users
>>> >
>>>
>>>
>>>
>>> --
>>> Didi
>>>
>>
>>
>