Make sure the autodiscovery settings on both the peered server-side and client-side appliances are the same. If they don't match, optimization may not work correctly.

Enables enhanced autodiscovery for IPv4 and mixed IPv4/IPv6 networks. This option relies on an IPv4 connection to the peer appliance over TCP, and your network must support IPv4 for the inner channels for this feature to function.

Enables enhanced auto-discovery for IPv6 networks. Enabling this option is required for IPv6 single-stack networks. This can be enabled for both single-stack IPv6 and dual-stack IPv4 + IPv6 networks. Enhanced IPv6 Auto-discovery is disabled is by default.

Supports up to 20,000 peers on high-end server-side SteelHeads The appliance’s data store organizes peers in groups of 1,024 in the global peer table. If you have more than 4,000 peers, we recommend enabling the extended peer table. By default, this option is disabled (the option is unavailable on models that don’t support it).

Before enabling, ensure you understand the performance and scaling implications. You should compare this with a serial cluster deployment for scalability.For details, see SteelHead Deployment Guide. After enabling, you must clear the RiOS data store and restart the service.

Enables peer appliances to pass traffic without optimization when the latency between them is below a set threshold. The default threshold is 10 milliseconds, but you can adjust it. The client-side SteelHead calculates the latency. When latency is low, sending unoptimized traffic can be faster than optimizing it. You can also use the Ignore Latency Detection option in peer in-path rules, if needed.