Brocade Flow Vision Administrators Guide (Supporting Fabric OS v7.3.0) User Manual
Page 48
| 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 proxy IDs
In a network set up as shown in
on page 45, for a flow passing from Device C to Device A
that is egressing through EX_Port1, the source device (srcdev) is Device C′, the destination device
(dstdev) is Device A, and the egress port (egrport) is EX_Port1. (Traffic is running from left to right,
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 two commands show the available ports and the
available Fibre Channel routers. The third command creates a Flow Monitor flow named
“b2e_dst_dcx” between device 02f001 and device 220200 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 EX-Port 10:00:00:05:33:ef:f1:1c \
219 10 27 01db00 id N16 Online FC F-Port 20:02:00:11:0d:51:00:00 \
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)
\ "Wasp_e2" (fabric id=50)(Trunk master)
\ "Gnat_e1" (fabric id=100)(Trunk master)
\ "fcr_xd_2_100"
DCX_Backbone128:admin> fcrproxydevshow
Proxy WWN Proxy Device Physical State
Created PID Exists PID
in Fabric in Fabric
-------------------------------------------------------------------------
50 10:00:00:05:1e:e8:e2:00 01f001 100 220200 Imported
100 20:00:00:11:0d:e4:18:00 01f001 50 030f00 Imported
100 20:02:00:11:0d:51:00:00 02f001 128 012f00 Imported
128 10:00:00:05:1e:e8:e2:00 02f001 100 220200 Imported
Total devices displayed: 4
DCX_Backbone128:admin> flow --create b2e_dst_dcx -feature monitor
-egrport 219 -srcdev 02f001 -dstdev 220200
DCX_Backbone128:admin> flow --show
------------------------------------------------------------------------- \
Flow Name | Feature | SrcDev | DstDev \
------------------------------------------------------------------------- \
b2e_dst_dcx |mon+ |02f001 |220200 \
------------------------------------------------------------------------- \
\ --------------------------------------
\ |IngrPt|EgrPt|BiDir| LUN | FrameType|
\ --------------------------------------
\ |- |219 |no |- |- |
\ --------------------------------------
+ Denotes feature is currently activated for the flow
DCX_Backbone128:admin> flow --show b2e_dst_dcx -feature monitor
===========================================================================
Name : b2e_dst_dcx Features: mon(Active) noConfig: Off
Definition: EgrPort(219),SrcDev(0x02f001),DstDev(0x220200)
Flow Monitor (Activated):
Monitor time: | Mon Jul 17 15:59:58 UTC 2013 |
---------------------------------------------------------
-----------------------------------------------------------------------------------------------
Monitoring a backbone-to-edge flow identified by proxy IDs
48
Flow Vision Administrators Guide
53-1003168-01