Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP All
Known Affected Versions:
11.2.1, 11.4.1, 11.5.1
Fixed In:
11.6.0, 11.5.2, 11.4.1 HF9, 11.2.1 HF15
Opened: Jun 12, 2014 Severity: 1-Blocking Related Article:
K16007
When booting an affected release, the system will not go active and mcpd will not come up. In /var/log/ltm, an error similar to the following will be seen. err mcpd[1234]: 01071335:3: Invalid logical_disk (0) for application volume (mysqldb_.2). This causes the system to have an inconsistent view of the disks and subsequent steps in the boot process fail to complete.
The system will not go active.
This only happens on the 11050 platform running an affected release. It occurs on boot into TMOS.
If there is a duplicate platform name in /etc/hal/platform-capabilities.xml, the xml file is loaded improperly which causes problems. Specifically, the software raid capability of the 11050 is not detected properly. The fix is to manually edit the /etc/hal/platform-capabilities.xml file and resolve this conflict, and then reboot. Changing the 11050 Nebs platform name to "BIG-IP 11050N" will workaround the issue. /etc/hal/platform-capabilities.xml: --BEFORE--- <platform name="BIG-IP 11050" pid="E102" > <!-- Turbo Apollo --> <raid type="software" /> </platform> <platform name="BIG-IP 11050" pid="E103" > <!-- Turbo Apollo NEBS --> <------ Duplicate entry <raid type="software" /> <nebs value="true" /> ---AFTER--- <platform name="BIG-IP 11050" pid="E102" > <!-- Turbo Apollo --> <raid type="software" /> </platform> <platform name="BIG-IP 11050N" pid="E103" > <!-- Turbo Apollo NEBS --> <------ fixed entry <raid type="software" /> <nebs value="true" /> </platform> All you need to do is add an "N", changing the platform name for Turbo Apollo NEBS to "BIG-IP 11050N", which resolves the conflict. After making the change, save the file, reboot the box, and it should come up normally.
The platform capabilities file which was causing this issue has been modified to allow the system to go active normally.