System logging, System logging introduction, System logging messages – Avaya Stackable Switch P3343T-ML User Manual
Page 86
Chapter 10 Switch Configuration
70
Avaya P334T-ML User’s Guide
System Logging
System Logging Introduction
The Avaya P330 System Logging feature is capable of storing system messages on a
device, outputting messages to the CLI console, Telnet session, or SSH session, and
reporting remotely to a Syslog server. System Logging is an important tool used for
routine maintenance, auditing, and monitoring access to the device.
The components of System Logging include:
•
Logging Messages
•
Sinks
•
Message filters based on application, severity, or access level
System Logging Messages
System logging messages provide the following information:
•
Module ID – The number of the module from which the message originated.
•
Event Time – The time the event occurred. The Event Time is included only if a
time server is configured for the device.
•
Application – The software sub-system from which the message originated.
•
Severity Level – The severity level of the message. Severity levels from the
highest severity to the lowest include: Emergency, Alert, Critical, Error,
Warning, Notification, Informational, Debug
•
Message Content – A description of the event.
In order to reduce the number of collected and transmitted messages, filtering
options should be used. The filtering options are based on message classification by
application and severity. For a specified sink, you can define the threshold severity
for messages output by each application. Messages with a severity lower than the
defined threshold are not sent to the specified sink.
In addition, the session sink filters the messages using the access level of the user.
This filtering depends on the syslog sink type:
•
Session – only messages the user is permitted to access (according to the user’s
access level) are output to the console or Telnet/SSH session.
•
Log file – when displaying the contents of the log file, the user can see only
messages appropriate to their access level.
•
Syslog server – the user should define the access level used when sending
messages to the syslog server. The user cannot specify an access level for the
syslog server higher than the level which has been assigned to the user.
You can define severity filters to overrule the default threshold. The following is a
list of default severity threshold for each syslog sink:
•
Syslog server – Warning
•
Log file – Informational