Design Considerations
Packet mode optimization does not support several network integration features available with TCP proxy optimization. The following are limitations to packet-mode optimized traffic.
Packet mode optimization in RiOS v8.5 or later supports:
only fixed-target (packet mode optimization). Auto-discovery is not supported.only correct addressing. Full transparency and port transparency are not supported. Because full transparency is not supported, VLAN transparency is also not supported.physically and virtually in-path deployments. The exception is WCCP for IPv6 traffic, because the SteelHead WCCPv2 implementation currently does not support IPv6. data reduction for all IPv4 and IPv6 traffic.connection reporting of packet-mode optimized traffic flows. Packet mode optimization does not support:
RSP data flow rules.NetFlow export of the packet-mode optimized traffic. connection forwarding. This does not imply that parallel SteelHead deployments do not work. As each flow is optimized unidirectionally, this means that asymmetry does not have the same relevance on packet-mode optimized traffic.SteelHead Interceptor deployments.server-side out-of-path configuration.QoS shaping, enforcement, or marking. All packet-mode optimized traffic matches the default QoS default rule and class. The exception is UDP IPv4 traffic, which you can place into an MX-TCP class. For more information about MX-TCP class, see
MX-TCP.