Fortinet 542 FortiWeb 5.0 Patch 6 Administration Guide
Currently, only RAID level 1 is supported, and cannot be changed. On FortiWeb 3000C/4000C
and 3000D/4000D, the RAID array has a hardware controller. On FortiWeb 1000D, the array has
a software controller. RAID level 1 is also known as “mirroring,” and writes all data twice — each
drive is an exact copy of the other. This does not increase disk write speed via striping, nor
detection and correction of errors via parity. However, it does improve availability by reducing
the overall hardware failure rate of the RAID: the chance that both disks together will fail is much
lower than the chance of failure of a single disk.
To access this part of the web UI, your administrator's account access profile must have Read
and Write permission to items in the System Configuration category. For details, see
“Permissions” on page 47.
Logging
To diagnose problems or track actions that the FortiWeb appliance performs as it receives and
processes traffic, configure the FortiWeb appliance to record log messages.
Log messages can record attack, system, and/or traffic events. They are also the source of
information for alert email and many types of reports.
When you configure protection profiles, many components include an Action option that
determines the response to a detected violation. Actions combine with severity levels and
trigger policies to determine whether and where a log message, message on the Attack Log
Console widget, SNMP trap, and/or alert email will be generated.
Figure 61:Dialog showing actions, severity level, and triggers that affect logging
Before logging will occur, however, you must first enable and configure it.
Rebuilding RAID after a disk failure will result in some loss of data in packet payloads retained
with corresponding logs.