[ovs-discuss] openvswitch not fault tolerant or contain failover mechanism

Fri Jan 25 00:02:56 UTC 2019

and I used this configuration also :

[root at localhost network-scripts]# cat ifcfg-br-ex
DEVICE=br-ex
TYPE=OVSBridge
DEVICETYPE=ovs
ONBOOT=yes
NM_CONTROLLED=no
BOOTPROTO=none
IPADDR=192.168.43.110
PREFIX=24
GATEWAY=192.168.43.1
DNS=192.168.43.1
BOOTPROTO=static

[root at localhost network-scripts]#

same result ...
[root at localhost network-scripts]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno16777736: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
master ovs-system state UP group default qlen 1000
    link/ether 00:0c:29:37:19:1f brd ff:ff:ff:ff:ff:ff
    inet6 fe80::20c:29ff:fe37:191f/64 scope link
       valid_lft forever preferred_lft forever
3: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 1000
    link/ether 1a:bb:19:b0:17:77 brd ff:ff:ff:ff:ff:ff
7: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 1000
    link/ether 9a:ed:b6:78:0c:48 brd ff:ff:ff:ff:ff:ff
9: br-tun: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 1000
    link/ether 56:40:b4:95:4f:4c brd ff:ff:ff:ff:ff:ff
10: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UNKNOWN group default qlen 1000
    link/ether 00:0c:29:37:19:1f brd ff:ff:ff:ff:ff:ff
    inet 192.168.43.110/24 brd 192.168.43.255 scope global br-ex
       valid_lft forever preferred_lft forever
    inet6 fe80::20c:29ff:fe37:191f/64 scope link
       valid_lft forever preferred_lft forever
11: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
state DOWN group default qlen 1000
    link/ether 52:54:00:32:ff:42 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
12: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0
state DOWN group default qlen 1000
    link/ether 52:54:00:32:ff:42 brd ff:ff:ff:ff:ff:ff
[root at localhost network-scripts]#

br-ex status UNKOWN

how can I make it UP

On Fri, Jan 25, 2019 at 2:59 AM Amer Hwitat <amer.hwaitat at gmail.com> wrote:

> I mean the configuration was for br-ex as follows:
>
> TYPE=OVSBridge
> DEVICE=br-ex
> DEVICETYPE=ovs
> DEFROUTE=yes
> IPV4_FAILURE_FATAL=no
> ONBOOT=yes
> IPADDR=192.168.43.110
> PREFIX=24
> GATEWAY=192.168.43.1
> DNS=192.168.43.1
> BOOTPROTO=static
> NM_CONTROLLED=no
> IPV4_FAILURE_FATAL=no
> IPV6INIT=yes
> IPV6_AUTOCONF=yes
> IPV6_DEFROUTE=yes
> IPV6_FAILURE_FATAL=no
> PROXY_METHOD=none
> BROWSER_ONLY=no
>
>
>
> On Fri, Jan 25, 2019 at 2:01 AM Amer Hwitat <amer.hwaitat at gmail.com>
> wrote:
>
>> Hi,
>>
>> I have the following issue:
>>
>> [root at localhost neutron]# systemctl status network
>> ● network.service - LSB: Bring up/down networking
>>    Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
>>    Active: active (exited) since Tue 2019-01-22 09:13:04 EST; 58min ago
>>      Docs: man:systemd-sysv-generator(8)
>>   Process: 10275 ExecStart=/etc/rc.d/init.d/network start (code=exited,
>> status=0/SUCCESS)
>>     Tasks: 0
>>
>> Jan 22 09:12:58 localhost.localdomain systemd[1]: Starting LSB: Bring
>> up/down networking...
>> Jan 22 09:12:59 localhost.localdomain network[10275]: Bringing up
>> loopback interface:  [  OK  ]
>> Jan 22 09:12:59 localhost.localdomain ovs-vsctl[10407]:
>> ovs|00001|vsctl|INFO|Called as ovs-vsctl -t 10 -- --may-exist add-br br-ex
>> Jan 22 09:13:04 localhost.localdomain network[10275]: Bringing up
>> interface br-ex:  [  OK  ]
>> Jan 22 09:13:04 localhost.localdomain ovs-vsctl[10573]:
>> ovs|00001|vsctl|INFO|Called as ovs-vsctl -t 10 -- --if-exists del-port
>> br-ex eno16777736 -- add-port...o16777736
>> Jan 22 09:13:04 localhost.localdomain network[10275]: Bringing up
>> interface eno16777736:  [  OK  ]
>> Jan 22 09:13:04 localhost.localdomain systemd[1]: Started LSB: Bring
>> up/down networking.
>> Hint: Some lines were ellipsized, use -l to show in full.
>> [root at localhost neutron]#
>>
>> casue by this configuration of eno16777736 interface on a VM:
>> settings:
>>
>> HWADDR=00:0C:29:37:19:1F
>> TYPE=OVSBridge
>> DEVICE=br-ex
>> DEVICETYPE=ovs
>> DEFROUTE=yes
>> IPV4_FAILURE_FATAL=no
>> UUID=c0addf73-98fe-464c-804a-b40110fd6157
>> ONBOOT=yes
>> IPADDR=192.168.43.110
>> PREFIX=24
>> GATEWAY=192.168.43.1
>> DNS=192.168.43.1
>> BOOTPROTO=static
>> NM_CONTROLLED=no
>> IPV4_FAILURE_FATAL=no
>> IPV6INIT=yes
>> IPV6_AUTOCONF=yes
>> IPV6_DEFROUTE=yes
>> IPV6_FAILURE_FATAL=no
>> PROXY_METHOD=none
>> BROWSER_ONLY=no
>>
>> HWADDR=00:0C:29:37:19:1F
>> TYPE=OVSPort
>> DEVICE=eno16777736
>> DEVICETYPE=ovs
>> UUID=c0addf73-98fe-464c-804a-b40110fd6157
>> OVS_BRIDGE=br-ex
>> BOOTPROTO=none
>> ONBOOT=yes
>> PROMISC=yes
>> PROXY_METHOD=none
>> DEFROUTE=yes
>> PEERDNS=yes
>> PEERROUTES=yes
>> NM_CONTROLLED=no
>> IPV4_FAILURE_FATAL=no
>> IPV6INIT=yes
>> IPV6_AUTOCONF=yes
>> IPV6_DEFROUTE=yes
>> IPV6_FAILURE_FATAL=no
>> NAME=eno16777736
>> PROXY_METHOD=none
>> BROWSER_ONLY=no
>>
>> which causes this bug:
>>
>> [root at localhost log]#
>> Message from syslogd at localhost at Jan 23 02:23:31 ...
>>  kernel:NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s!
>> [ovsdb-server:10088]
>>
>> which crashes the VM or Server CPU to may cause critical situation, and
>> repair , rescue and restore to the server...
>>
>> mentioned in
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1666598
>> https://bugs.launchpad.net/neutron/+bug/1811941
>> https://access.redhat.com/support/cases/#/case/02293077
>> https://postimg.cc/gallery/29c2o4ftu/
>> https://imgur.com/a/X6bEPop
>>
>> by me ... if there is a mis-configuration from my side please reply with
>> remedy solution please ...
>>
>> Best regards
>> Amer Hwitat
>>
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20190125/a93dd68f/attachment-0001.html>