VMware Cloud Community
TryllZ
Expert
Expert
Jump to solution

esxi server fails to connect to iSCSI on a different network / can ping..

Hi,

I have a lab setup on workstation where I have 2 clusters: Mgmt_Compute and Mgmt_Infrastructure.

Mgmt_Compute is on 192.168.105.0/24 network and has esxicomp1 and esxicomp2 esxi servers.

Mgmt_Infrastructure is on 192.168.100.0/24 network and has esxi1, esxi2, and esxi3 esxi servers.

A Firewall is configured and all devices can ping each other, and can be seen below device device esxicomp2 can ping its own gateway 192.168.105.3, and the DNS server 192.168.100.10 which is also the iSCSI storage server.

esxicomp2-2020-04-27-22-12-22.png

However when I configure iSCSI through vCenter the esxicomp1 and esxicomp2 do not connect to the iSCSI storage as can be seen below.

server-2020-04-27-22-13-13.png

server-2020-04-27-22-12-45.png

esxi1 showing as connected.

server-2020-04-27-22-12-37.png

Any specific reason for this or am I missing something.

And if it matters I have 1 DVSwitch with 1 Uplink and 2 portgroups, MgmtA which has esxi1, 2, and 3, and MgmtB which has esxicomp1 and esxicomp2.

Thanks..

1 Solution

Accepted Solutions
TryllZ
Expert
Expert
Jump to solution

Apologies for the delayed reply, got caught in work.

The issue was the port binding, the esxicomp1 did not have its port binding done.

After the port binding the iSCSI disk is now showing connected.

Thanks a lot, appreciate everyone's time.

View solution in original post

0 Kudos
12 Replies
IRIX201110141
Champion
Champion
Jump to solution

  1. If you wanna ping than use vmkping from command line and think about MTU and selecting the right outgoing VMK/NIC as well
  2. Some storages have a protection that only the first host can connecting unless you tick the box for multiple host connections
  3. Storage ACL needs to cover both Hosts
  4. Investigate  vmkernel.log instead looking the the GUI where nothing is shown

Regards,
Joerg

scott28tt
VMware Employee
VMware Employee
Jump to solution

Moderator: Thread moved to the vSphere area, your issue is not specific to vCenter Server.


-------------------------------------------------------------------------------------------------------------------------------------------------------------

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
0 Kudos
TryllZ
Expert
Expert
Jump to solution

Hi Joerg,

Thanks for pointing out all those out.

I have done a vmkping from the esxi and they result in success.

[root@esxicomp2:~] vmkping 192.168.100.10

PING 192.168.100.10 (192.168.100.10): 56 data bytes

64 bytes from 192.168.100.10: icmp_seq=0 ttl=127 time=0.851 ms

64 bytes from 192.168.100.10: icmp_seq=1 ttl=127 time=1.447 ms

64 bytes from 192.168.100.10: icmp_seq=2 ttl=127 time=2.032 ms

--- 192.168.100.10 ping statistics ---

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

round-trip min/avg/max = 0.851/1.443/2.032 ms

As for points 2 and 3 I'll go through the settings of the iSCSI, and will go through the vmkernel.log as well.

Thanks again.

0 Kudos
TryllZ
Expert
Expert
Jump to solution

So I went through the logs and there is only 1 mentioning of the iSCSI adapter (highlighted in red below), nothing else.

2020-04-26T18:43:51.091Z cpu0:2099189)Boot Successful

2020-04-26T18:43:51.415Z cpu0:2099201)Starting up rc scripts

2020-04-26T18:46:32.899Z cpu1:2097576)NMP: nmp_ResetDeviceLogThrottling:3580: Error status H:0x0 D:0x2 P:0x0 Sense Data: 0x5 0x20 0x0 from dev "mpx.vmhba0:C0:T0:L0" occurred 1 times(of 1 commands)

2020-04-26T18:48:02.905Z cpu0:2097173)ScsiDeviceIO: 3435: Cmd(0x459a425b44c0) 0x1a, CmdSN 0x33e from world 0 to dev "mpx.vmhba64:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2020-04-26T18:50:07.980Z cpu0:2097541)NRandom: 545: Entropy INTR health check passed

