About out-of-path deployment
In an out-of-path (OOP) deployment, SteelHead-v is not in the direct path between the client and the server. Servers see the IP address of the server-side SteelHead installation rather than the client IP address, which might have an impact on security policies. For a virtual OOP deployment, connect the primary interface to the physical in-path NIC and configure the router to forward traffic to this NIC. You must also enable OOP on the appliance. Also, these caveats apply to server-side OOP appliances:
• Autodiscovery is not supported. Configure fixed-target rules on client-side appliances.
• Interception is not supported on the primary interface.
• You must create an OOP connection from an in-path or logical in-path appliance and direct it to port 7810 on the primary interface of the server-side SteelHead. This setting is mandatory.
• An OOP configuration provides nontransparent acceleration from the server perspective. Clients connect to servers, but servers treat it like a server-side SteelHead connection. This affects log files, server-side ACLs, and bidirectional applications such as rsh.
• You can use OOP configurations along with in-path or logical in-path configurations.