Manual Chapter :
Software Management
Applies To:
Show VersionsBIG-IP APM
- 17.1.0, 17.0.0, 16.1.5, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0
BIG-IP Analytics
- 17.1.0, 17.0.0, 16.1.5, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0
BIG-IP Link Controller
- 17.1.0, 17.0.0, 16.1.5, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0
BIG-IP LTM
- 17.1.0, 17.0.0, 16.1.5, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0
BIG-IP PEM
- 17.1.0, 17.0.0, 16.1.5, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0
BIG-IP AFM
- 17.1.0, 17.0.0, 16.1.5, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0
BIG-IP DNS
- 17.1.0, 17.0.0, 16.1.5, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0
BIG-IP ASM
- 17.1.0, 17.0.0, 16.1.5, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0
Software Management
About software management
You can manage the software images, hotfixes, and boot locations on the BIG-IP system using the Configuration utility. You can also
enable the automatic software update feature.
Import a
software image
If you previously downloaded a BIG-IP
software image file (ISO) to a management workstation, you can upload that file to the
BIG-IP system.
You can use the Configuration utility to import an
ISO that you have stored on a management workstation.
- On the Main tab, click.The Image List screen displays a list of existing image files.
- ClickImport.The New Image screen opens.
- For theSoftware Imagesetting, clickBrowse.
- ClickImport.A progress indicator displays as the BIG-IP system uploads the file.Be sure that you do not navigate away from the screen until the image import process is complete.
Install a
software image
You can use the Configuration utility to install
an ISO that you have imported to the BIG-IP
system.
- On the Main tab, click.The Image List screen displays a list of existing image files.
- For theAvailable Imagessetting, select the ISO to install.The Install Software Image screen opens.
- For theSelect Disksetting, select the disk on which to install the software (for example, MD1 or HD1).You can install software only on inactive volumes. To install software to the active volume, you must boot to a different volume.
- For theVolume set namesetting, select the volume on which to install the software.
- ClickInstall.A progress indicator displays as the BIG-IP system installs the software image.
Import a hotfix image
If you previously downloaded a BIG-IP hotfix file
to a management workstation, you can upload that file to the BIG-IP
system.
You can use the Configuration utility to import a hotfix that you have
stored on a management workstation.
- On the Main tab, click.The Hotfix List screen displays a list of existing hotfix files.
- ClickImport.The Upload Hotfix screen opens.
- For theSoftware Imagesetting, clickBrowse.
- ClickImport.A progress indicator displays as the BIG-IP system uploads the file.Be sure that you do not navigate away from the screen until the image import process is complete.
Install a hotfix
image
You can use the Configuration utility to install a
hotfix that you have imported to the BIG-IP
system.
- On the Main tab, click.The Hotfix List screen displays a list of existing hotfix files.
- For theAvailable Imagessetting, select the hotfix to install.The Install Software Hotfix screen opens.
- For theSelect Disksetting, select the disk on which to install the software (for example, MD1 or HD1).You can install software only on inactive volumes. To install software to the active volume, you must boot to a different volume.
- For theVolume set namesetting, select the volume on which to install the software.
- ClickInstall.A progress indicator displays as the BIG-IP system installs the hotfix.
Boot to a
different volume
You can use the Configuration utility to boot to a
different software volume (target boot location) on the BIG-IP system.
- On the Main tab, click.The Boot Locations List screen displays a list of available boot locations.
- For theBoot Locationsetting, click a software volume name (the target boot location).
- For theGeneral Propertiessetting for the target boot location, select whether to copy the configuration from the current boot location to the target boot location.
- ClickActivate.The system reboots to the selected software volume.
Configure update check
You can use the Configuration utility to configure whether the
BIG-IP system automatically checks for updated software.
- On the Main tab, click.
- For theAutomatic Update Checksetting:
- SelectEnabledif you want the system to check for updates automatically.
- SelectDisabledif you want to check for updates manually.
- ClickApply Settingsto save your changes.
- ClickCheck Nowto manually check for updates.
About Liveinstall signature checking in ccmode
For each full release ISO, vADC OVA, and hotfix ISO, a corresponding signature file will be
available with the .sig extension. The signature file is handled exactly like an ISO. When the
ccmode feature is turned on, the installation process requires you to download the ISO file, as
well as the
iso.sig
.The signature file is located in
iso-name.384.sig
, and uses the 307 key/384 hash signature.
If an older key (2048 key/256 has signature) is also found, the system will attempt to validate the signature created by the
larger key size (the 307 key/384 hash signature).When you run the ccmode script to put the sensor into a Common Criteria configuration, a db
variable called
liveinstall.checksig
is automatically enabled. This feature
compares the ISO file against a sys software signature file, which is meant to catch integrity
issues with the product.This feature can only be controlled through
tmsh
.Signature validation is the first step performed during the liveinstall process, so if the
corresponding signature file for the selected software is not in the library, the installation
will not begin.
If
liveinstall.checksig
is enabled, software installs
will fail if the user copies only the ISO to the /shared/images
directory.
It is important to download both the ISO and the iso.sig
files to the
/shared/images
directory.In the event of liveinstall failure, two error messages can occur:
- Signature file not found
- This means you have not downloaded the correspondingiso.sigfile with the ISO. The best way to verify if theiso.sigis present is to run the commandlist sys software signature. The commandshow sys softwarewill not show theiso.sigfiles.
- Archive signature test failed
- This might happen if:
- The product ISO is in/shared/images.
- Theiso.sigis present in/shared/images.
- When theiso.sigfile was compared against the product ISO, the comparison failed.
iso.sigfiles and try again.
Download
the .sig file
If you are running your machine in ccmode, you will need to download an
iso.sig
file in addition to the ISO file that you normally
download.
- In a browser, open the F5 Downloads page (https://downloads.f5.com).
- From the Downloads Overview page, clickFind a Download.The Select a Product Line screen displays.
- Download the version's base ISO file, such as version 11.5, and its associated signature file. The signature file is located iniso-name.384.sig.The signature file has the same name as the ISO file with an additional .sig extension.
- Log in to the command-line interface of the system using the root account.
- Open the TMOS Shell (tmsh).tmsh
- Enable the signature file.modify sys db liveinstall.checksig value enableYou do not need a .sig file to install versions earlier than 11.5.
- Install the signature file.install sys software imagePressTabto use tab completion to list the ISO files that have a correspondingiso.sigfile present at the time you run the command.