Fortinet black logo

Administration Guide

Home FortiAnalyzer BigData 7.0.6 Administration Guide
7.0.6
7.4.0
7.2.7
7.2.6
7.2.5
7.2.4
7.2.3
7.2.2
7.2.1
7.2.0
7.0.6
7.0.5
7.0.4
7.0.3
7.0.1
6.4.6
6.4.5
6.2.5
6.2.1

How to replace a blade on a FortiAnalyzer-BigData appliance

How to replace a blade on a FortiAnalyzer-BigData appliance

This section contains instructions on how to gracefully remove and replace a malfunctioning hardware blade running one of the hosts in an active system. In order to allow the high availability mechanism to take effect, only one blade can be decommissioned at a time.

Note

Finding a blade's location

A blade’s host name uses the following naming convention:

blade-198-18-{chassis ID}-{blade ID}

For example, in a blade named blade-198-18-1-3, the number 1 represents the chassis ID and 3 represents the blade ID. Therefore, the blade is the third blade to the left on the first chassis. The internal IP of the blade is 198.18.1.3.
To replace a blade:
Caution

Before proceeding with the steps below, your version of FortiAnalyzer-BigData bootloader must match your current version of FortiAnalyzer-BigData. If you do not know the version of your bootloader, it is recommended that you upgrade the bootloader before proceeding.

To upgrade the bootloader, see Upgrade Bootloader.
  1. Power off the malfunctioned blade, and then remove the blade from the chassis.
  2. From Security Event Manager Controller run the following command to enable installation of system software on the new blade: fazbdctl enable pxe
  3. Insert the replacement blade, and power it on.
  4. From the bootloader (see Bootloader), set the chassis ID and the blade ID of the replacement blade to match the one from Cluster Manager > Hosts.
  5. Monitor the status of the blade from CMM (see "Remotely control blades via CMM" in Connect to the Chassis Management Module). Wait until the host OS completes booting. This may take 5-10 minutes.
  6. After the host boots up and joins the cluster, it will appear in Cluster Manager > Hosts web GUI.
  7. Go to Cluster Manager > Hosts and click Assign Role to recover the host. The new host will have a pending status.
  8. Wait for the Assign job to complete for all services to become healthy.
  9. Follow the Found New recommended configurations notification in the Cluster Manager > Hosts view (if it appears) to apply the optimized configuration for the newly added hosts.
  10. (Recommended) After the Assign Role job is complete, rebalance the data across the cluster. See How to rebalance the data.
Previous
Next

How to replace a blade on a FortiAnalyzer-BigData appliance

This section contains instructions on how to gracefully remove and replace a malfunctioning hardware blade running one of the hosts in an active system. In order to allow the high availability mechanism to take effect, only one blade can be decommissioned at a time.

Note

Finding a blade's location

A blade’s host name uses the following naming convention:

blade-198-18-{chassis ID}-{blade ID}

For example, in a blade named blade-198-18-1-3, the number 1 represents the chassis ID and 3 represents the blade ID. Therefore, the blade is the third blade to the left on the first chassis. The internal IP of the blade is 198.18.1.3.
To replace a blade:
Caution

Before proceeding with the steps below, your version of FortiAnalyzer-BigData bootloader must match your current version of FortiAnalyzer-BigData. If you do not know the version of your bootloader, it is recommended that you upgrade the bootloader before proceeding.

To upgrade the bootloader, see Upgrade Bootloader.
  1. Power off the malfunctioned blade, and then remove the blade from the chassis.
  2. From Security Event Manager Controller run the following command to enable installation of system software on the new blade: fazbdctl enable pxe
  3. Insert the replacement blade, and power it on.
  4. From the bootloader (see Bootloader), set the chassis ID and the blade ID of the replacement blade to match the one from Cluster Manager > Hosts.
  5. Monitor the status of the blade from CMM (see "Remotely control blades via CMM" in Connect to the Chassis Management Module). Wait until the host OS completes booting. This may take 5-10 minutes.
  6. After the host boots up and joins the cluster, it will appear in Cluster Manager > Hosts web GUI.
  7. Go to Cluster Manager > Hosts and click Assign Role to recover the host. The new host will have a pending status.
  8. Wait for the Assign job to complete for all services to become healthy.
  9. Follow the Found New recommended configurations notification in the Cluster Manager > Hosts view (if it appears) to apply the optimized configuration for the newly added hosts.
  10. (Recommended) After the Assign Role job is complete, rebalance the data across the cluster. See How to rebalance the data.
Previous
Next