Troubleshooting Tip: A peer ID with four random characters displays in IPSec in both the GUI and CLI

[vifi]

Description	This article describes how to work around an issue where a random 4 character string appears as the peer ID in IPSec. When this occurs, phhase1 is up, but phase2 stays down.
Scope	IPSec site-to-site in FortiGate. Known to occur in FortiOS 7.2.4.
Solution	This issue occurs when the peer-type configured is 'any', but FortiGate acknowledges 4 random characters as the peer-id. In the GUI Dashboard -> Network -> IPsec: In the CLI: diag vpn ike gateway list vd:root/0 name: To_Remote version:1 interface: wan 8 addr:192.168.1.1:4500 -> x.x.x.x:4500 tun_id:x.x.x.x/::x.x.x.x remote_location:0.0.0.0 network-id:0 created: 767s ago peer-id: *=;Z <-------- peer-id-auth: no nat: me IKE SA:created 2/2 established 2/2 time 10/15/20 ms IPSec SA:created 0/494 established 0/494 time 0/10/60 ms Workaround: 1) Consult an ASCII table to discern whether the random characters match the remote end IP. For example: http://www.unit-conversion.info/texttools/ascii/. If they do: 2) Change IKEv1 to IKEv2 to restore the phase2. This behavior affects IKEv1 traffic, but not IKEv2.