On Thu, Mar 14, 2013 at 11:03 AM, Denis Iskandarov
<[email protected]> wrote:
> After restarting network service.
> "ovs-vsctl show" and "ovs-vsctl list-br" showing nothing - empty.
> So nothing to delete. ifconfig -a not showing bridge as well.
> system restart doesn't help.
>
> My configs are:
> DEVICE=br0
> ONBOOT=yes
> DEVICETYPE=ovs
> TYPE=OVSBridge
> NM_CONTROLLED=no
> BOOTPROTO=static
> IPADDR=192.168.0.111
> NETMASK=255.255.255.0
> HOTPLUG=no
>
> DEVICE=eth0
> ONBOOT=yes
> DEVICETYPE=ovs
> TYPE=OVSPort
> OVS_BRIDGE=br0
> NM_CONTROLLED=no
> BOOTPROTO=none
> HOTPLUG=no
>
> DEVICE=eth1
> ONBOOT=yes
> DEVICETYPE=ovs
> TYPE=OVSPort
> OVS_BRIDGE=br0
> NM_CONTROLLED=no
> BOOTPROTO=none
> HOTPLUG=no
>
I am not sure what is the issue at your end. I used the same config as
yours (eth3 and eth4 instead of eth0 and eth1). Here is the log.
[root@localhost network-scripts]# ovs-vsctl show
f3f55f5e-d2ff-480a-b011-60753544500f
ovs_version: "1.9.0.18063"
[root@localhost network-scripts]# /etc/init.d/network start
Bringing up loopback interface: [ OK ]
Bringing up interface br0: [ OK ]
Bringing up interface eth3: [ OK ]
Bringing up interface eth4: [ OK ]
[root@localhost network-scripts]# ovs-vsctl show
f3f55f5e-d2ff-480a-b011-60753544500f
Bridge "br0"
Port "eth4"
Interface "eth4"
Port "br0"
Interface "br0"
type: internal
Port "eth3"
Interface "eth3"
ovs_version: "1.9.0.18063"
[root@localhost network-scripts]# ifconfig br0
br0 Link encap:Ethernet HWaddr 00:0C:29:6C:D3:77
inet addr:192.168.0.111 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::9cc3:98ff:fe8b:6c42/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:120 (120.0 b) TX bytes:720 (720.0 b)
[root@localhost network-scripts]# ifconfig eth4
eth4 Link encap:Ethernet HWaddr 00:0C:29:6C:D3:81
inet6 addr: fe80::20c:29ff:fe6c:d381/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:120 (120.0 b) TX bytes:650 (650.0 b)
[root@localhost network-scripts]# ifconfig eth3
eth3 Link encap:Ethernet HWaddr 00:0C:29:6C:D3:77
inet6 addr: fe80::20c:29ff:fe6c:d377/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:133 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:9634 (9.4 KiB)
[root@localhost network-scripts]# /etc/init.d/network stop
Shutting down interface br0: [ OK ]
Shutting down interface eth3: [ OK ]
Shutting down interface eth4: [ OK ]
Shutting down loopback interface: [ OK ]
[root@localhost network-scripts]# ovs-vsctl show
f3f55f5e-d2ff-480a-b011-60753544500f
ovs_version: "1.9.0.18063"
Having said that, I think there is a problem with this patch. If
someone yanks the power chord or there is a kernel panic, during the
next boot, since bridge has not been deleted from OVSDB, there won't
be reconfiguration, so bridge will be administratively down.
>
>
> On Thu, Mar 14, 2013 at 9:50 PM, Gurucharan Shetty <[email protected]>
> wrote:
>>
>> On Thu, Mar 14, 2013 at 10:37 AM, Denis Iskandarov
>> <[email protected]> wrote:
>> > Fail:
>> > Log shows that script only removes ports from bridge.
>> > Not removing bridge as previous script does (i don't know if it's
>> > actually
>> > neded).
>> > Main it can't create bridge in the and assign ports to it.
>> > Ports not leaving/entering promiscuous mode.
>> >
>> >> Mar 14 21:27:34 ovs-cent64 ovs-vsctl: 00001|vsctl|INFO|Called as
>> >> ovs-vsctl
>> >> -t 10 -- --if-exists del-port br0 eth0
>> >> Mar 14 21:27:34 ovs-cent64 ovs-vsctl: 00001|vsctl|INFO|Called as
>> >> ovs-vsctl
>> >> -t 10 -- --if-exists del-port br0 eth1
>> >> Mar 14 21:27:34 ovs-cent64 kernel: lo: Disabled Privacy Extensions
>> >> Mar 14 21:27:34 ovs-cent64 /etc/sysconfig/network-scripts/ifup-eth:
>> >> Device
>> >> br0 does not seem to be present, delaying initialization.
>> >> Mar 14 21:27:34 ovs-cent64 kernel: e1000: eth0 NIC Link is Up 1000 Mbps
>> >> Full Duplex, Flow Control: None
>> >> Mar 14 21:27:34 ovs-cent64 kernel: ADDRCONF(NETDEV_UP): eth0: link is
>> >> not
>> >> ready
>> >> Mar 14 21:27:34 ovs-cent64 kernel: ADDRCONF(NETDEV_CHANGE): eth0: link
>> >> becomes ready
>> >> Mar 14 21:27:34 ovs-cent64 kernel: e1000: eth1 NIC Link is Up 1000 Mbps
>> >> Full Duplex, Flow Control: None
>> >> Mar 14 21:27:34 ovs-cent64 kernel: ADDRCONF(NETDEV_UP): eth1: link is
>> >> not
>> >> ready
>> >> Mar 14 21:27:34 ovs-cent64 kernel: ADDRCONF(NETDEV_CHANGE): eth1: link
>> >> becomes ready
>> >
>> >
>> > Any other helpful info I can provide?
>> Whats the configuration (ifcfg-* ) that you are using.
>> Can you clean up your bridges (ovs-vsctl del-br $bridge_name;
>> ovs-vsctl show) and then repeat the test? It is possible that you have
>> some manually created bridges(or remnants during previos changes) in
>> which case, the script won't attempt to configure it.
>
>
_______________________________________________
dev mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/dev
