Hi,
I recognized the same problem today in two locations with PA-220. The users cannot login to GlobalProtect anymore, because the NAT and security policies which are applied by tag are not visible on the local devices anymore.
First just one location. Users told me about connection problems with GlobalProtect. By a look on the firewall I saw that the policies are missing, in the Panorama they were visible. I saw that there was an outstanding push on the Panorama, the preview showed that the policies I was missing should be applied to the location where they were missing. Very strange, because we just wanted to commit and push some shared objects to all locations. I pushed it and hoped it solves the problem. After the successful commit the policies still were not visible on the local device, just on the Panorama.
I tried a reboot of the Panorama and a reboot of the local firewall device without any improvement. Both locations with same configuration were running one month without any problems after the firmware upgrade to 10.1.3, since today. For testing I tried to trigger a new push of polices by applying a new security policy (also by tag) to the device-group-level where the two locations get the other policies (applied by tag) from. After the commit and push the second location, which was running fine up to this moment, got the same problems as the other one, the policies (the old ones) were not visible on the local device anymore. The new one for testing neither.
Panorama firmware version: 10.1.3-h1
My workaround: I cloned the polices (security and NAT) to each local device-group-level and deleted the device tag. Not nice, but working.
The answer from the Nikolay_Dimitrov does NOT point to the problem we described.
Best regards
... View more