Skip to main content
NetApp Knowledge Base

defALL_PORTS_OVERSUBSCRIBED events reported on Brocade Switch

Views:
1,628
Visibility:
Public
Votes:
6
Category:
fabric-interconnect-and-management-switches
Specialty:
brocade
Last Updated:

Applies to

Brocade Switches

Issue

  • defALL_PORTS_OVERSUBSCRIBED, defALL_PORTS_OVERSUBSCRIPTION_CLEAR along with TXQ latency events reported on F-port under errdump logs:

2022/05/09-14:19:59, [MAPS-3038], 9094, SLOT 2 | FID 128, WARNING, FAB2, slot11 port6, F-Port 11/6, Condition=ALL_PORTS(PORT_BANDWIDTH==OVERSUBSCRIBED), Current Value:[PORT_BANDWIDTH, OVERSUBSCRIBED, (TXQL=7 us, TX=72.2%) ], RuleName=defALL_PORTS_OVERSUBSCRIBED, Dashboard Category=Fabric Performance Impact.
2022/05/09-14:19:59, [MAPS-3038], 9095, SLOT 2 | FID 128, WARNING, FAB2, slot4 port7, F-Port 4/7, Condition=ALL_PORTS(PORT_BANDWIDTH==OVERSUBSCRIBED), Current Value:[PORT_BANDWIDTH, OVERSUBSCRIBED, (TXQL=6 us, TX=70.2%) ], RuleName=defALL_PORTS_OVERSUBSCRIBED, Dashboard Category=Fabric Performance Impact.
2022/05/09-14:20:59, [MAPS-3039], 9096, SLOT 2 | FID 128, INFO, FAB2, slot11 port6, F-Port 11/6, Condition=ALL_PORTS(PORT_BANDWIDTH==OVERSUBSCRIPTION_CLEAR), Current Value:[PORT_BANDWIDTH, OVERSUBSCRIPTION_CLEAR], RuleName=defALL_PORTS_OVERSUBSCRIPTION_CLEAR, Dashboard Category=Fabric Performance Impact.
2022/05/09-14:20:59, [MAPS-3039], 9097, SLOT 2 | FID 128, INFO, FAB2, slot4 port7, F-Port 4/7, Condition=ALL_PORTS(PORT_BANDWIDTH==OVERSUBSCRIPTION_CLEAR), Current Value:[PORT_BANDWIDTH, OVERSUBSCRIPTION_CLEAR], RuleName=defALL_PORTS_OVERSUBSCRIPTION_CLEAR, Dashboard Category=Fabric Performance Impact.

  • defALL_HOST_PORTSTX_95 rule is generated in errdump logs:

2022/12/18-05:19:50, [MAPS-1005], 7594245, SLOT 1 | FID 128, WARNING, NETM_X7_112_FAB2, slot10 port41-H.LIN.UPI-DB1.10.225.229.151.G7BY6T2.HBUPIDRDB1_40, F-Port 10/41, Condition=ALL_HOST_PORTS(TX/min>95.00), Current Value:[TX, 95.38 %], Rule defALL_HOST_PORTSTX_95 triggered 24 times in 1 hour and last trigger time Sun Dec 18 04:48:52 2022, Dashboard Category=Fabric Performance Impact.

  • defPORT_MAX_WR_PENDING_IO_250 alerts observed in the ems logs:

2024/07/16-23:00:29 (IST), [MAPS-1003], 352645, SLOT 1 | FID 128 | PORT 11/14, WARNING, Sxxy_X7_1xx_Fxx2, slot11 port14-Storage.E.UPI_5600_40850_CL8F.(Dedicated_Linux).3F, F-Port 11/14, Condition=ALL_TARGET_PORTS(MAX_WR_PENDING_IO/10SEC>250), Current Value:[PORT_MAX_WR_PENDING_IO, 251 IOs], RuleName=defPORT_MAX_WR_PENDING_IO_250, Dashboard Category=IO Latency, Quiet Time=10 min.
2024/07/16-23:10:49 (IST), [MAPS-1005], 352694, SLOT 1 | FID 128 | PORT 11/14, WARNING, Sxxy_X7_1xx_Fxx2, slot11 port14-Storage.E.UPI_5600_40850_CL8F.(Dedicated_Linux).3F, F-Port 11/14, Condition=ALL_TARGET_PORTS(MAX_WR_PENDING_IO/10SEC>250), Current Value:[PORT_MAX_WR_PENDING_IO, 253 IOs], Rule defPORT_MAX_WR_PENDING_IO_250 triggered 8 times in 10 min and last trigger time Tue Jul 16 23:10:29 2024, Dashboard Category=IO Latency. 

  • The high utilization isn't a fabric fault and there is nothing much we can help with regards to high utilization as it is not a fixable fault
  • It is a design and/or usage issue which means that due to traffic conditions (load demand), the current utilization is exceeding the available bandwidth
  • Switch serves the incoming requests coming from the end device connected to the port. So, if any point of time the requested workload is more and the tx on the switch port is getting utilized more than 95%, that is when the rule defALL_HOST_PORTSTX_95 are generated
  • High response time observed on storage devices due to buffer credits

 

 

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.