TopicFortiGate →
⌚ About 2 min read
Quickly check the state of the IPsec tunnels since the FortiGate LTC.
Avant de commencer : adaptez toujours les commandes et manipulations à votre environnement. Sur un système de production, prévoyez une backup ou un retour arrière lorsque l’action peut modifier la configuration.
Étapes à suivre
-
1
Connect to the CLI.
Use secure of administration access.
-
2
Show VPN Summary.
Use the ipsec tunnel summary.
-
3
Control a specific tunnel.
Use the name of the tunnel.
-
4
Check roads and policies.
A mounted tunnel does not guarantee that traffic is permitted.
-
5
Watch the logs if necessary
Analyze VPN andGamber events before you activate a deep debug.
Commands utiles
ip sec tunnel
The name of the tunnel list name
À retenir
- The exact commands can vary according to the FortiOS version.
- Disable debug after use to avoid unnecessary load and volume of logs.
FortiGate IPsec: Phase 1, Phase 2 and traffic are three separate validations
Technical checkpoints
Targeted CLI
Read gateways/SAs then filter debug on the peer instead of enabling unbounded global IKE debug.
get vpn ipsec tunnel summary
diagnose vpn ike gateway list
diagnose vpn tunnel listTopic-specific pitfalls
- A FortiGate ping without a source can use a different interface than user traffic.
- Phase 2 can be down because of selectors/proposals while Phase 1 is completely healthy.
How to validate
- Expected SAs are up and RX/TX counters increase during the real traffic test.
- Policy, route and session show the expected path without unintended NAT.