Skip to main content
NetApp Knowledge Base

Switch port faulty events reported on error logs

Views:
171
Visibility:
Public
Votes:
1
Category:
fabric-interconnect-and-management-switches
Specialty:
san
Last Updated:

Applies to

Brocade switches

Issue

Port faulty events reported on errdump output from switch logs
 
2022/01/11-13:07:35, [MAPS-1021], 404729, FID 128, WARNING, SWITCH1, RuleName=SWITCHFAULTY_PORTS_6, Condition=SWITCH(FAULTY_PORTS>=6.00), Obj:Switch [ FAULTY_PORTS,7.75 %] has contributed to switch status CRITICAL.
2022/01/11-13:07:35, [MAPS-1020], 404730, FID 128, WARNING, SWITCH1, Switch wide status has changed from HEALTHY to CRITICAL.
 
2022/01/11-16:02:35, [MAPS-1021], 404779, FID 128, WARNING, SWITCH2, RuleName=SWITCHFAULTY_PORTS_10, Condition=SWITCH(FAULTY_PORTS>=10.00), Obj:Switch [ FAULTY_PORTS,18.75 %] has contributed to switch status CRITICAL.
2022/01/11-16:02:35, [MAPS-1020], 404780, FID 128, WARNING, SWITCH2, Switch wide status has changed from HEALTHY to CRITICAL.
 
  • SWITCHFAULTY_PORTS_6" is triggered when more than 6 Ports are faulty on the switch.
  • SWITCHFAULTY_PORTS_10 is triggered when more than 10 Ports are faulty on the switch.

 

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.