Riverbed SteelHead 5080, Руководство по установке и настройке

Страница: 27 / 94

Installing and Configuring the SteelHead | 27
Checking your inventory
An out-of-path SteelHead deployment doesn’t use a redirecting mechanism. You configure fixed-
target in-path rules for the client-side SteelHead. The fixed-target in-path rules point to the primary
IP address of the out-of-path SteelHead. The out-of-path SteelHead uses its primary IP address
when communicating to the server. The remote SteelHead must be deployed either in a physical or
virtual in-path mode.
Figure 3-3. Out-of-path deployment
This table gives you a summary of the in-path and out-of-path deployment options.
Checking your inventory
Your shipping carton contains these items:
• The SteelHead appliance
• One standard Ethernet straight-through cable
• One standard Ethernet crossover cable
Deployment type Benefits Requires Challenges
Physical In-Path Simple to configure and uses
automatic discovery of peers. In-path rules Scaling, availability, cabling
Virtual In-Path Limited physical disruption,
routing forces traffic to WAN,
automatic discovery of peers. External setup to
use PBR, WCCP, a
SteelHead
Interceptor, or
Layer-4 switching Dependent on the external
configuration
Out-of-Path The client-side SteelHead
sends traffic directly to the
server-side SteelHead with no
physical disruption.
This configuration is typically
used as a way to rapidly deploy
a SteelHead in a site with very
complex or numerous
connections to the WAN.
Fixed-target rules Requires explicit manual
configuration.
Connections initiated from the site
with the out-of-path SteelHead
can’t be optimized.
Servers at the site detect the
optimized traffic coming from the
out-of-path SteelHead primary IP
address instead of a client IP
address.