服务器
Linux服务器更换主板后网络不通是什么原因?怎么解决?
必易
2025-12-04
6分钟前

遇到问题:
Linux服务器主板故障,更换完新主板后,发现服务器上的管理ip不通了,业务ip和存储ip正常。
分析原因:
1、从服务器的业务ip通过ssh登录上去检查
1.1ping同一网段的其它ip地址,发现确实不通
1.2使用ip addr命令查看ip地址信息

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet 127.0.0.1/8 scope host lovalid_lft forever preferred_lft foreverinet6 ::1/128 scope hostvalid_lft forever preferred_lft forever2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000link/ether 70:fd:45:7d:70:96 brd ff:ff:ff:ff:ff:ff3: ens1f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond2 state UP group default qlen 1000link/ether cc:05:77:c8:15:23 brd ff:ff:ff:ff:ff:ff4: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000link/ether 70:fd:45:7d:70:97 brd ff:ff:ff:ff:ff:ff5: ens1f1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1450 qdisc mq master bond1 state UP group default qlen 1000link/ether cc:05:77:c8:15:22 brd ff:ff:ff:ff:ff:ff6: eno3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000link/ether 70:fd:45:7d:70:98 brd ff:ff:ff:ff:ff:ff7: eno4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000link/ether 70:fd:45:7d:70:99 brd ff:ff:ff:ff:ff:ff8: bond2: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000link/ether cc:05:77:c8:15:23 brd ff:ff:ff:ff:ff:ffinet 10.220.245.86/27 brd 10.220.245.95 scope global noprefixroute bond2valid_lft forever preferred_lft foreverinet6 fe80::ce05:77ff:fec8:1523/64 scope linkvalid_lft forever preferred_lft forever9: bond1: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP group default qlen 1000link/ether cc:05:77:c8:15:22 brd ff:ff:ff:ff:ff:ffinet 10.230.173.60/28 brd 10.230.173.63 scope global dynamic noprefixroute bond1valid_lft 857042sec preferred_lft 857042secinet6 2409:8004:5cc0:bb01:0:ae6:ad30:5/128 scope global dynamic noprefixroutevalid_lft 97602sec preferred_lft 97602secinet6 fe80::ce05:77ff:fec8:1522/64 scope link noprefixroutevalid_lft forever preferred_lft forever10: bond0: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000link/ether cc:05:77:c8:15:24 brd ff:ff:ff:ff:ff:ffinet 10.220.210.86/26 brd 10.220.210.127 scope global noprefixroute bond0valid_lft forever preferred_lft forever 从ip addr输出可以看到当前状态: bond1: UP状态正常 bond2: UP状态正常 ens1f1: SLAVE状态,绑定到bond1 ens1f0: SLAVE状态,绑定到bond2 bond0:DOWN状态异常 eno3: UP状态正常,但未绑定到任何bond网卡 eno4: UP状态正常,但未绑定到任何bond网卡 eno1: UP状态正常,但未绑定到任何bond网卡 eno2: UP状态正常,但未绑定到任何bond网卡 从上面的信息可以判断,服务器上总共有6张网卡,并且还做了网卡聚合,多个物理网卡聚合成一个逻辑接口,bond0、bond1、bond2 就是聚合接口。
1.3继续查看网卡端口信息
cd /etc/sysconfig/network-scriptscat ifcfg-bond0DEVICE=bond0NAME=bond0TYPE=BondBONDING_MASTER=yesIPADDR=10.220.210.86GATEWAY=10.220.210.65NETMASK=255.255.255.192ONBOOT=yesBOOTPROTO=static #Maybe use dhcpIPV4_ROUTE_METRIC=1000NM_CONTROLLED=yesPEERDNS=noMACADDR=cc:05:77:c8:15:24IPV6INIT=noIPV6ADDR=IPV6_DEFAULTGW=DHCPV6C=noBONDING_OPTS='mode=4 miimon=100 use_carrier=1'cat ifcfg-bond1DEVICE=bond1NAME=bond1TYPE=BondBONDING_MASTER=yesIPADDR=GATEWAY=NETMASK=ONBOOT=yesBOOTPROTO=dhcp #Maybe use dhcpIPV4_ROUTE_METRIC=0NM_CONTROLLED=yesPEERDNS=noMACADDR=cc:05:77:c8:15:22IPV6INIT=yesIPV6ADDR=IPV6_DEFAULTGW=DHCPV6C=yesBONDING_OPTS='mode=4 miimon=100 use_carrier=1'cat ifcfg-bond2DEVICE=bond2NAME=bond2TYPE=BondBONDING_MASTER=yesIPADDR=10.220.245.86GATEWAY=10.220.245.65NETMASK=255.255.255.224ONBOOT=yesBOOTPROTO=static #Maybe use dhcpIPV4_ROUTE_METRIC=2000NM_CONTROLLED=yesPEERDNS=noMACADDR=cc:05:77:c8:15:23IPV6INIT=noIPV6ADDR=IPV6_DEFAULTGW=DHCPV6C=noBONDING_OPTS='mode=4 miimon=100 use_carrier=1'cat ifcfg-eno1DEVICE=eno1NAME=bond1-slave-eno1HWADDR=cc:05:77:c8:15:22TYPE=EthernetBOOTPROTO=noneONBOOT=yesMASTER=bond1SLAVE=yesNM_CONTROLLED=yescat ifcfg-eno2DEVICE=eno2NAME=bond2-slave-eno2HWADDR=cc:05:77:c8:15:23TYPE=EthernetBOOTPROTO=noneONBOOT=yesMASTER=bond2SLAVE=yesNM_CONTROLLED=yescat ifcfg-eno3DEVICE=eno3NAME=bond0-slave-eno3HWADDR=cc:05:77:c8:15:24TYPE=EthernetBOOTPROTO=noneONBOOT=yesMASTER=bond0SLAVE=yesNM_CONTROLLED=yescat ifcfg-eno4DEVICE=eno4NAME=bond0-slave-eno4HWADDR=cc:05:77:c8:15:25TYPE=EthernetBOOTPROTO=noneONBOOT=yesMASTER=bond0SLAVE=yesNM_CONTROLLED=yescat ifcfg-ens1f0DEVICE=ens1f0NAME=bond2-slave-ens1f0HWADDR=cc:05:77:ee:1e:51TYPE=EthernetBOOTPROTO=noneONBOOT=yesMASTER=bond2SLAVE=yesNM_CONTROLLED=yescat ifcfg-ens1f1DEVICE=ens1f1NAME=bond1-slave-ens1f1HWADDR=cc:05:77:ee:1e:52TYPE=EthernetBOOTPROTO=noneONBOOT=yesMASTER=bond1SLAVE=yesNM_CONTROLLED=yes 从上面的信息可以分析出端口聚合配置是: 管理bond0:物理网卡eno3+eno4 业务bond1:物理网卡eno1+ens1f1 存储bond2:物理网卡eno2+ens1f0
1.4查看6张物理网卡的当前MAC地址
#查看网卡的硬件MAC地址ethtool -P eno1ethtool -P eno2ethtool -P eno3ethtool -P eno4ethtool -P ens1f0ethtool -P ens1f1ethtool -P eno1Permanent address: 70:fd:45:7d:70:96ethtool -P eno2Permanent address: 70:fd:45:7d:70:97ethtool -P eno3Permanent address: 70:fd:45:7d:70:98thtool -P eno4Permanent address: 70:fd:45:7d:70:99ethtool -P ens1f0Permanent address: cc:05:77:ee:1e:51ethtool -P ens1f1Permanent address: cc:05:77:ee:1e:52 从上面的信息可以分析得到: 物理网卡eno1、eno2、eno3、eno4的MAC地址和网卡配置文件里面的MAC地址不一致。 物理网卡ens1f0、ens1f1的MAC地址和网卡配置文件里面的MAC地址一致。 由于是服务器更换主板后出现的问题,由此可以判断出物理网卡eno1、eno2、eno3、eno4是服务器板载网卡。 主板更换后,板载网卡也一起更换了,MAC地址也就发生了变化,而配置文件里面还是旧的MAC地址。 物理网卡ens1f0和ens1f1单独的硬件,更换主板不影响MAC地址。 管理bond0:物理网卡eno3+eno4聚合,这2个网卡MAC地址都变了,所以bond0网络不通了。 业务bond1:物理网卡eno1+ens1f1聚合,ens1f1这个MAC地址未发生变化,所以bond1还可以通,失去了高可用。 存储bond2:物理网卡eno2+ens1f0聚合,ens1f0这个MAC地址未发生变化,所以bond2还可以通,失去了高可用。
解决办法:
1、修改物理网卡eno1、eno2、eno3、eno4配置文件里面的HWADDR地址为当前的真实MAC地址。
cd /etc/sysconfig/network-scriptssed -i 's/^HWADDR=.*/HWADDR=70:fd:45:7d:70:96/' ifcfg-eno1sed -i 's/^HWADDR=.*/HWADDR=70:fd:45:7d:70:97/' ifcfg-eno2sed -i 's/^HWADDR=.*/HWADDR=70:fd:45:7d:70:98/' ifcfg-eno3sed -i 's/^HWADDR=.*/HWADDR=70:fd:45:7d:70:99/' ifcfg-eno4
2、重启bond0
nmcli con reload #重新加载配置文件nmcli con down bond0 #停止bond0nmcli con up bond0 #重新激活bond0#重启网络systemctl restart NetworkManager
3、查看 bond0 接口详细状态信息
cat /proc/net/bonding/bond0Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)Bonding Mode: IEEE 802.3ad Dynamic link aggregationTransmit Hash Policy: layer2 (0)MII Status: upMII Polling Interval (ms): 100Up Delay (ms): 0Down Delay (ms): 0Peer Notification Delay (ms): 0802.3ad infoLACP rate: slowMin links: 0Aggregator selection policy (ad_select): stableSystem priority: 65535System MAC address: cc:05:77:c8:15:24Active Aggregator Info:Aggregator ID: 1Number of ports: 2Actor Key: 9Partner Key: 13Partner Mac Address: 90:5d:7c:ed:bc:e8Slave Interface: eno3MII Status: upSpeed: 1000 MbpsDuplex: fullLink Failure Count: 0Permanent HW addr: 70:fd:45:7d:70:98Slave queue ID: 0Aggregator ID: 1Actor Churn State: nonePartner Churn State: noneActor Churned Count: 0Partner Churned Count: 0details actor lacp pdu:system priority: 65535system mac address: cc:05:77:c8:15:24port key: 9port priority: 255port number: 1port state: 61details partner lacp pdu:system priority: 32768system mac address: 90:5d:7c:ed:bc:e8oper key: 13port priority: 32768port number: 29port state: 61Slave Interface: eno4MII Status: upSpeed: 1000 MbpsDuplex: fullLink Failure Count: 0Permanent HW addr: 70:fd:45:7d:70:99Slave queue ID: 0Aggregator ID: 1Actor Churn State: nonePartner Churn State: noneActor Churned Count: 0Partner Churned Count: 0details actor lacp pdu:system priority: 65535system mac address: cc:05:77:c8:15:24port key: 9port priority: 255port number: 2port state: 61details partner lacp pdu:system priority: 32768system mac address: 90:5d:7c:ed:bc:e8oper key: 13port priority: 32768port number: 71port state: 61
4、测试网络是否正常
优化建议:
绑定多个网卡为一个虚拟接口
不要设置网卡配置文件里面的HWADDR的地址
不要设置虚拟接口配置文件里面的MACADDR地址
让系统自动分配HWADDR和MACADDR
可以避免网卡更换无法启动网络
至此,Linux服务器更换主板后网络不通问题解决办法完成。
本文内容仅供参考,不构成任何专业建议。使用本文提供的信息时,请自行判断并承担相应风险。
分享文章



