Skip to main content
NetApp Knowledge Base

IO_PERF_IMPACT and IO_LATENCY_CLEAR events reported on Brocade F-Ports due to heavy workload

  1. Last updated
  2. Save as PDF
Views:
390
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 events reported on F-Ports under errdump as shown below:

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.

 

 

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.