Dot Hill Systems SANnet II 200, Installation, Operation And Service Manual

Page: 125 / 186

Appendix B Cabling JBODs B-15
■
For expansion units, the RAID firmware event log
For more information about replacing the chassis, I/O module, or controller, refer to
the
SANnet II Family FRU Installation Guide .
Caution –
Whenever you are troubleshooting your array or replacing components,
there is an increased possibility of data loss. To prevent any possible data loss, back up
user data to another storage device prior to replacing a disk drive, or any other
component.
Before you begin troubleshooting a JBOD or expansion unit, check the cables that
connect the host to the JBOD or expansion unit. Look for bent pins, loose wires, loose
cable shields, loose cable casing, and any cables with 90 degree or more bends in
them. If you find any of these conditions, replace the cable.
The Figure B-8 flowchart provides troubleshooting procedures specifically for JBODs
and expansion units. For additional troubleshooting flowcharts, see “Power Supply and
Fan Module” on page 7-7 and “Drive LEDs” on page 7-9.
B.13.2.1 Writing Events to a Log File for an IBM AIX Host
For an IBM AIX operating system, the event logs are not logged by default. You might
need to change
/etc/syslog.conf
to enable it to write to a log file.
1. Modify
/etc/syslog.conf
to add the following line:
2. Make sure the file that is specified in the added line exists.
If it does not exist, you must create it. For example, in the above configuration, you
would create a file named
/tmp/syslog
.
3. Change to
/tmp/syslog
and restart the
syslog
by typing
:
*.info /tmp/syslog rotate size 1000k
kill -HUP ‘cat /etc/syslog.pid‘