云主机配置Docker Bridge,在重新颠倒配置,重启网卡,导致物理网卡不正常工作
2015-01-04 10:10
330 查看
1,物理机配置,eth0,eth1 配置bonding,bonding 作为bridge 物理网卡,在生成bond0 作为物理机管理口
2,虚拟机配置,eth1 作为bridge 虚拟网卡br500, eth0 配置正常网卡IP
3, 因eth0 为WEB 段, eth1 为DB 段,需颠倒配置,重启网卡,出现以下问题
4,相关错误日志:
an 3 14:46:41 localhost kernel: device vnet0 entered promiscuous mode Jan 3 14:46:41 localhost kernel: br100: port 2(vnet0) entering forwarding state Jan 3 14:46:41 localhost kernel: device vnet1 entered promiscuous mode Jan 3 14:46:41 localhost kernel: br101: port 2(vnet1) entering forwarding state Jan 3 14:46:56 localhost kernel: __ratelimit: 23 callbacks suppressed Jan 3 14:46:56 localhost kernel: kvm: 27962: cpu0 unhandled wrmsr: 0x391 data 2000000f Jan 3 14:46:56 localhost kernel: kvm: 27962: cpu2 unhandled wrmsr: 0x391 data 2000000f Jan 3 14:46:56 localhost kernel: br100: port 2(vnet0) entering forwarding state Jan 3 14:46:56 localhost kernel: br101: port 2(vnet1) entering forwarding state Jan 3 14:50:02 localhost kernel: __ratelimit: 91391 callbacks suppressed Jan 3 14:50:02 localhost kernel: vnet0: received packet with own address as source address Jan 3 14:50:02 localhost kernel: vnet0: received packet with own address as source address Jan 3 14:50:02 localhost kernel: vnet0: received packet with own address as source address Jan 3 14:50:02 localhost kernel: vnet0: received packet with own address as source address Jan 3 14:50:02 localhost kernel: vnet0: received packet with own address as source address Jan 3 14:50:02 localhost kernel: vnet0: received packet with own address as source address Jan 3 14:50:02 localhost kernel: vnet0: received packet with own address as source address Jan 3 14:50:02 localhost kernel: vnet0: received packet with own address as source address Jan 3 14:50:02 localhost kernel: vnet0: received packet with own address as source address Jan 3 14:50:02 localhost kernel: vnet0: received packet with own address as source address
解决办法: 1,在重启网卡之前,需要删除老的bridge 配置 ifconfig br500 down brctl delbr br500 ifdown eth1 systemctl stop network.service systemctl start network.service 2, 直接重启云主机
相关文章推荐
- 一台linux机器配置多个物理网卡,导致的上不了网的问题
- java环境配置为1.7jdk为什么cmd java -version查看版本是1.8||win7 java(tm) platform se binary 已停止工作 出现了一个问题,导致程序停止正常
- docker环境hosts配置错误导致的tomcat无法正常启动
- docker修改配置文件导致无法正常使用
- 测试Linux网卡是否正常工作
- 修复错误配置fstab文件导致系统无法正常启动
- Linux双网卡配置两个网关导致网络无法使用
- 物理网卡在ESXi/ESX服务器中的推荐配置方式
- BurstNET的linux vps 安装Kloxo面板后一切正常 今天重启导致错误Could not connect to Mysql server
- 备份的网卡配置文件导致网络故障
- 怎样让webservice 和struts2正常工作(web.xml的配置)
- 虚拟机bridge模式下每次启动都需要重新激活网卡
- 为什么在LINUX9中配置好的IP和网关一重启就得重新配置!
- 使网卡配置马上生效,不用重启机器(/etc/rc.d/init.d/network restart )
- msn问题 windows live messenger已停止工作,出现了一个问题,导致程序停止正常工作
- 某数据库pmon进程无法正常工作导致宕机的事故
- 网卡配置导致的网络性能问题
- 基于WEB服务器导致消息中心各组件之间无法正常工作的问题分析与解决
- Exchange不正常卸载导致无法重新安装
- 卡巴斯基导致SVN不能正常工作