[ovs-discuss] restarting openvswitch leaves ovs bridge down and with no IP

EDGAR CANTU eocantu at us.ibm.com
Wed Jan 27 22:04:49 UTC 2016


Hello,

The openvswitch version on master seems to be wiping out the bridge's IP
when openvswitch gets restarted and it is only after restarting network
services that the IP comes back.
I'm using commit 6872bf1eb7e46f9c202d512aa5ca6d99fe35d23e
I've also verified that I don' see this issue with versions 2.3.1 and 2.4.0

Here are the network-scripts I have:

# cat ifcfg-enp0s9
DEVICE=enp0s9
ONBOOT=yes
DEVICETYPE=ovs
TYPE=OVSPort
OVS_BRIDGE=br-ex
BOOTPROTO=none
HOTPLUG=no

# cat ifcfg-br-ex
DEVICE=br-ex
ONBOOT=yes
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=static
IPADDR=192.168.2.103
NETMASK=255.255.255.0
HOTPLUG=no


Before restarting openvswitch:
-------------------------

# ovs-vsctl show
d69922d5-097e-4b66-bd70-3cd568a35989
    Bridge br-ex
        Port br-ex
            Interface br-ex
                type: internal
        Port "enp0s9"
            Interface "enp0s9"
    ovs_version: "2.5.90"

# ovs-ofctl show br-ex
OFPT_FEATURES_REPLY (xid=0x2): dpid:000008002798f8e5
n_tables:254, n_buffers:256
capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan mod_dl_src
mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos mod_tp_src mod_tp_dst
 2(enp0s9): addr:08:00:27:98:f8:e5
     config:     0
     state:      0
     current:    1GB-FD COPPER AUTO_NEG
     advertised: 10MB-HD 10MB-FD 100MB-HD 100MB-FD 1GB-FD COPPER AUTO_NEG
     supported:  10MB-HD 10MB-FD 100MB-HD 100MB-FD 1GB-FD COPPER AUTO_NEG
     speed: 1000 Mbps now, 1000 Mbps max
 LOCAL(br-ex): addr:08:00:27:98:f8:e5
     config:     0
     state:      0
     speed: 0 Mbps now, 0 Mbps max
OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0

# ip addr
4: enp0s9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
master ovs-system state UP qlen 1000
    link/ether 08:00:27:98:f8:e5 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::a00:27ff:fe98:f8e5/64 scope link
       valid_lft forever preferred_lft forever
7: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UNKNOWN
    link/ether 08:00:27:98:f8:e5 brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.103/24 brd 192.168.2.255 scope global br-ex
       valid_lft forever preferred_lft forever
    inet6 fe80::f0d3:52ff:fee7:7e4a/64 scope link
       valid_lft forever preferred_lft forever



After restarting openvswitch:
------------------------

# ovs-ofctl show br-ex
OFPT_FEATURES_REPLY (xid=0x2): dpid:000008002798f8e5
n_tables:254, n_buffers:256
capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan mod_dl_src
mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos mod_tp_src mod_tp_dst
 2(enp0s9): addr:08:00:27:98:f8:e5
     config:     0
     state:      0
     current:    1GB-FD COPPER AUTO_NEG
     advertised: 10MB-HD 10MB-FD 100MB-HD 100MB-FD 1GB-FD COPPER AUTO_NEG
     supported:  10MB-HD 10MB-FD 100MB-HD 100MB-FD 1GB-FD COPPER AUTO_NEG
     speed: 1000 Mbps now, 1000 Mbps max
 LOCAL(br-ex): addr:08:00:27:98:f8:e5
     config:     PORT_DOWN
     state:      LINK_DOWN
     speed: 0 Mbps now, 0 Mbps max
OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0

# ovs-vsctl show
d69922d5-097e-4b66-bd70-3cd568a35989
    Bridge br-ex
        Port br-ex
            Interface br-ex
                type: internal
        Port "enp0s9"
            Interface "enp0s9"
    ovs_version: "2.5.90"

# ip addr
4: enp0s9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
master ovs-system state UP qlen 1000
    link/ether 08:00:27:98:f8:e5 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::a00:27ff:fe98:f8e5/64 scope link
       valid_lft forever preferred_lft forever
8: br-ex: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
    link/ether 08:00:27:98:f8:e5 brd ff:ff:ff:ff:ff:ff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20160127/a7269018/attachment-0002.html>


More information about the discuss mailing list