>
>
> Jan 3 14:46:07 filesrv2 kernel: bnx2 0000:04:00.0: eth4: NIC Copper Link is
> Down
> Jan 3 14:46:07 filesrv2 kernel: bnx2 0000:03:00.1: eth3: NIC Copper Link is
> Down
> Jan 3 14:46:07 filesrv2 kernel: bonding: bond1: link status definitely down
> for interface eth3, disabling it
> Jan 3 14:46:07 filesrv2 kernel: bonding: bond1: now running without any
> active interface !
> Jan 3 14:46:07 filesrv2 kernel: bonding: bond1: link status definitely down
> for interface eth4, disabling it
> Jan 3 14:46:10 filesrv2 kernel: bnx2 0000:03:00.1: eth3: NIC Copper Link is
> Up, 1000 Mbps full duplex, receive & transmit flow control ON
> Jan 3 14:46:10 filesrv2 kernel: bond1: link status definitely up for
> interface eth3, 1000 Mbps full duplex.
> Jan 3 14:46:10 filesrv2 kernel: bonding: bond1: making interface eth3 the
> new active one.
> Jan 3 14:46:10 filesrv2 kernel: bonding: bond1: first active interface up!
> Jan 3 14:46:10 filesrv2 kernel: bnx2 0000:04:00.0: eth4: NIC Copper Link is
> Up, 1000 Mbps full duplex, receive & transmit flow control ON
> Jan 3 14:46:10 filesrv2 kernel: bond1: link status definitely up for
> interface eth4, 1000 Mbps full duplex.
Both links are going down at same time. Did you connect them to the same switch?
Is there a switch reboot at that time or something else going on in the switch?
Sincerly,
Klaus
--
Linux-cluster mailing list
Linux-cluster@redhat.com
https://www.redhat.com/mailman/listinfo/linux-cluster