2020-04-26T18:50:40.182Z cpu0:2097540)NRandom: 811: random: nonblocking pool is initialized

2020-04-26T18:53:02.900Z cpu0:2097627)DVFilter: 5963: Checking disconnected filters for timeouts

2020-04-26T18:55:16.640Z cpu1:2099233)Tcpip: 1160: gateway = 0x369a8c0

2020-04-26T18:55:16.650Z cpu1:2099233)Config: 862: "HostName" = "esxicomp1.v.lab", Old value: "esxicomp1" (Status: 0x0)

2020-04-26T18:56:14.011Z cpu1:2099233)Tcpip: 1160: gateway = 0x369a8c0

2020-04-26T19:03:02.900Z cpu0:2097627)DVFilter: 5963: Checking disconnected filters for timeouts

2020-04-26T19:11:23.513Z cpu0:2099657)WARNING: NTPClock: 1561: system clock synchronized to upstream time servers

2020-04-26T19:12:02.188Z cpu0:2099717)WARNING: VisorFS: 1093: Attempt to setattr non sticky dir/file from tar mount

2020-04-26T19:14:23.910Z cpu0:2097627)DVFilter: 5963: Checking disconnected filters for timeouts

2020-04-26T19:17:53.910Z cpu0:2097576)NMP: nmp_ResetDeviceLogThrottling:3580: Error status H:0x0 D:0x2 P:0x0 Sense Data: 0x5 0x20 0x0 from dev "mpx.vmhba0:C0:T0:L0" occurred 1 times(of 1 commands)

2020-04-26T19:24:23.910Z cpu0:2097627)DVFilter: 5963: Checking disconnected filters for timeouts

2020-04-26T19:34:23.910Z cpu0:2097627)DVFilter: 5963: Checking disconnected filters for timeouts

2020-04-26T19:44:23.910Z cpu0:2097627)DVFilter: 5963: Checking disconnected filters for timeouts

2020-04-26T20:43:07.790Z cpu0:2097576)NMP: nmp_ResetDeviceLogThrottling:3580: Error status H:0x0 D:0x2 P:0x0 Sense Data: 0x5 0x20 0x0 from dev "mpx.vmhba0:C0:T0:L0" occurred 1 times(of 1 commands)

2020-04-28T06:20:39.204Z cpu0:2097627)DVFilter: 5963: Checking disconnected filters for timeouts

2020-04-28T06:26:21.252Z cpu0:2098486 opID=c8dba517)World: 11943: VC opID 6c9025ca-39-d259 maps to vmkernel opID c8dba517

2020-04-28T06:26:21.252Z cpu0:2098486 opID=c8dba517)NetPortset: 1959: Activating portset #3 as DvsPortset-0 (cswitch) with 2560 ports, index mask is 0xfff status Success

2020-04-28T06:26:21.274Z cpu0:2098486 opID=c8dba517)NetPort: 1359: enabled port 0x3000001 with mac 00:00:00:00:00:00

2020-04-28T06:26:21.282Z cpu0:2098486 opID=c8dba517)netioc: NetIOCSwitchActivate:770: Successfully activate the NetIOC for portset: DvsPortset-0

2020-04-28T06:26:21.283Z cpu1:2097566)CpuSched: 699: user latency of 2100871 VSwitchAgingWorld 0 changed by 2097566 vswitchHelper -6

2020-04-28T06:26:21.283Z cpu0:2098486 opID=c8dba517)NetDVS: 7765: DVSwitch 50 0d 4c bd 49 54 dd 6e-a9 d9 40 0b 8b df 69 c3 invalid opaqueDvs value: [false]

2020-04-28T06:26:21.283Z cpu0:2098486 opID=c8dba517)NetDVS: 7783: Associated DVS 50 0d 4c bd 49 54 dd 6e-a9 d9 40 0b 8b df 69 c3 with proxy DvsPortset-0

