Steelhead Appliance Installation and Configuration Guide
55
Protocol Optimization Errors
Troubleshooting
Protocol Optimization Errors
When there are protocol optimization errors, the Steelhead appliance does not optimize expected protocols.
Solutions
To resolve protocol optimization errors, check:
that connections have been successfully established.
that Steelhead appliances on the other side of a connection are turned on.
for secure or interactive ports that are preventing protocol optimization.
for any pass through rules that could be causing some protocols to pass through the Steelhead
appliances unoptimized.
that the LAN and WAN cables are not inadvertently swapped.
Server-Side Out-of-Path Connection Caveats
The following are the caveats for a server-side out-of-path (OOP) Steelhead appliance connection:
OOP configuration does not support auto-discovery. You must create a fixed-target rule on the client-
side Steelhead appliance.
You must create an OOP connection from an in-path or logical in-path Steelhead appliance and direct it
to port 7810 on the primary interface of the server-side Steelhead appliance. This setting is mandatory.
Interception is not supported on the primary interface.
An OOP configuration provides non-transparent optimization from the server perspective. Clients
connect to servers, but servers treat it like a server-side Steelhead appliance connection. This affects:
–
log files.
–
server-side ACLs.
–
bi-directional applications such as rsh.
You can use OOP configurations along with in-path or logical in-path configurations.
