Cloud Host Configuration Docker Bridge, reverse configuration, restart NIC, cause physical NIC not working properly

Source: Internet
Author: User

1, physical machine configuration, eth0,eth1 configuration bonding,bonding as bridge physical network card, in the generation of bond0 as a physical machine management port
2, virtual machine configuration, eth1 as bridge virtual NIC br500, eth0 configure normal NIC IP
3, because Eth0 is a Web segment, eth1 DB segment, reverse configuration, restart the network card, the following problems occur
4, related error log:
An  3 14:46:41 localhost kernel: device vnet0 entered promiscuous  modejan  3 14:46:41 localhost kernel: br100: port 2 (vnet0)   Entering forwarding statejan  3 14:46:41 localhost kernel: device  vnet1 entered promiscuous modejan  3 14:46:41 localhost kernel:  br101: port 2 (VNET1)  entering forwarding statejan  3 14:46:56  localhost kernel: __ratelimit: 23 callbacks suppressedJan  3  14:46:56 localhost kernel: kvm: 27962: cpu0 unhandled wrmsr: 0x391  data 2000000fJan  3 14:46:56 localhost kernel: kvm: 27962:  cpu2 unhandled wrmsr: 0x391 data 2000000fjan  3 14:46:56  LOCALHOST KERNEL: BR100: port 2 (vnet0)  entering forwarding statejan  3 14:46:56 localhost  kernel: br101: port 2 (VNET1)  entering forwarding statejan  3  14:50:02 localhost kernel: __ratelimit: 91391 callbacks suppressedjan   3 14:50:02 localhost kernel: vnet0: received packet with  Own address as source addressjan  3 14:50:02 localhost kernel:  vnet0: received packet with own address as source addressjan   3 14:50:02 localhost kernel: vnet0: received packet with  Own address as source addressjan  3 14:50:02 localhost kernel:  vnet0: received packet with own address as source addressjan   3 14:50:02 loCalhost kernel: vnet0: received packet with own address as source  addressjan  3 14:50:02 localhost kernel: vnet0: received packet  with own address as source addressjan  3 14:50:02 localhost  kernel: vnet0: received packet with own address as source  addressjan  3 14:50:02 localhost kernel: vnet0: received packet  with own address as source addressjan  3 14:50:02 localhost  kernel: vnet0: received packet with own address as source  addressjan  3 14:50:02 localhost kernel: vnet0: received packet  With own address as source address
Workaround: 1, before restarting the NIC, you need to remove the old bridge configuration ifconfig br500 down brctl delbr br500 ifdown eth1 Systemctl Stop Network.service systemctl start Network.service 2, restart the cloud host directly

This article from "Welcome comments, Welcome to like" blog, please be sure to keep this source http://swq499809608.blog.51cto.com/797714/1598870

Cloud Host Configuration Docker Bridge, reverse configuration, restart NIC, cause physical NIC not working properly

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.