Fortinet black logo

Administration Guide

How to replace a blade

How to replace a blade

This section contains instructions on how to gracefully remove and replace a malfunctioning hardware blade running one of the Security Event Manager 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 is follows a naming convention: blade-10-0-{chass ID}-{blade ID}.

A blade named "blade-10-0-1-3" means that "1" represents the chassis ID and the "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 10.0.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 from Security Event Manager Controller: 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 on page 20). 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. From the Hosts page, click Assign Role to recover the role on the host. The new host will have a pending label. When the Assign Role job completes, the blade replacement is done.
  8. (Recommended) After the Assign Role job is complete, rebalance the data across the cluster. SeeHow to rebalance the data.

How to replace a blade

This section contains instructions on how to gracefully remove and replace a malfunctioning hardware blade running one of the Security Event Manager 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 is follows a naming convention: blade-10-0-{chass ID}-{blade ID}.

A blade named "blade-10-0-1-3" means that "1" represents the chassis ID and the "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 10.0.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 from Security Event Manager Controller: 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 on page 20). 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. From the Hosts page, click Assign Role to recover the role on the host. The new host will have a pending label. When the Assign Role job completes, the blade replacement is done.
  8. (Recommended) After the Assign Role job is complete, rebalance the data across the cluster. SeeHow to rebalance the data.