Thank you for the video. I wish you would have covered dealing with duplicate address/service objects between Panorama and the firewall. That is where the whole process starts to get very interesting!
is there a way to compare Firewall's local configuration and configuration present on Panorama? I just want to confirm that Panorama has all the configuration that is present on the firewall locally.
Feature Request: If you have ever configured a PAN from CLI, you quickly learn that there is a proper sequence. Objects and services need to be present before policies are added. Unfortunately, Panorama gives users the ability with Device group trees and Templates to create things out of sequence. This usually shows up during an RMA, when you replace an existing PAN with a new, blank firewall. And 10 commits later it is finally back to normal. I wilsh Panorama did a better job of dependency checking when I have a tree structure.
At 4:48 where you mention the Shared Policy being in-sync, it is actually out of sync for the firewall you just exported to (the 5260).
Can we have a video for adding devices in HA into panorama and using variables for HA.
Thank you for the video. I wish you would have covered dealing with duplicate address/service objects between Panorama and the firewall. That is where the whole process starts to get very interesting!
Short, to the point, but great video!
Thanks, found this very helpful
Glad it helped
is there a way to compare Firewall's local configuration and configuration present on Panorama? I just want to confirm that Panorama has all the configuration that is present on the firewall locally.
Not bad , wish u showed the the initial part in detail, pano part configuration
Would be incredibly handy to have an HA import video
Hi Randy! We appreciate the feedback and will share this with our team. Thank you!
Wrong!! At 4.45/6.26 you are talking about PA-VM but not about PA-5260 & before this video ends you should had shown “ in sync “ status shows green.
Feature Request: If you have ever configured a PAN from CLI, you quickly learn that there is a proper sequence. Objects and services need to be present before policies are added. Unfortunately, Panorama gives users the ability with Device group trees and Templates to create things out of sequence. This usually shows up during an RMA, when you replace an existing PAN with a new, blank firewall. And 10 commits later it is finally back to normal. I wilsh Panorama did a better job of dependency checking when I have a tree structure.