How to make App-ID migration with a configuration splitted between Panorama and Firewall

Reply
L2 Linker

How to make App-ID migration with a configuration splitted between Panorama and Firewall

I have a customer installation with addresses and services defined in the Panorama as shared objects. On the other side, all rules (using those objects) are define as local policy on the firewall. When I import panorama config in migration tool I see all objects. But when I import firewall configuration, policies display addresses and addresses group object but not the services. All are set to "any". Did somebody allready had this kind of issues ? How can I make the link between panorama and firewall in the migration tool to be able to see my real configuration ?

L3 Networker

Re: How to make App-ID migration with a configuration splitted between Panorama and Firewall

> Shared Obects can be used on any managed device in any of the Device group

> Now, if you are able to see those shared objects and not the services there is a possible that the pushed configuration on the managed firewall had a manual override (Some one might have made the changes locally on that firewall)

 

> There is also a bug which states : Name overlaps between shared address and service objects and groups causes incorrect processing of unused shared objects on commit (PAN-OS 7.0.4)

 

> You can try to do a force push again all the device group and then try exporting the config on the managed firewall

L2 Linker

Re: How to make App-ID migration with a configuration splitted between Panorama and Firewall

Thanks for the reply.

The issue is not between Panorama and Paloalto device. The issue occurs when I import Paloalto configuration in the Migration tool. I see source and dest objects but not services.

So I'm not able to clone rules or split them between know and unknow traffic.

Highlighted
L2 Linker

Re: How to make App-ID migration with a configuration splitted between Panorama and Firewall

Can you share a screen shot descriping the issue?

L2 Linker

Re: How to make App-ID migration with a configuration splitted between Panorama and Firewall

OK, blelow is a config output from firewall where we can see in service member "Witness_UDP" or "Witness_TCP"

 

<entry name="Rule 5">
    <from>
        <member>INSIDE</member>
    </from>
    <to>
        <member>MANAGEMENT</member>
    </to>
    <source>
        <member>SVVPLXWIT001</member>
    </source>
    <destination>
        <member>NET-172.22.51.64-26</member>
    </destination>
    <application>
        <member>any</member>
    </application>
    <service>
        <member>Witness_UDP</member>
    </service>
    <action>allow</action>
</entry>
<entry name="Rule 6">
    <from>
        <member>INSIDE</member>
    </from>
    <to>
        <member>MANAGEMENT</member>
    </to>
    <source>
        <member>SVVPLXWIT001</member>
    </source>
    <destination>
        <member>NET-172.22.51.64-26</member>
    </destination>
    <application>
        <member>any</member>
    </application>
    <service>
        <member>Witness_TCP</member>
    </service>
    <action>allow</action>
</entry>

 

and here is the printscreen of the migration tool where we see that service is set to "any

Migration tool output

 

L7 Applicator

Re: How to make App-ID migration with a configuration splitted between Panorama and Firewall

Hi
have you tried with mt version 3.3??
L2 Linker

Re: How to make App-ID migration with a configuration splitted between Panorama and Firewall

It work with release 3.3. Thanks

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!