Rorke Data Galaxy Aurora LS Series Configuration And Setup page 85

Raid storage system
Table of Contents

Advertisement

G A L A X Y ®
A U R O U R A
L S
C O N F I G U R A T I O N
A N D
S Y S T E M
I N T E G R A T I O N
G U I D E
Going clockwise from the upper left, you have to have a RAID in order to create a LUN. The
user and Initiator are optional, however if there are any defined, the user you are trying to
communicate with must also be set up as a user and given read only or read/write access to
the LUN. Then the Target is optional, however if one is assigned to the LUN, then it must be
on the same connection that the client is going to be connected to. The SFP on the array
being used must be working – with no more than one connected to a switch if you are using a
switch (unless you are doing some careful zoning on the switch). For troubleshooting, if you
have a switch, you may want to remove it, otherwise either of the SFPs, cables, switch, or
zoning could be the problem. If you are using a switch, and it is zoned, make sure the array
and the client are in the same zone (I have had a tech support story once about a switch
which was rented by a customer, and although they didn't zone the switch, the previous renter
did, disabling the ports that were being used). Then on the client, the cable or SFP could be a
problem, and the HBA could have a problem. There could be an OS problem (which is rare),
or a problem with the driver. Here's the troubleshooting technique: If you look carefully at the
chart, there is a straight chain, going from RAID to the Fibre Driver on the client. You should
troubleshoot from one end of the chain to the other, otherwise it is confusing. Start by making
sure there is a RAID, with a LUN on it. Next, look at Users, and see if the user is showing up
at all. If not, skip to the other end of the chain, and start troubleshooting from that end. If the
user is showing up under users, then it is almost certainly a problem with an Initiator or target
setting – check to make sure either no targets exist, or that the target being used exists, and
check to make sure the initiators exist, and that the user in question is assigned to that LUN,
or that no initiators exist. If you had to troubleshoot going the other way, if the client is running
OS/X, make sure the Fibre card/drivers are working by going into Apple System Profiler. If it is
Linux, do an lsmod to find the Fibre driver. If it is Windows, go into the device manager, and
make sure you can see the Fibre channel card under Storage devices, and that there is no
yellow or red exclamation point next to it. If this is Linux, do an lsscsi to see if you can see the
LUN. If it is Windows, go into Disk Management and see if you can see the LUN. If it is OS/X,
go into Apple Disk Utility. At this point, if the array is all set correctly, and the client seems OK,
you may have a hardware problem. Check the LEDs on the array and the client – they should
84
Section 4 Troubleshooting Guide

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents