Skip to main content
NetApp Knowledge Base

EMS message fcp.io.status AEN 0x8048 RECV_ERROR occurring

  1. Last updated
  2. Save as PDF
Views:
3,076
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
san
Last Updated:

​ ​

Applies to

  • All NetApp FAS / AFF Hardware Platforms
  • All Data ONTAP Versions

Issue

  • An error string similar to the following appears in EMS logs:

NETAPP01: fct_tpd_thread_3: fcp.io.status:debug]: STIO Adapter:0e AEN 0x8048 (RECV_ERROR) MboxStatus1 0x1002 MboxStatus2 0xa1

  • Additionally, hosts may or may not show I/O errors on LUNs accessed via a LIF on the adapter mentioned
  • Hosts report high latency for LUNs/volumes presented from the node which report the above event.
  • Below checks need to be done to further isolate the issue:
    • Check FCP-ADAPTER.XML in a recent full or weekly ASUP, or run fcp adapter show -instance to verify received (RX) and transmitted (TX) laser power values
    • Review the Tx and Rx power on the switch port as well connected to the storage port.
    • If the SFP in the port reported has an unusually low TX value compared to the others (rule of thumb: less than 50%), replace the SFP
    • If the SFP in the port reported has an unusually low RX value compared to the others (rule of thumb: less than 50%), check the TX value of the switch-side SFP
    • If the SFP in the corresponding switch port has an unusually low TX value compared to the others, replace the SFP.
    • To isolate the issue  furthermore, move the cable to another switch port and check if issue follows, then that means its is cable which needs to be checked further.
    • If the SP Tx and Rx power are good on both ends, cable testing needs to be done.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.