I can confirm that link bonding is working:
Code
Feb 2 17:54:22 storage00 dhclient: DHCPDISCOVER on bond0 to 255.255.255.255 port 67 interval 8
Feb 2 17:54:22 storage00 kernel: [ 658.644006] bnx2 0000:06:00.0 eth1: NIC Copper Link is Up, 1000 Mbps full duplex
Feb 2 17:54:22 storage00 kernel: [ 658.644033]
Feb 2 17:54:22 storage00 kernel: [ 658.718020] bnx2 0000:07:00.0 eth3: NIC Copper Link is Up, 1000 Mbps full duplex
Feb 2 17:54:22 storage00 kernel: [ 658.718049]
Feb 2 17:54:22 storage00 kernel: [ 658.731280] bonding: bond0: link status up for interface eth1, enabling it in 0 ms.
Feb 2 17:54:22 storage00 kernel: [ 658.731289] bonding: bond0: link status up for interface eth3, enabling it in 200 ms.
Feb 2 17:54:22 storage00 kernel: [ 658.731294] bonding: bond0: link status definitely up for interface eth1, 1000 Mbps full duplex.
Feb 2 17:54:22 storage00 kernel: [ 658.731332] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Feb 2 17:54:22 storage00 kernel: [ 658.931390] bonding: bond0: link status definitely up for interface eth3, 1000 Mbps full duplex.
Feb 2 17:54:23 storage00 kernel: [ 659.199647] bnx2 0000:06:00.1 eth2: NIC Copper Link is Up, 1000 Mbps full duplex
Feb 2 17:54:23 storage00 kernel: [ 659.199674]
Feb 2 17:54:23 storage00 kernel: [ 659.231670] bonding: bond0: link status up for interface eth2, enabling it in 200 ms.
Feb 2 17:54:23 storage00 kernel: [ 659.431827] bonding: bond0: link status definitely up for interface eth2, 1000 Mbps full duplex.
Feb 2 17:54:23 storage00 kernel: [ 659.441941] bnx2 0000:07:00.1 eth4: NIC Copper Link is Up, 1000 Mbps full duplex
Feb 2 17:54:23 storage00 kernel: [ 659.441958]
Feb 2 17:54:23 storage00 kernel: [ 659.531907] bonding: bond0: link status up for interface eth4, enabling it in 200 ms.
Feb 2 17:54:23 storage00 kernel: [ 659.732062] bonding: bond0: link status definitely up for interface eth4, 1000 Mbps full duplex.
Feb 2 17:54:23 storage00 kernel: [ 659.874416] bnx2 0000:07:00.0 eth3: NIC Copper Link is Down
Feb 2 17:54:23 storage00 kernel: [ 659.932218] bonding: bond0: link status down for interface eth3, disabling it in 200 ms.
Feb 2 17:54:24 storage00 kernel: [ 660.132373] bonding: bond0: link status definitely down for interface eth3, disabling it
Feb 2 17:54:26 storage00 kernel: [ 662.223006] bnx2 0000:07:00.0 eth3: NIC Copper Link is Up, 1000 Mbps full duplex
Feb 2 17:54:26 storage00 kernel: [ 662.223033]
Feb 2 17:54:26 storage00 kernel: [ 662.233973] bonding: bond0: link status up for interface eth3, enabling it in 200 ms.
Feb 2 17:54:26 storage00 kernel: [ 662.434126] bonding: bond0: link status definitely up for interface eth3, 1000 Mbps full duplex.
Feb 2 17:54:30 storage00 dhclient: DHCPDISCOVER on bond0 to 255.255.255.255 port 67 interval 15
Feb 2 17:54:45 storage00 dhclient: DHCPDISCOVER on bond0 to 255.255.255.255 port 67 interval 20
Feb 2 17:55:05 storage00 dhclient: DHCPDISCOVER on bond0 to 255.255.255.255 port 67 interval 18
Feb 2 17:55:05 storage00 dhclient: DHCPOFFER from 10.1.0.1
Feb 2 17:55:05 storage00 dhclient: DHCPREQUEST on bond0 to 255.255.255.255 port 67
Feb 2 17:55:05 storage00 dhclient: DHCPACK from 10.1.0.1
Feb 2 17:55:05 storage00 avahi-daemon[2468]: Joining mDNS multicast group on interface bond0.IPv4 with address 10.1.0.2.