[Openstack-operators] Need help to setup instance tunnel.

Geo Varghese gvarghese at aqorn.com
Wed Nov 26 08:24:37 UTC 2014


Hi Andreas,

Thanks a lot for the reply.

options: {in_key=flow, local_ip="192.168.1.190",
out_key=flow, remote_ip="192.168.1.202"}

192.168.1.202 => is IP of controller node right?

In this case do you have two network interfaces?

I am using Virual machines(KVM) and currently i have only one interface
eth0 in compute node.

How can i configure this.

Thanks for your time.


On Wed, Nov 26, 2014 at 1:04 PM, Andreas Scheuring <
scheuran at linux.vnet.ibm.com> wrote:

> Hi Geo,
> your packet will be sent out of br-tun via the gre-xxxxx port "pointing"
> to your compute node. So what you have to do is to put the ip address to
> your eth interface connected to the wire. The same of course on the
> controller node. Putting the ip address on the br-tun does not make
> sense, as it just hangs around without any physical port plugged in.
>
> This is how my ovs-vsctl show looks like on the compute node.
>
> ovs-vsctl show
> 9253a3f8-3c28-4953-ae85-ca94aa0d4fb1
>     Bridge br-tun
>         Port br-tun
>             Interface br-tun
>                 type: internal
>         Port "gre-c0a801ca"
>             Interface "gre-c0a801ca"
>                 type: gre
>                 options: {in_key=flow, local_ip="192.168.1.190",
> out_key=flow, remote_ip="192.168.1.202"}
>         Port patch-int
>             Interface patch-int
>                 type: patch
>                 options: {peer=patch-tun}
>     Bridge br-int
>         Port br-int
>             Interface br-int
>                 type: internal
>         Port patch-tun
>             Interface patch-tun
>                 type: patch
>                 options: {peer=patch-int}
>         Port "qvo1c352474-0c"
>             tag: 1
>             Interface "qvo1c352474-0c"
>         Port "qvo5782980b-be"
>             tag: 4095
>             Interface "qvo5782980b-be"
>     ovs_version: "2.1.2"
>
>
>
> And this is the ip configuration of the net device used:
>
> 22: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
> state DOWN qlen 1000
>     link/ether 02:00:00:39:13:9a brd ff:ff:ff:ff:ff:ff
>     inet 192.168.1.190/24 brd 192.168.1.255 scope global eth0
>        valid_lft forever preferred_lft forever
>
>
>
>
>
> And this is my ml2.conf on the compute node
>
> [ovs]
> local_ip = 192.168.1.190
> tunnel_type = gre
> enable_tunneling = True
>
>
>
> Regards
>
>
> --
> Andreas
> (irc: scheuran)
>
>
> On Wed, 2014-11-26 at 01:39 +0530, Geo Varghese wrote:
> > Hi Team,
> >
> >
> >
> > I need some help to setup instance tunnel.
> >
> >
> > I tried 2 node installation today and successfully added new compute1
> > node.
> >
> > Later i have created new VM on new compute1 node. It successfully
> > spawned but the issue is it couldn't get dhcp ip.
> >
> > Due to this eth0 is not assigned with an IP address. I think instance
> > tunnel interface is not correct.
> >
> > Currently I set IP to automatically created interface br-tun, do i
> > need to create new instance tunnel?
> >
> > =========================================
> > br-tun Link encap:Ethernet HWaddr 6a:65:2d:ed:90:44
> > inet addr:192.168.123.179 Bcast:192.168.123.255 Mask:255.255.255.0
> > inet6 addr: fe80::98c7:a1ff:fef6:bcd7/64 Scope:Link
> > UP BROADCAST RUNNING MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:0 (0.0 B) TX bytes:648 (648.0 B)
> > =========================================
> >
> > And given this Ip addres(192.168.123.179) in [mvs] configuration
> > (/etc/neutron/plugins/ml2/ml2_conf.ini)
> >
> > [ovs]
> > local_ip = 192.168.123.179
> > tunnel_type = gre
> > enable_tunneling = True
> >
> > Is it correct? Please help me.
> >
> >
> > --
> > Regards,
> > Geo Varghese
> > _______________________________________________
> > OpenStack-operators mailing list
> > OpenStack-operators at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>



-- 
--
Regards,
Geo Varghese
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20141126/b304ba32/attachment.html>


More information about the OpenStack-operators mailing list