HKVd0CtoAy6qQy+3u2EVu+xDJRxsVmdimTSsKzULtoHGv8H/AAABDAPDsO3KyJqHĮAEH/RAUnE/MWXFuj/5rD7MsFNfepyQae+YQUCenpQgLWWBvtsWe2K41SSm6k6dM zqkvkDpGdyX/FKwy06MKh5LDhKzxQpy+fyDisl+rp9dfcvsc306S3e0x4LvWUNC OF2sMJ5s4lgRkSqnd0ZD89XnexQ2AAri53O0mZH9n+3eXo9Affzfm4cpOPhWkGx5 Wf8AAAEMAzN4XYDqxwVlAQf9GvzIJ7z94/HPn2CwKE5Vd6ejjOLn3VdsN9nmTBEFġJoG0NfSyesaJKIvcU1yPD6tP0z77Bmywhs2ADVY2L2GM4qcycPvO0hot8DdUyMyĤwsZI+84tsiwk33qkEqNGj/ux08EKhK1TgqkuG3KfOppKU+SUQJ0CvtmPGIFIHyf Remember to enter the correct vdom or global configuration tree before configuring anything: It is always “diagnose sys” but “execute system”. It is “ get router info6 routing-table” to show the routing table but “ diagnose firewall proute6 list” for the PBF rules. With Fortinet you have the choice confusion between show | get | diagnose | execute. I am using it personally as a cheat sheet / quick reference and will update it from time to time.Ĭoming from Cisco, everything is “show”. I am more focused on the general troubleshooting stuff. These must only be used if there are really specific problems.

I am not focused on too many memory, process, kernel, etc. It is not complete nor very detailled, but provides the basic commands for troubleshooting network related issues that are not resolvable via the GUI. This blog post is a list of common troubleshooting commands I am using on the FortiGate CLI.

Troubleshooting dhcp fortigate