2020-04-28T06:26:21.283Z cpu1:2097566)cswitch: VSwitchCreateAgingWorld:318: [nsx@6876 comp="nsx-esx" subcomp="vswitch"]Created aging timer world for vswitch DvsPortset-0

2020-04-28T06:26:21.296Z cpu0:2098486 opID=c8dba517)CDP: CdpEnableListen:3690: listening  on DvsPortset-0

2020-04-28T06:26:21.298Z cpu0:2098486 opID=c8dba517)VMKAPIMOD: 86: Failed to  check if port is Uplink : Failure

2020-04-28T06:26:21.348Z cpu0:2098486 opID=c8dba517)netioc: NetIOCSetRespoolVersion:246: Set netioc version for portset: DvsPortset-0 to 2,old version: 2

2020-04-28T06:26:21.352Z cpu0:2098486 opID=c8dba517)netioc: NetIOCPortsetNetSchedStatusSet:1209: Set sched status for portset: DvsPortset-0 to Inactive, old:Inactive

2020-04-28T06:26:21.353Z cpu0:2098486 opID=c8dba517)VLANMTUCheck: NMVCDeployClear:989: can't not find psReq for ps DvsPortset-0 via VSPHERE_CONTROL_PATH

2020-04-28T06:26:25.346Z cpu0:2098485 opID=a4230a68)World: 11943: VC opID 6d270063-6d-d27a maps to vmkernel opID a4230a68

2020-04-28T06:26:25.346Z cpu0:2098485 opID=a4230a68)NetPort: 1580: disabled port 0x2000002

2020-04-28T06:26:25.348Z cpu1:2097691)NetSched: 654: vmnic0-0-tx: worldID = 2097691 exits

2020-04-28T06:26:25.355Z cpu0:2098485 opID=a4230a68)Uplink: 11689: enabled port 0x3 with mac 00:0c:29:62:a6:80

2020-04-28T06:26:25.355Z cpu1:2097266)CpuSched: 699: user latency of 2100883 vmnic0-0-tx 0 changed by 2097266 NetSchedHelper -6

2020-04-28T06:26:25.358Z cpu1:2097599)NetPort: 1580: disabled port 0x2000003

2020-04-28T06:26:25.455Z cpu1:2098485 opID=a4230a68)Config: 862: "ManagementIface" = "", Old value: "vmk0" (Status: 0x0)

2020-04-28T06:26:25.456Z cpu1:2098485 opID=a4230a68)Tcpip_Vmk: 1286: TcpipDisablePort: current vnet 0x430974894f30 for nd 0x43097490cec0 portID: 0x2000004

2020-04-28T06:26:25.457Z cpu1:2098485 opID=a4230a68)Tcpip_Vmk: 1093: vmknic Rx dispatch stats: portID: 0x2000004, RxQ: 0, rxPkt: 7073, dispPkt: 7003

2020-04-28T06:26:25.458Z cpu1:2098485 opID=a4230a68)Tcpip_Vmk: 124: rn_delete: return NULL after checking rn_dupedkey

2020-04-28T06:26:25.458Z cpu1:2098485 opID=a4230a68)Tcpip_Vmk: 124: rn_delete: return NULL after checking rn_dupedkey

2020-04-28T06:26:25.461Z cpu1:2098485 opID=a4230a68)Tcpip_Vmk: 1352: TcpipClosePort: current vnet 0x430974894f30 for nd 0x43097490cec0 portID: 0x2000004

2020-04-28T06:26:25.461Z cpu1:2098485 opID=a4230a68)NetPort: 1580: disabled port 0x2000004

2020-04-28T06:26:25.462Z cpu1:2098485 opID=a4230a68)Net: 3712: disconnected client from port 0x2000004

2020-04-28T06:26:25.462Z cpu1:2098485 opID=a4230a68)Tcpip_Vmk: 927: TcpipFreePort: current vnet 0x430974894f30 for nd 0x43097490cec0 portID: 0x0

