Configuring logging
The following sections describe:
Setting the logging filters
●
Severity levels
●
Applications to be filtered
●
Setting the logging filters
For each sink, you can set logging filters by specifying a severity level per application, as
follows:
To create a filter for messages sent to a specified Syslog server, type set logging
●
server condition application severity ip address.
To create a filter for messages sent to a log file, type set logging file condition
●
application severity.
To create a filter for messages sent to a session log on a terminal screen, type set
●
logging session condition application severity.
where:
application - application for which to view messages (use all to specify all
●
applications). For the list of applications see
severity - minimum severity to log for the specified application (use none to disable
●
logging messages for the specified application). For a list of the severity levels and the
default severity settings, see
ip address - the IP address of the Syslog server.
●
G350-001(super)# set logging server condition dialer critical 147.2.3.66
Done!
G350-001(super)# set logging file condition dhcps warning
Done!
G350-001(super)# set logging file session isakmp information
Done!
You can also filter the show logging file content command by severity for each
application, using the same variables as in the set logging file condition command. In
addition, you can limit the number of messages to display. For example, to display the 50 most
recent messages from the QoS application with a severity level of critical or higher, type show
logging file content critical qos 50.
G350-001(super)#
110 Administration for the Avaya G250 and Avaya G350 Media Gateways
Severity levels
show logging file content critical qos 5
Applications to be filtered
on page 111.
0
on page 112.