Forum Discussion

adub11_313980's avatar
adub11_313980
Icon for Nimbostratus rankNimbostratus
Mar 31, 2017

ASM Security Policy Upload Failed

Our organization has the ASM installed in our production and QA environments. I am trying to import a security policy in our QA environment, but always receive the simple message "Upload failed. Please try again". In production, the import seems to work fine.

 

I saw another post (that I can't seem to find right now) that indicated the issue was a problem with disk space on the root of the drive. Are there any other issues that can cause this error or troubleshooting tips? I am still trying to confirm disk space is not an issue, but it doesn't appear to be based on my limited view into the system.

 

ASM Advanced WAF
security
  • samstep's avatar
    samstep
    Icon for Cirrocumulus rankCirrocumulus
    Apr 02, 2017

    Free space could be an issue especially if your QA is a Virtual F5, however it is difficult to troubleshoot without further details. I suggest that you check for any error messages in /var/log/asm & /var/log/ltm files and open a support case with F5 by e-mailing: support@

     

  • Jinshu's avatar
    Jinshu
    Icon for Cirrus rankCirrus
    Apr 04, 2017

    Hi mate,

     

    I'm not sure if you have tried below KB or the version you are using matches. Anyhow its worth checking the ASM root folder as well as signature sets.

     

    KB13246

     

    -Jinshu

     

  • adub11_313980's avatar
    adub11_313980
    Icon for Nimbostratus rankNimbostratus
    Apr 19, 2017

    Thanks very much to those who responded to my question. One of our engineering team worked with F5 and determined this was in fact a disk space issue. Here's the information that was passed along to resolve it.

     

    link text

     

    Check disk space, bash shell

     

    df -h

     

    -- 1. Extend the /shared directory by using the following command syntax: Note: Do not commit all of the disk resource that you have just added to the BIG-IP VE into extending the /shared directory, as the remaining added disk resource may be needed to perform software installation into a new software slot. tmsh modify /sys disk directory /shared new-size For example, you would enter the following command to extend the /shared directory to 10 GB: tmsh modify /sys disk directory /shared new-size 10485760 2. Save the configuration by typing the following command: tmsh save /sys config 3. Reboot the BIG-IP VE by typing the following command: reboot 4. When the BIG-IP VE is up, log in to the command line on the BIG-IP VE. 5. Verify that the /shared directory is successfully extended to the size you have specified in step 6, by typing the following command: tmsh show /sys disk directory