/var/log/messages during network restart: Nov 12 11:54:53 GZ-NS-C1-POOL-kvm-ops-150 kernel: br1: port 1(eth2) entering disabled state Nov 12 11:54:54 GZ-NS-C1-POOL-kvm-ops-150 kernel: bonding: bond0: Removing slave eth0 Nov 12 11:54:54 GZ-NS-C1-POOL-kvm-ops-150 kernel: bonding: bond0: Warning: the permanent HWaddr of eth0 - ec:f4:bb:c4:3e:90 - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts. Nov 12 11:54:54 GZ-NS-C1-POOL-kvm-ops-150 kernel: bonding: bond0: releasing active interface eth0 Nov 12 11:54:54 GZ-NS-C1-POOL-kvm-ops-150 kernel: bond0: mixed no checksumming and other settings. Nov 12 11:54:54 GZ-NS-C1-POOL-kvm-ops-150 kernel: device eth0 left promiscuous mode Nov 12 11:54:54 GZ-NS-C1-POOL-kvm-ops-150 kernel: bonding: bond0: making interface eth1 the new active one. Nov 12 11:54:54 GZ-NS-C1-POOL-kvm-ops-150 kernel: device eth1 entered promiscuous mode Nov 12 11:54:54 GZ-NS-C1-POOL-kvm-ops-150 kernel: bonding: bond0: Removing slave eth1 Nov 12 11:54:54 GZ-NS-C1-POOL-kvm-ops-150 kernel: bonding: bond0: releasing active interface eth1 Nov 12 11:54:54 GZ-NS-C1-POOL-kvm-ops-150 kernel: device eth1 left promiscuous mode Nov 12 11:54:54 GZ-NS-C1-POOL-kvm-ops-150 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -t 10 -- --if-exists del-port ovsbr0 bond0 Nov 12 11:54:54 GZ-NS-C1-POOL-kvm-ops-150 kernel: device bond0 left promiscuous mode Nov 12 11:54:54 GZ-NS-C1-POOL-kvm-ops-150 ovs-vswitchd: ovs|00072|bridge|INFO|bridge ovsbr0: using datapath ID 0000c2f9be679645 Nov 12 11:54:54 GZ-NS-C1-POOL-kvm-ops-150 kernel: device eth2 left promiscuous mode Nov 12 11:54:54 GZ-NS-C1-POOL-kvm-ops-150 kernel: br1: port 1(eth2) entering disabled state Nov 12 11:54:55 GZ-NS-C1-POOL-kvm-ops-150 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -t 10 -- --if-exists del-br ovsbr0 Nov 12 11:54:55 GZ-NS-C1-POOL-kvm-ops-150 kernel: device ovsbr0 left promiscuous mode Nov 12 11:54:55 GZ-NS-C1-POOL-kvm-ops-150 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -t 10 -- --if-exists del-br ovsbr0 Nov 12 11:54:55 GZ-NS-C1-POOL-kvm-ops-150 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -t 10 -- --may-exist add-br ovsbr0 Nov 12 11:54:55 GZ-NS-C1-POOL-kvm-ops-150 ovs-vswitchd: ovs|00073|ofproto_dpif|INFO|system@ovs-system: Datapath supports recirculation Nov 12 11:54:55 GZ-NS-C1-POOL-kvm-ops-150 ovs-vswitchd: ovs|00074|ofproto_dpif|INFO|system@ovs-system: MPLS label stack length probed as 0 Nov 12 11:54:55 GZ-NS-C1-POOL-kvm-ops-150 ovs-vswitchd: ovs|00075|ofproto_dpif|INFO|system@ovs-system: datapath does not support masked set action feature. Nov 12 11:54:55 GZ-NS-C1-POOL-kvm-ops-150 ovs-vswitchd: ovs|00076|ofproto_dpif|INFO|system@ovs-system: Datapath does not support unique flow ids Nov 12 11:54:55 GZ-NS-C1-POOL-kvm-ops-150 kernel: openvswitch: netlink: Key attribute has unexpected length (type=21, length=4, expected=0). Nov 12 11:54:55 GZ-NS-C1-POOL-kvm-ops-150 ovs-vswitchd: ovs|00001|ofproto_dpif_upcall(handler290)|INFO|received packet on unassociated datapath port 0 Nov 12 11:54:55 GZ-NS-C1-POOL-kvm-ops-150 ovs-vswitchd: ovs|00077|bridge|INFO|bridge ovsbr0: added interface ovsbr0 on port 65534 Nov 12 11:54:55 GZ-NS-C1-POOL-kvm-ops-150 kernel: device ovsbr0 entered promiscuous mode Nov 12 11:54:56 GZ-NS-C1-POOL-kvm-ops-150 ovs-vswitchd: ovs|00078|bridge|INFO|bridge ovsbr0: using datapath ID 000032137010614a Nov 12 11:54:56 GZ-NS-C1-POOL-kvm-ops-150 ovs-vswitchd: ovs|00079|connmgr|INFO|ovsbr0: added service controller "punix:/usr/var/run/openvswitch/ovsbr0.mgmt" Nov 12 11:54:58 GZ-NS-C1-POOL-kvm-ops-150 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready Nov 12 11:54:58 GZ-NS-C1-POOL-kvm-ops-150 kernel: 8021q: adding VLAN 0 to HW filter on device bond0 Nov 12 11:54:58 GZ-NS-C1-POOL-kvm-ops-150 kernel: bonding: bond0: Adding slave eth0. Nov 12 11:54:58 GZ-NS-C1-POOL-kvm-ops-150 kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Nov 12 11:54:58 GZ-NS-C1-POOL-kvm-ops-150 kernel: bond0: mixed no checksumming and other settings. Nov 12 11:54:58 GZ-NS-C1-POOL-kvm-ops-150 kernel: bonding: bond0: enslaving eth0 as a backup interface with a down link. Nov 12 11:54:58 GZ-NS-C1-POOL-kvm-ops-150 kernel: bonding: bond0: Adding slave eth1. Nov 12 11:54:58 GZ-NS-C1-POOL-kvm-ops-150 kernel: 8021q: adding VLAN 0 to HW filter on device eth1 Nov 12 11:54:58 GZ-NS-C1-POOL-kvm-ops-150 kernel: bond0: mixed no checksumming and other settings. Nov 12 11:54:58 GZ-NS-C1-POOL-kvm-ops-150 kernel: bonding: bond0: enslaving eth1 as a backup interface with a down link. Nov 12 11:54:58 GZ-NS-C1-POOL-kvm-ops-150 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready Nov 12 11:54:58 GZ-NS-C1-POOL-kvm-ops-150 kernel: 8021q: adding VLAN 0 to HW filter on device bond0 Nov 12 11:54:58 GZ-NS-C1-POOL-kvm-ops-150 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -t 10 -- --may-exist add-port ovsbr0 bond0 Nov 12 11:54:58 GZ-NS-C1-POOL-kvm-ops-150 kernel: device bond0 entered promiscuous mode Nov 12 11:54:58 GZ-NS-C1-POOL-kvm-ops-150 ovs-vswitchd: ovs|00080|bridge|INFO|bridge ovsbr0: added interface bond0 on port 1 Nov 12 11:54:58 GZ-NS-C1-POOL-kvm-ops-150 ovs-vswitchd: ovs|00081|bridge|INFO|bridge ovsbr0: using datapath ID 0000ecf4bbc43e90 Nov 12 11:54:58 GZ-NS-C1-POOL-kvm-ops-150 kernel: ADDRCONF(NETDEV_UP): eth2: link is not ready Nov 12 11:54:58 GZ-NS-C1-POOL-kvm-ops-150 kernel: 8021q: adding VLAN 0 to HW filter on device eth2 Nov 12 11:54:58 GZ-NS-C1-POOL-kvm-ops-150 kernel: device eth2 entered promiscuous mode Nov 12 11:55:01 GZ-NS-C1-POOL-kvm-ops-150 kernel: igb 0000:01:00.0: eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Nov 12 11:55:01 GZ-NS-C1-POOL-kvm-ops-150 kernel: bond0: link status definitely up for interface eth0, 1000 Mbps full duplex. Nov 12 11:55:01 GZ-NS-C1-POOL-kvm-ops-150 kernel: bonding: bond0: making interface eth0 the new active one. Nov 12 11:55:01 GZ-NS-C1-POOL-kvm-ops-150 kernel: device eth0 entered promiscuous mode Nov 12 11:55:01 GZ-NS-C1-POOL-kvm-ops-150 kernel: bonding: bond0: first active interface up! Nov 12 11:55:01 GZ-NS-C1-POOL-kvm-ops-150 kernel: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready Nov 12 11:55:01 GZ-NS-C1-POOL-kvm-ops-150 kernel: igb 0000:01:00.2: eth2: igb: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Nov 12 11:55:01 GZ-NS-C1-POOL-kvm-ops-150 kernel: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready Nov 12 11:55:01 GZ-NS-C1-POOL-kvm-ops-150 kernel: br1: port 1(eth2) entering forwarding state Nov 12 11:55:01 GZ-NS-C1-POOL-kvm-ops-150 kernel: igb 0000:01:00.1: eth1: igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Nov 12 11:55:02 GZ-NS-C1-POOL-kvm-ops-150 kernel: bond0: link status definitely up for interface eth1, 1000 Mbps full duplex.
On 12 November 2015 at 11:45, Tashi Lu <[email protected]> wrote: > Update: > Since there are too many messages, I cleaned the ovs-vswitchd.log and > found these after I restart network, > 2015-11-12T03:18:20.337Z|594939|dpif(revalidator406)|WARN|Dropped 3 log > messages in last 1 seconds (most recently, 1 seconds ago) due to excessive > rate > 2015-11-12T03:18:20.338Z|594940|dpif(revalidator406)|WARN|system@ovs-system: > get_stats failed (No such file or directory) > 2015-11-12T03:18:20.338Z|594941|netlink_socket(revalidator406)|INFO|Dropped > 1 log messages in last 1 seconds (most recently, 1 seconds ago) due to > excessive rate > 2015-11-12T03:18:20.338Z|594942|netlink_socket(revalidator406)|INFO|netlink > dump request error (No such file or directory) > 2015-11-12T03:18:20.725Z|05099|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on > ovsbr0 device failed: No such device > 2015-11-12T03:18:20.729Z|05100|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on > ovsbr0 device failed: No such device > 2015-11-12T03:18:21.337Z|594943|dpif(revalidator406)|WARN|Dropped 3 log > messages in last 1 seconds (most recently, 1 seconds ago) due to excessive > rate > 2015-11-12T03:18:21.337Z|594944|dpif(revalidator406)|WARN|system@ovs-system: > get_stats failed (No such file or directory) > 2015-11-12T03:18:21.337Z|594945|netlink_socket(revalidator406)|INFO|Dropped > 1 log messages in last 1 seconds (most recently, 1 seconds ago) due to > excessive rate > 2015-11-12T03:18:21.337Z|594946|netlink_socket(revalidator406)|INFO|netlink > dump request error (No such file or directory) > > "on ovsbr0 device failed, no such device"? But after restart, ovsbr0 was > up. And why those "No such file or directory"s? > > On 12 November 2015 at 11:02, Tashi Lu <[email protected]> wrote: > >> By the way, I just saw some one with the same situation: >> http://website-humblec.rhcloud.com/configure-openvswitch-in-virt-environment/ >> search with 'lost' you'll see that comment. >> >> And he used Ubuntu, so this problem is platform irrelevant. I'm guessing >> misconfiguration now. But I don't know where I did wrong. Here are my >> ifcfgs: >> >> ifcfg-bond0: >> DEVICE=bond0 >> ONBOOT=yes >> BOOTPROTO=none >> TYPE=OVSPort >> DEVICETYPE=ovs >> OVS_BRIDGE=ovsbr0 >> >> ifcfg-ovsbr0: >> IPADDR=10.3.150.20 >> NETMASK=255.255.255.0 >> DEVICE=ovsbr0 >> TYPE=OVSBridge >> DEVICETYPE=ovs >> ONBOOT=yes >> BOOT_PROTO=static >> >> >> On 12 November 2015 at 10:42, Tashi Lu <[email protected]> wrote: >> >>> Hi blp, Shetty, >>> >>> Sorry for my late reply. >>> uname -a: 2.6.32-504.el6.x86_64 #1 SMP Wed Oct 15 04:27:16 UTC 2014 >>> x86_64 x86_64 x86_64 GNU/Linux >>> >>> before restarting network: >>> [[email protected] openvswitch]# ovs-vsctl show >>> c5ee1b0f-e7ec-4c73-a3fa-c79662619cba >>> Bridge "ovsbr0" >>> Port "v5254007ec542" >>> tag: 142 >>> Interface "v5254007ec542" >>> Port "bond0" >>> Interface "bond0" >>> Port "ovsbr0" >>> tag: 150 >>> Interface "ovsbr0" >>> type: internal >>> >>> after: http://imgur.com/jU4CY2i (sorry for a image link, because the >>> network was lost I had to use virtual console thus unable to copy text) >>> >>> We can see both the vlan tag and the port I created for a virtual >>> machine was lost after the network restart. >>> I think it might be related to /etc/sysconfig/network-scripts/ifup-ovs, >>> since this is the only point ovs relates to `service network restart`. >>> >>> And there are no special logs in ovs-ctl.log, ovsdb-server.log, and >>> ovs-vswitchd.log. But my ovs-vswitchd.log keeps logging following lines >>> every second, is this relevant?: >>> >>> 2015-11-12T02:33:57.516Z|584314|dpif(revalidator406)|WARN|Dropped 3 log >>> messages in last 1 seconds (most recently, 1 seconds ago) due to excessive >>> rate >>> >>> 2015-11-12T02:33:57.516Z|584315|dpif(revalidator406)|WARN|system@ovs-system: >>> get_stats failed (No such file or directory) >>> 2015-11-12T02:33:57.516Z|584316|netlink_socket(revalidator406)|INFO|Dropped >>> 1 log messages in last 1 seconds (most recently, 1 seconds ago) due to >>> excessive rate >>> 2015-11-12T02:33:57.516Z|584317|netlink_socket(revalidator406)|INFO|netlink >>> dump request error (No such file or directory) >>> 2015-11-12T02:33:58.518Z|584318|dpif(revalidator406)|WARN|Dropped 3 log >>> messages in last 1 seconds (most recently, 1 seconds ago) due to excessive >>> rate >>> >>> 2015-11-12T02:33:58.518Z|584319|dpif(revalidator406)|WARN|system@ovs-system: >>> get_stats failed (No such file or directory) >>> 2015-11-12T02:33:58.518Z|584320|netlink_socket(revalidator406)|INFO|Dropped >>> 1 log messages in last 1 seconds (most recently, 1 seconds ago) due to >>> excessive rate >>> 2015-11-12T02:33:58.518Z|584321|netlink_socket(revalidator406)|INFO|netlink >>> dump request error (No such file or directory) >>> 2015-11-12T02:33:59.520Z|584322|dpif(revalidator406)|WARN|Dropped 3 log >>> messages in last 1 seconds (most recently, 1 seconds ago) due to excessive >>> rate >>> >>> 2015-11-12T02:33:59.520Z|584323|dpif(revalidator406)|WARN|system@ovs-system: >>> get_stats failed (No such file or directory) >>> 2015-11-12T02:33:59.520Z|584324|netlink_socket(revalidator406)|INFO|Dropped >>> 1 log messages in last 1 seconds (most recently, 1 seconds ago) due to >>> excessive rate >>> 2015-11-12T02:33:59.520Z|584325|netlink_socket(revalidator406)|INFO|netlink >>> dump request error (No such file or directory) >>> 2015-11-12T02:34:00.520Z|584326|dpif(revalidator406)|WARN|Dropped 3 log >>> messages in last 1 seconds (most recently, 1 seconds ago) due to excessive >>> rate >>> >>> 2015-11-12T02:34:00.520Z|584327|dpif(revalidator406)|WARN|system@ovs-system: >>> get_stats failed (No such file or directory) >>> 2015-11-12T02:34:00.520Z|584328|netlink_socket(revalidator406)|INFO|Dropped >>> 1 log messages in last 1 seconds (most recently, 1 seconds ago) due to >>> excessive rate >>> 2015-11-12T02:34:00.520Z|584329|netlink_socket(revalidator406)|INFO|netlink >>> dump request error (No such file or directory) >>> >>> On 11 November 2015 at 03:28, Ben Pfaff <[email protected]> wrote: >>> >>>> On Tue, Nov 10, 2015 at 08:52:19PM +0800, Tashi Lu wrote: >>>> > I set a tag on a port, but once I restart the network service, e.g. >>>> > /etc/init.d/network restart, the tag will be lost, tested on both >>>> 2.3.2 and >>>> > 2.4.0. Is this normal? How can I make vlan tag persistent? >>>> >>>> No, that doesn't make sense. >>>> >>>> How are you setting up your configuration? >>>> >>> >>> >> >
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
