After using the Openvswitch bridging network,
The following tag usually appears on the NIC
Reference bond1 with Ovs-system parameters
[root@ns-compute-209240 ~]# IP Addr list bond1
9:bond1: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> MTU 1500 Qdisc Noqueue Master Ovs-system State up
link/ether 00:e0:ed:29:a6:aa brd ff:ff:ff:ff:ff:ff inet6
: EDFF:FE29:A6AA/64 scope link
valid_lft forever preferred_lft Forever
[root@ns-compute-209240 ~]# IP Addr List Br-bond1
8:br-bond1: <BROADCAST,MULTICAST,UP,LOWER_UP> MTU 1500 Qdisc noqueue State UNKNOWN
Link/ether 00:E0:ED:29:A6:AA BRD ff:ff:ff:ff:ff:ff
inet 240.30.133.240/21 BRD 240.30.135.255 scope global Br-bond1
valid_ LfT Forever Preferred_lft Forever
inet6 fe80::e848:1eff:fe9d:9646/64 scope link
valid_lft forever preferred_ LfT Forever
If the NIC is configured correctly and cannot get the corresponding parameter, it can be considered incorrectly registered in the OVS network
Common failures are caused by the following problems
1 did not perform bonding alias
Workaround:
Echo "Alias Bond1 bonding" >/etc/modprobe.d/bond.conf
2 has already been configured to register before OvS, need to perform recharge
Reset method
Ovs-vsctl emer-reset
ovs-vsctl init
rm-rf/etc/openvswitch/*