topic Re: linux equiv to insf in Operating System - Linux

linux equiv to insf

Kim Kendall — Wed, 08 Oct 2003 11:53:08 GMT

Connecting a (RHAS) linux systems to a CLARiiON array. I've got them zoned, storage groups created, hosts added to the group, Raid group made, LUN created and added to the storage group.

Now... In HPUX, this is where I would go in and create the device files for the LUN's being presented to the host. Then on the CLARiiON, I would see the device file name for the LUN.

But on Linux, what do I need to do to create the device files for the LUN's?

Re: linux equiv to insf

Steven E. Protter — Wed, 08 Oct 2003 12:33:23 GMT

Actually, if your connection card(fiber) is supported, all you should need to do is boot the system. There should be auto detect of disks allocated on the array as soon as the driver for the card is configured.

SEP

Re: linux equiv to insf

Kim Kendall — Thu, 09 Oct 2003 09:15:31 GMT

well - the fiber card is a Qlogic QLA2200 (EMC supported). I still can't see the LUN (after a reboot), and on the array, I don't see what device file it thinks it belongs to.
---
The fiber card doesn't come up on its' own, I have to do a modprobe to get it to check-in to the Brocade.
---
After a boot, I take down the Navisphere agent, do a modprobe on the card, and bring the agent back up (see attached log file). As you can see in this log file, the system thinks there is a "sdb" device.
---
But doing a fdisk /dev/sdb results in the error : "Unable to open /dev/sdb"

Re: linux equiv to insf

Kim Kendall — Thu, 09 Oct 2003 09:22:27 GMT

I saw Ed Hoppe's post... maybe this is it...
---
There is a pair of internal disks (mirrored), these would be considered the first LUN, and the LUN on the EMC array would be a second LUN.
---
Would it be necessary then to include :
scsi_mod max_scsi_luns=2
in the modules.conf file?

Re: linux equiv to insf

Zeev Schultz — Thu, 09 Oct 2003 09:32:30 GMT

usually you use MAKEDEV (man MAKEDEV) to create
device files on Linux. I asume you can see the module with lsmod after Linux booted? Did you add proper line to /etc/modules.conf?
something like that:

alias scsi_hostadapterN qla2x00 (N starts with 0)

I attach EMC's Linux conf. gude for Qlogic HBAs on Linux. Seek somethere on pages 25+..

Re: linux equiv to insf

Kim Kendall — Thu, 09 Oct 2003 09:47:10 GMT

It's in the modules.conf:
-
alias scsi_hostadapter4 qla2200
-
on a reboot, lsmod shows there is no qla2200. Running modprobe qla2200 loads it fine. (see the first attachment, it shows what a manual "modprobe qla2200" records in the /var/log/messages file immed. following a reboot.

Re: linux equiv to insf

Zeev Schultz — Thu, 09 Oct 2003 09:57:15 GMT

From the guide I posted (p. 21) :

If the QLogic HBA is present in the system prior to a new installation
of Linux, the distribution installation application might automatically
load its version of the driver, which will be installed and inserted
automatically when the host reboots. For this reason, if the customer
is using Red Hat, EMC recommends installing the Linux operating
system and disabling kudzu before installing the QLogic HBAs.

Also I'd suggest to rebuild qlogic driver (and check if it appears in /lib/modules/*/modules.dep.) from scratch, remove unused qlogic modules from kernel, restart without kudzu and rebuild.

Zeev

Re: linux equiv to insf

Kim Kendall — Thu, 09 Oct 2003 12:58:31 GMT

Actually - in the EMC document:
---
EMC Support Matrix
October 2003
P/N 300â 000â 166
ECO 35097 Rev B28
---
I've cut a portion of the support matrix out and put it in a Word doc. In note #15, it states that the driver that is included in this kernel is supported.
---
I meet all of the requirements;
kernel : 2.4.9-e.25smp
Card: QLogic QLA2200F
Firmware: 1.83
Driver: 6.04.01
---
I added the /proc/scsi/qla2200/2 contents as an option in the modules.conf file and re-created the initrd image.

Now on boot-up, the card checks in with the Brocade fine, and it sees a "sdb", but I still can't do anything with

Re: linux equiv to insf

Kim Kendall — Thu, 09 Oct 2003 13:01:37 GMT

PS - I would have attached the EMC doc, but even zipped it's over 4.5MB