2020-04-28T06:26:25.474Z cpu1:2098485 opID=a4230a68)Net: 2456: connected vmk0  to vDS, portID 0x3000002

2020-04-28T06:26:25.474Z cpu1:2098485 opID=a4230a68)Net: 3148: associated dvPort 51 with portID 0x3000002

2020-04-28T06:26:25.474Z cpu1:2098485 opID=a4230a68)CpuSched: 699: user latency of 2100884 vmk0-rx-0 0 changed by 2098485 hostd-worker -6

2020-04-28T06:26:25.475Z cpu1:2098485 opID=a4230a68)CpuSched: 699: user latency of 2100885 vmk0-tx 0 changed by 2098485 hostd-worker -6

2020-04-28T06:26:25.475Z cpu1:2098485 opID=a4230a68)Tcpip_Vmk: 1610: mcast[0] = 33:33:ff:62:a6:80

2020-04-28T06:26:25.475Z cpu1:2098485 opID=a4230a68)Tcpip_Vmk: 1610: mcast[1] = 33:33:00:00:00:01

2020-04-28T06:26:25.475Z cpu1:2098485 opID=a4230a68)Tcpip: 1211: NIC supports Tso

2020-04-28T06:26:25.475Z cpu1:2098485 opID=a4230a68)Tcpip: 1218: NIC support IPv4 TX checksum offloading

2020-04-28T06:26:25.475Z cpu1:2098485 opID=a4230a68)Tcpip: 1225: NIC support IPv6 TX checksum offloading

2020-04-28T06:26:25.475Z cpu1:2098485 opID=a4230a68)Tcpip: 1231: NIC supports Scatter-Gather transmits

2020-04-28T06:26:25.475Z cpu1:2098485 opID=a4230a68)Tcpip_Vmk: 124: vmk0:

2020-04-28T06:26:25.475Z cpu1:2098485 opID=a4230a68)Tcpip_Vmk: 124: Ethernet address: 00:0c:29:62:a6:80

2020-04-28T06:26:25.475Z cpu1:2098485 opID=a4230a68)Tcpip: 1286: ether attach complete vmk 0 0

2020-04-28T06:26:25.477Z cpu1:2098485 opID=a4230a68)Tcpip_Vmk: 124: rn_delete: return NULL after checking rn_dupedkey

2020-04-28T06:26:25.477Z cpu1:2098485 opID=a4230a68)NetPort: 2680: resuming traffic on DV port 51

2020-04-28T06:26:25.477Z cpu1:2098485 opID=a4230a68)NetPort: 1359: enabled port 0x3000002 with mac 00:0c:29:62:a6:80

2020-04-28T06:26:25.485Z cpu1:2098485 opID=a4230a68)Tcpip: 1088: ip_addr = 0x1469a8c0, netmask = 0xffffff

2020-04-28T06:26:25.487Z cpu1:2098485 opID=a4230a68)Tcpip: 1160: gateway = 0x369a8c0

2020-04-28T06:26:25.487Z cpu1:2098485 opID=a4230a68)Config: 862: "ManagementIface" = "vmk0", Old value: "" (Status: 0x0)

2020-04-28T06:26:25.496Z cpu1:2098485 opID=a4230a68)Tcpip_Vmk: 124: rn_delete: return NULL after checking rn_dupedkey

2020-04-28T06:26:25.564Z cpu1:2097202)nvmxnet3: Nvmxnet3ActivateDev:1871: [vmnic0] pktSize 1622, rxBufPerPkt 1, ring sizes [2048 1024 1024]

2020-04-28T06:26:25.618Z cpu1:2097202)nvmxnet3: Nvmxnet3RqAllocRxBuf:677: [vmnic0] Rq[0] ring[0] allocRxBuf: 1024 allocated, next2fill 1023, next2comp 0

2020-04-28T06:26:25.618Z cpu1:2097202)nvmxnet3: Nvmxnet3RqAllocRxBuf:677: [vmnic0] Rq[0] ring[1] allocRxBuf: 1024 allocated, next2fill 1023, next2comp 0

