12.03.2015 Views

FortiGate Administration Guide - FirewallShop.com

FortiGate Administration Guide - FirewallShop.com

FortiGate Administration Guide - FirewallShop.com

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

High Availability cluster logging<br />

Log&Report<br />

High Availability cluster logging<br />

When configuring logging with a High Availability (HA) cluster, configure the<br />

primary unit to send logs to a FortiAnalyzer unit or a Syslog server. The settings<br />

will apply to the subordinate units. The subordinate units send the log messages<br />

to the primary unit, and the primary unit sends all logs to the FortiAnalyzer unit or<br />

Syslog server.<br />

If you configured a secure connection via an IPSec VPN tunnel between a<br />

FortiAnalyzer unit and a HA cluster, the connection is between the FortiAnalyzer<br />

unit and the HA cluster primary unit.<br />

See the <strong>FortiGate</strong> High Availability User <strong>Guide</strong> for more information.<br />

Storing Logs<br />

The type and frequency of log messages you intend to save dictates the type of<br />

log storage to use. For example, if you want to log traffic and content logs, you<br />

need to configure the <strong>FortiGate</strong> unit to log to a FortiAnalyzer unit or Syslog server.<br />

The <strong>FortiGate</strong> system memory is unable to log traffic and content logs because of<br />

their frequency and large file size.<br />

Storing log messages to one or more locations, such as a FortiAnalyzer unit or<br />

Syslog server, may be a better solution for your logging requirements than the<br />

<strong>FortiGate</strong> system memory. Configuring your <strong>FortiGate</strong> unit to log to a FortiGuard<br />

Analysis server may also be a better log storage solution if you have a<br />

<strong>FortiGate</strong>-100A unit or lower. Logging to a FortiGuard Analysis server will be<br />

available for all <strong>FortiGate</strong> units in future releases. See “Logging to a FortiGuard<br />

Analysis server” on page 479 for more information.<br />

If your <strong>FortiGate</strong> unit has a hard disk, you can also enable logging to the hard disk<br />

from the CLI. See the <strong>FortiGate</strong> CLI Reference for more information before<br />

enabling logging to the hard disk.<br />

If you require logging to multiple FortiAnalyzer units or Syslog servers, see the<br />

<strong>FortiGate</strong> CLI Reference for more information.<br />

Note: Daylight Saving Time (DST) is now extended by four weeks in accordance to the<br />

U.S. Energy Policy Act of 2005 and only affects North America. It is re<strong>com</strong>mended to check<br />

if you location observes this change, since it affects the accuracy and schedule of logs. See<br />

the Fortinet Knowledge Center article, New Daily Saving Time support, for more<br />

information.<br />

Logging to a FortiAnalyzer unit<br />

FortiAnalyzer units are network appliances that provide integrated log collection,<br />

analysis tools and data storage. Detailed log reports provide historical as well as<br />

current analysis of network and email activity to help identify security issues and<br />

reduce network misuse and abuse.<br />

<strong>FortiGate</strong> Version 3.0 MR5 <strong>Administration</strong> <strong>Guide</strong><br />

472 01-30005-0203-20070830

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!