Configuring simplified routing features
You can enable simplified routing under Networking > Network Integration: Simplified Routing.
Simplified routing collects the IP address for the next hop MAC address from each packet it receives to address traffic. With simplified routing, you can use either the WAN or LAN side device as a default gateway. The RiOS appliance learns the right gateway to use by watching where the switch or router sends the traffic, and associating the next-hop Ethernet addresses with IP addresses. Enabling simplified routing eliminates the need to add static routes when the appliance is in a different subnet from the client and the server.
Without simplified routing, if an appliance is installed in a different subnet from the client or server, you must define one router as the default gateway and static routes for the other routers so that traffic is not redirected back through the appliance. In some cases, even with the static routes defined, the ACL on the default gateway can still drop traffic that should have gone through the other router. Enabling simplified routing eliminates this issue.
Simplified routing has these constraints:
• WCCP cannot be enabled.
• The default route must exist on each RiOS appliance in your network.
For detailed configuration information, see the SteelHead Deployment Guide.
The SteelHead-c is not deployed in-path, but in its unique out-of-path method, using one interface. Simplified routing does not apply.
The simplified routing feature is compatible with IPv6.
Under Mapping Data Collection Setting, these configuration options are available:
Collect Mappings From specifies one of these options from the drop-down list:
• None does not collect mappings.
• Destination Only collects destination MAC data. Use this option in connection-forwarding deployments. This is the default setting.
• Destination and Source collects mappings from destination and source MAC data. Use this option in connection-forwarding deployments.
• All collects mappings for destination, source, and inner MAC data. Also collect data for connections that are un-NATed (that is, connections that aren’t translated using NAT).