FC not visible in VMWare ESXi 5.5

[Bandlow]

Hello,
I cannot see my LUN in VMWare.
Any help is apreciated.

FC connection is established

esxcli storage core adapter list

vmhba2    qlnativefc   link-up     fc.2000001b328ade38:2100001b328ade38  (0:8:0.0) QLogic Corp ISP2432-based 4Gb Fibre Channel to PCI Expres


in Quadstor Host /var/log/messages

Jan 22 20:31:47 san1 kernel: qla2xxx 0000:06:00.0: PCI INT A disabled
Jan 22 20:32:04 san1 kernel: qla2xxx [0000:00:00.0]-0005: : QLogic Fibre Channel HBA Driver: 8.06.00.08-k.
Jan 22 20:32:04 san1 kernel: qla2xxx 0000:06:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Jan 22 20:32:04 san1 kernel: qla2xxx [0000:06:00.0]-001d: : Found an ISP5432 irq 17 iobase 0xffffc90000c36000.
Jan 22 20:32:04 san1 kernel: qla2xxx 0000:06:00.0: firmware: requesting ql2400_fw.bin
Jan 22 20:32:04 san1 kernel: scsi6 : qla2xxx
Jan 22 20:32:04 san1 kernel: qla2xxx [0000:06:00.0]-00fb:6: QLogic QLE220 - PCI-e, HP QLE220 4Gb SMB HBA.
Jan 22 20:32:04 san1 kernel: qla2xxx [0000:06:00.0]-00fc:6: ISP5432: PCIe (2.5GT/s x4) @ 0000:06:00.0 hdma+ host#=6 fw=7.00.01 (9496).
Jan 22 20:32:05 san1 kernel: qla2xxx [0000:06:00.0]-505f:6: Link is operational (4 Gbps).
Jan 22 20:32:06 san1 kernel: qla2xxx [0000:06:00.0]-1020:6: **** Failed mbx[0]=4006, mb[1]=7fe, mb[2]=c8f4, mb[3]=8100, cmd=6a ****.
Jan 22 20:48:09 san1 kernel: qla2xxx [0000:00:00.0]-0005: : QLogic Fibre Channel HBA Driver: 8.06.00.08-k.
Jan 22 20:48:09 san1 kernel: qla2xxx 0000:06:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Jan 22 20:48:09 san1 kernel: qla2xxx [0000:06:00.0]-001d: : Found an ISP5432 irq 17 iobase 0xffffc90000c6a000.
Jan 22 20:48:09 san1 kernel: qla2xxx 0000:06:00.0: firmware: requesting ql2400_fw.bin
Jan 22 20:48:09 san1 kernel: scsi0 : qla2xxx
Jan 22 20:48:09 san1 kernel: qla2xxx [0000:06:00.0]-00fb:0: QLogic QLE220 - PCI-e, HP QLE220 4Gb SMB HBA.
Jan 22 20:48:09 san1 kernel: qla2xxx [0000:06:00.0]-00fc:0: ISP5432: PCIe (2.5GT/s x4) @ 0000:06:00.0 hdma+ host#=0 fw=7.00.01 (9496).
Jan 22 20:48:09 san1 kernel: qla2xxx [0000:06:00.0]-505f:0: Link is operational (4 Gbps).
Jan 22 20:48:09 san1 kernel: qla2xxx [0000:06:00.0]-1020:0: **** Failed mbx[0]=4006, mb[1]=7fe, mb[2]=2082, mb[3]=7100, cmd=6a ****.

Jan 22 20:48:23 san1 kernel: dd_load_thread:1033 ddtable load for group Default took 875 msecs
Jan 22 20:48:26 san1 kernel: scsi5 : QUADStor ldev
Jan 22 20:48:26 san1 kernel: scsi 5:0:0:0: Direct-Access     QUADSTOR VDISK            2.0  PQ: 0 ANSI: 6
Jan 22 20:48:26 san1 kernel: scsi 5:0:0:0: Attached scsi generic sg1 type 0
Jan 22 20:48:26 san1 kernel: sd 5:0:0:0: [sda] 419430400 512-byte logical blocks: (214 GB/200 GiB)
Jan 22 20:48:26 san1 kernel: sd 5:0:0:0: [sda] Write Protect is off
Jan 22 20:48:26 san1 kernel: sd 5:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jan 22 20:48:26 san1 kernel: sda: unknown partition table
Jan 22 20:48:26 san1 kernel: sd 5:0:0:0: [sda] Attached SCSI disk
Jan 22 20:48:36 san1 mcelog: failed to prefill DIMM database from DMI data
Jan 22 20:48:37 san1 abrtd: Init complete, entering main loop
Jan 22 20:57:33 san1 scsi_id[3624]: no device specified
Jan 22 21:17:28 san1 kernel: scsi6 : QUADStor ldev
Jan 22 21:17:28 san1 kernel: scsi 6:0:0:0: Direct-Access     QUADSTOR VDISK            2.0  PQ: 0 ANSI: 6
Jan 22 21:17:28 san1 kernel: sd 6:0:0:0: [sda] 41943040 512-byte logical blocks: (21.4 GB/20.0 GiB)
Jan 22 21:17:28 san1 kernel: sd 6:0:0:0: Attached scsi generic sg1 type 0
Jan 22 21:17:28 san1 kernel: sd 6:0:0:0: [sda] Write Protect is off
Jan 22 21:17:28 san1 kernel: sd 6:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jan 22 21:17:28 san1 kernel: sda: unknown partition table
Jan 22 21:17:28 san1 kernel: sd 6:0:0:0: [sda] Attached SCSI disk


 

