Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
07:01.0 Fibre Channel: Emulex Corporation LP8000 Fibre Channel Host Adapter (rev 02)
Subsystem: Emulex Corporation LP8000 Fibre Channel Host Adapter
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 248 (63750ns min), Cache Line Size: 128 bytes
Interrupt: pin A routed to IRQ 209
Region 0: Memory at fdff0000 (64-bit, non-prefetchable) [size=4K]
Region 2: Memory at fdfe0000 (64-bit, non-prefetchable) [size=256]
Region 4: I/O ports at 5000 [size=256]
My Question is: After load the module, what should I do to RH find the LUNs?
I send an email to Emulex support asking it and received the following reply:
The /sys/class/scsi_host/hostX tree is the correct way to gather information regarding the lpfc HBAs and scsi luns. Note that the lpfc driver is not a scsi driver but rather a fibre channel transport driver for the OS scsi layer (similar to ethernet and TCP packets). The lpfc driver logs into storage controllers only. The OS scsi layer discovers luns behind the storage controllers. You'd have to inquire with Red Hat to see if there is a way to get them to display lun acquisition information through scsi logging.