iSCSI GbE to SAS/SATA II RAID Subsystem
36
User Manual
Using
“Messenger”
, user must enable the service “Messenger” in Windows (Start
Æ
Control Panel
Æ
Administrative Tools
Æ
Services
Æ
Messenger), and then event logs
can be received. It allows up to 3 messenger addresses. User can choose the event log
levels and default setting enables the WARNING and ERROR event logs.
Using
“System log server”
, user can choose the facility and the event log level. The
default port of syslog is 514. The default setting enables event level: INFO, WARNING
and ERROR event logs.
Configuration
The following configuration is a sample for target and log server setting:
Target side
1.
Go to \System configuration\Notification setting\System log server.
2.
Fill the fields
3.
Server IP/hostname: enter the IP address or hostname of system log server.
4.
UDP Port: enter the UDP port number on which system log server is listening to.
The default port number is 514.
5.
Facility: select the facility for event log.
6.
Event level: Select the event log options.
7.
Click “Confirm” button.
Server side (Linux – RHEL4)
The following steps are used to log RAID subsystem messages to a disk file. In
the following, 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
Note: sysklogd has a parameter "-r" , which will enable sysklogd to receive
message from the network using the internet domain socket with the syslog
service, this option is introduced in version 1.3 of sysklogd package.
5.
Check the syslog port number,
e.g. , 10514
6.
Change controller’s system log server port number as above
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. http://www.winsyslog.com/en/
1.
Install winsyslog.exe
2.
Open "Interactives Syslog Server"
3.
Check the syslog port number, e.g., 10514
4.
Change controller’s system log server port number as above
5.
Start logging on "Interactives Syslog Server"
