iSCSI connection error

[NYSDHCR]

We used to have an iSCSI connection to one of our SANs from an ESX host (Dell PE 6850). I have since deleted the iSCSI LUN, deleted the iSCSI Initiators, and any reference to the iSCSI connection. I am still seing the following error messages in the vmkernel log files:

Dec 27 16:02:48 albvm8 vmkernel: 62:21:07:13.206 cpu7:1064)iSCSI: bus 0 target 1 trying to establish session 0x3e94fc88 to portal 1, address 10.66.144.18 port 3260 group 1002

Dec 27 16:02:48 albvm8 vmkernel: 62:21:07:13.206 cpu7:1064)iSCSI: session 0x3e94fc88 to iqn.1992-08.com.netapp:sn.101172514 failed to connect, rc -5, I/O error

Dec 27 16:02:48 albvm8 vmkernel: 62:21:07:13.206 cpu7:1064)iSCSI: session 0x3e94fc88 connect failed at 543283328

Dec 27 16:02:48 albvm8 vmkernel: 62:21:07:13.206 cpu7:1064)<5>iSCSI: session 0x3e94fc88 iSCSI: session 0x3e94fc88 retrying all the portals again, since the portal list got exhausted

Dec 27 16:02:48 albvm8 vmkernel: 62:21:07:13.206 cpu7:1064)iSCSI: session 0x3e94fc88 to iqn.1992-08.com.netapp:sn.101172514 waiting 60 seconds before next login attempt

Dec 27 16:03:48 albvm8 vmkernel: 62:21:08:13.206 cpu7:1064)iSCSI: bus 0 target 1 trying to establish session 0x3e94fc88 to portal 0, address 10.66.144.19 port 3260 group 1003

Dec 27 16:03:48 albvm8 vmkernel: 62:21:08:13.206 cpu7:1064)iSCSI: session 0x3e94fc88 to iqn.1992-08.com.netapp:sn.101172514 failed to connect, rc -5, I/O error

Dec 27 16:03:48 albvm8 vmkernel: 62:21:08:13.206 cpu7:1064)iSCSI: session 0x3e94fc88 connect failed at 543289328

Dec 27 16:03:48 albvm8 vmkernel: 62:21:08:13.206 cpu7:1064)iSCSI: session 0x3e94fc88 to iqn.1992-08.com.netapp:sn.101172514 waiting 60 seconds before next login attempt

Any idea how to kill this?

[ctfoster]

Does esxcfg-mpath -list command show any active paths to the 'deleted' host ?

[NYSDHCR]

I had sent an SR to VMware and they responded with the following:

"On the ESX host, please look in the /var/lib/iscsi/ directory for files with a list of hostnames or IP addresses. If they exist, remove the old entries from both of these files:

/var/lib/iscsi/vmkbindings

/var/lib/iscsi/vmkdiscovery

Then rescan the adaptor from VC or the VI client. If the problem persists, check the above files to see if the old entries came back." I also had to uncheck the iSCSI software client under the host Configuration > SecurityProfile tab.

[ctfoster]

Glad its sorted. Sounds like something didn't get cleaned up like it should !

[NYSDHCR]

Me too. By the quickness of VMware's response, it must have happened to others as well.