Allied Telesis AT-S63 - Manual (Page 134)

Chapter 11: Event Logs and the Syslog Client
134 Section II: Advanced Operations
Syslog Client
The management software features a syslog client to send event
messages to a syslog server on your network. A syslog server can
function as a central repository for events from many different network
devices.
In order for the switch to send events to a syslog server, you must define a
syslog output by specifying the IP address of the syslog server along with
other information, such as the types of event messages the switch is to
send to the server. You can create up to 19 syslog definitions on the
switch.
Note
The event logs, even when disabled, log all the AT-S63 initialization
events that occur when the switch is reset or power cycled. Any
switch events that occur after the AT-S63 initialization are entered
into the logs only if you enable the event log feature. The default
setting for the event log feature is enabled.
Observe the following guidelines when using this feature:
 You can define up to 19 log output definitions.
 The event logs on the switch must be activated in order for the switch
to send events to a syslog server.
 There must be a routing interface on a local subnet from where the
switch is communicating with a syslog server. The switch uses the IP
address of a routing interface as its source address to communicate
with a server. For background information on routing interfaces, refer
to Chapter 32, “Internet Protocol Version 4 Packet Routing” on page
363.
Note
Prior to version 2.0.0 of the AT-S63 Management Software, the
switch could only communicate with a syslog server through its
management VLAN. This restriction no longer applies. The switch
can now communicate with a syslog server from any local subnet
that has a routing interface.