Log - EnGenius EWS Series User Manual

Log

The Syslog protocol allows devices to send event notification messages in response to events, faults, or
errors occurring on the platform as well as changes in configuration or other occurrences across an IP
network to syslog servers. It then collects the event messages, providing powerful support for users to
monitor network operation and diagnose malfunctions. A Syslog-enabled device can generate a syslog
message and send it to a Syslog server.
Syslog is defined in RFC 3164. The RFC defines the packet format, content, and system log related
information of Syslog messages. Each Syslog message has a facility and severity level. The Syslog facility
identifies a file in the Syslog server. Refer to the documentation of your Syslog program for details. The
following table describes the Syslog severity levels.
Code Severity
0 EMERG System is unusable.
1 ALERT Action must be taken
immediately.
2 CRIT Critical conditions.
3 ERROR Error conditions.
4 WARNING Warning conditions.
5 NOTICE Normal but significant
condition.
Description
A "panic" condition usually affecting multiple
apps/servers/sites. At this level it would usually
notify all tech staff on call.
Should be corrected immediately, therefore notify
staff who can fix the problem. An example would be
the loss of a primary ISP connection.
Should be corrected immediately, but indicates
failure in a secondary system, an example is a loss of
a backup ISP connection.
Non-urgent failures, these should be relayed to
developers or admins; each item must be resolved
within a given time.
Warning messages, not an error, but indication that
an error will occur if action is not taken, e.g. file
system 85% full - each item must be resolved within
a given time.
Events that are unusual but not error conditions -
might be summarized in an email to developers or
admins to spot potential problems - no immediate
action required.
General Description
190