Skip to main content

NetApp_Insight_2020.png 

NetApp Knowledgebase

What does error 'Nblade.invTcpRecordMarker' mean?

Views:
426
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
nfs
Last Updated:

 

Applies to

  • ONTAP 8
  • ONTAP 9

Answer

This error is logged in EMS when one of three invalid TCP record markers is received:

  • TCP_FRAGMENT - Received a packet where the 'RPC Last Fragment' bit is set to 0

    • ONTAP does not support these calls

  • TCP_DATA_LENGTH_OVERFLOW - Received a packet where the record marker is greater than the maximum supported

    • Pre ONTAP 8.2 - 70KB

    • Clustered Data ONTAP 8.2 to Clustered Data ONTAP 8.3.2 - 300KB

    • ONTAP 9 and above - 1MB

  • TCP_DATA_LENGTH_UNDERFLOW - Received a packet where the record marker is less than 40 Bytes

Additional Information

Examples:

Nblade.invTcpRecordMarker:error]: Invalid TCP record marker received from remote IP address x.x.x.x on local port xxxx. Vserver ID associated with this operation is x. Invalid reason is TCP_FRAGMENT, invalid record marker is x. 

Nblade.invTcpRecordMarker:error]: Invalid TCP record marker received from remote IP address x.x.x.x on local port xxxx. Vserver ID associated with this operation is x. Invalid reason is TCP_DATA_LENGTH_OVERFLOW, invalid record marker is x. 

Nblade.invTcpRecordMarker:error]: Invalid TCP record marker received from remote IP address x.x.x.x on local port xxxx. Invalid reason is TCP_DATA_LENGTH_UNDERFLOW, invalid record marker is x.