Expedition API when migrating Checkpoint to VSYS - zone issues

Re: Expedition API when migrating Checkpoint to VSYS - zone issues



I've just tested the proposed approach using API:

From the API output manager

-send the interfaces

-send the virtual router

-remove the AE from the security zone

-send the zone

=> This is working indeed.

As mentioned, the Interface / Zone mapping is required to be performed manually when the config is loaded onto the device.


After the config was loaded via API (subint, vrouter and zone) I tried to get around the "zone to interface mapping" by:

-Performing a commint on the FW

-Re-import the device running config into Expedition

-Loading the project configuration with the (pre-zone cleanings / thus containing the zone & interface mappings)

-Export and Merge only the zone config. (the rest is already onn the device, only the zone to interface mapping is missing).

-Generate the API commands

-....but it fails in the same way.

{"21":{"device":"UTRFWONE5","status":"fail","text":"<msg><line><![CDATA[ zone -> Zone27 -> network -> layer3 \\'ae2.313\\' is not a valid reference]]><\/line><line><![CDATA[ zone -> Zone27 -> network -> layer3 is invalid]]><\/line><\/msg>","date":"2019-02-08 04:07:35"}}


Best regards,


Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!