Intranet & Internet Enhancements

Intranet/Internet Route Failover Based on Path State

In previous releases when there was a WAN link failure of the Intranet service, the appliance would forward traffic based on the WAN link defined for the Intranet service. There was no searching through the route table to determine if there was an alternate route to reach the destination. In release 2.3, an added enhancement now allows the appliance to continue searching through the Oracle SD-WAN Edge route table for a second route in the event of a WAN link failure.

For example, if there are two WAN links, WAN Link A and WAN link B, WAN link A is the MPLS circuit/WAN link while WAN link B is the Internet circuit. If the Intranet service is defined for WAN link A and that router becomes unreachable, the appliance will now continue searching the Oracle SD-WAN Edge route table for an alternative route when there is a new flow. If the user defined a second route to be a conduit route, the flow could traverse the conduit in the event of an Intranet WAN link failure. This provides a backup route in the event of a WAN link failure.

Intranet Name Support

In Oracle SD-WAN Edge release 2.2 and prior there is the concept of a single Intranet service. This single service was defined and all Intranet routes used this defined WAN link and gateway. There was also the ability to have a primary and secondary WAN link defined for the Intranet service. In Edge 2.3 the number of Intranet services has been increased to 32, allowing a user to define up to 32 separate Intranet services. The user would define separate services in the case where they had multiple MPLS routers each supporting specific subnets. The user could then define the separate Intranet service and point a specific route/subnet to the corresponding service. This allows a much more flexible solution when supporting Intranet traffic.