Bug ID 552481: Disk provisioning error after restarting ASM service.

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
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, 12.0.0, 12.0.0 HF1, 12.0.0 HF2

Fixed In:
12.1.0, 12.0.0 HF3, 11.6.1

Opened: Oct 14, 2015
Severity: 2-Critical
Related Article:
K25086712

Symptoms

Disk provisioning error after restarting ASM service. In newer BIG-IP software versions ASM uses a different application volume name. Older BIG-IP software versions identify the application volume as being owned by ASM, and allows ASM to be provisioned and start. However, in the older versions, ASM create the application volume so there will be two ASM application volumes. If ASM is restarted with bigstart or tmsh, or if the BIG-IP system is rebooted, provisioning does not allow ASM to start.

Impact

ASM does not start, and bigstart status asm indicates a disk provisioning error.

Conditions

ASM provisioned on both pre-v12.0.0 and post-v12.0.0 versions.

Workaround

Follow these steps: 1. Boot into the affected version of BIG-IP software. 2. If DoS profiles are applied, they need to be removed from the virtual servers before the provisioning can be carried out, for example: # tmsh modify ltm virtual all profiles delete { DoS-A-profile } # tmsh modify ltm virtual all profiles delete { DoS-B-profile } ..... 3. Run the command: tmsh modify sys provision asm level none. 4. Wait for unprovision to complete (do so by monitoring /var/log/asm). 5. Run the command: tmsh delete sys disk application-volume asmdata1. 6. Run the command: tmsh modify sys provision asm level nominal

Fix Information

ASM starts successfully with no disk provisioning error after restarting ASM service using newer BIG-IP software.

Behavior Change