![brocade san switch concepts brocade san switch concepts](https://slideplayer.com/slide/5924159/19/images/31/High+Availability+Fibre+Channel+Deployment+Scenarios.jpg)
Sets the error log start and end delimiter for Turn on the dynamic load sharing (DLS) optionĭisplay the state of the dynamic load sharing
![brocade san switch concepts brocade san switch concepts](http://www.itinstock.com/ekmps/shops/itinstock/images/emc-ed-dcx-4s-backbone-san-switch-100-652-565-3x-fc8-48-fx8-24-2x-cp8-2x-cr4s8-46283-p.jpg)
Turn off the dynamic load sharing (DLS) option Set or display diagnostic show-time mode.ĭisplay currently running diagnostic tests.ĭistributes data to switches in a fabric. Print zone configurations in transaction bufferĭisplay all Field Replaceable Units (FRU)ĭisplays the port registers for a given chipĭisplays a log of most recently executed CLIĭata retention test of the central memory SRAMs.ĭiagnostic debug parameters management package.ĭisplays the contents of port registers and Moves the effective configuration to the defined Verify QuickLoop’s Content Addressable Memoryĭisplay Effective zone configuration information Test for back-end ASIC pair to ASIC pair links.Įnables or disables blade beaconing or displays theįunctional test of port via blade processor path.Ĭlear errors that are stored in the non-volatileĭisplay errors that are stored in the non-volatile Get and set Advanced Performance Tuning policyīackplane connection test for multi-blade systems. Specifies all administration domain (AD)-levelĭisplays the Access Gateway information registered
#BROCADE SAN SWITCH CONCEPTS HOW TO#
In future blog posts I will show you the most common problem we see and how to avoid it.If I get a dollar for each time I searched for a SAN Switch command to achieve something, I would have been a one tenth of a millionaire by now ? Below is the cheat sheet I compiled to prevent me from becoming that one tenth of a millionaire. The below design is the most common that IBM SAN Central sees. These virtual fabrics are distinct entities and have separate zoning, name server databases and nearly everything else that a physical fabric has. Each of the virtual switches is a switch unto itself and when linked with other virtual switches will create a virtual fabric (or VSAN) within the physical fabric. Cisco calls these VSANs, Brocade calls them Virtual fabrics, but the idea is the same. However, in this new design each SAN switch is configured into logical virtual switches. As before, there are redundant fabrics on two different providers. Note the continued presence of the dedicated ISLs between the sites. An alternative design that uses only 4 switches is shown below. Because of the expense, this is an atypical design. The above design is more expensive than the other implementation options given that it requires 8 switches. Also remember that this applies to Stretched clusters as well.
#BROCADE SAN SWITCH CONCEPTS SERIES#
As with that post, while I may only reference SVC in this series (for exanple, the diagram below depicts an SVC cluster) any recommendations made apply equally to SVC, Spectrum Virtualize and IBM FlashSystem products. I will also show you some of the common mistakes that are made in the SAN implementation. This is one in a series of blog posts that will discuss some of the options for fabric design within that framework and provide some implementation details on Cisco and Brocade fabrics. There are various ways that SANs can be implemented to meet that requirement. The requirement at it's most basic when using Hyperswap is to have completely separate fabrics for private traffic, where the private traffic is used for only the inter-node communication within the cluster and there are one or more public fabrics for everything else. In that post I covered some of the problems that arise with improper SAN design for SVC clusters in a Hyperswap configuration. In February 2020 I wrote this post on the supported SAN design for SVC and Spectrum Virtualize Hyperswap clusters.