Panorama - SDWAN Autogenerated Config Nightmare

[dpayne]

I have spent the better part of two days deploying what should be a simple, standard SDWAN solution following the provided documentation. No matter how many times I try, every time I get to the point where I create the VPN Cluster, I get commit failures on the firewalls indicating that the tunnel.90x interfaces have no virtual router configured or zone configuration.

I have done this, with similar consternation, on another set of firewall running 10.0.2, and they are least pushing the autogenerated config correctly (although I am rather frightened to touch anything there). This is version 10.0.5. I have wiped all configs, pushed out from Panorama, following the docs. It all commits until this last step, and then I get what is below. I am now going to attempt to create this all manually, since I think it will be faster than this. Curious if anyone else has had similar experience.

[bschaper]

Sorry to hear you are having such problems. We deployed about a year ago and I do recall some similar problems, the dependence on panorama connectivity and kind of chicken and the egg problem seems to break the script. 

I will be curious if you get this to work. We run 10.0.3, but I can’t get a higher version of Panos to work. The sdwan interface stays down/init. 

[dpayne]

Thanks for the response. I am deploying the firewalls today manually. Once they are up and functional, I will get support to work with me on the errors and see where that leads. Will update then.

[Igor_Serov]

Hello! Have th same problem: Panorama 10.1.0, Plugin SD WAN plugin sd_wan-2.1.0,  NGFW  10.1.0

can anybody help with solving this problem?

[Jason_Miller1]

Please post Panorama SD-WAN device config and vpn cluster config.  I am using SD-WAN 2.1 on 10.0.5 and everything is working for me.

Thanks

[smehla]

I was stuck with the same problem for the past two days. Later realised that the virtual router config was being overridden locally on the firewall. This can be identified by the red gear icon appearing in front of the virtual router name on the Firewall GUI. When this is the case, config changes pushed from the Panorama don't get applied on the firewall.
Resolution - 
Please refer to https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u0000008UgM 

I hope this is helpful.

[delliott_6784]

I have had similar or same issues with my deployments.  The under the hood sdwan plugin script running is interrupted by any connectivity (channel) , network overrides, standard IPSec tunnel terminations, and sometimes can overwhelm itself.  I recently got a short vague error msg trying to push to a firewall.  TAC was zero help.  I successfully deployed by slowly backing out the sdwan cfg in panorama until I got a successful commit then slowly re-added back into pano with partial sdwan cfg and pushed to the firewall with several build back cfg commits until full. 

The pano connection is mandatory.  Connecting via the internet using a service route sourcing from the external Internet interface to a NAT that points to pano maintains a connection through the commit and push process.