in-path simplified routing
Enables simplified routing.
Syntax
[no] in-path simplified routing {none | all | dest-only | dest-source | mac-def-gw-only}
Parameters
none | Disables all options. |
all | Collects source and destination MAC data. Also collects data for connections that are un-NATted (connections that are not translated using NAT). This option cannot be used in connection forwarding deployments. |
dest-only | Collects destination MAC data. This option can be used in connection forwarding. This option is the default setting. |
dest-source | Collects destination and source MAC data. This option can be used in connection forwarding. |
mac-def-gw-only | Uses simplified routing entries only when a packet is sent to the in-path default gateway. This option enables you to override any simplified routing learning by putting in static routes. |
Usage
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 SteelHead 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 SteelHead is in a different subnet from the client and the server.
Without simplified routing, if a SteelHead 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 SteelHead. However, in some cases, even with 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 the following constraints:
• WCCP cannot be enabled.
• The default route must exist on each SteelHead in your network.
• Simplified routing requires a client-side and server-side SteelHead.
Optionally, you can also enable enhanced autodiscovery. When you enable simplified routing, Riverbed recommends that you also enable enhanced autodiscovery because it gives the SteelHead more information to associate IP addresses and MAC addresses (and potentially VLAN tags). For details, see
in-path peering auto.
When deploying SteelHeads on a nontrunk link, using simplified routing is recommended but optional. However, when deploying SteelHeads on VLAN trunks, enabling simplified routing is mandatory. Simplified routing plays a bigger role in keeping track of the IP, VLAN ID, and MAC address for each connection. Use the all option to learn from both source and destination MAC addresses.
If you are installing SteelHead on some type of shared L2 wan connection (local and remote in-path addresses in the same subnet, with or without VLANs):
in-path mac-except-locl (bug 16389)
If you are putting the SteelHead on a simple non-VLAN trunk:
in-path simplified routing all
!enables the new discovery protocol
in-path peering auto
in-path simplified mac-def-gw-only
in-path mac-except-locl
If you are putting the SteelHeads on a VLAN trunk link:
in-path simplified routing all
!enables the new discovery protocol
in-path peering auto
!keep LAN side traffic in its original VLAN; enabled by default
in-path vlan-conn-based
in-path simplified mac-def-gw-only
in-path mac-except-locl
!enabled by default
in-path mac-match-vlan
For details, see the SteelHead Deployment Guide.
The no command option disables simplified routing.
Example
amnesiac (config) # in-path simplified routing all
Product
SteelHead CX, SteelHead EX, SteelHead-v, SteelHead-c
Related Commands