SD-WAN Internet 3.3 release notes¶

November 29, 2010

Additions¶

The administration interfaces displays information about bonder hardware: product name (if provided by the manufacturer), CPU speed and cache size, and memory size.
The “delta” property of the flowlet balancing engine is managed from the administration site. See the User Manual for details.

The installation script no longer asks whether or not to restart Bonding.
Performance of the flowlet balancing engine has been improved significantly by porting it to the Cython programming language. The load it places on the CPU is about 20% of that of the old Perl implementation.
Leg connectivity checks run every five seconds instead of every 30 seconds. This reduces the time a bond is subject to packet loss when a failure occurs.
Leg delay is checked each time the leg is started or recovers from a failure, rather than once when Bonding is started.

Flowlet now supports legs of different speeds.
Failover legs start in the correct state when Bonding is started.
Leg up/down messages are sent from the config server to the aggregator, regardless of the previous state of the leg in the config server’s database. This will reduce the chance of aggregators getting out of sync with bonders.

When using the flowlet engine with legs of different speeds, performance is poor when balancing a low number of flows. To reach 80% of the theoretical maximum speed of a bond, there should be at least eight concurrent flows to balance.
The per-packet balancing engine does not support legs of different speeds.