<?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 Has anyone seen this: Message: ISCSI: iSCSI protocol violation, 'data segment length 65538 excee in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Has-anyone-seen-this-Message-ISCSI-iSCSI-protocol-violation-data-segment-length/m-p/137785#M30386</link>
    <description>&lt;P&gt;&lt;FONT face="Calibri" size="3" color="#000000"&gt;Been getting the message below recently.&amp;nbsp; Opened a ticket with Netapp support when we've seen this some months ago, and after a long investigation, their conclusion was that the message is informational.&amp;nbsp; However, now this is showing up on a different filer (FAS 8200 running CDOT 9.1).&amp;nbsp; We have iscsi boot LUNs, as well as normal iscsi LUNs being accessed from VMs.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Calibri" size="3" color="#000000"&gt;Message: iscsi.protocol.violation: ISCSI: iSCSI protocol violation, 'data segment length 65538 exceeds max 65536' &lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Calibri" size="3" color="#000000"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Calibri" size="3" color="#000000"&gt;Description: This event is issued when an initiator violates the iSCSI protocol. &lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Calibri" size="3" color="#000000"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Calibri" size="3" color="#000000"&gt;Corrective Action: Attempt to configure the initiator such that the protocol violation does not occur. If the event occurs occasionally but does not affect stability or performance, no corrective action is needed but the event should be monitored. If the event persists and/or iSCSI application performance degrades, starting and stopping the iSCSI service and restarting any iSCSI applications may help clear the condition. Contact NetApp technical support. &lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Calibri" size="3" color="#000000"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Calibri" size="3" color="#000000"&gt;Source: NwkThd_02&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Calibri" size="3" color="#000000"&gt;Sequence#: 57882&lt;/FONT&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 14:04:59 GMT</pubDate>
    <dc:creator>mikesicarup</dc:creator>
    <dc:date>2025-06-04T14:04:59Z</dc:date>
    <item>
      <title>Has anyone seen this: Message: ISCSI: iSCSI protocol violation, 'data segment length 65538 excee</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Has-anyone-seen-this-Message-ISCSI-iSCSI-protocol-violation-data-segment-length/m-p/137785#M30386</link>
      <description>&lt;P&gt;&lt;FONT face="Calibri" size="3" color="#000000"&gt;Been getting the message below recently.&amp;nbsp; Opened a ticket with Netapp support when we've seen this some months ago, and after a long investigation, their conclusion was that the message is informational.&amp;nbsp; However, now this is showing up on a different filer (FAS 8200 running CDOT 9.1).&amp;nbsp; We have iscsi boot LUNs, as well as normal iscsi LUNs being accessed from VMs.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Calibri" size="3" color="#000000"&gt;Message: iscsi.protocol.violation: ISCSI: iSCSI protocol violation, 'data segment length 65538 exceeds max 65536' &lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Calibri" size="3" color="#000000"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Calibri" size="3" color="#000000"&gt;Description: This event is issued when an initiator violates the iSCSI protocol. &lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Calibri" size="3" color="#000000"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Calibri" size="3" color="#000000"&gt;Corrective Action: Attempt to configure the initiator such that the protocol violation does not occur. If the event occurs occasionally but does not affect stability or performance, no corrective action is needed but the event should be monitored. If the event persists and/or iSCSI application performance degrades, starting and stopping the iSCSI service and restarting any iSCSI applications may help clear the condition. Contact NetApp technical support. &lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Calibri" size="3" color="#000000"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Calibri" size="3" color="#000000"&gt;Source: NwkThd_02&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Calibri" size="3" color="#000000"&gt;Sequence#: 57882&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 14:04:59 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Has-anyone-seen-this-Message-ISCSI-iSCSI-protocol-violation-data-segment-length/m-p/137785#M30386</guid>
      <dc:creator>mikesicarup</dc:creator>
      <dc:date>2025-06-04T14:04:59Z</dc:date>
    </item>
  </channel>
</rss>

