We have enabled NIC Bonding on several new Gen4 hardware appliances we purchased to improve our redundancy/fault tolerance/single point of failure, and so far it is working on most of them.
We did however run in to an issue on one device and we were forced to disable NIC Bonding. Prior to disabling, we had to physically disconnect the ethernet cable from one of the ports, once the system was stable, we were able to disable the "Mgmt 2" NIC, thus disabling the Bonded interface.
This happened on an ERC-2600, we were seeing about 50% packet loss when performing a continuous ping.
NIC Bonding is supposed to allow you to setup some basic fault tolerance, using two ethernet ports connected on the same VLAN but using two different switches, the bonded interface advertises the same IP and MAC on both eth0 (Mgmt1) and eth1 (Mgmt2), this is supposed to work in an Active/Standby mode from what I understood.
NIC Bonding was introduced in version 9.4.0 - from the release notes:
Network interface controller (NIC) bonding
All devices with two management NICs support network interface bonding to improve communications reliability. Network interface bonding creates a virtual interface that contains two NICs, either one or both of which are active. For redundancy, when bonding is active, both NICs can be connected to either a single switch or separate switches, implementing automatic failover in the event of loss of link on a single NIC.