VMware Cloud Community
NWP_Tom
Enthusiast
Enthusiast

what is the meaning of these errors in vmkernel log file?

I'm seeing some entries in the vmkernel log file that I'm unclear as to what they are. I'm hoping someone can shed some light on them.

We have a Dell MD3000i iSCSI san connected to a Dell 5424 switch. The san has dual storage controllers setup on 2 different subnets (one port from each storage controller is 192.168.130.x subnet and the other 2 ports are on 192.168.131.x)

Host has 2 pNics attached to Dell 5424 switch. Those two pNics are connected to vSwitch1. VMKernel ip is 192.168.131.x and SC is 192.168.131.x. The VMHBA32 iSCSI adapter has a send targets dynamic discovery address of 192.168.131.101 (ip of one of the storage controller ports).

Why am I seeing session attempts to the ip 192.168.130.101 when there are NO nics, vmkernels, sc's, etc coded to that IP subnet? All subnet masks are 255.255.255.0

Here is the log entries I'm seeing

Nov 10 13:56:09 VMESX1 vmkernel: 0:00:49:18.291 cpu2:1075)iSCSI: bus 0 target 0 trying to establish session 0x35203f90 to portal 0, address 192.168.130.101 port 3260 group 1

Nov 10 13:56:24 VMESX1 vmkernel: 0:00:49:33.290 cpu2:1073)iSCSI: login phase for session 0x35203f90 (rx 1075, tx 1074) timed out at 297330, timeout was set for 297330

Nov 10 13:56:24 VMESX1 vmkernel: 0:00:49:33.290 cpu2:1075)iSCSI: session 0x35203f90 connect timed out at 297330

Nov 10 13:56:24 VMESX1 vmkernel: 0:00:49:33.290 cpu2:1075)<5>iSCSI: session 0x35203f90 iSCSI: session 0x35203f90 retrying all the portals again, since the portal list got exhausted

Nov 10 13:56:24 VMESX1 vmkernel: 0:00:49:33.290 cpu2:1075)iSCSI: session 0x35203f90 to iqn.1984-05.com.dell:powervault.6001ec9000d3058c00000000484852b9 waiting 60 seconds before next login attempt

0 Kudos
1 Reply
Texiwill
Leadership
Leadership

Hello,

Most likely the iSCSI Server is responding with its 'active' IP Address and the system attempts it. When it fails it goes to the other one. That would be the only reason for this I can see. I would contact Dell and have them explain the behavior or help you to fix it.


Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

SearchVMware Blog: http://itknowledgeexchange.techtarget.com/virtualization-pro/

Blue Gears Blogs - http://www.itworld.com/ and http://www.networkworld.com/community/haletky

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
0 Kudos