2020-04-28T06:26:25.622Z cpu1:2097202)nvmxnet3: Nvmxnet3CheckLink:1244: [vmnic0] NIC Link is Up 10000 Mbps

2020-04-28T06:26:25.622Z cpu1:2097202)nvmxnet3: Nvmxnet3UplinkMTUSet:151: [vmnic0] MTU changed to 1600

2020-04-28T06:26:25.651Z cpu0:2098485 opID=a4230a68)NetPort: 1580: disabled port 0x3

2020-04-28T06:26:25.651Z cpu1:2100883)NetSched: 654: vmnic0-0-tx: worldID = 2100883 exits

2020-04-28T06:26:25.651Z cpu0:2098485 opID=a4230a68)NetPort: 2680: resuming traffic on DV port 35

2020-04-28T06:26:25.651Z cpu0:2098485 opID=a4230a68)cswitch: L2Sec_EnforcePortCompliance:174: [nsx@6876 comp="nsx-esx" subcomp="vswitch"]FRP is not yet set on port 3000003

2020-04-28T06:26:25.651Z cpu1:2097266)CpuSched: 699: user latency of 2100886 vmnic0-0-tx 0 changed by 2097266 NetSchedHelper -6

2020-04-28T06:26:25.651Z cpu0:2098485 opID=a4230a68)Uplink: 11689: enabled port 0x3000003 with mac 00:0c:29:62:a6:80

2020-04-28T06:26:25.652Z cpu0:2097599)Net: 2456: connected Shadow of vmnic0  to null config, portID 0x3000004

2020-04-28T06:26:25.652Z cpu0:2097599)Mirror.cswitch: VSwitchMirrorPortEnable:2697: [nsx@6876 comp="nsx-esx" subcomp="vswitch"]Failed to get port 3000004 linkup flag

2020-04-28T06:26:25.652Z cpu0:2097599)NetPort: 1359: enabled port 0x3000004 with mac 00:50:56:5f:9c:84

2020-04-28T06:26:30.197Z cpu0:2097202)NetqueueBal: 4970: vmnic0: new netq module, reset logical space needed

2020-04-28T06:26:30.197Z cpu0:2097202)NetqueueBal: 4999: vmnic0: plugins to call differs, reset logical space

2020-04-28T06:26:30.197Z cpu0:2097202)Uplink: 537: Driver claims supporting 0 RX queues, and 0 queues are accepted.

2020-04-28T06:26:30.197Z cpu0:2097202)Uplink: 533: Driver claims supporting 0 TX queues, and 0 queues are accepted.

2020-04-28T06:26:30.198Z cpu0:2097202)NetPort: 1580: disabled port 0x3000003

2020-04-28T06:26:30.198Z cpu0:2097202)NetPort: 2680: resuming traffic on DV port 35

2020-04-28T06:26:30.198Z cpu0:2097202)Uplink: 11689: enabled port 0x3000003 with mac 00:0c:29:62:a6:80

2020-04-28T06:26:30.198Z cpu1:2100886)NetSched: 654: vmnic0-0-tx: worldID = 2100886 exits

2020-04-28T06:26:30.198Z cpu1:2097266)CpuSched: 699: user latency of 2101009 vmnic0-0-tx 0 changed by 2097266 NetSchedHelper -6

2020-04-28T06:26:38.879Z cpu1:2100891 opID=a3603c8c)World: 11943: VC opID HB-SpecSync-host-40@0-15246702-b7-d2a1 maps to vmkernel opID a3603c8c

2020-04-28T06:26:38.879Z cpu1:2100891 opID=a3603c8c)Config: 703: "HostLocalSwapDirEnabled" = 0, Old Value: 0, (Status: 0x0)

2020-04-28T06:26:55.467Z cpu1:2097616)Tcpip: 1473: Cleaning 2 Leaked routes on 'vmk0'

2020-04-28T06:26:55.467Z cpu1:2097616)Tcpip: 1480: Freeing interface 'vmk0'

