<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic P4300 ISCSI warning in StoreVirtual Storage</title>
    <link>https://community.hpe.com/t5/storevirtual-storage/p4300-iscsi-warning/m-p/4704700#M9292</link>
    <description>&lt;P&gt;we have a 3-nodes Hyperv Cluster R2 using a cluster of 5 P-4300 nodes &lt;BR /&gt;Each Hosts has 4 ISCSI NIC &lt;BR /&gt;On these nodes we see some of these message &lt;BR /&gt;&lt;BR /&gt;Log Name: System&lt;BR /&gt;Source: MSiSCSI&lt;BR /&gt;Date: 10/26/2010 2:26:50 AM&lt;BR /&gt;Event ID: 113&lt;BR /&gt;Task Category: None&lt;BR /&gt;Level: Warning&lt;BR /&gt;Keywords: Classic&lt;BR /&gt;User: N/A&lt;BR /&gt;Computer: hv02.xxxx.net&lt;BR /&gt;Description:&lt;BR /&gt;iSCSI discovery via SendTargets failed with error code 0xefff0003 to target portal *192.168.50.100 0003260 B06BDRV\L4SC&amp;amp;PCI_163914E4&amp;amp;SUBSYS_7059103C&amp;amp;REV_20\7&amp;amp;d409019&amp;amp;0&amp;amp;30051B00_0 .&lt;BR /&gt;Event Xml:&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt; 113&lt;BR /&gt; 3&lt;BR /&gt; 0&lt;BR /&gt; 0x80000000000000&lt;BR /&gt; &lt;BR /&gt; 45703&lt;BR /&gt; System&lt;BR /&gt; hv02.xxxx.net&lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt; 0xefff0003&lt;BR /&gt; *192.168.50.100 0003260 B06BDRV\L4SC&amp;amp;PCI_163914E4&amp;amp;SUBSYS_7059103C&amp;amp;REV_20\7&amp;amp;d409019&amp;amp;0&amp;amp;30051B00_0&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;P.S. This thread has been moved&amp;nbsp;from Storage Area Networks (SAN) (Small and Medium Business) to HP StoreVirtual Storage / LeftHand. - Hp Forum Moderator&lt;BR /&gt; &lt;/P&gt;</description>
    <pubDate>Mon, 25 May 2015 05:55:35 GMT</pubDate>
    <dc:creator>stefano colombo_1</dc:creator>
    <dc:date>2015-05-25T05:55:35Z</dc:date>
    <item>
      <title>P4300 ISCSI warning</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/p4300-iscsi-warning/m-p/4704700#M9292</link>
      <description>&lt;P&gt;we have a 3-nodes Hyperv Cluster R2 using a cluster of 5 P-4300 nodes &lt;BR /&gt;Each Hosts has 4 ISCSI NIC &lt;BR /&gt;On these nodes we see some of these message &lt;BR /&gt;&lt;BR /&gt;Log Name: System&lt;BR /&gt;Source: MSiSCSI&lt;BR /&gt;Date: 10/26/2010 2:26:50 AM&lt;BR /&gt;Event ID: 113&lt;BR /&gt;Task Category: None&lt;BR /&gt;Level: Warning&lt;BR /&gt;Keywords: Classic&lt;BR /&gt;User: N/A&lt;BR /&gt;Computer: hv02.xxxx.net&lt;BR /&gt;Description:&lt;BR /&gt;iSCSI discovery via SendTargets failed with error code 0xefff0003 to target portal *192.168.50.100 0003260 B06BDRV\L4SC&amp;amp;PCI_163914E4&amp;amp;SUBSYS_7059103C&amp;amp;REV_20\7&amp;amp;d409019&amp;amp;0&amp;amp;30051B00_0 .&lt;BR /&gt;Event Xml:&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt; 113&lt;BR /&gt; 3&lt;BR /&gt; 0&lt;BR /&gt; 0x80000000000000&lt;BR /&gt; &lt;BR /&gt; 45703&lt;BR /&gt; System&lt;BR /&gt; hv02.xxxx.net&lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt; 0xefff0003&lt;BR /&gt; *192.168.50.100 0003260 B06BDRV\L4SC&amp;amp;PCI_163914E4&amp;amp;SUBSYS_7059103C&amp;amp;REV_20\7&amp;amp;d409019&amp;amp;0&amp;amp;30051B00_0&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;P.S. This thread has been moved&amp;nbsp;from Storage Area Networks (SAN) (Small and Medium Business) to HP StoreVirtual Storage / LeftHand. - Hp Forum Moderator&lt;BR /&gt; &lt;/P&gt;</description>
      <pubDate>Mon, 25 May 2015 05:55:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/p4300-iscsi-warning/m-p/4704700#M9292</guid>
      <dc:creator>stefano colombo_1</dc:creator>
      <dc:date>2015-05-25T05:55:35Z</dc:date>
    </item>
    <item>
      <title>Re: P4300 ISCSI warning</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/p4300-iscsi-warning/m-p/4704701#M9293</link>
      <description>Hi Stefano,&lt;BR /&gt;&lt;BR /&gt;my suggestion is to check the following bulletins:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02429763&amp;amp;dimid=1159776690&amp;amp;dicid=alr_jul10&amp;amp;jumpid=em_alerts/us/jul10/all/xbu/emailsubid/mrm/mcc/loc/rbu_category/alerts" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02429763&amp;amp;dimid=1159776690&amp;amp;dicid=alr_jul10&amp;amp;jumpid=em_alerts/us/jul10/all/xbu/emailsubid/mrm/mcc/loc/rbu_category/alerts&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&amp;amp;cc=us&amp;amp;prodTypeId=12169&amp;amp;prodSeriesId=3936136&amp;amp;swItem=co-82828-1&amp;amp;prodNameId=3936176&amp;amp;swEnvOID=54&amp;amp;swLang=13&amp;amp;taskId=135&amp;amp;mode=4&amp;amp;idx=0" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&amp;amp;cc=us&amp;amp;prodTypeId=12169&amp;amp;prodSeriesId=3936136&amp;amp;swItem=co-82828-1&amp;amp;prodNameId=3936176&amp;amp;swEnvOID=54&amp;amp;swLang=13&amp;amp;taskId=135&amp;amp;mode=4&amp;amp;idx=0&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://support.microsoft.com/kb/972107" target="_blank"&gt;http://support.microsoft.com/kb/972107&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;are you using the latest lfh DSM (8.5 p10068 IIRC)or the MS initiator as the posted message is suggesting?&lt;BR /&gt;&lt;BR /&gt;Anyway my personal check list with this kind of problems (yes i'm cisco OSI bottom-up approach addicted=)&lt;BR /&gt;&lt;BR /&gt;L2 problems:&lt;BR /&gt; 1) LACP/Bonding problems on LFN nodes side (ALB used ?) server side (HP teaming?)&lt;BR /&gt; 2) (x)STP problems..yeah! TRILL me baby!&lt;BR /&gt; 3) flow control /jumbo frames problems&lt;BR /&gt; 4) VLANS problems&lt;BR /&gt; 5) NICs / HBA (BROADCOMMMMMMMMMMMMM!!)&lt;BR /&gt;L3/L4: &lt;BR /&gt; 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!!&lt;BR /&gt;L7:&lt;BR /&gt; MPIO settings i.e. policy (AFAIK DSM 8.5 support correctly fail over only at the moment) &lt;BR /&gt; &lt;BR /&gt;Hope this'll help you to solve the problem,&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;&lt;BR /&gt;Antonio</description>
      <pubDate>Wed, 27 Oct 2010 19:13:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/p4300-iscsi-warning/m-p/4704701#M9293</guid>
      <dc:creator>Antonio Milanese</dc:creator>
      <dc:date>2010-10-27T19:13:38Z</dc:date>
    </item>
  </channel>
</rss>

