Configuring Simplified Routing
Simplified routing is only effective in topologies where the in-path SteelHead resides on a different network than the end hosts. Riverbed recommends that you use simplified routing in deployments where a Layer 3 switch separates the end hosts from the SteelHead.
For an overview of simplified routing and packet ricochet, see
Overview of Simplified Routing.
You can enable simplified routing with the in-path simplified routing <option> command or in the Management Console. The following options determine if simplified routing is enabled and what packet elements the SteelHead can use (that is, what is learned).
To configure simplified routing from the CLI
Connect to the CLI and enter the following command:in-path simplified routing <option>
The following table summarizes the simplified routing command options.
Parameter | Definition |
None | Does not collect mappings. This setting disables simplified routing learning. The <none> option is required for virtual in-path deployments. |
Destination only | Collects mappings from destination IP, destination MAC, and VLAN tag (when deployed on 802.1q trunk). Riverbed recommends that you use <destination only> for most deployments with multiple in-paths or connection forwarding SteelHeads. Destination only is enabled by default on appliances manufactured with RiOS v6.0 or later. SteelHeads do not usually learn incorrect mappings unless the network devices themselves are routing incorrectly. |
Destination and source | Collects mappings from destination and source IP, destination and source MAC, and VLAN tag (when deployed on 802.1q trunk). |
All | Collects mappings for destination and source IP, destination and source MAC, VLAN tag, and SteelHead inner connection traffic and auto-discovery options. This option has the advantage of learning simplified entries faster than the destination only. option Riverbed recommends that you use <all> in topologies when you deploy the SteelHead a 802.1q trunk. |
You can view the simplified routing table that includes the in-path interface learned information, the entry, IP address, MAC address, VLAN tag ID, and the times the entry was used.
To view the simplified routing table on the SteelHead
Connect to the CLI and enter the following command to see the following output:show in-path macmap-tables
relay ip_addr mac_addr vlan ref_count
inpath0_0 10.18.4.9 00:0d:66:95:e8:00 0 6
You can use the output of this command if an entry points to an incorrect MAC address, such as a firewall. Riverbed recommends that you collaborate with Riverbed Support for troubleshooting—the understanding of simplified routing learning in complex topologies can require detailed traffic flow analysis.
Simplified routing has the following constraints:
The <none> option must be used when you configure simplified routing in a virtual in-path (WCCP/PBR/SteelHead Interceptor) environment.The default route must exist on the SteelHead.In the following deployment examples, the recommended simplified routing settings are specified in the CLI configurations.