Bug ID 927713: Clsh reboot hangs when executed from the primary blade.

Last Modified: Oct 16, 2023

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5

Fixed In:
16.1.0,, 14.1.5

Opened: Jul 16, 2020

Severity: 3-Major


-- When 'clsh reboot' is executed on the primary blade, it internally calls ssh reboot on all secondary blades and then reboots the primary blade. The 'clsh reboot' script hangs, and there is a delay in rebooting the primary blade. -- Running 'ssh reboot' on secondary blades hangs due to sshd sessions getting killed after network interface down.


A secondary blade is not rebooted until clsh or ssh closes the connection to that blade.


-- Running 'clsh reboot' on the primary blade. -- Running 'ssh reboot' on secondary blades.


Perform a reboot from the GUI.

Fix Information

Running 'clsh reboot' on the primary blade or 'ssh reboot' on a secondary blade no longer hangs, so operations complete as expected.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips