[ovs-discuss] OpenvSwitch - Issue Support Required

Jesse Gross jesse at nicira.com
Tue Jun 4 16:37:22 UTC 2013


Please keep this on the mailing list.

Can you not ping from the VM or the host? Your first message made it
sound like the former and this one the latter. If it's the host that
has the problem then you need to assign an IP address to that
interface as well.

On Mon, Jun 3, 2013 at 9:06 PM, Moovarkku Mudhalvan
<moovarkku.mudhalvan at sifycorp.com> wrote:
> Hi Jesse,
>         Thanks and I spend couple of hours before posting it.
>
>         Q:can you access the network from the hypervisor through OVS?,
>         A:Please let me know how can I check and confirm it.
>
>         Q: what does the configuration look like when you start the new VM?
>         A: When I create a virtual machine I can specify the IP address as the same segment of Host. It is getting assigned and ping only from the VM. I am not able to ping from the Host. But in the host vnet0 is getting created.
>
> Regards
> Mudhalvan M.M
>
> -----Original Message-----
> From: Jesse Gross [mailto:jesse at nicira.com]
> Sent: Tuesday, June 04, 2013 7:06 AM
> To: Moovarkku Mudhalvan
> Cc: discuss at openvswitch.org
> Subject: Re: [ovs-discuss] OpenvSwitch - Issue Support Required
>
> On Mon, Jun 3, 2013 at 4:03 AM, Moovarkku Mudhalvan <moovarkku.mudhalvan at sifycorp.com> wrote:
>> Dear OpenvSwitch Team,
>>
>>
>>
>>
>>
>>                Greetings. I have installed CentOS 6.4 in the Blade server.
>> Also installed and configured openvswitch
>>
>>
>>
>> 1.      Confirmed openvswitch is installed and configured
>>
>>
>>
>> [root at clab-kvm02 ~]# lsmod |grep openvswitch
>>
>> openvswitch            37890  0
>>
>> [root at clab-kvm02 ~]# ovs-vsctl -V
>>
>> ovs-vsctl (Open vSwitch) 1.9.0
>>
>> Compiled Jun  2 2013 14:14:18
>>
>> [root at clab-kvm02 ~]#
>>
>>
>>
>> 2.      Confirmed Switch , Interface and Port
>>
>>
>>
>> [root at clab-kvm02 network-scripts]# cat ifcfg-eth0
>>
>> DEVICE=eth0
>>
>> BOOTPROTO=none
>>
>> NM_CONTROLLED=no
>>
>> TYPE=OVSPort
>>
>> ONBOOT=yes
>>
>> IPV6INIT=no
>>
>> HWADDR=00:21:5A:9B:00:00
>>
>> DEVICETYPE=ovs
>>
>> OVS_BRIDGE=ovsbr0
>>
>>
>>
>> [root at clab-kvm02 network-scripts]# cat ifcfg-ovsbr0
>>
>> DEVICE=ovsbr0
>>
>> ONBOOT=yes
>>
>> DEVICETYPE=ovs
>>
>> TYPE=OVSBridge
>>
>> BOOTPROTO=static
>>
>> IPADDR=172.16.5.12
>>
>> GATEWAY=172.16.5.1
>>
>> NETMASK=255.255.255.0
>>
>> DNS1=172.16.5.13
>>
>> HOTPLUG=no
>>
>> [root at clab-kvm02 network-scripts]#
>>
>>
>>
>>
>>
>> [root at clab-kvm02 ~]# route -n
>>
>> Kernel IP routing table
>>
>> Destination     Gateway         Genmask         Flags Metric Ref    Use
>> Iface
>>
>> 172.16.5.0      0.0.0.0         255.255.255.0   U     0      0        0
>> ovsbr0
>>
>> 192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0
>> virbr0
>>
>> 0.0.0.0         172.16.5.1      0.0.0.0         UG    0      0        0
>> ovsbr0
>>
>>
>>
>> [root at clab-kvm02 ~]# brctl show
>>
>> bridge name     bridge id               STP enabled     interfaces
>>
>> virbr0          8000.525400ea5aeb       yes             virbr0-nic
>>
>>
>>
>> [root at clab-kvm02 ~]#
>>
>>
>>
>>
>>
>> [root at clab-kvm02 libvirt]# ovs-vsctl show
>>
>> 999f5e2f-bd63-4026-8956-2b6a5c726db8
>>
>>     Bridge "ovsbr0"
>>
>>         Port "ovsbr0"
>>
>>             Interface "ovsbr0"
>>
>>                 type: internal
>>
>>         Port "eth0"
>>
>>             Interface "eth0"
>>
>>     ovs_version: "1.9.0"
>>
>>
>>
>>
>>
>> Now when I create a new virtual machine using virt-manager it is not
>> getting IP and working. If any one of you have come across the same
>> and know the solution please share it.
>
> You need to do more analysis before simply posting that you cannot receive traffic. For example, can you access the network from the hypervisor through OVS?, what does the configuration look like when you start the new VM?, etc.
>
>
>
>
> Get your world in your inbox!
>
> Mail, widgets, documents, spreadsheets, organizer and much more with your Sifymail WIYI id!
> Log on to http://www.sify.com
>
> ********** DISCLAIMER **********
> Information contained and transmitted by this E-MAIL is proprietary to
> Sify Technologies Limited and is intended for use only by the individual or entity to
> which it is addressed, and may contain information that is privileged,
> confidential or exempt from disclosure under applicable law. If this is a
> forwarded message, the content of this E-MAIL may not have been sent with
> the authority of the Company. If you are not the intended recipient, an
> agent of the intended recipient or a  person responsible for delivering the
> information to the named recipient,  you are notified that any use,
> distribution, transmission, printing, copying or dissemination of this
> information in any way or in any manner is strictly prohibited. If you have
> received this communication in error, please delete this mail & notify us
> immediately at admin at sifycorp.com



More information about the discuss mailing list