Last Modified: Apr 24, 2024
Affected Product(s):
BIG-IP vCMP
Known Affected Versions:
14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 17.0.0, 17.0.0.1, 17.0.0.2
Opened: Oct 27, 2020 Severity: 3-Major
Attempting to deploy an engineering hot fix (EHF) for ID871561 (https://cdn.f5.com/product/bugtracker/ID871561.html) fails in the same manner
Unable to perform software installations on vCMP guests using installation media located on the vCMP host even if fix for ID871561 is available on VCMP guest.
-- Attempting to install an EHF containing a fix for ID871561 on a vCMP guest -- The fix for ID871561 has not already been applied to the vCMP guest
Option 1: =========== Make sure that the .iso files for both base image and engineering hotfix are copied to the vCMP guest (under /shared/images) before starting the installation. If installing the software from the command line, use syntax similar to the following: tmsh install sys software hotfix <hotfix-image-name> volume <volume.name> Option 2: =========== Even if the engineering hotfix installation has failed, the base image should still have been installed properly. You can restart the vCMP guest and perform a hotfix installation on top of already installed base image, using syntax similar to the following: tmsh install sys software hotfix <hotfix-image-name> volume <volume.name> Option 3: =========== Even if the engineering hotfix installation has failed, the base image should still have been installed properly. Ensure there is copy of the engineering hotfix image locally within the vCMP Guest. Then restart the lind service on the vCMP Guest: tmsh restart sys service lind If running the vCMP Guest on multiple slots, you may need to restart lind on all slots. From the primary slot on the vCMP Guest, run: clsh tmsh restart sys service lind The hotfix installation should begin again, this time using the hotfix from within the /shared/images/ location on the vCMP Guest. Option 4: =========== Manually eject the CD from the vCMP guest's virtual CD drive, and then restart lind. On the vCMP Guest: 1. Confirm the wrong ISO image is still locked (inserted in the CD drive): isoinfo -d -i /dev/cdrom Note: Pay attention to the volume ID in the output from within the vCMP guest. 2. Unlock (eject) the image: eject -r -F /dev/cdrom && vcmphc_tool -e 3. Verify the CD drive is now empty: isoinfo -d -i /dev/cdrom The output should report an error that includes: <...> Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0 <…> 4. Restart lind: tmsh restart sys service lind If running the vCMP Guest on multiple slots, you may need to restart lind on all vCMP Guest slots. From the primary slot on the vCMP Guest, run: clsh tmsh restart sys service lind
None