Brocade Flow Vision Administrators Guide (Supporting Fabric OS v7.3.0) - Manual (Page 86)

+ Denotes feature is currently activated for the flow
switchP2:admin> flow --show fm_edge1_edge2 -feature mirror
=======================================================================================================
Name : fm_edge1_edge2 Features: mir(Activated) noConfig: Off
Definition: IngrPort(3/22),SrcDev(0x010000),DstDev(0x02f001),MirPort(3/43)
Flow Mirror (Activated):
--------------------------------------------------------------------------------------------
No of Mirrored Frames : 1903144, No of RX Mirrored Frames : 1903144, No of TX Mirrored Frames : 0
--------------------------------------------------------------------------------------------
=======================================================================================================
Troubleshooting using Flow Mirror
The following use cases describe how to use Flow Mirror to troubleshoot typical fabric performance
problems.
Diagnosing excessive SCSI reserve and release activity
If there is excessive SCSI reserve and release activity in a virtualized environment, you can use Flow
Mirror to identify the affected LUNs.
The following example creates a flow to mirror all the SCSI release frames from multiple servers to
LUNs on the target on port 1/20. You can then analyze the mirrored frames to determine the impacted
LUNs.
switch:admin> flow --create flow_scsi -feature mirror -egrport 1/20 -srcdev "*" -dstdev "*" -frametype
scsiresrel
-------------------------------------------------------------------------------------------------------
| SID(*) | DID(*) | OXID | RXID | SOF | EOF | Frame_type | LUN(*) | Dir | Time-Stamp |
-------------------------------------------------------------------------------------------------------
| b28600 | a2bd00 | 0f27 | ffff | SOFi3 | EOFt | SCSI3_Rel | 0003 | Tx | Jul 16 17:21:47:253 |
| b28000 | a2bd00 | 09de | ffff | SOFi3 | EOFt | SCSI3_Rel | 0002 | Tx | Jul 16 17:21:47:253 |
| b2c680 | a2bd00 | 0afe | ffff | SOFi3 | EOFt | SCSI3_Rel | 0001 | Tx | Jul 16 17:21:47:253 |
| b28600 | a2bd00 | 0f51 | ffff | SOFi3 | EOFt | SCSI3_Rel | 0005 | Tx | Jul 16 17:21:47:253 |
| b28000 | a2bd00 | 09f0 | ffff | SOFi3 | EOFt | SCSI3_Res | 0002 | Tx | Jul 16 17:21:47:253 |
| b28600 | a2bd00 | 0f1f | ffff | SOFi3 | EOFt | SCSI3_Rel | 0004 | Tx | Jul 16 17:21:47:253 |
(output truncated)
Diagnosing a slow-draining F_Port
A slow-draining F_Port can be challenging to diagnose. Bottleneck detection allows you to identify the
slow draining F_Port, and Flow Mirroring helps you identify the affected LUN on that F_Port.
The following example creates a flow to mirror traffic passing in both directions from device 0x020200
to F_Port 15 on device 0x040F00, and then displays the output. (The “Frame Contents” column has
been trimmed in this example.) The following image provides a illustration of what is happening in the
example.
Troubleshooting using Flow Mirror
86 Flow Vision Administrators Guide
53-1003168-01