Why Increasing Buffer Credits Is Not A Cure For A Slow Drain Device


When I am working on performance problems, a frequent question I  get is why increasing buffer credits for a particular port is not a fix for a slow drain device attached to that port.  In this video, I explain the concept of congestion and illustrate why increasing the number of buffer credits is not a fix, without addressing the underlying cause of the congestion.   There are some exceptions to this rule.  The most common is when dealing with long-distance links, but that will be addressed in a future blog post (and perhaps a future video).  




As always,  you can leave feedback in the comments, or find me on LinkedIn or Twitter

Comments

Post a Comment

Popular posts from this blog

I Will Be At Technical University in Atlanta

Image
IBM Tech U Atlanta 2019 This is just a quick post to say that I will be at IBM Technical University in Atlanta. I will be there from April 29 through May 3 My sessions for this event are: s106417 The Path of an FC Frame Through a Cisco MDS Director s106420 Proactive Monitoring of a Cisco Fabric s106421 Troubleshooting Cisco SAN Performance Issues - Part 1 s106422  Troubleshooting Cisco SAN Performance Issues - Part 2 Find these sessions and many more at Technical University. Click the banner at the top of the page to register or for more information. As always, if you have any questions, leave them in the comments at the end of this blog or find me on LinkedIn or Twitter.
Read more

Fabric Zoning for the IBM Spectrum Virtualize and FlashSystem NPIV Feature

Image
Zoning Basics Before I talk about some zoning best-practices, I should explain two different types of zoning and how they work.  There are two types of zoning:  WWPN Zoning and Switch-Port Zoning World-wide Port Name (WWPN) Zoning WWPN zoning is also called "soft" zoning and is based off the WWPN that is assigned to a specific port on a fibre-channel adapter.  The WWPN serves a similar function as a MAC address does on an ethernet adapter.  WWPN-based zoning uses the WWPN of devices logged into the fabric to determine which device can connect to which other devices.  Most fabrics are zoned using WWPN zoning.  It is more flexible than switch-port zoning - a device can be plugged in anywhere on the SAN (with some caveats beyond the scope of this blog post) and the device can connect to the other devices it is zoned to.    It has one distinct advantage over Switch-Port based zoning, which is that zoning can always be specified on a single WWPN level.   Switch-Port Z
Read more

SAN Design Best-Practices for IBM SVC and FlashSystem Stretched and Hyperswap Clusters

Image
I recently worked with a customer who had their SAN implemented as depicted in the diagram for a Hyperswap V7000 cluster.   An SVC or FlashSystem cluster that is configured for Hyperswap has half of the nodes at one site, and half of the nodes at the other site.  The I/O groups are configured so that nodes at each site are in the same I/O group.  In the example from the diagram, the nodes at Site 1 were in one I/O group, the nodes at the other were in another I/O group.  A stretched cluster also has the nodes in a cluster at two sites, however each I/O group is made up of nodes from each site.  So for our diagram below,  in a Stretched configuration, a node from Site 1 and a node from Site 2 would be in an I/O Group.   From the diagram we see that each site had two V7000 nodes.  Each node had connections to two switches at each site.  The switches were connected as pictured in the diagram to create two redundant fabrics that spanned the sites.   The customer had hosts and third-p
Read more