F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

masterdead's avatar
masterdead
Icon for Nimbostratus rankNimbostratus
Mar 07, 2017

ASM xml/json profile failed - viprion

Hi,

 

we are experienced a strange problem with ASM in our viprion two blades setup. Situation: We have configured a 18 policies in ASM. Currently i need to create another one, but just a copy from existing policy. I tried two ways: first i tried to export policy (binary format) and import to new policy. Second, create a template from origin and create new policy from this template. It is ok, no problem. But, when i enable policy to production, only viprion blade number one has a problem with json and xml profiles, causing "Malformed JSON data" and "Malformed XML data". Second blade doesn't report this messages. I tried to use origin policy to project, everything is ok, without error. It is really weird, because this problematic policy i removed many times, and still experiencing problem on blade number one.

 

Did anyone experience with this problem?

 

I didn't restart ASM process, but maybe i have to in the future.

 

ASM Advanced WAF
BIG-IP
security

1 Reply

  • Leonardo_Souza's avatar
    Leonardo_Souza
    Icon for Cirrocumulus rankCirrocumulus
    Mar 08, 2017

    As long as you are doing the changes in the primary blade, the configuration should sync with the secondary blade. You can check the configuration in each blade, to make sure the policy change has been correctly synchronized with the other blade.

     

    If synchronization does not work, there is major problem there. You can try a mcpd reload, that includes a reboot, and check if fixes. You could also open a F5 support case, and provide the data they ask for.

     

    Solution about mcpd reload:

     

    https://support.f5.com/csp/article/K13030