• Link Routing Policy — You can now specify how FortiADC routes traffic is routed among available ISP links, including by source or destination address and port. See “Link load balancing for outbound traffic”.

• Virtual Tunnel — This feature builds a tunnel between two FortiADC appliances and balances traffic across multiple links to each appliance. A typical scenario is a VPN between a branch office and headquarters for application-specific access. See “Defining a virtual tunnel”.

• Persistent Routing — You can now configure connections that persist regardless of the FortiADC link load balancing activity. You can configure persistence based on source IP, destination IP, and subnet. See “Adding persistence to outgoing link load balancing”.

• Proximity-Based Routing — Maximize WAN efficiency by using link proximity to determine latency between FortiADC and remote WAN sites so that FortiADC can choose the best route for traffic. See “Configuring routing by most efficient route or static route”.

• Scheduled LLB — You can now apply a link load balancing policy to a specific time period. See “Defining schedules to use with a link policy”.

• One-to-one (1-to-1) NAT — You can now fully define source and destination IP address translation. This feature is useful when you require a different address range for each ISP. FortiADC also supports port forwarding. See “Applying one-to-one NAT”.

• PPPoE interface support — To support DSL connectivity, you can now configure interfaces as PPPoE (Point-to-Point Protocol over Ethernet). See “Configuring the network interfaces”.

• Custom error page — You can now upload a custom error page to FortiADC that it can use to respond to clients when HTTP service is unavailable. See “Customizing the error page or message”.

• Full NAT for Layer 3/4 load balancing — Layer 3/4 load balancing now supports full NAT (translation of both source and destination IP addresses). FortiADC can now round robin among a pool of source IP addresses for its connections to back-end servers. See “Applying full NAT to forwarded packets”.

• Standby server — You can now configure FortiADC to forward traffic to a hot standby (called a Backup Server) when all other servers in the pool are unavailable. See “Defining your pool of back-end servers”.

• Log cache memory — To avoid hard disk wear and tear, FortiADC can cache logs in memory and then periodically write them to disk in bulk. Previously, FortiADC always wrote each log message to disk instantaneously. See “Reducing hard disk usage by caching logs”.

• HA sync for health check status with IPv6 — For high availability FortiADC clusters, the Layer 4 health check status of IPv6-enabled virtual servers is now synchronized. See “HA heartbeat & synchronization”.

• Link load balancing — FortiADC now supports load balancing among its links, in addition to distributing among local and globally distributed servers. Depending on if the traffic is inbound or outbound, different mechanisms are available: outbound can use weighted round robin; inbound can use DNS-based round robin or weighted round robin. See “Load balancing among links”.

• HTTP response compression — FortiADC now can compress responses from your back-end servers, allowing you to off load compression from your back-end servers for performance tuning that delivers faster replies to clients. See “Compressing HTTP responses”.

• Quality of service (QoS) — FortiADC now can guarantee bandwidth and queue based upon source/destination address, direction, and network service. See “Guaranteeing bandwidth & controlling queueing (QoS)”.

• Source NAT (SNAT) — When applying NAT, FortiADC can now apply either static or dynamic source NAT, depending on your preference. See “Applying source NAT (SNAT)”.

• Session persistence by source IP segment — FortiADC now can apply session persistence for entire segments of source IPs such as 10.0.2.0/24. Previously, session persistence applied to a single source IP. See “Specifying server-side session persistence”.

• Health check enhancements — FortiADC now supports additional health check types for servers that respond to these protocols: email (SMTP, POP3, IMAP), TCPS, TCP SYN (half-open connection), SNMP, and UDP. See “Monitoring your servers’ responsiveness”.

• HA enhancements — FortiADC HA now synchronizes Layer 3/4 and Layer 7 sessions and connections for session persistence and uninterrupted connections when the standby assumes control of traffic. See “Data that is not synchronized by HA”.

• Support for FortiADC 200D and FortiADC-VM— FortiADC software has been released to support these new platforms.