Introduction; 1.1. Log Message Structure - D-Link NetDefend DFL-210 Log Reference Manual

Chapter 1. Introduction
• Log Message Structure, page 29
• Context Parameters, page 31
• Severity levels, page 35
This guide is a reference for all log messages generated by NetDefendOS. It is designed to be a
valuable information source for both management and troubleshooting.

1.1. Log Message Structure

All log messages have a common design with attributes that include category, severity and
recommended actions. These attributes enable the easy filtering of log messages, either within
NetDefendOS prior to sending them to a log receiver, or as part of analysis that takes place after the
logging and storage of messages on an external log server.
The following information is provided for each specific log message:
Name
ID
Category
Default Severity
Log Message
The name of the log message, which is a short string, 1-6 words
separated by _. Please note that the name cannot be used as a unique
identification of the log message, as several log messages might share
the same name.
The ID is a number made up of a string of 8 digits which uniquely
identifies the log message. The first 3 digits identify the category to
which the log message belongs.
Note
In this guide, the Name and the ID of the log message
form the title of the section describing the log message.
Log messages are grouped into categories, where each category maps
to a specific subsystem in NetDefendOS. For instance, the IPSEC
category includes some hundreds of log messages, all related to IPSec
VPN activities. Other examples of categories include ARP, DHCP,
IGMP and USERAUTH.
In this guide, categories are listed as sections in Chapter 2, Log
Message Reference.
As previously mentioned, the category is identified by the first 3 digits
in the message ID. All messages in a particular category have the same
first 3 digits in their ID.
The default severity level for this log message. For a list of severity
levels, please see section Section 1.3, "Severity levels".
A brief explanation of the event that took place. This explanation often
features references to parameters, enclosed in angle brackets.
Example:
Administrative user <username> logged in via <authsystem>. Access
level: <access_level>
Note that this information is only featured in this reference guide, and
29