Fortinet white logo
Fortinet white logo

Firmware upgrade and downgrade

Firmware upgrade and downgrade

Before you upgrade or downgrade, back up your configuration and any other stored data. For details, see the FortiMail Administration Guide.

After any firmware upgrade or downgrade, if you are using the web UI, clear the browser cache prior to login on the FortiMail unit to ensure proper display of the web UI screens. Also verify that the build number and version number match the image loaded, which indicates that the upgrade was successful.

The FortiGuard Antivirus signatures included with an image upgrade may be older than those currently available from the Fortinet FortiGuard Distribution Network (FDN). Fortinet recommends performing an immediate antivirus signature update as soon as possible.

Caution

Firmware downgrading is not recommended and not supported in general. Before downgrading, consult Fortinet Technical Support first.

Upgrade path

6.0.5 (build 148) > 6.2.4 (build 272) > 6.4.5 (build 453) > 7.0.6 (build 216) > 7.2.2 (build 380) > 7.4.3 (build 600) > 7.6.4 (build 818)

Firmware downgrade

Downgrading to previous firmware versions results in configuration loss on all models. Only the following settings are retained:

  • operation mode
  • interface IP/management IP
  • static route table
  • DNS settings
  • admin user accounts
  • admin access profiles

Firmware image checksums

When you download software, use checksums to verify that the file has not been modified or corrupted.

  1. On the Fortinet Support site, go to Downloads > Firmware Images.

  2. Select FortiMail

  3. Click the Download tab and then click to go into the version folder.

  4. Next to the file, click HTTPS to download the file. Then click Checksum to show the file's checksum.

    To verify the file's integrity, the checksum shown by the website should match the checksum of the file on your computer.

  5. Use a checksum tool and compute the firmware file's checksum. For example, you could use certutil on the Windows command line:

    certutil -hashfile firmware.out SHA512

    If the file's checksum shown on the Fortinet Support website matches the file's checksum on your computer, then the file is intact.

Firmware upgrade and downgrade

Firmware upgrade and downgrade

Before you upgrade or downgrade, back up your configuration and any other stored data. For details, see the FortiMail Administration Guide.

After any firmware upgrade or downgrade, if you are using the web UI, clear the browser cache prior to login on the FortiMail unit to ensure proper display of the web UI screens. Also verify that the build number and version number match the image loaded, which indicates that the upgrade was successful.

The FortiGuard Antivirus signatures included with an image upgrade may be older than those currently available from the Fortinet FortiGuard Distribution Network (FDN). Fortinet recommends performing an immediate antivirus signature update as soon as possible.

Caution

Firmware downgrading is not recommended and not supported in general. Before downgrading, consult Fortinet Technical Support first.

Upgrade path

6.0.5 (build 148) > 6.2.4 (build 272) > 6.4.5 (build 453) > 7.0.6 (build 216) > 7.2.2 (build 380) > 7.4.3 (build 600) > 7.6.4 (build 818)

Firmware downgrade

Downgrading to previous firmware versions results in configuration loss on all models. Only the following settings are retained:

  • operation mode
  • interface IP/management IP
  • static route table
  • DNS settings
  • admin user accounts
  • admin access profiles

Firmware image checksums

When you download software, use checksums to verify that the file has not been modified or corrupted.

  1. On the Fortinet Support site, go to Downloads > Firmware Images.

  2. Select FortiMail

  3. Click the Download tab and then click to go into the version folder.

  4. Next to the file, click HTTPS to download the file. Then click Checksum to show the file's checksum.

    To verify the file's integrity, the checksum shown by the website should match the checksum of the file on your computer.

  5. Use a checksum tool and compute the firmware file's checksum. For example, you could use certutil on the Windows command line:

    certutil -hashfile firmware.out SHA512

    If the file's checksum shown on the Fortinet Support website matches the file's checksum on your computer, then the file is intact.