System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Install hp SAN on CentOS 4.3: problem

mharb
Occasional Visitor

Install hp SAN on CentOS 4.3: problem

hi guys ,

I have ML380 Hp server, and I connected Fibre Channel: Emulex Corporation Zephyr LightPulse Fibre Channel Host Adapter (rev 01) , on it,

and I can see Card when I apply lspci, and when I download driver from this hp link(http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=1143949&prodTypeId=12169&prodSeriesId=1809835&swLang=8&taskId=135&swEnvOID=2025)

I made all steps that HP advice to do , but I can see my SAN .

on the dmesg log this piece related my card:

Emulex MultiPulse module version 2.2.39
Copyright(c) 2003-2006 Emulex. All rights reserved.
lpfcmpl:Using AutoConfiguration: Type 1
Emulex LightPulse Fibre Channel SCSI driver 8.0.16.40
Copyright(c) 2003-2008 Emulex. All rights reserved.
ACPI: PCI interrupt 0000:17:00.0[A] -> GSI 19 (level, low) -> IRQ 193
PCI: Setting latency timer of device 0000:17:00.0 to 64
lpfc 0000:17:00.0: 0:1303 Link Up Event x1 received Data: x1 xf7 x8 x0
scsi0 : HP FC2142SR 4Gb PCI-e, SC, Fibre Channel Adapter on PCI bus 17 device 00 irq 193
scsi: unknown device type 12
Vendor: HP Model: HSV210 Rev: 6000
Type: RAID ANSI SCSI revision: 02
lpfcmpl:PathSM Dev:0:0:0 Path:0:1:0 : event DOWN: From STANDBY to FAILED
lpfcmpl:PathSM Dev:0:0:0 Path:0:1:0 : event DISABLE: From FAILED to DISABLED
scsi: unknown device type 12
Vendor: HP Model: HSV210 Rev: 6000
Type: RAID ANSI SCSI revision: 02
lpfcmpl:PathSM Dev:0:0:0 Path:0:2:0 : event DOWN: From STANDBY to FAILED
lpfcmpl:PathSM Dev:0:0:0 Path:0:2:0 : event DISABLE: From FAILED to DISABLED
scsi: unknown device type 12
Vendor: HP Model: HSV210 Rev: 6000
Type: RAID ANSI SCSI revision: 02
lpfcmpl:PathSM Dev:0:0:0 Path:0:3:0 : event DOWN: From STANDBY to FAILED
lpfcmpl:PathSM Dev:0:0:0 Path:0:3:0 : event DISABLE: From FAILED to DISABLED
scsi: unknown device type 12
Vendor: HP Model: HSV210 Rev: 6000
Type: RAID ANSI SCSI revision: 02



Is there any adnive.
5 REPLIES
Steven E. Protter
Exalted Contributor

Re: Install hp SAN on CentOS 4.3: problem

Shalom,

The emulex HBA driver is not in your initrd ramdisk image. It needs to be.

You need to make a new initrd image.

General procedure, once the drivers are installed.

cd /boot
mv initrd-....img to initrd-....img.orig

mkinitrd

mkinitrd initrd-2.6.9-42.0.3.ELsmp.img 2.6.9-42.0.3.ELsmp


SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Uwe Zessin
Honored Contributor

Re: Install hp SAN on CentOS 4.3: problem

From the logs it looks like the adapter sees only the EVA controller devices at LUN address #0 - this is not a disk LUN onto which you can store any data. Did you create a Host entry with the adapter's WWPN and map a virtual disk to it?
.
mharb
Occasional Visitor

Re: Install hp SAN on CentOS 4.3: problem

hello Steven, thnx for your advice, but when I download the hp driver(A8002A) from link in my first message.

and when I Apply ./INSTALL, this command make creation for a new initrd image.

is there any way to Insure that the new image created??

and if there is any way to insure that about driver , because I afraid that I download wrong one.

Thank for your cooperation
mharb
Occasional Visitor

Re: Install hp SAN on CentOS 4.3: problem

hello Uwe Zessin, thnx for your advice.

this is another problem, because thser is other team work on SAN and do configuration, and I do remotely support for system just, So I don't know what must do on SAN side, can you please advice steps that I need to do on SAN side??

thank for your cooperation
Uwe Zessin
Honored Contributor

Re: Install hp SAN on CentOS 4.3: problem

The EVA administrator must create a "Host" entry and use the World Wide Port Name (WWPN) of your server's Fibre Channel adapter. Then (s)he must create a virtual disk to reserve space within the EVA for your use. Finally the virtual disk must be presented to the Host created.

Next, you should reboot the server - in some environments it is not possible to use a simple rescan.
.