Chapter 7: Configuring logging
System logging is a method of collecting system messages generated by system events. This
chapter provides information on G250/G350 system logging and contains the following
sections:
Logging overview
●
Configuring a Syslog server
●
Configuring a log file
●
non-volatile memory, and how to display and delete the log file
Configuring a session log
●
logging messages to your screen
Configuring logging filters
●
level and by applications
Logging configuration examples
●
logging sink
Logging overview
The Avaya G250/G350 Media Gateway includes a logging package that collects system
messages in several output types. Each of these types is called a sink. When the system
generates a logging message, the message can be sent to each sink that you have enabled.
Table 3: Logging sinks
Sink
Syslog
Log file
Session
— overview of the G250/G350 logging process
— instructions on how to configure and enable Syslog servers
— instructions on how to configure and enable message logging to
— instructions on how to configure and enable the display of
— instructions on how to filter logging messages by severity
Description
Logging messages are sent to up to three configured servers, using
Syslog protocol as defined in RFC 3164. Messages sent to the Syslog
server are sent as UDP messages.
Logging data is saved in the flash memory. These compressed, cyclic files
serve as the system logging database.
Logging messages are sent to the terminal screen:
For a local connection - messages appear online on the local
●
terminal.
For a remote Telnet/SSH connection - messages appear online on
●
the remote terminal.
This sink is deleted whenever a session ends.
— demonstrations of the configuration of each type of
Issue 1.1 June 2005
103