APC RAID Subsystem SCSI-SATA II User Manual
Page 32
- 32 -
means that event log can be forwarded from the RAID subsystem to another
running syslogd which it can actually log to a disk file.
Figure 3.4.9.1
1. Server IP/hostname: enter the IP address or hostname of system log server.
2. Port: enter the UDP port number on which system log server is listening to.
The default port number is 514.
3. Facility: select the facility for event log.
4. Event level: Select the event log options
5. Click “Confirm” button.
Server side (Linux – RHEL4)
The following steps are used to log RAID subsystem messages to a disk file. In
the followings, all messages are setup with facility “Local1” and event level
“WARNING” or higher are logged to /var/log/raid.log.
1. Flush firewall
2. Add the following line to /etc/syslog.conf
Local1.warn /var/log/raid.log
3. Send a HUP signal to syslogd process, this lets syslogd perform a re-initialization.
All open files are closed, the configuration file (default is /etc/syslog.conf) will be
reread and the syslog(3) facility is started again.
4. Activate the system log daemon and restart
5. Check the syslog port number, e.g., 10514
6. Change controller’s system log server port number as above
7. Then, syslogd will direct the selected event log messages to /var/log/raid.log
when syslogd receive the messages from RAID subsystem.
For more detail features, please check the syslogd and syslog.conf manpage
(e.g.,man syslogd).
Server side (Windows - 2003)
Windows doesn’t provide system log server, user needs to find or purchase a
client from third party, below URL provide evaluation version, you may use it for
test first.
1. Install winsyslog.exe
2. Open "Interactives Syslog Server"
3. Check the syslog port number, e.g., 10514