Execute the command:
To view the phase2 status for a specific tunnel.
# diagnose vpn tunnel list name <phase2-name>
can also be executed to view the phase2 status of all tunnels.
# diagnose vpn tunnel list
When Phase1 is Down:
When Phase2 is Up:
Step 4: Analyze the IKE phase 1 messages on the responder for a solution. [Phase 1 not up].
Troubleshooting IKE Phase 1 problems is best handled by reviewing VPN status messages on the responder firewall.
The responder is the receiver side of the VPN that is receiving the tunnel setup requests.
The initiator is the side of the VPN that sends the initial tunnel setup requests.
Checklist:
Is there any other device upstream to the firewall?
Is the VPN Gateway configured to use the correct outgoing interface?
Is the remote IP configured correctly?
Run packet capture on the outgoing interface and confirm it is possible to see traffic from the remote peer. If not,
Make sure if IKE traffic on port 500/4500 is allowed in the network device connected upstream
Packet capture can be run from CLI or GUI :
GUI:
CLI:
# diagnose sniffer packet any 'host <remote-peer-ip> and port (500 or 4500)' 6 0 l
, control + c to stop
If is possible to see traffic on port 500/4500 the follow the steps below to troubleshoot this issue:
a) Run below commands(on receiver) to capture the IKE logs and initiate tunnel/traffic from the remote end.
Note: Try to run the packet capture and the logs at the same time.
If VDOMs is enabled, make sure to be in the VDOM context and then execute the above commands.
Step 5: Phase1 has established but Phase2 is down .
Checklist:
Confirm if the Encryption and Hashing algorithms match on both receiver and initiator.
Check if PFS is enabled, if yes, make sure the configuration is matched on both the units.
Make sure, if the quick mode selectors (interesting traffic) is matching on both units.
If Phase-2 is still not up, run the packet capture on port 500/4500 and run the below commands,
# diagnose vpn ike gateway list (or diagnose vpn ike gateway list name <tunnel-name>)# diagnose debug console timestamp enable # diagnose debug application ike -1# diagnose debug enable
Note: If VDOMs is enabled, make sure to be in the VDOM context and then execute the above commands.
Packet capture can be collected as show below:
[image phase 2 Up]{images/kb_19769_9.png}
Step 6: Phase2 is up but traffic is not passing.
Once the tunnel is up, traffic will be encapsulated in ESP (Encapsulating Security Payload) protocol and sent to the remote peer.
Checklist:
Make sure the quick mode selector defined in Phase2 is configured properly to allow the traffic flow, which is having the issue.
For example:
Phase 2 define below allows traffic between – 192.168.1.0/24 and 192.168.2.0/24.
Let assume that the IP address of the PC having issue is 10.10.100.100/24.
If this PC is trying to reach any host in 192.168.2.0/24 network, FortiGate will drop this traffic because the phase2 quick mode selector does not have this source network include in it.
Check the IPv4 policies and confirm:
a) If there is policy defined for this traffic flow.
b) If there are any source and destination addresses defined, make sure it is configured to allow this traffic flow.
If the issue still persists:
a) Enable packet capture for remote peer’s ip address and set protocol to 50(ESP).
b) Open two SSH session and run the below commands:
SSH session 1:
# diagnose debug console timestamp enable # diagnose debug flow filter addr <destination-IP># diagnose debug flow filter proto <1 or 17 or 6> (optional) where 1=ICMP, 6 = TCP, 17 = UDP…# diagnose debug flow show iprope enable# diagnose debug flow trace start 1000
Note other protocol numbers can used as well for example OSPF(89).
SSH Session 2:
# diagnose vpn tunnel list (or # diagnose vpn tunnel list name <phase2_tunnel_name> ).
Note: If VDOMs is enabled, make sure it is not in the VDOM context and then execute the above command.
Make sure to collect packet capture and the logs mentioned above around the same and attach it to the Fortinet case updates.
Along with this information, attach network topology (if any).
With this information, TAC will try to decrypt the ESP traffic in Wireshark.
If the remote peer is FortiGate as well, take packet capture on this unit as well which will make sure that this unit received the encrypted traffic or if it was lost in the middle.
Step 7: Troubleshoot IPsec VPN that is flapping.
Checklist:
Does the issue affect one VPN or all configured VPNs?
a) If all VPN tunnels are affected:
Check Internet connection.
Run the below command to find out errors/logs associated with firewall/interface.
# diagnose debug crashlog read# diagnose sys top 2 50, control + c to stop (run for 5 iterations)# get system performance status# diagnose hardware sysinfo conserve# diagnose hardware deviceinfo nic <interface-name> # execute tac report
Note: If VDOMs is enabled, make sure it is not in the Global context and then execute the above commands.
* b) If a only one tunnel is flapping :
- Collect the ‘VPN Events’ log as show below:
* c) Was the VPN stable for a period of time and now it is going up and down?
Yes - Investigate for network or unit changes or if any new network equipment has been added to the environment. If so, confirm changes/additions are correct.
No, Collect logs and packet capture as mentioned on Step 4
Make sure to collect packet capture and all the logs mentioned above around the same and attach it to the Fortinet case updates.
Along with this information, attach network topology (if any). With this information, TAC will investigate this issue.
Step 8: Logs to be collected and attached to TAC case.
# diagnose debug crashlog read# diagnose sys top 2 50, control + c to stop (run for 5 iterations)# get system performance status# diagnose hardware sysinfo conserve# diagnose hardware deviceinfo nic <interface-name> # diagnose vpn ike gateway list# diagnose vpn tunnel list# execute tac report
First Packet capture - IKE Traffic on ports 500/4500.
