Failed to autogenerate SDWAN configuration: Unable to update tenant ID SDB. Exiting...
6255
Created On 11/11/22 09:05 AM - Last Modified 09/30/24 21:28 PM
Symptom
-
When deploying PANOS SD-WAN via Panorama and SD-WAN plugin, getting commit error during "Push to devices":
Operation Commit All
Status Completed
Result Failed
Details Internal error during commit processing
Warnings Failed to autogenerate SDWAN configuration
- On firewall, configd.log (less mp-log configd.log), the following messages are displayed.
.015 +0100 start pan_cfg_save_commit_candidate
.024 +0100 Error: _pan_schema_verify_node(pan_schema_obj.c:7446): unexpected here. Discarding. , node: dns near line 1184
.036 +0100 Error: pan_cfg_transform_fullpath(pan_cfg_utils.c:6936): error generating transform /opt/pancfg/mgmt/factory/tplrenamemapfrompushreq.xsl
.038 +0100 Error: pan_cfg_tpl_renamemap_from_request(pan_cfg_templates.c:5236): failed to generate tpl rename map from request
File "/opt/pancfg/mgmt/transforms/cluster-gen.py", line 1896, in <module>
if xml_to_file(gen_auto_config(root, tpl_config), xml_outfile, True) < 0:
File "/opt/pancfg/mgmt/transforms/cluster-gen.py", line 1658, in gen_auto_config
cluster_name)
........ (output omitted)....
cluster-gen.py", line 72, in gen_fqdn
tenant_id = retrieve_tenant_id()
File "/opt/pancfg/mgmt/transforms/cluster-gen.py", line 43, in retrieve_tenant_id
raise Exception("Unable to update tenant ID SDB. Exiting...")
.320 +0100 Error: pan_cfg_pushtpl_autogen_config_merge(pan_cfg_templates.c:7106): self.prisma_cluster:False
self.prisma_cluster:False
gen_bgp_ecmp: False
self.prisma_cluster:False
going to generate ipsec for l: ethernet1/1 and p: ethernet1/4
Failed to auto generate SD-wan config:
Unable to update tenant ID SDB. Exiting...
***Traceback***
Environment
- Panorama with SD-WAN plugin
- Supported PAN-OS
- SD-WAN
Cause
- One or more interfaces in HUB template is configured as DHCP/PPPoE client.
- Although DHCP(PPPoE) Client is supported for a hub or branch interface, on a hub interface it is preferable for you to assign a Static address instead of DHCP(PPPoE) Client.
- Using DHCP(PPPoE) on a hub requires the Palo Alto Networks DDNS service.
- Using a Static address at the hub site creates a more stable environment because DDNS is not involved to resolve the DHCP(PPPoE) IP address changes, and because the DDNS service can take a few minutes to register the new IP address when it changes.
Resolution
- Use Static address instead of DHCP/PPPoE client on hub interface, OR
- Configure Palo Alto Networks DDNS service with ZTP Service.
Additional Information
- Reference: https://docs.paloaltonetworks.com/sd-wan/3-0/sd-wan-admin/configure-sd-wan/configure-a-physical-ethernet-interface-for-sd-wan