Bug ID 927713: Secondary blade IPsec SAs lost after standby reboot using clsh reboot

Last Modified: Jan 22, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,

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.


Secondary blade IPSec Security Associations (SAs) are lost, resulting in SA sync issues.


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


Perform a reboot from the GUI.

Fix Information


Behavior Change