Skip to main content

FortiGate: Upgrading the firmware via CLI

FortiGate: Upgrading the firmware via CLI

To use the following procedure, you must have a TFTP or FTP server that FortiDB can connect to. You must also log in using the “admin” administrator account.
  1. Start the FTP or TFTP server.
  2. Copy the new firmware image file to the FTP or TFTP server.
  3. Log into the CLI.
  4. Verify that FortiDB can connect to the FTP or TFTP server. For example, if the IP address of the TFTP server is 192.168.1.168, enter the CLI command: 
    execute ping 192.168.1.168
  5. Enter the following command to copy the firmware image from the TFTP server to FortiDB: 
    execute restore image ftp  
execute restore image tftp
    Where is the name and location of the firmware image file and or is the IP address of the FTP or TFTP server. For example, if the firmware image file name is image.out and the IP address of the FTP or TFTP server is 192.168.1.168, enter:
    execute restore image tftp image.out 192.168.1.168
    FortiDB responds with the message:
    This operation will replace the current firmware version!
Do you want to continue? (y/n)
  6. Type y. FortiDB downloads the firmware image file, upgrades to the new firmware version, and restarts. This process takes a few minutes.
  7. Reconnect to the CLI.
  8. To confirm the new firmware image is successfully installed, enter: 
    get system status
Labels:

Comments

Post a Comment

Popular posts from this blog

CLI Commands for Troubleshooting FortiGate Firewalls

CLI Commands for Troubleshooting FortiGate Firewalls 2015-12-21 Fortinet , Memorandum , Network Cheat Sheet , CLI , FortiGate , Fortinet , Quick Reference , SCP , Troubleshooting Johannes Weber This blog post is a list of common troubleshooting commands I am using on the FortiGate CLI . It is not complete nor very detailled, but provides the basic commands for troubleshooting network related issues that are not resolvable via the GUI. I am not focused on too many memory, process, kernel, etc. details. These must only be used if there are really specific problems. I am more focused on the general troubleshooting stuff. I am using it personally as a cheat sheet / quick reference and will update it from time to time. Coming from Cisco, everything is “show”. With Fortinet you have the choice confusion between show | get | diagnose | execute . Not that easy to remember. It is “ get router info6 routing-table” to show the routing table but “ diagn...
Post a Comment
Read more

common Switch troubleshooting commands

common Switch troubleshooting commands For CPU related issues: Show process cpu sorted Show process cpu history Show platform port-asic stats drop Show controllers cpu-interface Debug platform cpu-queues Show plat for ip For memory issues Show memory statistics Show process memory sorted Show buffers For link issues Show interface status | inc connected Test cable-diagnostics tdr interface <> Show cable-diagnostic tdr interface <> Show interface <> Show interface <> counters Show interface <> counters errors Show interface counter errors Show controller Ethernet-controller <> Show platform pm if-numbers Show controllers Ethernet-controller port-asic statistics Show platform port-asic stats drop <> Layer 2 forwarding issues Show interface <> status Show spanning-tree interface <> Show interface <> counter Show mac address-table interfa...
Post a Comment
Read more