Fortinet Document Library

Version:

Version:

Version:

Version:


Table of Contents

FortiGate-7000 Handbook

Download PDF
Copy Link

Replacing a failed FPM or FIM

This section describes how to remove a failed FPM or FIM and replace it with a new one. The procedure is slightly different depending on if you are operating in HA mode with two FortiGate-7000s or just operating a standalone FortiGate-7000.

Replacing a failed module in a standalone FortiGate-7000

  1. Power down the failed module by pressing the front panel power button.
  2. Remove the module from the chassis.
  3. Insert the replacement module. It should power up when inserted into the chassis if the chassis has power.
  4. The module's configuration is synchronized and its firmware is upgraded to match the firmware version on the primary FIM. The new module reboots.
  5. Confirm that the new module is running the correct firmware version either from the GUI or by using the get system status command.

    Manually update the module to the correct version if required. You can do this by logging into the module and performing a firmware upgrade. See Firmware upgrades.

  6. Use the diagnose sys confsync status | grep in_sy command to confirm that the configuration has been synchronized. The field in_sync=1 indicates that the configurations of the modules are synchronized.

    If in_sync is not equal to 1, or if a module is missing in the command output you can try restarting the modules in the chassis by entering execute reboot from any module CLI. If this does not solve the problem, contact Fortinet Support.

Replacing a failed module in a FortiGate-7000 chassis in an HA cluster

  1. Power down the failed module by pressing the front panel power button.
  2. Remove the module from the chassis.
  3. Insert the replacement module. It should power up when inserted into the chassis if the chassis has power.
  4. The module's configuration is synchronized and its firmware is upgraded to match the configuration and firmware version on the primary module. The new module reboots.
  5. Confirm that the module is running the correct firmware version.
    Manually update the module to the correct version if required. You can do this by logging into the module and performing a firmware upgrade.
  6. Configure the new module for HA operation. For example:

    config system ha

    set mode a-p

    set chassis-id 1

    set hbdev m1 m2

    set hbdev-vlan-id 999

    set hbdev-second-vlan-id 990

    end

  7. Optionally configure the hostname:

    config system global

    set hostname <name>

    end

    The HA configuration and the hostname must be set manually because HA settings and the hostname is not synchronized.

  8. Use the diagnose sys confsync status | grep in_sy command to confirm that the configuration has been synchronized. The field in_sync=1 indicates that the configurations of the modules are synchronized.

    If in_sync is not equal to 1, or if a module is missing in the command output you can try restarting the modules in the chassis by entering execute reboot from any module CLI. If this does not solve the problem, contact Fortinet support at https://support.fortinet.com.

Replacing a failed FPM or FIM

This section describes how to remove a failed FPM or FIM and replace it with a new one. The procedure is slightly different depending on if you are operating in HA mode with two FortiGate-7000s or just operating a standalone FortiGate-7000.

Replacing a failed module in a standalone FortiGate-7000

  1. Power down the failed module by pressing the front panel power button.
  2. Remove the module from the chassis.
  3. Insert the replacement module. It should power up when inserted into the chassis if the chassis has power.
  4. The module's configuration is synchronized and its firmware is upgraded to match the firmware version on the primary FIM. The new module reboots.
  5. Confirm that the new module is running the correct firmware version either from the GUI or by using the get system status command.

    Manually update the module to the correct version if required. You can do this by logging into the module and performing a firmware upgrade. See Firmware upgrades.

  6. Use the diagnose sys confsync status | grep in_sy command to confirm that the configuration has been synchronized. The field in_sync=1 indicates that the configurations of the modules are synchronized.

    If in_sync is not equal to 1, or if a module is missing in the command output you can try restarting the modules in the chassis by entering execute reboot from any module CLI. If this does not solve the problem, contact Fortinet Support.

Replacing a failed module in a FortiGate-7000 chassis in an HA cluster

  1. Power down the failed module by pressing the front panel power button.
  2. Remove the module from the chassis.
  3. Insert the replacement module. It should power up when inserted into the chassis if the chassis has power.
  4. The module's configuration is synchronized and its firmware is upgraded to match the configuration and firmware version on the primary module. The new module reboots.
  5. Confirm that the module is running the correct firmware version.
    Manually update the module to the correct version if required. You can do this by logging into the module and performing a firmware upgrade.
  6. Configure the new module for HA operation. For example:

    config system ha

    set mode a-p

    set chassis-id 1

    set hbdev m1 m2

    set hbdev-vlan-id 999

    set hbdev-second-vlan-id 990

    end

  7. Optionally configure the hostname:

    config system global

    set hostname <name>

    end

    The HA configuration and the hostname must be set manually because HA settings and the hostname is not synchronized.

  8. Use the diagnose sys confsync status | grep in_sy command to confirm that the configuration has been synchronized. The field in_sync=1 indicates that the configurations of the modules are synchronized.

    If in_sync is not equal to 1, or if a module is missing in the command output you can try restarting the modules in the chassis by entering execute reboot from any module CLI. If this does not solve the problem, contact Fortinet support at https://support.fortinet.com.