Courseiva
FortiGate lab 6

Troubleshoot a FortiGate with diagnose debug flow

Users have no Internet, names do not resolve and the GUI is unreachable. Trace the packets with diagnose debug flow and the session table, find each fault and fix it.

About 35 minutes 4 devices 3 tasksAdvanced

Scenario

Since a weekend change on HQ-FGT, PC1 cannot ping or browse the Internet, DNS lookups to 8.8.8.8 fail, and the administrators cannot open the FortiGate GUI from the LAN. The change log is lost. The ISP gateway is 203.0.113.1. Users must be able to ping, browse and resolve names, and the GUI must be reachable from the LAN at 10.0.1.1 over HTTPS. Find every fault: the debug flow tells you at which stage each packet dies.

port1Gi0/0port2eth0Gi0/1eth0HQ-FGTHQ-FGT — Firewall (FortiGate-VM64)ISPISP — Router (2911)INETINET — ServerPC1PC1 — PC

Your tasks

  1. PC1 can ping 8.8.8.8.
  2. PC1 can open 8.8.8.8 on TCP 80 and query it on UDP 53.
  3. PC1 can open the FortiGate GUI at 10.0.1.1 over HTTPS.

The lab checks the result, not the exact commands. For example, a ping task passes only when the ping really succeeds through the network you built.

Start the lab