ESX vmkernel errors - solved!

Let's start with the errors I was seeing in: /var/log/vmkernel

Everything was fine until this showed up:

Mar 10 22:09:13 osh-esx-1 vmkernel: 0:00:06:47.624 cpu0:4096)<3>e1000: vmnic2: e1000_clean_tx_irq: Detected Tx Unit Hang
Mar 10 22:09:13 osh-esx-1 vmkernel: Tx Queue <0>
Mar 10 22:09:13 osh-esx-1 vmkernel: TDH
Mar 10 22:09:13 osh-esx-1 vmkernel: TDT
Mar 10 22:09:13 osh-esx-1 vmkernel: next_to_use
Mar 10 22:09:13 osh-esx-1 vmkernel: next_to_clean <13>
Mar 10 22:09:13 osh-esx-1 vmkernel: buffer_info[next_to_clean]
Mar 10 22:09:13 osh-esx-1 vmkernel: t
Mar 10 22:09:15 osh-esx-1 vmkernel: 0:00:06:49.377 cpu7:4256)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: vmhba34:CH:0 T:1 CN:0: Failed to receive data: Connection reset by peer
Mar 10 22:09:15 osh-esx-1 vmkernel: 0:00:06:49.377 cpu7:4256)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Sess [ISID: 00023d000001 TARGET: workstation-disks TPGT: 1 TSIH: 0]
Mar 10 22:09:15 osh-esx-1 vmkernel: 0:00:06:49.377 cpu7:4256)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Conn [CID: 0 L: 10.10.10.5:56632 R: 10.10.10.1:3260]
Mar 10 22:09:15 osh-esx-1 vmkernel: 0:00:06:49.377 cpu7:4256)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: vmhba34:CH:0 T:1 CN:0: Connection rx notifying failure: Failed to Receive. State=Online
Mar 10 22:09:15 osh-esx-1 vmkernel: 0:00:06:49.377 cpu7:4256)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Sess [ISID: 00023d000001 TARGET: workstation-disks TPGT: 1 TSIH: 0]
Mar 10 22:09:15 osh-esx-1 vmkernel: 0:00:06:49.377 cpu7:4256)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Conn [CID: 0 L: 10.10.10.5:56632 R: 10.10.10.1:3260]
Mar 10 22:09:15 osh-esx-1 vmkernel: 0:00:06:49.377 cpu7:4256)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba34:CH:0 T:1 CN:0: Processing CLEANUP event
Mar 10 22:09:15 osh-esx-1 vmkernel: 0:00:06:49.377 cpu7:4256)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: 00023d000001 TARGET: workstation-disks TPGT: 1 TSIH: 0]
Mar 10 22:09:15 osh-esx-1 vmkernel: 0:00:06:49.377 cpu7:4256)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 10.10.10.5:56632 R: 10.10.10.1:3260]

At which point I would then get things like this repeated a lot:

I am going to post the whole log at the end of this post because I found searching for specific chunks of log helped on Google.

I discovered that I could accelerate the issue by starting a second VM. When running one it was just fine. After starting the second and seeing this error log output, I noticed that I could no longer vmkping my iSCSI Target, and I could not ping the iSCSI initiator from the target.

I played around with physical stuff, and even changed the VMnic from E1000 to VMxnet2, but the error persisted. I came back to the logs. It took me a while to get to the 'you turn on the 2nd and it breaks' thing because it wasn't instantaneous. I was trying to install 2008 R2 onto the 2nd VM I was starting up, and it kept failing right around 42%. That clued me into the idea that it was a time thing.

Anyways, since I'm using StarWind iSCSI, I decided to check the settings. Sure enough, deleting the target and re-creating with MULTIPATHING checked off has resolved the issue. I have no clue why that was not checked in the first place.

So there you have it...if you're seeing these log errors, you've not set MultiPathing up for StarWind, or if that's not the case, I'd wager it's got something to do with cache/bandwidth running out.


Edit...I'm not really sure how to re-size the blog width...the vmkernel log looks ridiculous, and excessively long, posted plaintext. I'll have to link a TXT file or something.

Comments

  1. Hello,

    I'm using iSCSI StarWind with 3 Servers, each server has got 2 targets and those targets are assigned to 4 ESX vSphere Update1. I'm seeing this warning only on one of the ESX hosts.

    Any help?

    ReplyDelete
  2. Better late than never?...

    So you've re-created your connections with the multipathing option checked off?

    I'm pretty sure these errors come up with misconfigured iSCSI. Triple-check and re-create all of your connections on that host from scratch.

    Compared working configs to the broken config? Post some of it?

    Again, this error has only come up when I've botched iSCSI configuration.

    ReplyDelete

Post a Comment

Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

Fixing duplicate SPNs (service principal name)

Logstash to Nagios - alerting based on Windows Event ID