We are pleased to announce the release of Multapplied SD-WAN version 6.4. This release delivers the following capabilities:
1) Support for both IPv4 and IPv6 tunnels. IPv6 support has been added to enable the delivery of a virtually unlimited address space. This reduces reliance on limited and costly IPv4 addressing space and provides easier routing for management traffic directly to devices, faster convergence of auto-configured host addresses and eliminates the requirement for Network Address Translation (NAT). Eliminating NAT greatly simplifies network configurations and troubleshooting. With support for IPv6 Aggregators, Private WAN routers, outbound Gateways, QoS and classification profiles can use IPv6 addresses. Legs can also use multiple IP addresses, including both IPv4 and IPv6 addresses, enabling better failover and recovery. Legs can also support “Auto IPv6” address schemes using a combination of DHCPv6 and Router Advertisement to acquire addresses. Connect IPs and routes now support IPv6.
2) A Redesigned Bond Networking Configuration User Interface to support IPv6 and simplify the user experience. The user interface now makes the distinction between Interfaces, Legs and Address clear to avoid scenarios when multiple addresses and legs share the same interface.
3) Packet Loss Chart Improvements and New CPU Utilization Charts. Packet loss charts for bonds now scale to make service-impacting amounts of packet loss clearly visible. Per-core CPU charts have been added to show when a core is at full utilization to improve Node and CPE management and troubleshooting.
4) New API. Version 4.0 of the API is available with this release. Version 4.0 is required to support new IPv6-enabled objects and separated interfaces, legs, and connected IPs. Version 3.0 of the API will continue to function, but all future features and capabilities will be available through Version 4.0 only.
5) API Performance Increases. Slower API calls, such as BondingList, will now return results faster.
6) BondingAdmin Fixes and Performance Increases. These improvements include:
- BondingAdmin password reset now requires re-login
- Configuration update service handling updates after connectivity loss
- Management VPN connectivity to a heavily loaded BondingAdmin server
- API call for latest backup
- Packet loss reporting on speed tests more accurate
- Nginx Web server properly restarts on Let’s Encrypt certificate updates
7) BondingNode Fixes and Performance Increases. These improvements include:
- Private WAN route sets on busy aggregators now recover correctly after an outage caused by high packet loss at upstream providers
- Memory leak fixed on Private WAN routers that occurs when peer nodes frequently reconnect due to outages or restarts
- A rare crash situation on Peer Private WAN nodes no longer occurs when disabling a Private WAN router as its connections are being established on other nodes
- Fixed a memory leak that can occur if an aggregator record on another management server contains a duplicate IP address for an aggregator
- Fixed a rare crash in path MTU detection that can occur when the leg flap
8) Speed and Performance Impacts and Options for Improvement. Changes implemented to support IPv6 have increased CPU utilization by around 5%. However, some new options are available to mitigate this impact. Enabling the following options has resulted in better performance than version 6.3 on certain hardware platforms. We will release a new set of benchmarks across a select range of hardware in the future.
- A new bond-level option “Batched leg send operations” can improve CPU utilization at the cost of a small (about 1ms) increase in latency on any sent This option does not work on Debian 7 (Wheezy) bonders or aggregators and will be ignored.
- On a CPE/bonder, the tunnel process can now be assigned to work on a specific CPU core, which can have performance improvements on some hardware platforms.
If you have any further questions please don’t hesitate to Contact Us