Deployment Guide
FIGURE 16 A Flow Mirror revealing a slow drain
switch:admin> flow --create slwdrn -feature mirror -egrport 15 -dstdev 0x040f00 -srcdev 0x020200 -bidir
switch:admin> flow --show slwdrn -feature mirror -verbose
Name : flow_slowdrain Features: mir(Active)
Definition: EgrPort(15),SrcDev(0x020200),DstDev(0x040f00),BiDir
Flow Mirror (Active):
-------------------------------------------------------------------------------------------------
| Time-Stamp | Dir | SOF | EOF | Frame_type | LUN(*) | Frame Contents |
-------------------------------------------------------------------------------------------------
| Jul 12 06:29:13:637 | Rx | SOFn3 | EOFn | Data | ---- | 01040f00 00020200 08000008 … |
| Jul 12 06:29:13:639 | Rx | SOFi3 | EOFt | SCSIRead | 0000 | 06040f00 00020200 08290000 … |
| Jul 12 06:29:13:639 | Rx | SOFi3 | EOFt | SCSIWrite | 0000 | 06040f00 00020200 08290000 … |
| Jul 12 06:29:13:639 | Rx | SOFi3 | EOFt | SCSIRead | 0000 | 06040f00 00020200 08290000 … |
| Jul 12 06:29:13:639 | Rx | SOFn3 | EOFn | Data | ---- | 01040f00 00020200 08000008 … |
| Jul 12 06:29:13:639 | Rx | SOFi3 | EOFt | SCSIRead | 0000 | 06040f00 00020200 08290000 … |
| Jul 12 06:29:49:398 | Rx | SOFi3 | EOFt | FLOGI | ---- | 22fffffe 00000000 01290000 … |
| Jul 12 06:29:49:411 | Rx | SOFi3 | EOFt | PLOGI | ---- | 22fffffc 00020200 01290000 … |
| Jul 12 06:29:49:411 | Rx | SOFi3 | EOFt | ELSframe | ---- | 22fffffd 00020200 01290000 … |
| Jul 12 06:29:51:614 | Rx | SOFi3 | EOFt | PRLI | ---- | 22fffc04 00020200 01290000 … |
(output truncated)
--------------------------------------------------------------------------------------------
No of Mirrored Frames : 530, No of RX Mirrored Frames : 530, No of TX Mirrored Frames : 0
--------------------------------------------------------------------------------------------
Tracking SCSI commands
There are many reasons why you might want to see the SCSI commands being initiated by a host. For
example, such a flow could be used to find all the targets that the host is communicating with. Getting
this data can help identify the favorite targets of a host, which would then allow you to provide additional
privileges like QoS or TI path creation between those devices.
If you want to see all the SCSI frames being initiated by a host device (for example, the host H1
connected to port F1 on switch SW Dom1 in the following figure), you would create a pair of flow
definitions such as the following on the switch SW Dom 2:
switch:admin> flow –create SCSIflow1 –feature mirror –egrport F3 –srcdev H1 –
frametype scsicmd
switch:admin> flow –create SCSIflow1 –feature mirror -ergrport F4 –srcdev H1 –
frametype scsicmd
Then you would create a flow definition similar to the following on the switch SW Dom 1:
switch:admin> flow -create SCSIflow2 -feature mirror -ingrport F1 -frametype scsicmd
This flow will mirror all the frames containing SCSI commands that ingress through port F1. As you can
have only one mirror flow active at a time for a chassis or fixed port switch, you cannot trap all the
frames initiated by H1 to both T2 and T3 at the same time. This makes it almost impossible to capture
all the SCSI command frames initiated by H1. However, by using the –frametype option along with –
ingrport option, you can still track frames between a given initiator and target pair. This will help you
view any of the SCSI frames which are being sent out by H1 to any target in the zone.
Tracking SCSI commands
Flow Vision Administrators Guide 87
53-1003168-01