[QUADStor Support]

Which version of quadstor and the os distribution are you using ?
Can you send the list of devices detected. Specifically is there a
device with product string 'FCSCBRIDGE' ?

> --
> You received this message because you are subscribed to the Google Groups
> "QUADStor Storage Virtualization" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to quadstor-vir...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

[Bandlow]

I am using CentOS 6.5 x64 and the newest Quadstor rpms

There is no FCSCBRIDGE anywhere. Where should i find this device? lsscsi?

on builditf I get following error, maybe this is the cause

ERROR: modinfo: could not find module iscsit
ERROR: modinfo: could not find module ldev
ERROR: modinfo: could not find module coredev
ERROR: modinfo: could not find module ib_srpt

[QUADStor Support]

On Thu, Jan 23, 2014 at 1:37 PM, Bandlow <karsten...@gmail.com> wrote:
> I am using CentOS 6.5 x64 and the newest Quadstor rpms
>
> There is no FCSCBRIDGE anywhere. Where should i find this device? lsscsi?

That would be the first device presented to a host (LUN 0). VDisks
appear on LUN 1, LUN 2 etc. Would a rescan of the HBA from ESXi show
this ?

How is the connection between the ESXi host and the quadstor FC ports
(switched, point-to-point etc) ?

Check if there are any fcconfig rules you have added which may prevent
detection of the VDisks. If you are not sure what fcconfig is, then no
problem, you haven't done any LUN access control at the VDisk level

Please send the following directly to us at sup...@quadstor.com

1. From the HTML GUI "System" -> "Run Diagnostics" please click on
submit and send us the tar/gzip file

2. Also the /var/log/messages file from the quadstor machine

3. The /var/log/vmkernel.og and /var/log/vmkwarning.log from the ESXi machine.

> on builditf I get following error, maybe this is the cause
>
> ERROR: modinfo: could not find module iscsit
> ERROR: modinfo: could not find module ldev
> ERROR: modinfo: could not find module coredev
> ERROR: modinfo: could not find module ib_srpt

These warnings are ok. After installing the new qla2xxx driver we
recreate the initrd image. At that time the script searches for all
modules currently loaded and the above modules aren't in the standard
path, hence the warning.

[Carlos Rodrigues]

Hi to all,

Your issue resolved?

I have the same problem.

I have a server with Quadstor v3.1.76 and the iSCSI components his working fine, with a vdisk volume presented to 3 ESXi Hosts.

I wanted to test the fiber channel component.

Quadstor server have HBA from Emulex and ESXi Hosts QLogic.

All devices are connected to a FC switch.

I configure the fcconfig with a all allow to the vdisk.

From ESXi Hosts side the HBAs is link-up but no volumes.

[QUADStor Support]

On Tue, May 5, 2015 at 4:19 PM, Carlos Rodrigues
<carlos.f.v....@gmail.com> wrote:
> Hi to all,
>
> Your issue resolved?
> I have the same problem.
>
> I have a server with Quadstor v3.1.76 and the iSCSI components his working
> fine, with a vdisk volume presented to 3 ESXi Hosts.
>
> I wanted to test the fiber channel component.
>
> Quadstor server have HBA from Emulex and ESXi Hosts QLogic.
> All devices are connected to a FC switch.

You will need QLogic cards on the quadstor server as well. Emulex
isn't supported.

>
> I configure the fcconfig with a all allow to the vdisk.
>
> From ESXi Hosts side the HBAs is link-up but no volumes.
>

> --
> You received this message because you are subscribed to the Google Groups
> "QUADStor Storage Virtualization" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to quadstor-vir...@googlegroups.com.

> For more options, visit https://groups.google.com/d/optout.



--
Storage Virtualization Features
http://www.quadstor.com/storage-virtualization.html
Offloaded Data Transfers (ODX) Introduction
http://www.quadstor.com/offloaded-data-transfers-odx.html
vStorage APIs for Array Integration (VAAI)
http://www.quadstor.com/vstorage-apis-for-array-integration-vaai.html
Documentation http://www.quadstor.com/storage-virtualization-documentation.html

[Carlos Rodrigues]

Hello quadstor,

After change the HBAs from Emulex to QLogic, the FC in now working!

Thanks for the tip! :)

Regards,

[Dmitry Polezhaev]

Sorry for the disturbance, as I collected info from other projects, today the QLogic FC adapters are the only, which supporting 'target mode'. Thus, while planing the storage node hardware, it must be equipped with QLogic only, not Emulex, not LSI, not Brocade, not Cisco. Still have no information regarding HP mezzanines, which are QLogic-based hardware, but the microcode, modified by HP ...