Deployment Guide
-srcdev 20:00:00:11:0d:e4:18:00 -dstdev 10:00:00:05:1e:e8:e2:00
DCX_Backbone128:admin> flow --show
----------------------------------------------------------------------------- \
Flow Name | Feature | SrcDev | DstDev | \
----------------------------------------------------------------------------- \
e2e_dst_dcx |mon+ |20:00:00:11:0d:e4:18:00 |10:00:00:05:1e:e8:e2:00 | \
----------------------------------------------------------------------------- \
\ ---------------------------------------
\ |IngrPt|EgrPt |BiDir|LUN |FrameType|
\ ---------------------------------------
\ |- |219 |no |- |- |
\ ---------------------------------------
\ + Denotes feature is currently activated for the flow
DCX_Backbone128:admin> flow --show e2e_dst_dcx -feature monitor
===========================================================================
Name : e2e_dst_dcx Features: mon(Active) noConfig: Off
Definition: EgrPort(219),SrcDev(20:00:00:11:0d:e4:18:00),
DstDev(10:00:00:05:1e:e8:e2:00)
Flow Monitor (Activated):
Monitor time: | Mon Jun 17 14:59:58 UTC 2013 |
---------------------------------------------------------
------------------------------------------------------------------------------------------------
| Tx Frames Count| Tx Frames per Sec.| Tx Bytes Count| Tx Throughput(Bps)| Avg Tx Frm Sz(Bytes)|
------------------------------------------------------------------------------------------------
| 2.85G | 8.44M | 387.88G | 1.12G | 132 |
------------------------------------------------------------------------------------------------
Monitoring a backbone-to-edge flow identified by WWNs
In a network set up as shown in Figure 4 on page 41, for a flow passing from Device C to Device A that
is egressing through EX_Port1, the source device (srcdev) is port “WWN c”, the destination device
(dstdev) is port “WWN a”, and the egress port (egrport) is EX_Port1. (Traffic is running from right to left,
and the flow definitions are based on the Edge 1 Fabric’s perspective.)
The following example creates a flow that filters out frames passing from the backbone fabric to an
edge fabric using a specific egress port. The first command shows the available ports and the available
Fibre Channel routers. The second command creates a Flow Monitor flow named “b2e_dst_dcx”
between device 20:02:00:11:0d:51:00:00 and device 10:00:00:05:1e:e8:e2:00 egressing through port
219, and the last command displays the results of the flow.
NOTE
The slash character (\) in the example indicates a break inserted because the output is too long to
display here as a single line.
DCX_Backbone128:admin> switchshow |grep Port
Index Slot Port Address Media Speed State Proto
37 3 5 012500 id N16 Online FC EX-Port 10:00:00:05:33:ef:f1:1c \
47 3 15 012f00 id N8 Online FC F-Port 20:02:00:11:0d:51:00:00 \
219 10 27 01db00 id N16 Online FC EX-Port 10:00:00:05:33:ee:d0:a5 \
E-Port 50:00:51:e4:91:9e:0f:28 \
\ "Wasp_e2" (fabric id=50)(Trunk master)
\
\ "Gnat_e1" (fabric id=100)(Trunk master)
\ "fcr_xd_2_100"
DCX_Backbone128:admin> flow --create b2e_dst_dcx -feature monitor -egrport 219
-srcdev 20:02:00:11:0d:51:00:00 -dstdev 10:00:00:05:1e:e8:e2:00
DCX_Backbone128:admin> flow --show
---------------------------------------------------------------------------- \
Flow Name | Feature | SrcDev | DstDev | \
---------------------------------------------------------------------------- \
b2e_dst_dcx |mon+ |20:02:00:11:0d:51:00:00 |10:00:00:05:1e:e8:e2:00 | \
---------------------------------------------------------------------------- \
\ --------------------------------------
\ |IngrPt|EgrPt|BiDir| LUN | FrameType|
Monitoring a backbone-to-edge flow identified by WWNs
Flow Vision Administrators Guide 43
53-1003168-01