About FilipElsen.Proximus

Hi,   I have a 2 Checkpoint clusters to be migrated to Palo Alto, Panorama managed. The checkpoints are centrally managed via 1 security policy , while on each cluster the routing and dmz can be different. In the example clusterA has 1 local dmz, which isn't exsiting on ClusterB. 1. I've imported the Checkpoint objects, rulebases, policy into Expedition: OK 2. I've re-created the 2 routing tables for ClusterA and ClusterB: OK When performing an "auto-zone assign" on all rules, using the virtual router of ClusterA, the zone info is added and is correct with regards to the 1 local dmz: OK When performing a 2nd "auto-zone assign" on all rules, but using the virtual router of ClusterB, the zone info is overwritten (not appended) by this lookup. Is there any possibility to "append" the zones when running "auto-zone assign" with multiple virtual routers?   Thanks a lot, Filip ... View more

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 Elsen API calls Config merge     ... View more

Hi,   I'm installing Minemeld behind a proxy server using the Ubuntu 14.04.05LTS image. The strange thing is that last week I've used exactly the same approach for demo purposes and Minemeld worked like a charm and got a 'Go' for it for production. This week, following the same approach the Minemeld instalation fails. I confirm that the VM has internet access by configuring the proxy settings in: /etc/environment AND /etc/apt/apt.conf "Curl -k http://minemeld-updates.panw.io" is working fine. I've tried with and without installing the lastest Ubuntu patches, but not luck. Tried using the unstable version, but no luck either.   I'm uploading the output during the instalation.   Following were issues detected: Setting up collectd-core (5.4.0-3ubuntu2.2) ... * Starting statistics collection and monitoring daemon collectd ...fail!   Setting up minemeld (0.9.11-2build1) ... 2018-06-05 16:34:59,609 ERROR:0.9.11 Symbolic link current in /opt/minemeld/engine not found: [Errno 2] No such file or directory: '/opt/minemeld/engine/current' 2018-06-05 16:34:59,609 ERROR:0.9.11 Symbolic link current in /opt/minemeld/www not found: [Errno 2] No such file or directory: '/opt/minemeld/www/current' 2018-06-05 16:34:59,610 ERROR:0.9.11 Symbolic link current in /opt/minemeld/prototypes not found: [Errno 2] No such file or directory: '/opt/minemeld/prototypes/current' 2018-06-05 16:34:59,610 INFO:0.9.11 Current status: 2018-06-05 16:34:59,610 INFO:0.9.11 minemeld-engine: current: None latest: None 2018-06-05 16:34:59,610 INFO:0.9.11 minemeld-webui: current: None latest: None 2018-06-05 16:34:59,610 INFO:0.9.11 minemeld-prototypes: current: None latest: None 2018-06-05 16:39:38,032 CRITICAL:0.9.11 Error running curl: curl: (7) Failed to connect to minemeld-updates.panw.io port 80: Connection timed out   Any ideas about this issue? Thanks a lot, Filip     ... View more