Panorama 4.0.5 Pushing Policy to 3.1.9

L0 Member

Panorama 4.0.5 Pushing Policy to 3.1.9

Confirmed with support that if Panorama is running 4.0.5 and a managed device is 3.1.9 policy will not Push to the remote device from Panorama.  The workaround would be to downgrade Panorama to 4.0.4 which requires reboot and reindexing or upgrade remote device to 4.0.x  As per the recent discussions of the data plan resets of the latter version. (See perhaps its best to wait until they fix it on 4.0.6.

L5 Sessionator

Re: Panorama 4.0.5 Pushing Policy to 3.1.9

We are aware of Panorama 4.0.5 not able to commit to 3.1.x devices. As you mention, workaround is to downgrade Panorama to 4.0.4. Fix should be in upcoming Panorama version 4.0.6. Note that we do not have an issue with Panorama 4.0.5 commiting to 4.0.x PAN devices. So if all your PA devices are on 4.0.x then you should not have a commit issue with Panorama 4.0.5.


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!