![链接始终为 NO-CARRIER,但预计可以正常工作](https://linux22.com/image/5007/%E9%93%BE%E6%8E%A5%E5%A7%8B%E7%BB%88%E4%B8%BA%20NO-CARRIER%EF%BC%8C%E4%BD%86%E9%A2%84%E8%AE%A1%E5%8F%AF%E4%BB%A5%E6%AD%A3%E5%B8%B8%E5%B7%A5%E4%BD%9C.png)
在某些时候,我开始收到“NO-CARRIER”错误消息。这是什么意思以及如何解决它?我的链接“物理上已启动” - 绿灯闪烁。对面的链路已接通,但没有流量。甚至没有ARP响应。
网络管理器被禁用。如果我启用了 NetworkManager,那么无论如何我总是有“NO-CARRIER”。
[root@localhost ovazhnev]# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT qlen 1000
link/ether 00:25:90:fc:ba:3e brd ff:ff:ff:ff:ff:ff
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:25:90:fc:ba:3f brd ff:ff:ff:ff:ff:ff
4: enp2s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:0f:53:22:79:d0 brd ff:ff:ff:ff:ff:ff
5: enp2s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:0f:53:22:79:d1 brd ff:ff:ff:ff:ff:ff
[root@localhost ovazhnev]# ip link set enp2s0f0 up
[root@localhost ovazhnev]# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT qlen 1000
link/ether 00:25:90:fc:ba:3e brd ff:ff:ff:ff:ff:ff
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:25:90:fc:ba:3f brd ff:ff:ff:ff:ff:ff
4: enp2s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT qlen 1000
link/ether 00:0f:53:22:79:d0 brd ff:ff:ff:ff:ff:ff
5: enp2s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:0f:53:22:79:d1 brd ff:ff:ff:ff:ff:ff
我认为链接在物理上没问题,因为:
- 升级到 RHEL 7.1 后立即出现 NO-CARRIER 问题,这意味着该问题可能出在软件中
- 回滚到 RHEL 7.0 后 NO-CARRIER 仍然存在
- 拔掉并插入电源线后解决了 NO-CARRIER 问题
- 安装RHEL 7.1后再次出现NO-CARRIER问题
- 拔下并插入电源线后,NO-CARRIER 问题仍然存在
最后,我不知道是什么原因导致“无载体问题”,但似乎链接在物理上没有问题,因为有时它们可以工作。另外,两个链接不太可能同时损坏,我正在使用 LACP。