This article provides information regarding an issue where multiple KMD core files are generated by the device after VPN-related configuration changes are made.

After VPN configuration changes, multiples site-to-site VPNs could go down with below log in messages log file.

IKE negotiation failed with error: IKE gateway configuration lookup failed during negotiation. IKE Version: 1, VPN: Not-Available Gateway: Not-Available

Apart from the above, multiple KMD cores as shown below will be generated
> show system core-dumps no-forwarding
-rw-rw---- 1 root wheel   7021236 Dec 19 03:16 /var/tmp/kmd.core-tarball.0.tgz
-rw-rw---- 1 root wheel   6546249 Dec 19 03:16 /var/tmp/kmd.core-tarball.1.tgz
-rw-rw---- 1 root wheel   6558881 Dec 19 03:16 /var/tmp/kmd.core-tarball.2.tgz

While making changes to address the attribute of an existing VPN tunnel, when the peer address is removed or changed after a commit, the device generates multiple kmd cores continuously unless we set the address to the IP address of the peer. This issue has been addressed in the following JunOS versions:
Junos: 20.4R3-S3, 20.4R3-S4, 21.2R3, 21.3R3, 21.4R2, 21.4R3, 22.1R1, 22.1R2, 22.2R1, 22.3R1

Workaround:
Ensure that the required address attribute in the IKE gateway configuration is set for a site-to-site VPN tunnel.  

2024-07-06 : Article Created