There is no specific command to list out hanging zones in the fabric, we have to use SAN health to identify the hanging zone. The zone in which all initiators or all targets are inactive are considered as hanging zone. Hanging zones are the purposeless zones residing in the zoning configuration. In case an error is listed, before troubleshooting clear the status using below commands and observe it again.Īpart from this, there are other commands to display the current data transfer rate of a port or all ports, such as: #porterrorshow -i Port_Index Both these commands will list the errors in a particular port. #porterrshow This will list all ports in error state. Physical layer issue is, either Cable issue or SFP issue.īelow are the commands to identify the port errors: Bottleneck issue we have already addressed above. Most of the time, its due to bottleneck issue/ physical layer issue. If there is latency or congestion bottleneck, it should to be fixed by logging a support case with Server/Storage hardware vendor. The commands used to identify latency as well as congestion bottleneck are: In the next write-up we will discuss in detail, about the causes of a congestion bottleneck. Whereas, Congestion bottleneck occurs due to high rate of data transfer in the port. SFP which has a voltage or power issue.Slow drain devices, is a device which either has all or any one of the bellow mentioned issues: Even initiator or target ports can report latency, no matter what kind of port it is, if a slow drain device is attached, there will be bottleneck in that port. Latency bottleneck occurs when a slow drain device is connected to the port.

But, the once prominent in SAN fabric are Latency bottleneck and congestion bottleneck. #zoneshow –alias Alias_Name This lists the zone name and component aliases. #alishow |grep wwn -b2 This lists the alias. In order to know the zoning details through the WWN of the device, use below mentioned command: As both the activities clear the fabriclog. Note: This command will fail in case the FOS upgrade or Switch reboot activity was performed. #fabriclog -s |grep -E “ Port Index |GMT” This command states the ports which went offline before. #fabriclog -s States the ports which went offline recently. Thus, when ‘WWN/ Alias went offline’ is recorded, use the below mentioned commands to identify, when the port went offline and which port went offline.

This error is recorded due to the following reasons: Let’s read in brief about, how to identify the errors and how to troubleshoot them.

Listed below are few of the operational error codes/prompts: For better understanding of the commands, let us first understand the day to day operational challenges faced in the SAN fabric. This write-up, focuses on the basic trouble shooting commands used in Brocade SAN switch. We have already discussed about, Brocade SAN switch Zoning steps Via CLI and CISCO MDS Zoning steps via CLI

Old brocade san switch gui error