Flow Mirror Example Procedures - Brocade Communications Systems WFT-2D User Manual

8. Click Close to close the Flow Vision dialog box.

Flow Mirror example procedures

The following use cases describe how to use Flow Mirror to troubleshoot typical fabric performance
problems.
Diagnosing SCSI reserve and SCSI release performance
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 port 1/20. You can then analyze the
mirrored frames to determine the impacted LUNs.
1. Right-click a target port (1/20) and select Fabric Vision > Flow > Add.
Brocade Network Advisor SAN User Manual
53-1003154-01
TABLE 97
Flows table fields and components (Mirror Flow) (Continued)
Field and components
Mirrored Frames Count (frames)
Mirrored Transmit Frames (frames)
Mirrored Receive Frames (frames)
Ingress Port
Egress Port
Mirror Port
LUN
Bi-Directional
Flow Definition Persistence
Last Updated Time
The Add Flow Definition dialog box displays with the following criteria and flow identifiers
pre-populated:
•
Feature — Monitor
•
Direction — Bidirectional
•
Source Device — Source identifier
•
Destination Device — * (an asterisk allows you to use any port)
•
Egress port — port number (1/20)
Description
The number of mirrored frames as reported in the last data point
received for the flow.
The number of transmitted mirrored frames as reported in the last data
point received for the flow.
The number of received mirrored frames as reported in the last data
point received for the flow.
The ingress port defined in the flow definition. The port name is a
hyperlink. Click to launch the port's property sheet. A yellow icon
indicates a bottlenecked port.
The egress port defined in the flow definition. The port name is a
hyperlink. Click to launch the port's property sheet. A yellow icon
indicates a bottlenecked port.
The mirror port identifier defined in the flow definition.
Any LUN values defined in the flow definition.
Whether the flow is bidirectional (yes) or not (no).
Whether the flow is configured to persist over switch reboots (yes) or
not (no).
The date and time the sub-flow was last updated.
29
Flow Mirror
1197