Manual Chapter :
Troubleshooting an INOPERATIVE guest
Applies To:
Show Versions
BIG-IP LTM
- 17.1.2, 17.1.1, 17.1.0, 17.0.0, 16.1.5, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0, 14.0.1, 14.0.0, 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0
BIG-IP DNS
- 17.1.2, 17.1.1, 17.1.0, 17.0.0, 16.1.5, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0, 14.0.1, 14.0.0, 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0
Troubleshooting an INOPERATIVE guest
After you upgrade the vCMP host to another BIG-IP software version, a vCMP guest sometimes remains in an INOPERATIVE state. If you then open a console window on the guest, you might see the following messages logged to the log file
/var/log/ltm
:To change the state of the guest to DEPLOYED, use the following procedure.01071038:5: Loading keys from the file. 012a0004:4: halStorageRead: unable to read storage on this platform. 01071029:5: Cannot open unit key store
- On the vCMP host, activate the boot partition that was active prior to the BIG-IP software upgrade.For example, if the previously-active boot partition was HD1.1, you can run this command:switchboot HD1.1.
- Display the master key for the host by opening a console window on the host, and at the system prompt, typing the commandf5mku -K.Here is sample output from thef5mku -Kcommand:8/igZhCdlag5Z4rbuOpFtg==
- Activate the boot partition that contains the upgraded version of the BIG-IP software.For example, if the boot partition for the upgraded BIG-IP version is HD1.2, you can run this command again:switchboot HD1.2.
- Verify that the master key on the upgraded version is the same as the master key on the previous version (viewed in Step 2) by typing the commandf5mku -Kagain.
- If the master key is not the same on both software versions, then update the master key on the upgraded version (in the newly-active partition):typing this command:f5mku -rmaster key
- If you know the unencrypted password or passphrase, type this command:tmsh modify /sys master-key prompt-for-password. This is the recommended way to reset the master key.
- If you only know the encrypted password or passphrase, type this command:f5mku -r. Use this command with caution. Using themaster key-roption when the file/config/bigip.confcontains encrypted passwords or passphrases will cause a BIG-IP load operation to fail.
For example:f5mku -r 8/igZhCdlag5Z4rbuOpFtg== - At the system prompt, comment out the sym-unit-key of every guest by typing this command:sed -i.bak 's/sym-unit-key/#sym-unit-key/g' /config/bigip.confThis command edits the file /config/bigip.conf.A backup of this file is automatically created: /config/bigip.conf.bak
- At the system prompt on the host, load the host configuration by typing this command:tmsh load sys config
- Reboot the host by typing the commandtmsh rebootWithout a reboot, the changes will not take effect.
After the host has finished rebooting, all guests should boot normally.
