Page 1
53-1002999-01 9 September 2013 Flow Vision Administrator’s Guide Supporting Fabric OS v7.2.0
Page 2
Copyright © 2013 Brocade Communications Systems, Inc. All Rights Reserved. ADX, Any IO, Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS, ICX, MLX, My Brocade, Open Script, VCS, VDX, and ...
Page 3
Contents About This Document In this chapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Supported hardware and software . . . . . . . . . . . ...
Page 4
Chapter 2 Flow Monitor In this chapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 Overview of Flow Monitor. . . . . . . . . . . . . . . . . . ....
Page 5
SIM-Port attributes and configuration . . . . . . . . . . . . . . . . . . . . . . . . . .41 Sending traffic using a Fabric Assigned WWN . . . . . . . . . . . . . . . . . . .42 Flow Generator and MAPS ...
Page 6
vi Flow Vision Administrator’s Guide
Page 7
About This Document In this chapter •Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii •Document conventions . . . . . . . . . . . . . . . . . . . . ...
Page 8
Brocade 6520 switch Brocade 6547 embedded switch Brocade 7800 extension switch Brocade VA-40FC Brocade Encryption Switch Brocade DCX Backbone family: Brocade DCX Brocade DCX-4S Brocade DCX 8510 Backbo...
Page 9
Command syntax conventions Command syntax in this manual follows these conventions: command Commands are in bold. --option, option Command options are in bold. -argument, arg Arguments. Optional eleme...
Page 10
Brocade Flow Vision terminology The following terms are used in this document. Term Description Defined flow User-created flow; it can be active or inactive. Local flow Flow defined on the switch on w...
Page 11
White papers, online demonstrations, and data sheets are available through the Brocade website at: http://www.brocade.com/products-solutions/products/index.page For additional Brocade documentation, v...
Page 12
The serial number label is located as follows: Brocade 300, 5100, 5300, 6505, M6505, 6520, 6547, 7800, VA-40FC, and Brocade Encryption Switch—On the switch ID pull-out tab located inside the chassis o...
Page 13
Chapter Flow Vision In this chapter •Overview of Flow Vision. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . •Flow Vision features . . . . . . . . . . . . . . . . ...
Page 14
Flows1 Flows A flow is a set of Fibre Channel (FC) frames or packets that share similar traits, such as an ingress port or egress port identifier or any other data that can be used to differentiate on...
Page 15
Flows When creating or viewing a flow, you can specify any combination of the three features in the flow command. For example: flow --create flowname -feature monitor,generator <parameters> flow...
Page 16
Flows1 Flow frametype parameters Frame monitoring can be done for a variety of frames using predefined -frametype parameters. Table 3 list these parameters and the frames counted for each. On Gbps-cap...
Page 17
Flows Numbers of flows supported Flow Vision supports a maximum of 512 flows on chassis-based platforms and a maximum of flows on fixed-port platforms. However, there is a combined limit from all feat...
Page 18
Flow Vision references1 The following example displays all the existing flows on the switch. switch:admin> flow --show Flow Name Feature Src Dev Dst Dev |Ingr Pt|Egr Pt |Bi Dir| LUN Frame Type| loc...
Page 19
Flow Vision references Firmware upgrading and downgrading and Flow Vision There are no restrictions on upgrading the firmware of a switch that has Flow Vision installed. Downgrading the firmware on a ...
Page 20
Flow Vision references1 Flow Vision Administrator’s Guide
Page 21
Chapter X Flow Monitor In this chapter •Overview of Flow Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . •Flow Monitor management . . . . . . . . . . . . . . ...
Page 22
Flow Monitor management2 Flow Monitor management The following sections describe how to manage the Flow Monitor feature. Creating Flow Monitor flows To create a Flow Monitor flow, enter the flow --cre...
Page 23
Flow Monitor management Creating an inactive flow in Flow Monitor To create an inactive Flow Monitor flow, enter the flow --create command with the -noactivate keyword. flow --create flowname -feature...
Page 24
Flow Monitor management2 Viewing Flow Monitor flows To display Flow Monitor flows, enter flow --show flowname -feature monitor. The displayed information includes: Frame Statistics: Frame count and ra...
Page 25
Flow Monitor examples Resetting Flow Monitor flow statistics To clear the statistics for a Flow Monitor flow, enter flow --reset flowname -feature monitor. The following example clears the statistics ...
Page 26
Flow Monitor examples2 I/O Count I/O Per Sec.(IOPS) I/O bytes Transferred I/O bytes Per Sec. Reads Writes/ Total Reads Writes/ Total Reads Writes/ Total Reads Writes/ Total Viewing summary flow data f...
Page 27
Flow Monitor examples |Ingr Pt|Egr Pt |Bi Dir| LUN Frame Type| |30 |no Denotes feature is currently activated for the flow switch:admin> flow --show ingress TT -feature monitor Name ingresstt Featu...
Page 28
Flow Monitor examples2 |Frame Size(Bytes)| Tx Rx I/O Count I/O Per Sec.(IOPS) I/O bytes Transferred I/O bytes Per Sec. Reads Writes/ Total Reads Writes/ Total Reads Writes/ Total Reads Writes/ Total F...
Page 29
Flow Monitor examples Ingress or egress Top Talker monitor You can use the learn flow (“*”) parameter to create the equivalent to a Top Talker monitor. A Talker monitor is used to identify high volume...
Page 30
Flow Monitor examples2 switch:admin> flow --show egresstt Name egresstt Features: mon(Activated) no Config: Off Definition: Egr Port(0/30),Src Dev(*),Dst Dev(*) Flow Monitor (Activated): Monitor ti...
Page 31
Monitoring Fibre Channel routed fabrics NOTE You cannot create a learned flow in a trunk group. The following example displays the trunked ports and then creates four flows, one for each member of the...
Page 32
Monitoring Fibre Channel routed fabrics2 In Figure 3, the physical devices are A, B, and C, and have the port WWNs a, b, and c, respectively. Figure 4 provides the port WWN values for the following ex...
Page 33
Monitoring Fibre Channel routed fabrics Definition: Ingr Port(219),Src Dev(10:00:00:05:1e:e8:e2:00),Dst Dev(20:00:00:11:0d:e4:18:00) Flow Monitor (Activated): Monitor time: Mon Jun 14:59:58 UTC Rx Fra...
Page 34
Monitoring Fibre Channel routed fabrics2 Backbone-to-edge To monitor a flow from Device C to Device A egressing through EX_Port1, the source device (srcdev) is “Port WWN c”, the destination device (ds...
Page 35
Monitoring Fibre Channel routed fabrics Edge-to-backbone To monitor a flow from Device A to Device C ingressing through EX_Port1, the source device (srcdev) is “Port WWN a”, the destination device (ds...
Page 36
Monitoring Fibre Channel routed fabrics2 Monitoring FC router fabrics using proxy IDs The following examples present flow definitions using deviceidmode set to PID mode. flow --control -deviceidmode p...
Page 37
Monitoring Fibre Channel routed fabrics DCX_Backbone128:admin> switchshow |grep Port Index Slot Port Address Media Speed State Proto id N16 Online FC EX-Port 10:00:00:05:33:ef:f1:1c "Wasp_edge...
Page 38
Monitoring Fibre Channel routed fabrics2 Edge-to-edge through an egress port To monitor a flow from Device B to Device A egressing through EX_Port1, the source device (srcdev) is Device B′, the destin...
Page 39
Monitoring Fibre Channel routed fabrics Backbone-to-edge To monitor a flow from Device C to Device A egressing through EX_Port1, the source device (srcdev) is Device C′, the destination device (dstdev...
Page 40
Monitoring Fibre Channel routed fabrics2 Edge-to-backbone To monitor a flow from Device A to Device C ingressing through EX_Port1, the source device (srcdev) is Device A, the destination device (dstde...