18.11.2014 Views

Clavister cOS Core Administration Guide

Clavister cOS Core Administration Guide

Clavister cOS Core Administration Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 2: Management and Maintenance<br />

• Emergency<br />

• Alert<br />

• Critical<br />

• Error<br />

• Warning<br />

• Notice<br />

• Info<br />

• Debug<br />

By default, <strong>cOS</strong> <strong>Core</strong> sends all messages of level Info and above to any configured log servers but<br />

the level for sending can be changed by the administrator. The Debug severity is intended for<br />

system troubleshooting only and should only be used if required. All log event messages of all<br />

severity levels are listed in the separate <strong>cOS</strong> <strong>Core</strong> Log Reference <strong>Guide</strong>.<br />

Event Message Timestamping<br />

When a log messages are sent by <strong>cOS</strong> <strong>Core</strong> to external log receivers, they are always<br />

timestamped with time expressed as UTC/GMT (Greenwich Mean Time). This means that it is easy<br />

to compare events from a network consisting of many security gateways spread over different<br />

time zones.<br />

The exception to this is log messages displayed through Memlog which are always stamped with<br />

the current system time.<br />

2.2.3. Creating Log Receivers<br />

To distribute and log the event messages generated by <strong>cOS</strong> <strong>Core</strong>, it is necessary to define one or<br />

more event receivers that specify what events to capture, and where to send them.<br />

<strong>cOS</strong> <strong>Core</strong> can distribute event messages to different types of receivers and these are enabled by<br />

creating any of the following Log Receiver objects.<br />

• MemoryLogReceiver<br />

<strong>cOS</strong> <strong>Core</strong> has its own logging mechanism also known as the MemLog. This retains all event<br />

log messages in memory and allows direct viewing of recent log messages through the Web<br />

Interface.<br />

This is enabled by default but can be disabled.<br />

This receiver type is discussed further below in Section 2.2.4, “Logging to MemoryLogReceiver”.<br />

• Syslog Receiver<br />

Syslog is the de-facto standard for logging events from network devices. If other network<br />

devices are already logging to Syslog servers, using syslog with <strong>cOS</strong> <strong>Core</strong> messages can<br />

simplify overall administration.<br />

This receiver type is discussed further below in Section 2.2.5, “Logging to Syslog Hosts”.<br />

• FWLog<br />

The <strong>Clavister</strong> proprietary format for logging event messages, the FWLog format has a high<br />

level of detail and is suitable for analyzing large amounts of log data.<br />

This receiver type is discussed further below in Section 2.2.6, “Logging to the <strong>Clavister</strong> Logger”.<br />

• SNMP Traps<br />

68

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

Saved successfully!

Ooh no, something went wrong!