← All posts SSH automation

ServerAliveInterval vs TCPKeepAlive for SSH connection liveness

The Tryssh team ·

For ServerAliveInterval vs TCPKeepAlive, the safest approach is a bounded operational change, not a command pasted without context. This runbook starts with effective state, shows the smallest candidate action, and finishes by repeating the real user or system path.

TL;DR: ServerAlive messages travel inside the encrypted SSH channel and can bound an unresponsive peer, while TCPKeepAlive relies on operating-system TCP probes with different timing and spoofability. Capture a baseline with ssh -G example-host | rg 'serveraliveinterval|serveralivecountmax|tcpkeepalive', make the reviewed change only when the evidence matches, then verify with ssh -vvv -o ServerAliveInterval=15 -o ServerAliveCountMax=3 example-host 'sleep 60; true' and keep the rollback ready.

Audience: operators writing unattended SSH, SFTP, or rsync jobs who already have a separate interactive recovery path. This guide assumes familiarity with SSH automation and a change window appropriate to the system.

ServerAliveInterval vs TCPKeepAlive for SSH connection liveness observe, interpret, change, and verify workflow

The direct answer

A healthy session survives normal idle periods and a black-holed path fails within the documented bound. That is the success condition for ServerAliveInterval vs TCPKeepAlive; command completion by itself is not enough.

The important boundary is configuration expansion, host identity, user authentication, transport liveness, session setup, remote command, and exit status. ServerAlive messages travel inside the encrypted SSH channel and can bound an unresponsive peer, while TCPKeepAlive relies on operating-system TCP probes with different timing and spoofability. If an observation does not identify which side of that boundary failed, collect a narrower observation before changing state.

How the mechanism works

For ServerAliveInterval vs TCPKeepAlive, use this mental model: OpenSSH expands configuration for one destination, verifies host identity, authenticates a user, opens channels over one transport, and returns local status based on transport and remote execution. The model prevents a common mistake—treating configuration text, control-plane acceptance, process state, and end-user behavior as the same proof.

Follow four stages:

  1. Observe: identify the exact host, object, version, owner, and active configuration.
  2. Interpret: write the expected result, the abnormal result, and what would remain inconclusive.
  3. Change: apply one reviewed action at the narrowest layer that contradicts the baseline.
  4. Verify: repeat the original path and compare the same evidence, including adjacent safety controls.

Preflight and safety boundary

Test with a non-production host, an explicit user and destination, bounded timeouts, and a dedicated least-privilege key before moving the command into automation.

Before ServerAliveInterval vs TCPKeepAlive, record UTC time, the current version or digest, the exact target, recent changes, and who owns the workload. The rollback for this runbook is: restore the previous keepalive settings, reconnect, and resume only idempotent work or follow the application's recovery procedure.

Do not continue if the target identity is ambiguous, the current state cannot be saved, the only recovery session would be at risk, or the proposed command affects more objects than the brief names.

Capture the read-only baseline

Run these commands one at a time. Replace example names and addresses deliberately; do not paste production secrets into a transcript.

ssh -G example-host | rg 'serveraliveinterval|serveralivecountmax|tcpkeepalive'
ssh -vvv example-host true
sysctl net.ipv4.tcp_keepalive_time 2>/dev/null

Interpret the baseline before moving on:

  • Expected: a healthy session survives normal idle periods and a black-holed path fails within the documented bound.
  • Abnormal: an application command is legitimately silent but transport remains alive, or an intermediate device has a shorter idle timeout.
  • Inconclusive: missing output can also mean the wrong context, permissions, namespace, log window, binary, or target. Prove those assumptions before treating absence as health.

Save the decisive output, exit status, and timestamp. Redact credentials, customer data, private topology, tokens, and complete environment dumps.

Apply the smallest candidate change

The following is state-changing example syntax, not an instruction to run it unchanged:

ssh -o ServerAliveInterval=15 -o ServerAliveCountMax=3 example-host

For ServerAliveInterval vs TCPKeepAlive, the proposed change is acceptable only when the read-only baseline predicts its effect and the rollback is available. The key risk is: aggressive liveness values can terminate healthy sessions during transient delay and interrupt stateful remote work.

Prefer an immutable artifact, validated configuration, dry-run, transaction, candidate object, or staged target when the tool supports one. Record the exact command and UTC time so later telemetry can be correlated to the change.

Verify the result from the outside in

ssh -vvv -o ServerAliveInterval=15 -o ServerAliveCountMax=3 example-host 'sleep 60; true'
printf 'exit=%s\
' \"$?\"

Verification for ServerAliveInterval vs TCPKeepAlive has three layers:

  1. The control plane or command reports the intended effective state.
  2. The process, resource, or data path reflects that state without a new pressure signal.
  3. The original user-visible or dependent-system path succeeds from an independent vantage point.

If ssh -vvv -o ServerAliveInterval=15 -o ServerAliveCountMax=3 example-host 'sleep 60; true' succeeds but the original path still fails, stop. The change may have repaired a local symptom while DNS, policy, routing, caching, dependency, or client state remains broken.

Failure branches

The baseline does not match this runbook

When an application command is legitimately silent but transport remains alive, or an intermediate device has a shorter idle timeout, do not force the candidate command. Return to identity and scope, compare a healthy peer only through effective settings, and name a new falsifiable mechanism.

The change succeeds but behavior does not

A successful ssh -o ServerAliveInterval=15 -o ServerAliveCountMax=3 example-host proves that one interface accepted a request. It does not prove convergence, readiness, data compatibility, external routing, or client recovery. Re-run the same evidence at each downstream boundary.

The change makes the system worse

Execute the written rollback: restore the previous keepalive settings, reconnect, and resume only idempotent work or follow the application's recovery procedure. Preserve the failed candidate and relevant logs long enough to explain the outcome; do not destroy the evidence with broad cleanup or repeated restarts.

Operator checklist

  • Confirm the exact target, context, identity, version, and active owner.
  • Capture the read-only baseline and one disconfirming observation.
  • Label ssh -o ServerAliveInterval=15 -o ServerAliveCountMax=3 example-host as state-changing during review.
  • Keep recovery access and rollback independent of the path being edited.
  • Change one layer, record UTC time, and wait for its real convergence boundary.
  • Verify the original path, adjacent controls, resource pressure, and persistence.
  • Update the runbook when observed behavior differs from the source-reviewed model.

Investigate it in Tryssh

Tryssh keeps the command, approval boundary, output, and verification beside the host conversation.

Tryssh can preserve this evidence loop and show a state-changing command for human approval. It does not make the operator's identity, recovery access, rollback, or platform authority decisions.

Evidence and review status

This ServerAliveInterval vs TCPKeepAlive runbook was source-reviewed on 2026-07-29 against current first-party documentation. The commands are illustrative and use example targets. The page does not claim that the change was reproduced across every distribution, managed service, version, network, or workload.

Limitations and trade-offs

Aggressive liveness values can terminate healthy sessions during transient delay and interrupt stateful remote work. Managed platforms may generate configuration, restrict privileges, replace local state, or expose a different control plane than the upstream project. Confirm the installed version and provider contract before applying a repair.

Search visibility is not proof of operational correctness. Treat this page as a decision aid, preserve independent recovery, and stop when the evidence contradicts its assumptions.

Related operator runbooks

Continue with SSH Match exec, ExitOnForwardFailure, the SSH automation foundation guide, and the SSH hardening checklist.

Sources and further reading