FortiAnalyzer
FortiAnalyzer can receive logs and Windows host events directly from endpoints connected to EMS, and you can use FortiAnalyzer to analyze the logs and run reports.
mpapisetty
Staff
Staff
Article Id 333705
Description

This article describes that FortiAnalyzer comes with physical disk drives that are configured in RAID.

The RAID controller runs a scheduled consistency check on all the RAID arrays to ensure that all data is consistent.

This check generally involved scanning for any block errors, or parity errors, and when such an error is caught, the controller then rewrites this data as per the RAID configuration.  Depending on the available resources and configuration, the consistency check can consume disk resources for a long time.  

Scope FortiAnalyzer.
Solution

To check the current configuration of the RAID Consistency Check, execute the command 'diagnose system raid cc'. Here is a sample output of the 'diagnose system raid cc' command: 

 

FAZ-1$ diagnose system raid cc
Adapter 0
Operation Mode: Concurrent
Execution Delay: 2184
Next start time: 07/06/2024, 03:00:00
Current State: Active
Number of iterations: 24
Number of VD completed: 0
Excluded VDs : None
Adapter 0: Check Consistency Rate = 10%
Check Consistency on VD 0 (target id 0) Completed 12% in 359 Minutes.
FAZ-1$

 

Below is what each of the fields in the output means:

  • Execution Delay: This is the delay between the previous consistency check completion and the next iteration of the check in hours. 2184 in the above output translates to 91 days. 
  • Next start time: This is the schedule for when the next check will start. The timestamp will get updated once the current iteration of the consistency check is complete based on the configured execution delay. 
  • Current State: 'Active' signifies that there is a consistency check actively running on the FortiAnalyzer. 
  • Number of iterations: This is the number of times a consistency check has been run on this FortiAnalyzer. 
  • Check Consistency Rate: The configuration resource allocation threshold for the check. In this case, the consistency check can consume up to 10% of the disk resources. 

 

The last line in the output shows the current progress of the operation. In this case, 12% is complete in 359 minutes. 

 

Depending on how busy the FortiAnalyzer is, the execution delay and rate can be configured to optimize resource utilization.

Below is the command reference for this configuration :

 

diagnose system raid cc <rate> <delay>

 

where the rate is the percentage between 1-100 and delay is the hours ranging from 1-8760 hours. 

Contributors