RHEL 5.3 with Emulex HBA on P2000

[Matthias Kretschmer]

Hello,
We are trying to get a DL380 G7 with Emulex HBA connected to an P2000 running.
I already installed hp-fc-enablement-2010-03-31.tar.gz and rebooted.

The driver is loaded during startup:
# cat /var/log/dmesg | grep Emulex
Emulex LightPulse Fibre Channel SCSI driver 8.2.0.33.3p
Copyright(c) 2004-2008 Emulex. All rights reserved.

# cat /var/log/dmesg | grep lpfc
lpfc 0000:0e:00.0: 0:1303 Link Up Event x1 received Data: x1 x1 x10 x2 x0 x0 0
lpfc 0000:0e:00.1: 1:1303 Link Up Event x1 received Data: x1 x1 x10 x2 x0 x0 0

I can discover the WWPN of my both HBAs:
# cat /sys/class/fc_host/host2/port_name
0x10000000c9f2a092
# cat /sys/class/fc_host/host3/port_name
0x10000000c9f2a093

Do not know why there is no host1?

I can also discover the WWPN of the P2000:
# cat /sys/class/fc_remote_ports/rport-2\:0-0/port_name
0x207000c0ff10b7f0

This means for me, that the driver is running and the HBAs can connect to the P2000.

But now I do not know how to proceed. Where are the luns I already created on the P2000?
In my understanding there should be a lpfc folder under /dev/scsi, but there is not.

Could somebody give me a hint what I am missing and where to look.

Thank you very much in advance.
BR
Matthias Kretschmer

[Matthias Kretschmer]

Sorry, I meant of course /proc/scsi

# ll /proc/scsi/
total 0
-r--r--r-- 1 root root 0 Nov 23 23:07 device_info
-r--r--r-- 1 root root 0 Nov 23 23:07 scsi
dr-xr-xr-x 2 root root 0 Nov 23 23:07 sg

BR
Matthias Kretschmer

[Alzhy]

So what is your issue? That you do not have a host1? From your account - your Emulex is doing fine.

If your issue is it does not see your P2000 LUNs -- Are you sure you have "presented" LUNS to this server?

What does:

multipath -ll
cat /proc/scsi/scsi

show you?

Do you have /etc/multipath.conf from the HP Device Mapper Enablement Kit? Is HPDM kit installed? Do you have the suggested lpfc /etc/modprobe.conf settings?

[Matthias Kretschmer]

Thank you for your fast reply.

To answer your questions:
"If your issue is it does not see your P2000 LUNs?"
Yes, this is my only issue. And yes, I am sure.
I tested it with a Windows Server connected to the P2000 and I can see the Lun on the server.

I installed now the HP Device Mapper Enablement Kit.

Now I have the following situation:

# multipath -ll
mpath0 (3600c0ff00010d828ef08fd4c01000000) dm-2 HP,P2000 G3 FC
[size=1.5T][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=50][active]
\_ 2:0:0:0 sda 8:0 [active][ready]
\_ round-robin 0 [prio=10][enabled]
\_ 3:0:0:0 sdb 8:16 [active][ready]

# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: TEAC Model: DV-28S-W Rev: C.2D
Type: CD-ROM ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: HP Model: P2000 G3 FC Rev: T201
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: HP Model: P2000 G3 FC Rev: T201
Type: Direct-Access ANSI SCSI revision: 05

The /etc/modprobe.conf has this entry:
options lpfc lpfc_lun_queue_depth=16 lpfc_nodev_tmo=30 lpfc_discovery_threads=32

It was generated during the isntallation of the hp-fc-enablement-2010-03-31.tar.gz and I did not change it.

So I think the lun is visible, but I do not know how to use it. I thought the lun will be available at /dev/sda?

Hope you can give me the needed last hint to get my lun configured.

BR
Matthias

[Alzhy · Accepted solution]

"So I think the lun is visible, but I do not know how to use it. I thought the lun will be available at /dev/sda?"

Oh boy... so is this your first time on a Linux system with externally connected SAN disks?

If so, treat that disk -- in this case /dev/mpath0 as either:

1.) an LVM Physical VOlume and a rve an VM VG and an LVOL on it and a filesystem on top of the LVOL.
2.) Use it directly (BAD idea as it's device name could change

Or you can edit the /etc/multipath.conf and give that "lun" a friendly name as follows:


multipath {
wwid 3600c0ff00010d828ef08fd4c01000000
alias P2000_lun1
}

Then do a multipath -v2.

That disk should now have a "persistent" friendly name immune to whatever /dev/dm-NN changes. It will now be named /dev/mpath/P2000_lun1 or /dev/mapper/P2000_lun1 which you can still use under LVM or directly create an ext2/3/4 filesystem on top and directly mount.



Cheers!

[Matthias Kretschmer]

Thank you very much.
That was what I am looking for.

Just to clarify this.
Yes this was the first time I used Emulex and the first time I used the in-box kernel driver.
Until now we used QLogic and the qla2xxx driver, and the behavior is different with this combination.
Therfore I stucked at this point.

Thanks again.

BR