AFM Firewall Policy Export / Import

Do you have any issues to ask this question? If the rules use vlans then the same vlans should exist in Velos like in Viprion but outside of that the AFM rules are not related to blade or platform from what I have seen, so if you make the Velos and VIPRION be the same version, you should not have issues in my opinion.

Outside of that if you are migrating between VIPRION and VELOS better use the migration tool:

GitHub - f5devcentral/f5-journeys: F5 Journeys Migration Utility - migrate or upgrade BIG-IP into new F5 platforms

 Migrate your BIG-IP Configuration using F5 Journeys App (youtube.com)

Also if the rules use zones, address lists or port lists (shared objects) then they probably should be on Velos before the policy being imported but then you will see this issue even if you do policy export and import from one Viprion to another maybe if you have test one.

About AFM address and port lists,About AFM address and port lists,About AFM address and port lists,About AFM address and port lists,About AFM address and port lists,About AFM address and port lists,About AFM address and port lists,About AFM address and port lists,About AFM address and port lists (f5.com)

Hello T0nyP,

the underlaying plattform/Hardware is not important at this step.

It seems you are just want to "copy" your afm policies from your viprion GUEST to a new velos TENANT.

Since AFM is not yet ported to BIGIP Next, I expect you mean an BIGIP Classic tenant which is just like a viprion guest.

so you have all abilities bigip offers you on both plattforms.

About AFM Policies:

I dont know any "export" Button to do this.

My first try would be via CLI TMSH / Plane Configuration files

of course addressing the underlaying dependencies Nikoolayy1 mentioned like VLANs and Objects