Bug ID 538911: AAM module storage device missing

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP AAM(all modules)

Known Affected Versions:
11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
12.0.0

Opened: Aug 10, 2015
Severity: 3-Major
Related AskF5 Article:
K17128

Symptoms

Proper use of the AAM module in vADC requires that the BIG-IP user attach a second disk to the virtual appliance. However, there is no enforcement of this. If the BIG-IP user does not provide the second disk, the primary disk is over-committed and there is no space left to perform upgrades.

Impact

The primary disk is full; software management actions fail with 'disk full' errors.

Conditions

Provisioning AAM in a 'better' or 'best' vADC image.

Workaround

1. Login as root, either via ssh to the management IP address or using the console. (Note: Using a self IP address does not work because the software stops TMM during this process.) 2. To determine whether HD2 is already set to datastor mode, run the following command: tmsh list /sys disk logical-disk HD2 When HD2 is not in datastor mode, the command returns output similar to the following example: sys disk logical-disk HD2 { size 20480 vg-reserved 4096 } 3. To modify HD2 to be datastor mode, run the following command: tmsh modify /sys disk logical-disk HD2 { mode datastor } 4. To verify HD2 is in datastor mode, run the following command: tmsh list /sys disk logical-disk HD2 When HD2 is in datastor mode, the command returns output similar to the following example: sys disk logical-disk HD2 { mode datastor size 20480 vg-reserved 4096 } 5. Save the changes by running the following command: tmsh save /sys config 6. Stop all daemons by running the following command: bigstart stop 7. Determine the full path in the /dev directory for the datastor logical volume by running a command similar to the following example: lvscan | grep datastor Example output: ACTIVE '/dev/vg-db-sda/app.datastor.dat.datastor' [81.32 GB] inherit 8. Remove the datastor volume by running a command similar to the following example: lvremove /dev/vg-db-sda/app.datastor.dat.datastor 9. Reboot the system by running the following command: reboot 10. Wait for the system to come back up before upgrading the system.

Fix Information

Specific reference to the AskF5 Article is also provided in the installation log when the software upgrade attempt fails.

Behavior Change