[ovs-discuss] OVS host management with Vlan tagged port
Ariel Moreno
ariel.moreno at mercadolibre.com
Tue Jan 17 23:01:48 UTC 2012
Ben
do you think it should avoid I configure the IP address to the vlan446 interface?
I have added the physical ports to the bridge, but interface vlan446 is still not recognize d.
Thanks
root at ism15vms:~# ovs-vsctl show
93741536-21a1-4216-9d84-f49dfbef0752
Bridge br-int
Port "vlan446"
tag: 446
Interface "vlan446"
type: internal
Port "eth1"
Interface "eth1"
type: internal
Port "eth0"
Interface "eth0"
type: internal
Port br-int
Interface br-int
type: internal
Port "bond0"
Interface "bond0"
type: internal
root at ism15vms:~# ifconfig -a
bond0 Link encap:Ethernet HWaddr 00:25:90:1f:b5:ae
inet addr:172.16.167.24 Bcast:172.16.167.255 Mask:255.255.255.0
inet6 addr: fe80::225:90ff:fe1f:b5ae/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:46506 errors:0 dropped:0 overruns:0 frame:0
TX packets:9349 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4621227 (4.6 MB) TX bytes:1273679 (1.2 MB)
br-int Link encap:Ethernet HWaddr 4e:e6:05:50:b2:47
BROADCAST PROMISC MULTICAST MTU:1500 Metric:1
RX packets:2231 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:142868 (142.8 KB) TX bytes:0 (0.0 B)
eth0 Link encap:Ethernet HWaddr 00:25:90:1f:b5:ae
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:34284 errors:0 dropped:0 overruns:0 frame:0
TX packets:4679 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2258411 (2.2 MB) TX bytes:638668 (638.6 KB)
Interrupt:28 Memory:fbce0000-fbd00000
eth1 Link encap:Ethernet HWaddr 00:25:90:1f:b5:ae
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:12222 errors:0 dropped:0 overruns:0 frame:0
TX packets:4670 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2362816 (2.3 MB) TX bytes:635011 (635.0 KB)
Interrupt:29 Memory:fbde0000-fbe00000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:106343 errors:0 dropped:0 overruns:0 frame:0
TX packets:106343 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:68740376 (68.7 MB) TX bytes:68740376 (68.7 MB)
Regards
Ariel Moreno
----- Original Message -----
From: "Ben Pfaff" <blp at nicira.com>
To: "Ariel Moreno" <ariel.moreno at mercadolibre.com>
Cc: discuss at openvswitch.org
Sent: Tuesday, January 17, 2012 6:41:00 PM
Subject: Re: [ovs-discuss] OVS host management with Vlan tagged port
"ovs-vsctl show" doesn't list any physical ports on your bridge.
On Tue, Jan 17, 2012 at 05:35:08PM -0400, Ariel Moreno wrote:
> Ben
> it is still not working. I have already tried this option, and also tag the bond0 interfaces already recognized by the host. But nothing.
>
> See my log
>
> root at ism15vms:~# ovs-vsctl show
> 93741536-21a1-4216-9d84-f49dfbef0752
> Bridge br-int
> Port "vlan446"
> tag: 446
> Interface "vlan446"
> Port br-int
> Interface br-int
> type: internal
> root at ism15vms:~# ovs-vsctl set Interface vlan446 type=internal
> root at ism15vms:~# ifconfig vlan446 172.16.167.24
> SIOCSIFADDR: No such device
> vlan446: ERROR while getting interface flags: No such device
> root at ism15vms:~# ifconfig -a
> bond0 Link encap:Ethernet HWaddr 00:25:90:1f:b5:ae
> inet addr:172.16.167.24 Bcast:172.16.167.255 Mask:255.255.255.0
> inet6 addr: fe80::225:90ff:fe1f:b5ae/64 Scope:Link
> UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
> RX packets:45832 errors:0 dropped:0 overruns:0 frame:0
> TX packets:9059 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:4537072 (4.5 MB) TX bytes:1237484 (1.2 MB)
>
> br-int Link encap:Ethernet HWaddr 4e:e6:05:50:b2:47
> BROADCAST PROMISC MULTICAST MTU:1500 Metric:1
> RX packets:2231 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:500
> RX bytes:142868 (142.8 KB) TX bytes:0 (0.0 B)
>
> eth0 Link encap:Ethernet HWaddr 00:25:90:1f:b5:ae
> UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
> RX packets:33847 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4534 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:2217746 (2.2 MB) TX bytes:620235 (620.2 KB)
> Interrupt:28 Memory:fbce0000-fbd00000
>
> eth1 Link encap:Ethernet HWaddr 00:25:90:1f:b5:ae
> UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
> RX packets:11985 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4525 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:2319326 (2.3 MB) TX bytes:617249 (617.2 KB)
> Interrupt:29 Memory:fbde0000-fbe00000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:81554 errors:0 dropped:0 overruns:0 frame:0
> TX packets:81554 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:51024739 (51.0 MB) TX bytes:51024739 (51.0 MB)
>
> root at ism15vms:~# ovs-vsctl show
> 93741536-21a1-4216-9d84-f49dfbef0752
> Bridge br-int
> Port "vlan446"
> tag: 446
> Interface "vlan446"
> type: internal
> Port br-int
> Interface br-int
> type: internal
> root at ism15vms:~#
>
>
>
>
>
>
>
>
>
>
>
> Ariel Moreno
>
> ----- Original Message -----
>
> From: "Ben Pfaff" <blp at nicira.com>
> To: "Ariel Moreno" <ariel.moreno at mercadolibre.com>
> Cc: discuss at openvswitch.org
> Sent: Tuesday, January 17, 2012 6:28:53 PM
> Subject: Re: [ovs-discuss] OVS host management with Vlan tagged port
>
> Oops, I see I made a second typo. Sorry about that.
> Let me repeat the whole corrected recipe:
>
> # Create access port.
> ovs-vsctl add-port br-int vlan446 tag=446 \
> set Interface vlan446 type=internal
>
> # Put IP address on vlan446.
> ifconfig vlan446 172.16.167.24
>
> On the other hand the description in ovs-vsctl(8) was correct.
>
> On Tue, Jan 17, 2012 at 05:25:58PM -0400, Ariel Moreno wrote:
> > Ben
> > Thank again for your support.
> >
> > I have destroy my bridge and I followed you recipe.
> >
> > Here is my log.
> >
> >
> > root at ism15vms:~# ovs-vsctl show
> > 93741536-21a1-4216-9d84-f49dfbef0752
> > Bridge br-int
> > Port "bond0"
> > tag: 446
> > Interface "bond0"
> > type: internal
> > Port "eth0"
> > Interface "eth0"
> > type: internal
> > Port br-int
> > Interface br-int
> > type: internal
> > root at ism15vms:~# ovs-vsctl del-br br-int
> > root at ism15vms:~#
> > root at ism15vms:~#
> > root at ism15vms:~#
> > root at ism15vms:~# ovs-vsctl
> > ovs-vsctl: missing command name (use --help for help)
> > root at ism15vms:~# ovs-vsctl show
> > 93741536-21a1-4216-9d84-f49dfbef0752
> > root at ism15vms:~# ovs-vsctl add-br br-int
> > root at ism15vms:~# ovs-vsctl add-port br-int vlan446 tag=446
> > root at ism15vms:~# ovs-vsctl set Interfaces br-int type=internal
> > ovs-vsctl: unknown table "Interfaces"
> > root at ism15vms:~# ovs-vsctl set Interface br-int type=internal
> > root at ism15vms:~# ifconfig -a
> > bond0 Link encap:Ethernet HWaddr 00:25:90:1f:b5:ae
> > inet addr:172.16.167.24 Bcast:172.16.167.255 Mask:255.255.255.0
> > inet6 addr: fe80::225:90ff:fe1f:b5ae/64 Scope:Link
> > UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
> > RX packets:45367 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:8795 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:4488898 (4.4 MB) TX bytes:1202634 (1.2 MB)
> >
> > br-int Link encap:Ethernet HWaddr 4e:e6:05:50:b2:47
> > BROADCAST PROMISC MULTICAST MTU:1500 Metric:1
> > RX packets:2231 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:500
> > RX bytes:142868 (142.8 KB) TX bytes:0 (0.0 B)
> >
> > eth0 Link encap:Ethernet HWaddr 00:25:90:1f:b5:ae
> > UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
> > RX packets:33823 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:4402 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:2214477 (2.2 MB) TX bytes:602910 (602.9 KB)
> > Interrupt:28 Memory:fbce0000-fbd00000
> >
> > eth1 Link encap:Ethernet HWaddr 00:25:90:1f:b5:ae
> > UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
> > RX packets:11544 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:4393 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:2274421 (2.2 MB) TX bytes:599724 (599.7 KB)
> > Interrupt:29 Memory:fbde0000-fbe00000
> >
> > lo Link encap:Local Loopback
> > inet addr:127.0.0.1 Mask:255.0.0.0
> > inet6 addr: ::1/128 Scope:Host
> > UP LOOPBACK RUNNING MTU:16436 Metric:1
> > RX packets:78888 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:78888 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:49138094 (49.1 MB) TX bytes:49138094 (49.1 MB)
> >
> > root at ism15vms:~# ifconfig vlan446 172.16.167.24
> > SIOCSIFADDR: No such device
> > vlan446: ERROR while getting interface flags: No such device
> > root at ism15vms:~#
> >
> > As you see, the vlan446 is not recognize for the host to configure the IP address.
> >
> > Regards
> >
> >
> >
> >
> >
> >
> >
> >
> > Ariel Moreno
> >
> >
> >
> > ----- Original Message -----
> >
> > From: "Ben Pfaff" <blp at nicira.com>
> > To: "Ariel Moreno" <ariel.moreno at mercadolibre.com>
> > Cc: discuss at openvswitch.org
> > Sent: Tuesday, January 17, 2012 6:14:45 PM
> > Subject: Re: [ovs-discuss] OVS host management with Vlan tagged port
> >
> > You've got OVS misinstalled somehow. This works.
> >
> > I did include a typo in my last command. It is probably obvious, but
> > it should have read:
> > ifconfig vlan446 172.16.167.24
> >
> > If you want to debug the problem, please report what "ovs-vsctl show"
> > and "ifconfig -a" now output.
> >
> > Thanks,
> >
> > Ben.
> >
> > On Tue, Jan 17, 2012 at 05:11:27PM -0400, Ariel Moreno wrote:
> > > Ben
> > > thanks a lot for your support. Unfortunately it did not work.
> > > Although I was able to configure the access port (step2), my server does not recognize "vlan446" as a valid device to configure the ip address.
> > >
> > > I found also a recipe using a fake bridge and it did not work.
> > > Any other idea?
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Ariel Moreno
> > >
> > >
> > >
> > > ----- Original Message -----
> > >
> > > From: "Ben Pfaff" <blp at nicira.com>
> > > To: "Ariel Moreno" <ariel.moreno at mercadolibre.com>
> > > Cc: discuss at openvswitch.org
> > > Sent: Tuesday, January 17, 2012 2:42:49 PM
> > > Subject: Re: [ovs-discuss] OVS host management with Vlan tagged port
> > >
> > > On Tue, Jan 17, 2012 at 12:08:04PM -0400, Ariel Moreno wrote:
> > > > We are facing a problem configuring ovs to manage VLAN tagged
> > > > traffic, in particular we have configured a bridge "bt-int" and
> > > > added a bond0 interface joining eth0 and eth1
> > > >
> > > > root at ism15vms:~# ovs-vsctl show
> > > > 93741536-21a1-4216-9d84-f49dfbef0752
> > > > Bridge br-int
> > > > Port "bond0"
> > > > trunks: [446]
> > > > Interface "eth0"
> > > > Interface "eth1"
> > > > Port br-int
> > > > Interface br-int
> > > > type: internal
> > > >
> > > >
> > > > And following the recipes I have configured the host mgmt IP to the
> > > > bond0 interface
> > > >
> > > > bond0 Link encap:Ethernet HWaddr 00:25:90:1f:b5:ae
> > > > inet addr:172.16.167.24 Bcast:172.16.167.255 Mask:255.255.255.0
> > > > inet6 addr: fe80::225:90ff:fe1f:b5ae/64 Scope:Link
> > > > UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
> > > > RX packets:23613 errors:0 dropped:0 overruns:0 frame:0
> > > > TX packets:7635 errors:0 dropped:0 overruns:0 carrier:0
> > > > collisions:0 txqueuelen:0
> > > > RX bytes:2960928 (2.9 MB) TX bytes:1061892 (1.0 MB)
> > >
> > > You have configured bond0 as a trunk port that trunks only a single
> > > VLAN. Presumably that is the VLAN on which you want the configured IP
> > > address. However, Linux doesn't directly understand how to talk IP
> > > when it is encapsulated in an 802.1Q header. In the case of bridged
> > > networking, you would create a VLAN device and put the IP address on
> > > that; in the case of Open vSwitch, you create an access port as an
> > > internal device and put the IP address on that, e.g.:
> > >
> > > # Remove IP address from bond0, since it won't be useful.
> > > ifconfig bond0 0.0.0.0
> > >
> > > # Create access port.
> > > ovs-vsctl add-port br-int vlan446 tag=446 \
> > > set Interface br-int type=internal
> > >
> > > # Put IP address on vlan446.
> > > ifconfig bond0 172.16.167.24
> > >
> > > This is also covered in the "Configuration Cookbook" section of
> > > ovs-vsctl(8).
> > >
> >
>
_______________________________________________
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/20120117/2e321e4a/attachment.html>
More information about the discuss
mailing list