Last Modified: Nov 07, 2022
Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 12.1.4, 22.214.171.124, 12.1.5, 126.96.36.199, 188.8.131.52, 184.108.40.206, 12.1.6
Opened: Jun 07, 2016 Severity: 2-Critical Related Article:
Related Article: K26397341
In rare conditions, Control REST may core when necessary services and resources are not fully initialized. One typical scenario for this is logging in immediately after restarting the BIG-IP system.
Impacts usability of iControl REST. This is a rare occurrence.
This happens when all the necessary services required by iControl REST are not available, such as when they are not fully initialized upon restart.
To work around this issue, allow the BIG-IP system to fully start before you access the iControl REST API.
iControl REST no longer rarely cores when logging in immediately after restarting the BIG-IP system.