Fortinet black logo

Administration Guide

Hard reset FortiAnalyzer-BigData

Hard reset FortiAnalyzer-BigData

Caution

Improperly resetting your FortiAnalyzer-BigData may result in losing all data.

When you hard reset your device, the command resets the OS on each host and formats all data drives. All log data and configurations will be lost. FortiAnalyzer-BigData shuts down during the reset process. The entire process takes approximately 45 minutes.

You can add an extra option to the reset command to keep certain configurations constant:

  • all-settings resets all settings.
  • all-except-ip keeps the public IP constant
  • all-except-ssh keeps the ssh public key constant.
  • all-except-ip-ssh keeps the ssh public key and public IP constant.

For more information about extra CLI options, see the reset command in the CLI Reference in the Fortinet Doc Library..

To hard reset your FortiAnalyzer-BigData:
Caution

Before proceeding with the steps below, your version of FortiAnalyzer-BigData bootloader must match your current version of FortiAnalyzer-BigData. Check the version of your bootloader and upgrade it to match your FortiAnalyzer-BigData as needed.

To check the bootloader version, run the following command from the Security Event Manager Controller: fazbdctl show version

To upgrade the bootloader, see Upgrade Bootloader.

  1. Access the Security Event Manager Controller, and run the following command:

    fazbdctl reset cluster [--all-settings|--all-except-ip|--all-except-ssh|--all-except-ip-ssh]

    The Security Event Manager Controller reboots after a few minutes.

  2. After the Security Event Manager Controller reboots, re-connect to it and run the following command to verify that all members are detected and that the version is up-to-date:

    fazbdctl show members

  3. After verifying that all the members have a Joined state and status is not failed, run the following command to initialize the Security Event Manager:

    fazbdctl init cluster

  4. Wait about 45 minutes until the following message is displayed on the terminal:

    [100%] The system has been initialized successfully.

Hard reset FortiAnalyzer-BigData

Caution

Improperly resetting your FortiAnalyzer-BigData may result in losing all data.

When you hard reset your device, the command resets the OS on each host and formats all data drives. All log data and configurations will be lost. FortiAnalyzer-BigData shuts down during the reset process. The entire process takes approximately 45 minutes.

You can add an extra option to the reset command to keep certain configurations constant:

  • all-settings resets all settings.
  • all-except-ip keeps the public IP constant
  • all-except-ssh keeps the ssh public key constant.
  • all-except-ip-ssh keeps the ssh public key and public IP constant.

For more information about extra CLI options, see the reset command in the CLI Reference in the Fortinet Doc Library..

To hard reset your FortiAnalyzer-BigData:
Caution

Before proceeding with the steps below, your version of FortiAnalyzer-BigData bootloader must match your current version of FortiAnalyzer-BigData. Check the version of your bootloader and upgrade it to match your FortiAnalyzer-BigData as needed.

To check the bootloader version, run the following command from the Security Event Manager Controller: fazbdctl show version

To upgrade the bootloader, see Upgrade Bootloader.

  1. Access the Security Event Manager Controller, and run the following command:

    fazbdctl reset cluster [--all-settings|--all-except-ip|--all-except-ssh|--all-except-ip-ssh]

    The Security Event Manager Controller reboots after a few minutes.

  2. After the Security Event Manager Controller reboots, re-connect to it and run the following command to verify that all members are detected and that the version is up-to-date:

    fazbdctl show members

  3. After verifying that all the members have a Joined state and status is not failed, run the following command to initialize the Security Event Manager:

    fazbdctl init cluster

  4. Wait about 45 minutes until the following message is displayed on the terminal:

    [100%] The system has been initialized successfully.