Host not connecting with one LUN

[shikran]

i have 2 Hosts (VSphere6.0) with Dell equalogic SAN (with 2 iSCSI adapters) where i have configured 4 logical volumes and all were working fine.. yesterday i saw errors on Host 1 events and further checking in details i came to know that one of the volume is not accessible by Host 1, but on Host2 all is working fine. on Host 1 i have also checked the iSCSI targets of both adapters in static discovery and i can see all 4 volumes are listed but when i try to add manually storage on this host, the particular LUN does not exists.  i have also restarted the Host 1 but still facing issue .. any help in this regard is highly appreciated.. thanks ?

[admin]

I hope yellow bricks page would help you to get right solution http://www.yellow-bricks.com/2008/12/11/enableresignature-andor-disallowsnapshotlun/

if you found my answer to be useful, feel free to mark it as Helpful or Correct.

[shikran]

thanks you are referring an old article and this option has been removed and not supported by VMware for ages...

[hussainbte]

Could share the below details

Equalogic model.

out of " esxcfg-mpath -b " from both hosts

output of esxcfg-scsidevs -m" from host 1

[hussainbte]

Just another thing.

output for

esxcli  iscsi session list --adapter=vmhbaxx

[shikran]

dell equallogic PS4210 series

please find the attached file

[hussainbte]

so valappvol is not accessible from host1. naa.64817127c47305005375b5547f4aed54

their is no iscsi session from vmhba33 to the LUN.. and the ISID: 00023d000003 has only one LUN which is the test LUN.

Could you vmkping the target IPs from vmkernel adapters used for vmhba33.. if there are more than 1 and you have done iSCSI port binding please verify that both vmkernel ports active..

share the vmkernel log from host1 if you can

[shikran]

yes valappvol is not accessible from host1..

I can vmkping the target IPs from both vmkernel adapters used for vmhba33 and 34.. I am not using port binding..

vmkernel error log is attached

[hussainbte]

It is recommended to do vmkernel port binding to vmhba33 as you have more than one vmkernel ports..

configure the same and check..

if you can migrate the vms to another host and put this in maintenance it would be good.