2020-04-28T06:26:59.354Z cpu1:2099037 opID=d94ab854)World: 11943: VC opID 5e8f53ad-ce-d2b6 maps to vmkernel opID d94ab854

2020-04-28T06:26:59.354Z cpu1:2099037 opID=d94ab854)CDP: CdpDisableListen:3728: disabling listening on vSwitch0

2020-04-28T06:26:59.362Z cpu0:2099037 opID=d94ab854)NetPortset: 1697: De activating portset vSwitch0 status Success

2020-04-28T06:26:59.362Z cpu0:2099037 opID=d94ab854)NetPort: 1580: disabled port 0x2000001

2020-04-28T06:28:14.580Z cpu0:2098523 opID=93b8da9)World: 11943: VC opID k9hg3i1l-1508-auto-15x-h5:70000848-af-d7-d2c7 maps to vmkernel opID 93b8da9

2020-04-28T06:28:14.580Z cpu0:2098523 opID=93b8da9)Device: 1466: Registered device: 0x43048fb7b070 logical#swdevroot#com.vmware.iscsi_vmk0 com.vmware.iscsi_vmk (parent=0x2e9d43048fb7b32b)

2020-04-28T06:28:14.687Z cpu0:2101074)Loading module iscsi_vmk ...

2020-04-28T06:28:14.704Z cpu0:2101074)Elf: 2101: module iscsi_vmk has license VMware

2020-04-28T06:28:14.756Z cpu0:2101074)Device: 192: Registered driver 'iscsi_vmk' from 97

2020-04-28T06:28:14.756Z cpu0:2101074)CpuSched: 699: user latency of 2101075 iscsi-rx-world-0 0 changed by 2101074 vmkeventd -6

2020-04-28T06:28:14.756Z cpu0:2101074)CpuSched: 699: user latency of 2101076 iscsi-rx-world-1 0 changed by 2101074 vmkeventd -6

2020-04-28T06:28:14.757Z cpu0:2101074)CpuSched: 699: user latency of 2101077 iscsi-tx-world-0 0 changed by 2101074 vmkeventd -6

2020-04-28T06:28:14.757Z cpu0:2101074)CpuSched: 699: user latency of 2101078 iscsi-tx-world-1 0 changed by 2101074 vmkeventd -6

2020-04-28T06:28:14.757Z cpu0:2101074)Mod: 4962: Initialization of iscsi_vmk succeeded with module ID 97.

2020-04-28T06:28:14.757Z cpu0:2101074)iscsi_vmk loaded successfully.

2020-04-28T06:28:14.779Z cpu1:2097552)PCI: 91: Device 0x89943048fb80b45 is not a PCI vmkDevice

2020-04-28T06:28:14.779Z cpu1:2097552)VMK_PCI: 1532: 0x89943048fb80b45 is not a PCI device.

2020-04-28T06:28:14.779Z cpu1:2097552)DMA: 548: Couldn't get PCI device for props device 'iscsivmkDMAEngine'

2020-04-28T06:28:14.779Z cpu1:2097552)DMA: 679: DMA Engine 'iscsivmkDMAEngine' created using mapper 'DMANull'.

2020-04-28T06:28:14.779Z cpu1:2097552)Device: 327: Found driver iscsi_vmk for device 0x89943048fb80b45

2020-04-28T06:28:14.780Z cpu1:2097552)Device: 1466: Registered device: 0x43048fb7b070 logical#logical#swdevroot#com.vmware.iscsi_vmk0#0 com.vmware.HBAPort (parent=0x89943048fb80b45)

2020-04-28T06:28:14.793Z cpu1:2097552)PCI: 91: Device 0x172c43048fb80df9 is not a PCI vmkDevice

2020-04-28T06:28:14.794Z cpu1:2097552)Device: 327: Found driver psa for device 0x172c43048fb80df9

2020-04-28T06:28:14.807Z cpu0:2097199)ScsiNpiv: 1519: GetInfo for adapter vmhba65, [0x430301bf3000], max_vports=0, vports_inuse=0, linktype=0, state=0, failreason=0, sts=bad0020

