Allied Telesis AT-S63 - Manual (Page 108)

Chapter 9: Event Logs and the Syslog Client
108 Section II: Advanced Operations
Syslog Client
The management software features a syslog client for sending 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 AT-S63 initialization
events that occur when the switch is reset or power cycled. Any
switch events that occur after 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.
ˆ The local subnet on the switch where the syslog server is a member
must have a routing interface. The switch uses the IP address of the
routing interface as its source address when communicating with the
server. For background information on routing interfaces, refer to
Chapter 28, “Internet Protocol Version 4 Packet Routing” on page 305.
Note
Prior to version 2.0.0 of the AT-S63 management software, a syslog
server had to be a member of the switch’s management VLAN. This
restriction no longer applies. The server can be located on any local
subnet of the switch, so long as the subnet has been assigned a
routing interface on the switch.