in-path kickoff
Resets open connections upon start up.
Syntax
[no] in-path kickoff
Parameters
None
Usage
When the SteelHead service restarts with kickoff enabled, it breaks existing connections and forces clients to open new connections.
With kickoff disabled, open connections are not broken, but they are unoptimized. New connections are optimized.
When the appliance is not powered on or the SteelHead service is not running, the failover appliance takes over so that connections continue to be made to the WAN.
Generally, connections are short lived and kickoff is not necessary; kickoff is suitable for very challenging remote environments. For example, in an environment with 128 Kbps and 1.5 seconds of latency, you might want to cancel an HTTP download so that your traffic is optimized; whereas in a remote branch-office with a T1 and 35 ms round-trip time, you would want connections to migrate to optimization gracefully, rather than risk interruption with kickoff.
Do not enable kickoff for in-path SteelHeads that use autodiscovery or if you do not have a SteelHead on the remote side of the network. If you do not set any in-path rules, the default behavior is to auto-discover all connections. If kickoff is enabled, all connections that existed before the SteelHead started are reset.
The no command option disables the in-path kickoff feature.
Example
amnesiac (config) # in-path kickoff
Product
SteelHead CX, SteelHead EX, SteelHead-v, SteelHead-c
Related Commands