How to remove a chassis from a stacked setup

If you have an established multi-chassis FortiAnalyzer-BigData Security Event Manager and need to scale down, you can remove any extender chassis you have added to the main chassis.

Removing an extender chassis will hard reset BOTH the extender and the main chassis. All user data and configurations will be lost. The entire process takes approximately an hour.

Remove an extender chassis

Perform this process in a location where you can immediately disconnect the Internal Switch Modules at step 3. This step must be done in a timely manner.

To remove an extender chassis:

1. Stop the DHCP service. To do this, access the Security Event Manager Controller of the main chassis and run the following command:

   systemctl stop dhcpd

   For information about accessing the Security Event Manager Controller, see To connect to the Security Event Manager Controller:.

2. Reset all hosts connected to the current controller by running the following command:

   fazbdctl unstack-chassis

   Wait for the message “[Info] factory reset members done, and [info] factory reset the controller" in the command output before proceeding to the next step without any delay.

3. Disconnect the connection between the Internal Switch Modules (Switch Module #1) between the main and extender chassis.
4. On the main chassis, access the Security Event Manager Controller.
   1. Access the Bootloader of the Blade A2. See Bootloader.
   2. From Bootloader, select option 7,  Reset OS and Clear User Data, to hard reset the host.
   3. Wait until the Bootloader finishes rebooting and log back into the controller.
   4. Initialize the cluster using the following command: 

      fazbdctl init cluster

5. On the extender chassis, access Blade A2.
   1.  Access the Bootloader of the Blade A2. See Bootloader.
   2.   From Bootloader, select option 3, Set Role, input choice: Controller, to set the role to Controller.
   3. From Bootloader, select option 7, Reset OS and Clear User Data, to hard reset the host.
   4. Wait until the Bootloader finishes rebooting and log back into the controller.
   5. Initialize the cluster by running the following command: 

      fazbdctl init cluster