How to configure Latency Detection to automatically bypass a peer based on low latency

Categories: SteelHead CX (Appliance), SteelHead CX (Virtual Steelhead)
Solution Number: S33526


RiOS 9.9 include a Latency Detection feature to helps client-side SteelHead to automatically bypass a peer based on low latency, without needs using peering rule or In-path rule. When latency between peers is low enough, simply passing through unoptimized traffic can be faster than transmitting optimized traffic.
When the Latency Detection is enable, the client-side SteelHead appliance will pass through traffic without optimizing it when the latency between the peers is below the configured threshold which is by default 10 ms.

Configuration commands
in-path latency-detection enable
no in-path latency-detection enable                   # Disable this feature
in-path latency-threshold <thres_value>           # The default value is 10 ms

Check commands
show in-path latency-detection
show in-path latency-threshold
show peers latency-detected

For example:
Steelhead # show in-path latency-detection
Latency-Detection Enabled:   yes <<

Steelhead # show in-path latency-threshold
Latency Threshold Value: 10 <<


SteelHead - All Models
NOTICE: Riverbed® product names have changed. Please refer to the Product List for a complete list of product names.
Last Modified: 2019-10-03
Can't find an answer? Create a case