[ovs-discuss] OVSost rpm worked in OL6.4, but not in 6.5?
Gurucharan Shetty
shettyg at nicira.com
Wed Mar 26 16:10:59 UTC 2014
On Wed, Mar 26, 2014 at 2:47 AM, Hoot, Joseph <joe.hoot at itec.suny.edu>wrote:
> Hi Shetty,
>
> I thought about this a bit, but hadn't dug into it much further when I
> saw my bridges up and running. I guess I should have looked a bit further
> to validate that more than just the interfaces were online.
>
As long as your bridges are up and running, you should be fine.
>
> Here is what I had in the old kernel (2.6.32-358..):
>
> [root at os-controller ~]# lsmod | grep open
> openvswitch 37890 1
> [root at os-controller ~]# modinfo openvswitch
> filename:
> /lib/modules/2.6.32-358.el6.x86_64/kernel/net/openvswitch/openvswitch.ko
> license: GPL
> description: Open vSwitch switching datapath
> srcversion: 56D59658C3B9FADCD146B12
> depends:
> vermagic: 2.6.32-358.el6.x86_64 SMP mod_unload modversions
> [root at os-controller ~]#
>
> Here is what I have in the new kernel (2.6.32-431...).. Basically a
> similar thing except it looks like this new module depends on vxlan:
>
> [root at os-controller ~]# lsmod | grep open
> openvswitch 37890 0
> vxlan 25102 1 openvswitch
> [root at os-controller ~]# modinfo openvswitch
> filename:
> /lib/modules/2.6.32-431.5.1.el6.x86_64/kernel/net/openvswitch/openvswitch.ko
> license: GPL
> description: Open vSwitch switching datapath
> srcversion: 993363C44DF474BD67B03CC
> depends: vxlan
> vermagic: 2.6.32-431.5.1.el6.x86_64 SMP mod_unload modversions
> [root at os-controller ~]#
>
> I do have an interest in using VXLAN, but only for internal openstack
> communication. But since I have van's in my physical environment, I would
> like to get those networks into openvswitch first.
>
> Could there be a config somewhere that is attempting to use vxlan? I
> didn't put anything in place to use it yet. Besides adjusting my
> interfaces, where else might I tell openvswitch to use vxlan or not?
>
Don't worry about my earlier comment about the kernel module. As long as
you see something with "lsmod | grep openvswitch", you should not have any
problems with vlan.
Now the question about why things are not working with 6.5, you can start
with a simple configuration to see if it works and build on top of it. It
is a little hard for me to guess with the information I have in hand.
For log messages, you can look at /var/log/openvswitch/ovs-vswitchd.log
>
> ===========================
> Joseph R. Hoot @ SUNY ITEC
> Supervising Programmer/Analyst
> (w) 716-878-4832 (Office - Service Desk)
> (w) 716-878-4863 (Direct - no voicemail)
> (c) 716-759-HOOT
> joe.hoot at itec.suny.edu
> GPG KEY: 7145F633
> ===========================
>
> Managing trade-offs, attempting to reduce risk, instilling trust, and
> accepting responsibility for the system and networking team at SUNY ITEC.
>
> From: Gurucharan Shetty <shettyg at nicira.com>
> Date: Tuesday, March 25, 2014 at 12:47 PM
> To: Joseph Hoot <joe.hoot at itec.suny.edu>
> Cc: "discuss at openvswitch.org" <discuss at openvswitch.org>
> Subject: Re: [ovs-discuss] OVSost rpm worked in OL6.4, but not in 6.5?
>
>
>
>
> On Tue, Mar 25, 2014 at 9:38 AM, Hoot, Joseph <joe.hoot at itec.suny.edu>wrote:
>
>> Hi all,
>>
>> I have been looking to setup a sandbox environment to test out
>> openstack. In doing so, I found that I really need to understand how Open
>> vSwitch is working first. So I did the following to get things working
>> using the OL6.4 (essentially red hat compatible kernel
>> 2.6.32-358.el6.x86_64), but am now having issues after upgrading to the
>> latest EL6.5 kernel (2.6.32-431.5.1.el6.x86_64).
>>
>> Here's what I've done:
>>
>> 1. install OL6.4 from iso
>> 2. Since my goal is to test how VLAN's can flow through open vSwitch,
>> I've set a trunk into my test server
>> 3. So I carved off VID 302 on eth0 so I can set an IP and reach my
>> gateway by passing VID 302.
>> 4. I followed the openstack.redhat.com quickstart notes to get the
>> YUM repo that fedora uses: `sudo yum install -y
>> http://rdo.fedorapeople.org/rdo-release.rpm`<http://rdo.fedorapeople.org/rdo-release.rpm>
>> 5. I then simply did a `yum install openvswitch` and it grabbed the
>> latest openvswitchrpm from one of those repos (
>> http://repos.fedorapeople.org/repos/openstack/openstack-havana/epel-6/openvswitch-1.11.0_8ce28d-1.el6ost.x86_64.rpm)
>>
>> 6. After that, I reviewed some notes by doing a lot of google
>> searching. I think I ended up pretty much following this:
>> http://blog.scottlowe.org/2013/02/07/exploring-rhel-ovs-integrations/
>> 7. I was able to get everything working and can get in/out of the
>> system using that br-vlan302 fake bridge.
>> 8. However, I ran a `yum update` and rebooted of the latest kernel
>> (2.6.32-431.5.1) and, although everything appears to startup properly and I
>> see proper routes and don't see anything in /var/log/messages, I cannot
>> send traffic in or out.
>>
>> Does anyone know if there is an issue (or if I need to do something else
>> to allow that version of openvswitch to work with the latest RHEL6.5 kernel?
>>
> You mentioned that things worked fine with 6.4 and not with 6.5. Looking
> through your steps, it looks like you installed openvswitch once.
> openvswitch has a kernel module and hence is dependent on the kernel. Since
> you upgraded your kernel, I am wondering the newer kernel was compatible
> with the kernel module that you installed. So I would look at "lsmod | grep
> openvswitch" to see whether that exists.
>
>
>
>>
>> At the end of this, I have an openvswitch environment with eth0 and
>> eth1 coming into bond0 configured as active-backup and vlan_mode=trunk.
>> That bond0 connects into a br-bond0 bridge. I then carve out what some
>> have referred to has "fake bridges?" I do this so I can set a mgmt IP that
>> sits on a VLAN (for test purposes I randomly picked a VID 302). And the
>> fake bridge that I used to test with is called br-vlan302 and br-vlan37.
>> You can see this all below:
>>
>> [root at os-controller ~]# ovs-vsctl show
>> 5a878f19-b904-477c-a694-4142598c2150
>> Bridge "br-bond0"
>> Port "br-bond0"
>> Interface "br-bond0"
>> type: internal
>> Port "bond0"
>> Interface "eth0"
>> Interface "eth1"
>> Port "br-vlan37"
>> tag: 37
>> Interface "br-vlan37"
>> type: internal
>> Port "br-vlan302"
>> tag: 302
>> Interface "br-vlan302"
>> type: internal
>> Bridge "br-bond1"
>> Port "br-bond1"
>> Interface "br-bond1"
>> type: internal
>> Port "bond1"
>> Interface "eth2"
>> Interface "eth3"
>> ovs_version: "1.11.0"
>> [root at os-controller ~]#
>>
>> I also have the following diagram that represents some of what I setup
>> above (I'm not sure if this graphic will transfer across the list, but
>> we'll see).
>>
>> Thanks,
>> Joe
>>
>> ===========================
>> Joseph R. Hoot @ SUNY ITEC
>> Supervising Programmer/Analyst
>> (w) 716-878-4832 (Office - Service Desk)
>> (w) 716-878-4863 (Direct - no voicemail)
>> (c) 716-759-HOOT
>> joe.hoot at itec.suny.edu
>> GPG KEY: 7145F633
>> ===========================
>>
>> Managing trade-offs, attempting to reduce risk, instilling trust, and
>> accepting responsibility for the system and networking team at SUNY ITEC.
>>
>> _______________________________________________
>> discuss mailing list
>> discuss at openvswitch.org
>> http://openvswitch.org/mailman/listinfo/discuss
>>
>>
>
> _______________________________________________
> discuss mailing list
> discuss at openvswitch.org
> http://openvswitch.org/mailman/listinfo/discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20140326/3eab80af/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ost-network.png
Type: image/png
Size: 75113 bytes
Desc: not available
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20140326/3eab80af/attachment-0002.png>
More information about the discuss
mailing list