Last Modified: Oct 16, 2023
Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 126.96.36.199, 188.8.131.52, 184.108.40.206
14.0.0, 220.127.116.11, 18.104.22.168
Opened: Sep 26, 2017 Severity: 3-Major Related Article:
Related Article: K93145012
Software 'install hotfix' commands fail with a message similar to the following: Image (BIG-IP-22.214.171.124.0.317.iso) has a software image entry in MCP database but does not exist on the filesystem.
Cannot apply hotfix until the full base image is present.
Before installing the hotfix, the necessary full (base) software image prerequisite was added to the images directory, but then was removed before issuing the hotfix command. For example, to apply 'Hotfix-BIG-IP-126.96.36.199.0.338-HF2.iso', the system must have access to the base image; 'BIG-IP-188.8.131.52.0.317.iso'. Here is another example: on multi-bladed VIPRION systems, where it is resolved by running 184.108.40.206. 1) Install and boot into 12.0.0 on the VIPRION system: -- install /sys software image 12.0.0.iso create-volume volume HD1.test -- reboot volume HD1.test 2) Install and boot into 220.127.116.11.402.249: -- install /sys software hotfix Hotfix-BIG-IP-18.104.22.168.402.249-ENG.iso create-volume volume HD1.test2 -- reboot volume HD1.test2 3) Delete 12.0.0.iso and volume HD1.test: -- delete sys software image 12.0.0.iso -- delete sys software volume HD1.test 4) Copy over Hotfix-BIG-IP-22.214.171.124.0.17.1-ENG.iso without the 126.96.36.199 base image. 5) Check the /var/log/ltm logs for the following message: -- lind: 013c0006:5: Image (BIG-IP-188.8.131.52.0.606.iso) has a software image entry in MCP database but does not exist on the filesystem.
Perform the following procedure: 1. Copy the base image to the images directory on the BIG-IP system. 2. Restart the 'lind' daemon. 3. Try the hotfix installation operation again.
Issuing a 'install hotfix' command when the base image is not available sends the system into a 'wait' state. The process status is 'waiting for base image', which should make clear what needs to be done. When the base image becomes available (in the images directory), the hotfix installation proceeds.