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

[pglohr]

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 ?

[vkalal]

> 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

[pglohr]

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.

[M.Alzahaby]

Can you share a screen shot descriping the issue?

[pglohr]

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

[alestevez · Accepted solution]

Hi
have you tried with mt version 3.3??

[pglohr]

It work with release 3.3. Thanks