Last Modified: Jul 18, 2026
Affected Product(s):
BIG-IP All
Known Affected Versions:
11.5.1, 11.5.1 hf1, 11.5.1 hf2, 11.5.1 hf3, 11.5.1 hf4, 11.5.1 hf5, 11.5.1 hf6, 11.5.1 hf7, 11.5.1 hf8, 11.5.1 hf9, 11.5.1 hf10, 11.5.1 hf11, 11.5.2, 11.5.2 hf1, 11.5.3, 11.5.3 hf1, 11.5.3 hf2, 11.5.4, 11.5.4 hf1, 11.5.4 hf2, 11.5.4 hf3, 11.5.4 hf4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3
Fixed In:
12.0.0
Opened: Oct 01, 2014 Severity: 3-Major Related Article:
K17367
Attempts to modify the ssh daemon logging level have no effect. The log level is always 'info' (the system default). Note: You might find sshd log messages in a different log file from prior releases. Beginning with 11.5.0, the system posts log messages from sshd in /var/log/ltm. In pre-11.5.0 releases, sshd messages appeared in /var/log/secure.
sshd continues to log info-level messages, so users are unable to filter ssh logs.
The results of this issue are evident when you modify sshd log-level by running a command similar to the following: tmsh modify /sys sshd {log-level error}. However, there are no special conditions to trigger the sshd log message delivery to /var/log/ltm or /var/log/secure.
None.
Setting the sshd log-level now correctly logs entries.