VMware Cloud Community
larstr
Champion
Champion

Problems mapping up an MSA2324 san with 4.0u1

Hi,

I'm having a DL380G6 with two Qlogic hbas connected via an HP StorageWorks 8/8 switch.

As far as I can see the firmware versions of the hbas match the one in the HCL.

I'm running ESX 4u1 on the host side and it's setup with MRU paths.

I have a problem seeing the LUNs from the ESX side. When I do a rescan I get the following error messages in the vmkernel:

Nov 30 14:45:07 hk-vmsrv2 vmkernel: 0:03:29:26.869 cpu4:4117)WARNING: vmw_psp_fixed: psp_fixedUnclaimPath: Unable to find a preferred path in ACTIVE/STANDBY state.

Nov 30 14:45:07 hk-vmsrv2 vmkernel: 0:03:29:26.869 cpu4:4117)vmw_psp_mru: psp_mruSelectPathToActivateInt: Changing active path from NONE to vmhba1:C0:T0:L0 for device "naa.600c0ff000d8e3d80000000000000000".

Nov 30 14:45:07 hk-vmsrv2 vmkernel: 0:03:29:26.983 cpu10:4106)NMP: nmp_CompleteCommandForPath: Command 0x12 (0x41000801e940) to NMP device "mpx.vmhba3:C0:T0:L0" failed on physical path "vmhba3:C0:T0:L0" H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

Nov 30 14:45:07 hk-vmsrv2 vmkernel: 0:03:29:26.983 cpu10:4106)ScsiDeviceIO: 747: Command 0x12 to device "mpx.vmhba3:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

Nov 30 14:45:56 hk-vmsrv2 vmkernel: 0:03:30:15.689 cpu2:4119)ScsiScan: 843: Path 'vmhba2:C0:T1:L0': Vendor: 'HP ' Model: 'MSA2324fc ' Rev: 'M110'

Nov 30 14:45:56 hk-vmsrv2 vmkernel: 0:03:30:15.689 cpu2:4119)ScsiScan: 846: Path 'vmhba2:C0:T1:L0': Type: 0xd, ANSI rev: 5, TPGS: 1 (implicit only)

Nov 30 14:45:56 hk-vmsrv2 vmkernel: 0:03:30:15.689 cpu2:4119)ScsiScan: 843: Path 'vmhba2:C0:T0:L0': Vendor: 'HP ' Model: 'MSA2324fc ' Rev: 'M110'

Nov 30 14:45:56 hk-vmsrv2 vmkernel: 0:03:30:15.689 cpu2:4119)ScsiScan: 846: Path 'vmhba2:C0:T0:L0': Type: 0xd, ANSI rev: 5, TPGS: 1 (implicit only)

Nov 30 14:45:56 hk-vmsrv2 vmkernel: 0:03:30:15.815 cpu10:4106)NMP: nmp_CompleteCommandForPath: Command 0x12 (0x410008034440) to NMP device "mpx.vmhba3:C0:T0:L0" failed on physical path "vmhba3:C0:T0:L0" H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

Nov 30 14:45:56 hk-vmsrv2 vmkernel: 0:03:30:15.815 cpu10:4106)ScsiDeviceIO: 747: Command 0x12 to device "mpx.vmhba3:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

Nov 30 14:45:56 hk-vmsrv2 vmkernel: 0:03:30:15.840 cpu8:4118)Vol3: 1488: Could not open device '4b139753-65ed976e-b3f2-0025b3dea3fc' for probing: No such target on adapter

Nov 30 14:45:56 hk-vmsrv2 vmkernel: 0:03:30:15.840 cpu8:4118)Vol3: 608: Could not open device '4b139753-65ed976e-b3f2-0025b3dea3fc' for volume open: No such target on adapter

Nov 30 14:45:56 hk-vmsrv2 vmkernel: 0:03:30:15.840 cpu8:4118)FSS: 3702: No FS driver claimed device '4b139753-65ed976e-b3f2-0025b3dea3fc': Not supported

Nov 30 14:45:58 hk-vmsrv2 vmkernel: 0:03:30:17.309 cpu2:4119)ScsiScan: 843: Path 'vmhba1:C0:T1:L0': Vendor: 'HP ' Model: 'MSA2324fc ' Rev: 'M110'

