Skip to main content
NetApp Knowledge Base

PERF_IMPACT and LATENCY_CLEAR events reported on F-Ports due to slow drain device

  1. Last updated
  2. Save as PDF
Views:
1,123
Visibility:
Public
Votes:
0
Category:
fabric-interconnect-and-management-switches
Specialty:
brocade
Last Updated:

Applies to

Brocade Switches

Issue

IO_PERF_IMPACT and IO_LATENCY_CLEAR along with Frame Delay events reported on F-Ports under errdump as shown below:

2022/12/20-14:55:01:562972, [MAPS-1003], 327854/274163, SLOT 1 | FID 128, WARNING, SWITCHXX, slot9 port40-Host.LINUX, F-Port 9/40, Condition=ALL_PORTS(DEV_LATENCY_IMPACT==IO_PERF_IMPACT), Current Value:[DEV_LATENCY_IMPACT, IO_PERF_IMPACT, (30.3% of 10 secs in VC: 2) ], RuleName=defALL_PORTS_IO_PERF_IMPACT_UNQUAR, Dashboard Category=Fabric Performance Impa., raslogAction.c, line: 170, comp:md, ltime:2022/12/20-14:55:01:562789

2022/12/20-14:58:01:638771, [MAPS-1004], 327855/274164, SLOT 1 | FID 128, INFO, SWITCHXX, slot9 port40-Host.LINUX, F-Port 9/40, Condition=ALL_PORTS(DEV_LATENCY_IMPACT==IO_LATENCY_CLEAR), Current Value:[DEV_LATENCY_IMPACT, IO_LATENCY_CLEAR], RuleName=defALL_PORTS_IO_LATENCY_CLEAR, Dashboard Category=Fabric Performance Impact., raslogAction.c, line: 170, comp:md, ltime:2022/12/20-14:58:01:638573

 

2022/01/20-20:49:37, [MAPS-1002], 100580, SLOT 1 | FID 128, ERROR, BROCADE, BROCADE_21.E_PORT.192., F-Port 8/0, Condition=ALL_PORTS(DEV_LATENCY_IMPACT==IO_PERF_IMPACT), Current Value:[DEV_LATENCY_IMPACT, IO_PERF_IMPACT, (10 ms Frame Delay) ], RuleName=ALL_PORTS_IO_PERF_IMPACT_UNQUAR, Dashboard Category=Fabric Performance Impact.
2022/01/20-20:50:37, [MAPS-1002], 100581, SLOT 1 | FID 128, ERROR, BROCADE_21, BROCADE_21.E_PORT.192., F-Port 8/0, Condition=ALL_PORTS(DEV_LATENCY_IMPACT==IO_LATENCY_CLEAR), Current Value:[DEV_LATENCY_IMPACT, IO_LATENCY_CLEAR], RuleName=ALL_PORTS_IO_LATENCY_CLEAR, Dashboard Category=Fabric Performance Impact.

 

  • Review the SFP Tx and Rx power on the affected switch port and ensure that they are within the recommended range.
  • Inspect the device attached to the affected switch port including hardware checks as well as workload and and address the slow response from the end device side.
  • Check for any such physical layer issues observed on the port.
  • In case of major disruption caused by this, as a workaround disable the port until the issue is resolved.

 

 

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.