Deployment Guide
| Tx Frames Count| Tx Frames per Sec.| Tx Bytes Count| Tx Throughput(Bps)|Avg Tx Frm Sz(Bytes)|
-----------------------------------------------------------------------------------------------
| 142.93M | 3.74M | 26.97G | 724.78M | 204 |
-----------------------------------------------------------------------------------------------
Monitoring an edge-to-backbone flow identified by proxy IDs
In a network set up as shown in Figure 6 on page 45, for a flow passing from Device A to Device C that
is ingressing through EX_Port1, the source device (srcdev) is Device A, the destination device (dstdev)
is Device C′, and the ingress port (ingrport) 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 an edge fabric to the
backbone fabric using a specific ingress port. The first two commands show the available ports and the
available Fibre Channel routers. The third command creates a Flow Monitor flow named “e2b_src_dcx”
between device 220200 and device 02f001 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> 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 e2b_src_dcx -feature monitor -ingrport 219
-srcdev 220200 -dstdev 02f001
DCX_Backbone128:admin> flow --show
------------------------------------------------------------------------- \
Flow Name | Feature | SrcDev | DstDev \
------------------------------------------------------------------------- \
e2b_src_dcx |mon+ |220200 |02f001 \
------------------------------------------------------------------------- \
\ ----------------------------------------
\ |IngrPt|EgrPt|BiDir| LUN | FrameType|
\ ----------------------------------------
\ |219 |- |no |- |- |
\ ----------------------------------------
+ Denotes feature is currently activated for the flow
DCX_Backbone128:admin> flow --show e2b_src_dcx -feature monitor
===========================================================================
Name: e2b_src_dcx Features: mon(Active) noConfig: Off
Definition: IngrPort(219),SrcDev(0x220200),DstDev(0x02f001)
Flow Monitor (Activated):
Monitor time: | Mon Jul 17 15:59:58 UTC 2013 |
---------------------------------------------------------
Monitoring an edge-to-backbone flow identified by proxy IDs
Flow Vision Administrators Guide 49
53-1003168-01