ISCSI bad Checksum 0x000

i´m having performance problems when configuring new iscsi environment. 
in desesperated effort find cause of problem, i´m using wireshark capture traffic, , check packages. 
i´m seeing lot of packages header checksum errors... 0x0000 [incorrect, should 0xfe79]

i´m seeing lot of packages [tcp acked lost segment] iscsi-target > 49152 [ack] seq=229 
ones i´m suspecting wireshark isn´t capable of capturing packages, it´s missing some, end displaying errors. 

checksum errors, shouldn´t happen.. 

any ideas of should be, or do, or troubleshoot steps ? 

thanks in advance. 

---

luiz a. camilo network administrator

hi, 

actually i´m currenctly in contact storage manufacturer, month, hasn´t solved problem. 
correcting information, yes, there errors storage server, they're re-transmission packages. filtering , analysing package capture, , crc errors server storage. 

firs using windows server 2008 r2 enterprise ver: 6.1 (build 7600). 
created lun on storage, , installed windows server 2008 enterprise (not r2) , problem same. 
i´ve been using different nic driver versions, error same. 
tried using off-board nic connect storage, error same ... 
pointing hardware problem, nic´s firmware probaly changed fujitsu support storage communications. 
i´m telling because on intel downloads website, especific nic there tools change iscsi firmware, , upload nic´s eprom. 

here follow logs : 

 

log name:      application
source:        mssqlserver
date:          25/06/2010 22:27:55
event id:      833
task category: (2)
level:         information
keywords:      classic
user:          n/a
computer:      servername
description:
sql server has encountered 13 occurrence(s) of i/o requests taking longer 15 seconds complete on file [f:\mssqldata\dbecomex_data.mdf] in database [dbecomex] (6).  os file handle 0x00000af0.  offset of latest long i/o is: 0x000000e390a000

log name:      system
source:        iscsiprt
date:          25/06/2010 12:00:47
event id:      20
task category: none
level:         error
keywords:      classic
user:          n/a
computer:      servername
description:
connection target lost. initiator attempt retry connection.

wish paste here package capture, wireshark doean´t allow me copy readble text .. 

troubleshoot level reached, don´t believe it´s configuration problem.. seems hardware. 

thank help 

 

 

---

luiz a. camilo network administrator

Windows Server  >  Network Infrastructure Servers