Nov 30 14:45:58 hk-vmsrv2 vmkernel: 0:03:30:17.309 cpu2:4119)ScsiScan: 846: Path 'vmhba1:C0:T1:L0': Type: 0xd, ANSI rev: 5, TPGS: 1 (implicit only)

Nov 30 14:45:58 hk-vmsrv2 vmkernel: 0:03:30:17.310 cpu2:4119)ScsiScan: 843: Path 'vmhba1:C0:T0:L0': Vendor: 'HP ' Model: 'MSA2324fc ' Rev: 'M110'

Nov 30 14:45:58 hk-vmsrv2 vmkernel: 0:03:30:17.310 cpu2:4119)ScsiScan: 846: Path 'vmhba1:C0:T0:L0': Type: 0xd, ANSI rev: 5, TPGS: 1 (implicit only)

Nov 30 14:45:58 hk-vmsrv2 vmkernel: 0:03:30:17.394 cpu4:4117)Vol3: 1488: Could not open device '4b139753-65ed976e-b3f2-0025b3dea3fc' for probing: No such target on adapter

Nov 30 14:45:58 hk-vmsrv2 vmkernel: 0:03:30:17.394 cpu4:4117)Vol3: 608: Could not open device '4b139753-65ed976e-b3f2-0025b3dea3fc' for volume open: No such target on adapter

Nov 30 14:45:58 hk-vmsrv2 vmkernel: 0:03:30:17.394 cpu4:4117)FSS: 3702: No FS driver claimed device '4b139753-65ed976e-b3f2-0025b3dea3fc': Not supported

Nov 30 14:45:58 hk-vmsrv2 vmkernel: 0:03:30:17.855 cpu10:4106)NMP: nmp_CompleteCommandForPath: Command 0x12 (0x410008069800) to NMP device "mpx.vmhba3:C0:T0:L0" failed on physical path "vmhba3:C0:T0:L0" H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

Nov 30 14:45:58 hk-vmsrv2 vmkernel: 0:03:30:17.855 cpu10:4106)ScsiDeviceIO: 747: Command 0x12 to device "mpx.vmhba3:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

..and here's the HBA info:

root@xx-vmsrv2 scsi--# more qla2xxx/5

QLogic PCI to Fibre Channel Host Adapter for HPAK344A:

Firmware version 4.04.09 , Driver version 8.02.01-k1-vmw43

BIOS version 2.02

FCODE version 2.00

EFI version 2.01

Flash FW version 4.03.02

ISP: ISP2532

Request Queue = 0xdc0cc000, Response Queue = 0xdc14d000

Request Queue count = 4096, Response Queue count = 512

Total number of interrupts = 2191

Device queue depth = 0x20

Number of free request entries = 3705

Number of mailbox timeouts = 0

Number of ISP aborts = 0

Number of loop resyncs = 1

Host adapter:loop state = <READY>, flags = 0x105ac3

Dpc flags = 0x0

MBX flags = 0x0

Link down Timeout = 008

Port down retry = 005

Login retry count = 008

Execution throttle = 2048

ZIO mode = 0x6, ZIO timer = 1

Commands retried with dropped frame(s) = 0

Product ID = 0000 0000 0000 0000

NPIV Supported : Yes

Max Virtual Ports = 255

SCSI Device Information:

scsi-qla1-adapter-node=50014380029cb6bd:150200:0;

scsi-qla1-adapter-port=50014380029cb6bc:150200:0;

FC Target-Port List:

scsi-qla1-target-0=217000c0ffd8bfb5;

scsi-qla1-target-1=257000c0ffd8bfb5;

FC Port Information:

scsi-qla1-port-0=208000c0ffd8bfb5:217000c0ffd8bfb5:150000:81;

scsi-qla1-port-1=208000c0ffd8bfb5:257000c0ffd8bfb5:150100:82;

Any idea what could be wrong?

Lars

Reply
0 Kudos
2 Replies
binoche
VMware Employee
VMware Employee

how many luns from MSA2324 mapped to the host?

vmkernel messages show only L0 (lun 0) scanned out, could you please re-check,

1, lun 0 has been mapped or not?

2, if no lun 0 mapped, how MSA2324 should be configured to present such as lun 1 2 3... to the host?

binoche, VMware VCP, Cisco CCNA

larstr
Champion
Champion

Thanks a lot for your feedback. I had the SAN guy to look at this setup again and he found a mismatch in the WWNs that where setup at the SAN/switches. Now everything is working as expected.

Lars

Reply
0 Kudos