Hi --
I've been doing more digging regarding the replies I've received
so far:
Rich Fenton wrote:
Have you tried running SANSurfer and seeing what targets/luns it
sees - this is usually pretty good at helping to debug problems
I downloaded & installed the SANsurferHBA GUI for Linux/IA32 &
ran it from one of the candidate boxes. It reports ...
Error: SDOpenDevice(0, xx) failed (0x20000074) (Out of memory)
Error: **NO** compatible HBAs found during scan - Terminating...
... which isn't overly surprising to me. I didn't expect to have
the RedHat Enterprise Linux 3 AS Release 3 recognize & support the
Qlogic card without a bunch of steps. One issue is installing the
Linux driver for the card. The instructions I've found so far are,
well, gnarly at best. Is there something I'm missing about this?
But really, if zoning on the switch and masking on the NetApp
are correct, shouldn't one be able to see the LUNs from the Qlogic
Fast!Util BIOS configuration app? Or am I mistaken about this?
Britt Bolen wrote:
You definitly use the WWPN not the WWNN in the igroups.
You must use an igroup to map a lun, there's no way around it.
When you're probing the luns from BIOS does 'fcp show initiator'
list the initiators as logged in?
I'm 99% certain that I'm using the cards' WWPNs, as listed by
the switch. When booting one of the candidate Dell servers &
firing up Fast!Util, "fcp show initiator" lists:
servername> fcp show initiator
Initiators connected on adapter 9a:
Portname Group
.
.
.
21:00:00:e0:8b:09:6e:7b cruncher1Group
.
.
.
... which matches the entry on the switch. If I shut down the
Dell server in question, then this entry disappears from the
output.
And here's one LUN that should be visible:
serverName> lun show -m /vol/san/cruncher1
/vol/san/cruncher1 cruncher1Group 0 FCP
serverName>
[I wiped out some extra spaces to make the line mail-friendly.]
This leads me to think that the zoning and masking are set
correctly: the NetApp sees the initiator, knows which group
it's in, and has a LUN ready to serve to that group. Yet the
Dell server in question can't see it.
Ilya Birman wrote:
What SAN switches are you using? It possible to mask LUNS on
your switch too. Cisco MDS can discover luns and then mask
them to host.
I have a generic Qlogic SANbox2-16. There is a minor firmware
update available for it, so I plan to upgrade it in the next day
or two. Perhaps that is one of the issues. But I don't seem to
see any hooks on this switch for LUN masking. This is the switch
through which all of our Dell and HP-UX servers see LUNs served
from the old DotHill SAN RAID controller, and through which our
HP-UX servers see their LUNs served by the NetApp. But Fast!Util
on all of our Dells can't see the NetApp's LUNs: the "Fibre Disk
Utility" reports "Selected device is not a disk device" when
selecting one of the NetApp IDs.
Thanks to all of you for your replies. Are there other tricks
worth trying?
Have a great day!
Don Glascock
--
Donald S. Glascock
Mailstop RO-SN-2-220
Special Purpose Processor Development Group
Mayo Foundation
Rochester, MN 55905
Glascock.Donald@Mayo.EDU +1.507.538.5467 +1.507.284.9171 (fax)
http://www.mayo.edu/sppdg
"No matter where you go, there you are."
> -----Original Message-----
> From: Glascock, Donald
> Sent: Wednesday, July 13, 2005 5:05 PM
> To: 'Mun.Luke'; toasters@mathworks.com
> Subject: RE: FAS960 / DOT 7.0.1R1 / SAN LUN for Dell servers...?
>
>
>
> Hi, Luke --
>
> Thanks for taking the time to respond.
>
> I've just re-verified that the cards have the correct & latest
> BIOS firmware. These range from old QLA2200 cards to new, Dell-
> specific QLA2322 cards.
>
> Since they all fail to see their NetApp LUNs, there must be
> something going on that I just don't understand, but I don't know
> what, since they see the DotHill RAID controller's masked LUNs.
> Since the Dell servers can see the NetApp's HBAs, my guess is that
> the NetApp's initiator groups are the most likely candidates. Does
> one use the WWPN listed in the switch's GUI, as I did for our HP-UX
> servers? Is there a way to serve a NetApp LUN without assigning it
> to an initiator group (for debugging purposes)?
>
> Thanks for your help!
>
> Don Glascock
>
> --
> Donald S. Glascock
> Mailstop RO-SN-2-220
> Special Purpose Processor Development Group
> Mayo Foundation
> Rochester, MN 55905
> Glascock.Donald@Mayo.EDU +1.507.538.5467 +1.507.284.9171 (fax)
>
http://www.mayo.edu/sppdg
> "No matter where you go, there you are."
>
>
> > -----Original Message-----
> > From: Mun.Luke [mailto:Luke.Mun@IGT.com]
> > Sent: Tuesday, July 12, 2005 11:43 AM
> > To: 'Glascock, Donald S.'; toasters@mathworks.com
> > Subject: RE: FAS960 / DOT 7.0.1R1 / SAN LUN for Dell servers...?
> >
> >
> > Update your Firmware on Qlogic HBA. I've seen this problem
> > Emulex card
> > before and that fixed it.
> >
> > luke
> >
> > -----Original Message-----
> > From: owner-toasters@mathworks.com
> > [mailto:owner-toasters@mathworks.com] On
> > Behalf Of Glascock, Donald S.
> > Sent: Tuesday, July 12, 2005 9:11 AM
> > To: toasters@mathworks.com
> > Subject: FAS960 / DOT 7.0.1R1 / SAN LUN for Dell servers...?
> >
> >
> > Hi --
> >
> > We have a few Dell PowerEdge servers (2850s, 2650s, 6850s)
> > attached to our baby SAN: a single Qlogic SANbox2. Our first
> > foray into SAN disk service was through a DotHill SANnet4320,
> > which worked well and was cheap in a time when SAN standards
> > were still developing.
> >
> > If the boot process of any of the Dell servers is interrupted
> > with a ^Q, the Qlogic FC HBA FAST!UTIL BIOS leaps into high gear.
> > The disk utilities therein can see the LUNs offered by the DotHill
> > box.
> >
> > However, the Qlogic FAST!UTIL disk utility cannot see the LUNs
> > offered by our new NetApp FAS960. Our HP-UX servers see their
> > associated LUNs offered from it, and the Dell servers see the two
> > HBAs to which the NetApp is attached to the SAN. But no LUNs.
> >
> > I'm copying & pasting the WWPN for the Dell servers from the
> > SANsurfer switch admin GUI into the initiator group fields in
> > FilerView on the NetApp, and these are the numbers I use on the
> > DotHill box. The format seems fine, and typing the colon-separated
> > numbers in by hand seems to make no difference.
> >
> > It is not clear to me how one offers a LUN from the NetApp without
> > LUN masking: if the LUN were global, then at least this would be
> > a good test.
> >
> > I've created several NetApp LUNs with different properties, and
> > none seem to please the Dell boxes. Serving LUNs to the HP-UX
> > servers worked on the first try, so I figure that I'm missing
> > something obvious. But I don't know what. I've tried searching
> > the Toasters archive, but haven't seen references to FAST!UTIL.
> >
> > Would you send me any suggestions you may have as to why
> > FAST!UTIL and/or the NetApp seem to be unhappy, please?
> >
> > Thanks for your time & have a great day!
> >
> > Don Glascock
> >
> > --
> > Donald S. Glascock
> > Mailstop RO-SN-2-220
> > Special Purpose Processor Development Group
> > Mayo Foundation
> > Rochester, MN 55905
> > Glascock.Donald@Mayo.EDU +1.507.538.5467 +1.507.284.9171 (fax)
> >
http://www.mayo.edu/sppdg
> > "No matter where you go, there you are."
> >
>
Glascock, Donald S.