Help the Newbies

[Edwin Groothuis]

The in-path rules decide what to happen when a naked SYN comes onto the LAN interface: forward to a Steelhead appliance or pass it through. When a SYN arrives at the WAN or LAN side, it will forward it to a local Steelhead appliance.

Only when the two Steelhead appliances have setup their optimized connection the interceptors will forward that traffic.

The rest gets passed through just as fast as it came in.

Edwin

[mpi]

So ... in-path rules on the Interceptor ... are not only for locally generated traffic?

In-path rules for Interceptor ... can be used as the service group 61 on the WAN side for the data centers?

I'm looking into wccp vs interceptor for the clasic scenario with remote sites and Interceptor at data center:

http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/white_paper_c11-629052.html

At the remote sites, use service group 61 on the LAN side and service group 62 on the WAN side. For the data center, reverse the orientation with service group 61 on the WAN side and service group 62 on the LAN. This would mean the WCCP load balancing at both the data center and the remote sites would be based on the client IP's addresses.

http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/white_paper_c11-629052.html

[Edwin Groothuis]

The WCCP redirection ACL equivalent is the in-path rules on the IC.

Edwin

[mpi]

Hi,

Quick question ... I'm running a quick Interceptor test in the lab for FTP protocol and I would like to make sure traffic for FTP server is pass-through ... not redirected to SH for optimization.

I tried in-path and load-balancing rules ... somehow  FTP sessions get optimized.

What is the equivalent of WCCP redirect ACL for Riverbed Interceptor?

Thank you.