Phase 2 commit: Warning: DP pods not connected

i.haciyev07 — Tue, 24 Dec 2024 05:40:10 GMT

Hello. In Managed Device<Summary, Phase 2 commit shows: Warning: DP pods not connected. Could someone please help?

Re: Phase 2 commit: Warning: DP pods not connected

Luongchacha1 — Wed, 16 Jul 2025 03:47:56 GMT

Im not sure but the reason may be IPSEC Tunnel between MP and DP Pod not established because of authentication failed.

Try to " kubectl exec -it -n kube-system <pan ngfw dep pod name> -- bash "

then " cd /var/log/pan/ "

then you should read the file named "cat charon.log"

If you saw a line such as "Authentication Failed" that mean you got same issues as my case.

Try to reach Support Case. TAC Engineer have gave me a workaround that we should bypass cert authentication for the VPN tunnel.

For workground, you can bypass certicate authentication for VPN tunnel:

"Engineering suggests to disable cert authentication and enable PSK authentication:
1. In pan-cn-mgmt-configmap.yaml, uncomment line 31 (remove the # in front of "IPSEC_CERT_BYPASS):
=====
{{- else }}
IPSEC_CERT_BYPASS: "" # No values needed
{{- end }}
=====

2. In pan-cn-ngfw-configmap.yaml, uncomment line 17 (remove the # in front of "IPSEC_CERT_BYPASS):
=====
{{- else }}
IPSEC_CERT_BYPASS: "" # No values needed
{{- end }}
=====

Then run helm install again after modifying those 2 files, and observe if the IPSec tunnel can come up."

topic Re: Phase 2 commit: Warning: DP pods not connected in CN-Series Discussions

Phase 2 commit: Warning: DP pods not connected

Re: Phase 2 commit: Warning: DP pods not connected