root@lvs1012:~# grep 'Apr 28 15:03:59' /var/log/kern.log Apr 28 15:03:59 lvs1012 kernel: [6660615.515541] bnx2x 0000:03:00.1 eth1: NIC Link is Down Apr 28 15:03:59 lvs1012 kernel: [6660615.631558] bnx2x 0000:03:00.1 eth1: NIC Link is Up, 10000 Mbps full duplex, Flow control: ON - receive & transmit Apr 28 15:03:59 lvs1012 kernel: [6660615.771564] bnx2x 0000:03:00.1 eth1: NIC Link is Down Apr 28 15:03:59 lvs1012 kernel: [6660615.843576] bnx2x 0000:03:00.1 eth1: NIC Link is Up, 10000 Mbps full duplex, Flow control: ON - receive & transmit Apr 28 15:03:59 lvs1012 kernel: [6660615.887575] bnx2x 0000:03:00.1 eth1: NIC Link is Down Apr 28 15:03:59 lvs1012 kernel: [6660615.991589] bnx2x 0000:03:00.1 eth1: NIC Link is Up, 10000 Mbps full duplex, Flow control: ON - receive & transmit Apr 28 15:03:59 lvs1012 kernel: [6660616.027645] bnx2x 0000:03:00.1 eth1: NIC Link is Down Apr 28 15:03:59 lvs1012 kernel: [6660616.095597] bnx2x 0000:03:00.1 eth1: NIC Link is Up, 10000 Mbps full duplex, Flow control: ON - receive & transmit Apr 28 15:03:59 lvs1012 kernel: [6660616.271607] bnx2x 0000:03:00.1 eth1: NIC Link is Down Apr 28 15:03:59 lvs1012 kernel: [6660616.339621] bnx2x 0000:03:00.1 eth1: NIC Link is Up, 10000 Mbps full duplex, Flow control: ON - receive & transmit Apr 28 15:03:59 lvs1012 kernel: [6660616.387618] bnx2x 0000:03:00.1 eth1: NIC Link is Down root@lvs1012:~# grep 'Apr 28' /var/log/kern.log |grep -c 'eth1: NIC Link is Down' 39590
I've just set the interface as down. Please investigate the fiber and set it up again. Various previously unseen kernel warnings were emitted when I ran ip link set eth1 down, the driver may be in a funky state and the machine in need of a reboot.