SteelHead™ Deployment Guide : Out-of-Path Deployments : Configuring Out-of-Path Deployments
  
Configuring Out-of-Path Deployments
Figure 17‑1 shows a scenario in which fixed-target in-path rules are configured for an out-of-path SteelHead primary interface.
This section provides the basic steps for out-of-path network deployments. It does not provide detailed procedures. Use this section as a general guide.
Figure 17‑1. A Fixed-Target In-Path Rule to an Out-of-Path SteelHead Primary IP Address
In this example, you configure:
  • SteelHead A with a fixed-target in-path rule specifying that traffic destined to a particular Web server at the data center is optimized by the out-of-path SteelHead B.
  • The TCP connection between the out-of-path SteelHead, SteelHead B, and the server uses the SteelHead primary IP address as the source, instead of the client IP address.
  • To configure a basic out-of-path deployment
    On SteelHead A, connect to the CLI and enter the following commands:
    enable
    configure terminal
    in-path rule fixed-target target-addr 12.3.0.5 dstaddr 192.168.50.0/24 dstport 80 rulenum end
    On SteelHead B, connect to the CLI and enter the following commands:
    enable
    configure terminal
    out-of-path enable