P4300 ISCSI warning

[stefano colombo_1]

we have a 3-nodes Hyperv Cluster R2 using a cluster of 5 P-4300 nodes
Each Hosts has 4 ISCSI NIC
On these nodes we see some of these message

Log Name: System
Source: MSiSCSI
Date: 10/26/2010 2:26:50 AM
Event ID: 113
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: hv02.xxxx.net
Description:
iSCSI discovery via SendTargets failed with error code 0xefff0003 to target portal *192.168.50.100 0003260 B06BDRV\L4SC&PCI_163914E4&SUBSYS_7059103C&REV_20\7&d409019&0&30051B00_0 .
Event Xml:



113
3
0
0x80000000000000

45703
System
hv02.xxxx.net



0xefff0003
*192.168.50.100 0003260 B06BDRV\L4SC&PCI_163914E4&SUBSYS_7059103C&REV_20\7&d409019&0&30051B00_0 

P.S. This thread has been moved from Storage Area Networks (SAN) (Small and Medium Business) to HP StoreVirtual Storage / LeftHand. - Hp Forum Moderator

[Antonio Milanese]

Hi Stefano,

my suggestion is to check the following bulletins:

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02429763&dimid=1159776690&dicid=alr_jul10&jumpid=em_alerts/us/jul10/all/xbu/emailsubid/mrm/mcc/loc/rbu_category/alerts

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=12169&prodSeriesId=3936136&swItem=co-82828-1&prodNameId=3936176&swEnvOID=54&swLang=13&taskId=135&mode=4&idx=0

http://support.microsoft.com/kb/972107

are you using the latest lfh DSM (8.5 p10068 IIRC)or the MS initiator as the posted message is suggesting?

Anyway my personal check list with this kind of problems (yes i'm cisco OSI bottom-up approach addicted=)

L2 problems:
1) LACP/Bonding problems on LFN nodes side (ALB used ?) server side (HP teaming?)
2) (x)STP problems..yeah! TRILL me baby!
3) flow control /jumbo frames problems
4) VLANS problems
5) NICs / HBA (BROADCOMMMMMMMMMMMMM!!)
L3/L4:
1) mostly damned TOE engines (i ALWAYS disable every TOE bit i can find especially with BROADCOM hardware): stability stability and, yes, i love to waste new hypercubic GHz CPU cycles!!
L7:
MPIO settings i.e. policy (AFAIK DSM 8.5 support correctly fail over only at the moment)

Hope this'll help you to solve the problem,

regards

Antonio