Reply
L1 Bithead
Posts: 8
Registered: ‎11-08-2016

Expedition API when migrating Checkpoint to VSYS - zone issues

Hi,

 

I'm having a project for migrating several Checkpoint clusters to Palo Alto Vsys.

I'm using Expedition version: 1.0.106 (the issue also resides in earlier versions).

 

I'm hitting an issue when migrating the zones.

1.Interfaces, virtual router and zones will be directly configured on the related gateway using API.

2.Security policy and NAT will be loaded into the Panorama's specific devicegroup.

 

The issues is at stage 1.

>migrating and configuring the interfaces using API works fine.

>migrating and configuring the VR using the API works fine.

>However the migration of zones isn't working at all.

The zones (L3) has an interface associated which is also migrated and for which the creation (by API) worked out fine.

 

The API error output: 

{"6":{"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":"2018-10-16 05:51:22"}}

I confirm in the situation above the interface: ae2.313 has been successfully configured using API.

 

=> Only when you detach all interfaces from ALL zones, export the config - merge - generate API cmds - send API cmds the zones are created.

 

Couple remarks:

-Interfaces can be mapped (manually) to the correct VSYS in the Expedition tool.

-Virtual routers cannot be mapped to a VSYS in the Expedition tool.

-Zones cannot be mapped to a VSYS  in the Expedition tool, but within the zone view you can select an extra column: vsys.

.... but it cannot be edited?

 

Would be good to have a solution on this one....

Thanks a lot,

Filip ElsenExpedition_API calls.PNGAPI callsExpedition_Merge.PNGConfig merge

 

 

L7 Applicator
Posts: 908
Registered: ‎03-22-2011

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

Hi,

 

Im not sure if I understand the problem....

 

Have you clicked on MERGE after the drag and drop?

 

Then from the PANOS config you can go to DEVICE - VIRTUAL SYSTEM and attach the VR and Interfaces there. The same from the Zones itself you can assign to the VSYS...

 

What is exactly the problem you are facing?

L1 Bithead
Posts: 8
Registered: ‎11-08-2016

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

Hi,

 

Yes, the config has been merged.

The issue is that when using the API to sent the network config towards the gateway (Pa5250), the subinterfaces, virtual router and routes get created, but the zones not.

The zones only get pushed towards the gateway if all interfaces are detached from it, prior to performing a merge.

 

Best regards,

Filip

 

L1 Bithead
Posts: 8
Registered: ‎11-08-2016

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

Hi, any update on this one?

Thanks,

 

L1 Bithead
Posts: 8
Registered: ‎11-08-2016

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

Interfaces are correcly created on the gateway using the API.

Routes are correctly created on the gateway using the API.

For every zone within the configuration, I'm receiving the output as shown below:

The API error output: 

{"6":{"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":"2018-10-16 05:51:22"}}

 

All interfaces are L3, created earlier and have a correct ipv4 associated.

 

L7 Applicator
Posts: 908
Registered: ‎03-22-2011

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

[ Edited ]

Have you send the Interfaces first?

L1 Bithead
Posts: 8
Registered: ‎11-08-2016

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

Yes, sure. These are created using API.

Only the zone(s) - all of them - are causing issues.

Has this been validated, tested?

 

Thanks a lot,

Filip

L3 Networker
Posts: 63
Registered: ‎05-01-2009

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

I was able to recreate your issue and will file a report for review:

 

Workaround - to send the config via API calls to Panorama

-send the interfaces, ethernet and aggregate interfaces first

-send the zones (remove the AE interface first from the zone)

-on panorama edit the zone and add the AE as a member

L3 Networker
Posts: 63
Registered: ‎05-01-2009

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

after more testing and debugging found the issue is with PanOS and not with the API request being generated by Expedition.

 

This only applies to AE interfaces being added to a security zone.

 

Workaround:

Assumption is that the AE configuration has been completed in Expedition

 

From the API output manager

-send the interfaces

-send the virtual router

-remove the AE from the security zone

-send the zone

 

Transition to Panorama and add the AE to the appropriate security zone

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!