2020-04-28T06:28:15.671Z cpu0:2098523 opID=93b8da9)WARNING: VisorFS: 1093: Attempt to setattr non sticky dir/file from tar mount

0 Kudos
berndweyand
Expert
Expert
Jump to solution

do a vmkping with specifying the vmkernel-Port on which you do iscsi: vmkping -I vmkX 192.168.100.10

is the firewall-config correct ? port 3260 open ?

0 Kudos
TryllZ
Expert
Expert
Jump to solution

Hi bewe,

The ping is successful with the vmk0 as it is the only vmk on the esxi server.

[root@esxicomp1:~] vmkping -I vmk0 192.168.100.10

PING 192.168.100.10 (192.168.100.10): 56 data bytes

64 bytes from 192.168.100.10: icmp_seq=0 ttl=127 time=0.855 ms

64 bytes from 192.168.100.10: icmp_seq=1 ttl=127 time=1.595 ms

64 bytes from 192.168.100.10: icmp_seq=2 ttl=127 time=1.645 ms

--- 192.168.100.10 ping statistics ---

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

round-trip min/avg/max = 0.855/1.365/1.645 ms

The firewall config is the same for all networks, no special configuration was done, I still opened port 3260 on the firewall and tried again, did not work.

Thanks..

0 Kudos
berndweyand
Expert
Expert
Jump to solution

Firewall on esxi for Software iSCSI is also open ? iSCSI-discovery setup properly ?

do an vmkiscsi-tool -T vmhba65 on the host and see the output

0 Kudos
TryllZ
Expert
Expert
Jump to solution

Firewall on esxi for iSCSI is open.

server-2020-04-28-09-15-12.png

As for iSCSI-Discovery is set for Dynamic Discovery.

server-2020-04-28-09-18-25.png

While the command has no output.

[root@esxicomp1:~] vmkiscsi-tool -T vmhba65

No active targets.

And just to confirm because iSCSI settings on all servers are same, I just added esxi1 server and it adds iSCSI properly.

[root@esxi1:~] vmkiscsi-tool -T vmhba65

------ Target [iqn.1991-05.com.microsoft:vserver-esxihosts-target] info ------

NAME                              : iqn.1991-05.com.microsoft:vserver-esxihosts-target

ALIAS                             :

DISCOVERY METHOD FLAGS            : 8

SEND TARGETS DISCOVERY SETTABLE   : 0

SEND TARGETS DISCOVERY ENABLED    : 0

Portal 0                          : 192.168.100.10:3260

Portal 1                          : 192.168.105.2:3260

Portal 2                          : 192.168.110.2:3260

-------------------------------------------

Thanks again, appreciate the help..

0 Kudos
berndweyand
Expert
Expert
Jump to solution

what does vmkiscsi-tool -D vmhba65 say ?

but in my opinion you should search the problem at the storage

0 Kudos
TryllZ
Expert
Expert
Jump to solution

For the command I get..

[root@esxicomp1:~] vmkiscsi-tool -D vmhba65

=========Discovery Properties for Adapter vmhba65=========

iSnsDiscoverySettable    : 0

iSnsDiscoveryEnabled     : 0

iSnsDiscoveryMethod      : 0

iSnsHost.ipAddress       : ::

staticDiscoverySettable  : 0

staticDiscoveryEnabled   : 1

sendTargetsDiscoverySettable  : 0

sendTargetsDiscoveryEnabled   : 1

slpDiscoverySettable  : 0

DISCOVERY ADDRESS          : 192.168.100.10

No Static Discovery Targets Found

I'm looking into the storage for any issues..

0 Kudos
berndweyand
Expert
Expert
Jump to solution

you can test from the esxi if the port on the storage server can be reached:

nc -z 192.168.100.10 3260

TryllZ
Expert
Expert
Jump to solution

Apologies for the delayed reply, got caught in work.

The issue was the port binding, the esxicomp1 did not have its port binding done.

After the port binding the iSCSI disk is now showing connected.

Thanks a lot, appreciate everyone's time.

0 Kudos