Due to an IKED coredump, the internal IPsec tunnel for MNHA did not come up with the “reason that Control-Plane is down”. We were not able to recover this until we performed a node reboot (backup).

In cases where iked is restarting multiple times and not coming up 5 times in a row, SRG1 enters Ineligible state due to "Control plane down":

Nov 28 11:16:15.317 2023 backup_node kernel: %KERN-6: pid 13874 (iked), jid 0, uid 0: exited on signal 6 (core dumped)
Nov 28 11:16:20.493 2023 backup_node kernel: %KERN-6: pid 3305 (iked), jid 0, uid 0: exited on signal 6 (core dumped)
Nov 28 11:16:30.674 2023 backup_node kernel: %KERN-6: pid 3690 (iked), jid 0, uid 0: exited on signal 6 (core dumped)
Nov 28 11:16:40.923 2023 backup_node kernel: %KERN-6: pid 4106 (iked), jid 0, uid 0: exited on signal 6 (core dumped)
Nov 28 11:16:51.137 2023 backup_node kernel: %KERN-6: pid 4586 (iked), jid 0, uid 0: exited on signal 6 (core dumped)
Nov 28 11:16:51.163 : SRG[1] state BACKUP -> INELIGIBLE, Reason: Control plane down

Starting from Junos release 22.4R1 it is not necessary to do a node reboot to recover from the Control plane down situation. Once iked is running, node will recover itself.