Description
This article describes how to power cycle or reboot the physical blade in FortiAnalyzer BigData hardware e.g. 4500F/4500G when the individual blade is not responding or in the hang state with a red in health status in the Cluster Manager GUI but the Chassis Management Module (CMM) GUI still showing power status: On and Status: Normal.
Scope
FortiAnalyzer BigData 4500F/4500G.
Solution
In general, it is possible to take an action to reboot the physical blade when the following troubleshooting action to reboot is not available, the general methods can be taken in sequence to troubleshoot for the reboot as follows.
- Reboot the blade via the Cluster Manager GUI, navigate to Cluster Manager -> Hosts, and select -> Restart.
- Reboot the blade via the Cluster Manager GUI, and navigate to Cluster Manager -> Hosts, and select
-> CLI Console.
After the CLI Console is launched, run the CLI command: fazbdctl execute shell to access with a root user to run the CLI command: reboot in order to reboot, it is run under blade 14 for this example as follows:
- Alternatively, SSH from the controller to the blade that having the issue and run a CLI command: reboot to reboot that blade.
See KB article on how to access each blade via SSH: Technical Tip: How to SSH from the controller to the other Hosts and FortiAnalyzer blade in FortiAna...
It is run under blade 14 for this example as follows:
[root@blade-10-0-1-2 ~]$ fazbdctl show members
Management IP/Mask is 172.16.100.99/24
Chassis Blade Role Address Ext Address Host Name State Status
1 2 controller 10.0.1.2 blade-10-0-1-2 joined alive
1 3 member 10.0.1.3 blade-10-0-1-3 joined alive
1 4 member 10.0.1.4 blade-10-0-1-4 joined alive
1 5 member 10.0.1.5 blade-10-0-1-5 joined alive
1 6 member 10.0.1.6 blade-10-0-1-6 joined alive
1 7 member 10.0.1.7 blade-10-0-1-7 joined alive
1 8 member 10.0.1.8 blade-10-0-1-8 joined alive
1 9 member 10.0.1.9 blade-10-0-1-9 joined alive
1 10 member 10.0.1.10 blade-10-0-1-10 joined alive
1 11 member 10.0.1.11 blade-10-0-1-11 joined alive
1 12 member 10.0.1.12 blade-10-0-1-12 joined alive
1 13 member 10.0.1.13 blade-10-0-1-13 joined alive
1 14 member 10.0.1.14 blade-10-0-1-14 joined unknown
[root@blade-10-0-1-2 ~]$ ssh 10.0.1.14
Last login: Tue Sep 12 17:08:53 2023
[root@blade-10-0-1-14 ~]$ reboot
- Login into the Chassis Management Module (CMM) GUI, navigate to Blade Status, Select the corresponding blade, and select the Power Cycle on the top menu bar to reboot the blade. It is run under blade 14 for this example as follows:
- Login into Chassis Management Module (CMM) GUI, and navigate to Blade Status, On the BMC IPV4 column, select the BMC IPV4 link that corresponds to the blade to access the BMC remote console, then the GUI login will be prompted for a login and the default login credentials username/password are on the Fortinet Product Credentials card -> Remote Control, select Console Redirection or iKVM/HTML5, login into the host or blade with default username/password: root/fortinet@123 if it has not been changed, log in with the correct credential.
A sample of the Fortinet Product Credentials card looks like this below, It comes together with the hardware package:
- If all of the above methods is not feasible, the last resort is to power cycle the blade physically on-site. There is a power button action for each blade and the action possible to take is to press and hold to turn Off and then press to turn On. See also FortiAnalzyer BigData hardware guide.
