Last Modified: Oct 16, 2026
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
17.5.1.5, 17.5.1.6, 17.5.1.8, 17.5.1.9, 17.5.1.10, 21.0.0.3, 21.1.0, 21.1.0.1, 21.1.0.2, 21.1.0.3
Opened: Oct 14, 2026 Severity: 3-Major
When a client sends a valid reboot request to the BIG-IP iControl REST endpoint, the system may initiate the reboot but close the HTTPS connection before returning an HTTP status code or JSON payload. The client may report response code 000. This indicates that no HTTP status line was received; it is not an HTTP status returned by BIG-IP.
-- REST API clients cannot reliably determine whether the reboot request was accepted because the BIG-IP may reboot without returning an HTTP acknowledgment. -- The issue also impacts Big-IQ-managed BIG-IP upgrades. BIG-IQ may report a false reboot or upgrade failure when the BIG-IP closes the connection during reboot, even though the BIG-IP boots to the intended volume and the upgrade may complete. The upgrade workflow may not proceed to post-installation tasks.
-- BIG-IP iControl REST is used to initiate a system reboot. -- The request is sent to the /mgmt/tm/sys endpoint. -- The request contains the reboot command, with or without a target volume. -- The BIG-IP begins reboot processing while the HTTPS management connection is still active.
None
None