Multiple Intranet Services Defined
In prior releases (2.2 and prior) Oracle only supported a single defined Intranet service. This is a WAN service the APNA could be configured to use if traffic was not conduit based. The Intranet services were defined on a WAN link to be either the primary WAN link or the secondary WAN link. The new enhancement now allows a user the flexibility to configure up to 32 Intranet services.
Each service may have a primary and a secondary defined WAN link. When adding routes to the Oracle SD-WAN Edge configuration file, the user can assign a route to a defined Intranet service if multiple Intranet services exist. A single WAN link can have multiple Intranet services defined. The commands required for this capability are provided below:
Service definition would use the following commands:
add intranet_service name=Intranet-1
{
} add intranet_service name=Intranet-0
{
}
Adding the service to a specific wan link would use the following commands:
Command | Command |
---|---|
add net_usage |
intranet_service_name=Intranet-0 service_type=intranet wan_egress_rate_pct=10 wan_ingress_rate_pct=10; |
If a route was added for the service, it would appear like the following:
Command | Command |
---|---|
add route |
net=192.168.80.0/24 intranet_service_name=Intranet-0 cost=6 service=INTRANET; |
These commands could be repeated for the individual routes and services as required.
Route Learning via SNMP
In Oracle SD-WAN Edge release 2.3, the APNA allows a user to define routers so that they can be polled for routes using SNMPv2. Once the routes have been learned by the APNA, the user can define rules which will include or exclude the routes from the
APNA route table. These routes will then be advertised or propagated to other APNAs within the Oracle SD-WAN Edge. Additional capabilities include the ability to continue polling the router for routes and, if a route is removed from the routing table of the router, propagate the topology change across the Oracle SD-WAN Edge. The polling intervals supported are “poll now,” “every 30 seconds,” “every minute,” or “every 5 minutes.” If the router that is probed is not reachable, the APNA can also be configured to purge the learned routes or maintain them. When using this capability, care must be taken when adding the routes. The user must define the routes properly to avoid any routing loop or problems. Routes included must be assigned to the correct Oracle SD-WAN Edge service; if Intranet(Internet) service is selected it must match the service defined in the configuration. This capability has the following design considerations:
- Currently only support for SNMPv2 is provided
- Probes the interface using the MIB: RFC 2096 IP Forwarding Table MIB and RFC1213-MIB
- Uses specific intervals to poll the router
- Router must support (configured) the MIB defined above (some routers do not)
- Can purge routes if router is not reachable
- Can include or exclude routes as required, excluded by default
- When defining the include/exclude rule, a user must assign a route to the correct service – local, intranet etc.
- Routes are local to each appliance, so the process is performed per appliance
- If no community string is defined, “public” is used
- Static routes learned from a polled router are displayed with the unknown interface
- Community string only supports alphanumeric characters
- Only Local routes are propagated via the Oracle SD-WAN Edge
- The polling takes place through the APNA management interface
- All straddle segments are added to the Oracle's route table by default
Log into the web console of the appliance and proceed to Manage Network -> SNMP Route Learning. Shown in Figure 3 are four sections to the web page: Configuration, Include/Exclude Rules, Included Routes, Excluded Routes.