arzucore
Contributor
Contributor

ESXi doesn't see LUNs - iSCSI

Jump to solution

Greetings!

We have connected a vCenter 6.7 U1 with 3 ESXi hosts (6.7 U1) and a shared storage (VMFS5) via iSCSI. We want to replace 2 hosts. Now we replaced one host and wanted to connect it to the storage via iSCSI. The new host also finds the storage device, but does not mount the two existing LUNs. The settings are completely identical to the two old hosts still in operation. Here the vmkernel.log after the rescan:

2019-02-27T08:39:05.035Z cpu25:2098143)WARNING: iscsi_vmk: iscsivmk_ConnCommandResponse:2840: Conn [CID: 0 L: 192.168.168.162:36120 R: 192.168.168.121:3260]

2019-02-27T08:39:05.035Z cpu25:2098143)WARNING: iscsi_vmk: iscsivmk_ConnCommandResponse:2838: iSCSI command failed to complete: Invalid

2019-02-27T08:39:05.035Z cpu25:2098143)WARNING: iscsi_vmk: iscsivmk_ConnCommandResponse:2839: Sess [ISID: 00023d000002 TARGET: iqn.1992-05.com.emc:ckm001212009220000-5-vnxe TPGT: 1 TSIH: 0]

2019-02-27T08:39:05.035Z cpu25:2098143)WARNING: iscsi_vmk: iscsivmk_ConnCommandResponse:2840: Conn [CID: 0 L: 192.168.168.162:36120 R: 192.168.168.121:3260]

2019-02-27T08:47:06.061Z cpu22:2098124)ScsiDeviceIO: 3068: Cmd(0x45a240be0080) 0x1a, CmdSN 0x256a from world 0 to dev "naa.6003005711c4c35023ad0ec708733569" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

Can anyone help me out?

Thank you!

0 Kudos
1 Solution

Accepted Solutions
arzucore
Contributor
Contributor

Problem solved!

This article helpded me out: VMware Knowledge Base . I deleted vmkernel-ports and created they new.Now it's working.

View solution in original post

0 Kudos
4 Replies
arzucore
Contributor
Contributor

I tried vmkping and that's strange:

vmkping -s 8784 192.168.168.121

PING 192.168.168.121 (192.168.168.121): 8784 data bytes

--- 192.168.168.121 ping statistics ---

3 packets transmitted, 0 packets received, 100% packet loss

and:

vmkping -s 8784 -d 192.168.168.121

PING 192.168.168.121 (192.168.168.121): 8784 data bytes

sendto() failed (Message too long)

sendto() failed (Message too long)

sendto() failed (Message too long)

--- 192.168.168.121 ping statistics ---

3 packets transmitted, 0 packets received, 100% packet loss

and:

nc -z 192.168.168.121 3260

Connection to 192.168.168.121 3260 port [tcp/*] succeeded!

In vCenter I can see the Storage but not the LUNs. They are shown as "Datastore Not Consumed".

That's strange because vmKernel-Ports and vSwitch MTU is definitely set to 9000. Physical Switch and Storage is set to 9000 too. The other 2 Hosts are working with same settings.

Someone an idea?

0 Kudos
dskwared
VMware Employee
VMware Employee

Are you sure the -s (packet size) parameter in the vmkping command is set correctly? See this VMware Knowledge Base (KB 1003728) where -s should be set to 8972 for jumbo frames.

0 Kudos
arzucore
Contributor
Contributor

I've tried it with 8972 too, but same results 😞

I will try this: VMware Knowledge Base , but it seems thats for 5.5 only.

0 Kudos
arzucore
Contributor
Contributor

Problem solved!

This article helpded me out: VMware Knowledge Base . I deleted vmkernel-ports and created they new.Now it's working.

View solution in original post

0 Kudos