NimbostratusI am unable to export one of the ASM Policy. It is simply showing "could not export". How can I troubleshoot it?
Note: ASM Policy is in Transparent Mode.
Other policies in transparent modes are exporting.
NimbostratusI have a similar issue, but I cannot import a policy
NimbostratusPlease check the error it is specifying during import and go to that line number and see. If you want to share the error msg then welcome.
NimbostratusHi,
I got the answer (but is assumption). The only difference with other policies is that of name. It contains the dot (.) and Colon (:) in their name. for example: ASM Policy name: abc.test.com:1234
NimbostratusASM Policy is in blocking mode now. But still I m unable to export the ASM Plicy.
Nimbostratus
Please check this error while exporting the policy. All other policies are able to export but only this one is not able to export.
CirrocumulusThe name of the policy might be a clue - when you export and download the policy from ASM it is converted from mySQL database on ASM into a file and ":" character is illegal in file names. What version of BIG-IP are you using? in version 12.1 the export works fine and the invalid characters are converted into underscore "_" so policy name abc.test.com:1234 becomes abc.text.com_1234
a reminder that you cannot use the following special characters in file names (on Windows)
\ / : * ? | < > "
Avoid using the above characters for any object names or file names.
Also check for any errors in /var/log/asm and post here and of course - do raise a Support case with F5!
CirrocumulusI have just discovered that this error 'ASM Could not export policy' also appears when there is not enough disk space left in your default download location. Check the Downloads folder of your browser and check the available disk space.