53-1003168-01 27 June 2014 Flow Vision Administrators Guide Supporting Fabric OS v7.3.
© 2014, Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, Brocade Assurance, ADX, AnyIO, DCX, Fabric OS, FastIron, HyperEdge, ICX, MLX, MyBrocade, NetIron, OpenScript, VCS, VDX, and Vyatta are registered trademarks, and The Effortless Network and the On-Demand Data Center are trademarks of Brocade Communications Systems, Inc., in the United States and in other countries. Other brands and product names mentioned may be trademarks of others.
Contents Preface..................................................................................................................................... 7 Document conventions......................................................................................7 Text formatting conventions.................................................................. 7 Command syntax conventions.............................................................. 7 Notes, cautions, and warnings....................................
Creating Flow Monitor learning flows................................................ 37 Learning Flow creation on offline or slave ports............................... 38 Flow Monitor learning on E_Ports and EX_Ports..............................38 Configuring Flow Monitor for a trunk group...................................................39 Monitoring Fibre Channel routed fabrics....................................................... 40 Monitoring FC router fabrics using port WWNs.........................
Activating Flow Mirror flows............................................................................ 80 Automatic activation of a Flow Mirror flow...........................................80 Viewing Flow Mirror flows............................................................................... 80 Summary information view of a Flow Mirror flow................................ 81 Verbose information view of a Flow Mirror flow.................................. 81 Viewing a Flow Mirror flow in time blocks.
Flow Vision Administrators Guide 53-1003168-01
Preface ● Document conventions......................................................................................................7 ● Brocade resources............................................................................................................ 9 ● Contacting Brocade Technical Support.............................................................................9 ● Document feedback........................................................................................................
Notes, cautions, and warnings Convention Description value In Fibre Channel products, a fixed value provided as input to a command option is printed in plain text, for example, --show WWN. [] Syntax components displayed within square brackets are optional. Default responses to system prompts are enclosed in square brackets. {x|y|z} A choice of required parameters is enclosed in curly brackets separated by vertical bars. You must select one of the options.
Brocade resources Brocade resources Visit the Brocade website to locate related documentation for your product and additional Brocade resources. You can download additional publications supporting your product at www.brocade.com. Select the Brocade Products tab to locate your product, then click the Brocade product name or image to open the individual product page. The user manuals are available in the resources module at the bottom of the page under the Documentation category.
Document feedback • Brocade Supplemental Support augments your existing OEM support contract, providing direct access to Brocade expertise. For more information, contact Brocade or your OEM. • For questions regarding service levels and response times, contact your OEM/Solution Provider. Document feedback To send feedback and report errors in the documentation you can use the feedback form posted with the document or you can e-mail the documentation team.
About This Document ● Supported hardware and software.................................................................................. 11 ● What's new in this document...........................................................................................12 ● Brocade Flow Vision terminology....................................................................................
What's new in this document TABLE 2 Brocade DCX Backbone family Gen 4 platform (8-Gpbs) Gen 5 platform (16-Gbps) Brocade DCX Brocade DCX 8510-4 Brocade DCX-4S Brocade DCX 8510-8 What's new in this document The following items are new or revised in this version of the Flow Vision Administrator's Guide: • • • • • • • Supported hardware and software on page 11 Firmware upgrade and downgrade restrictions Predefined flow creation and monitoring Increase in total number of concurrent flows supported Incre
Brocade Flow Vision terminology 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 which the flow command is being run. Root flow Instance of a static flow used to create learned flows. Static flow Flow created when learning is not used. Sub-flow System auto-created flow based on a root flow. There can be more than one sub-flow.
Brocade Flow Vision terminology 14 Flow Vision Administrators Guide 53-1003168-01
Flow Vision ● Overview of Flow Vision..................................................................................................15 ● Roles and access in Flow Vision ....................................................................................16 ● Flow Vision flows.............................................................................................................16 ● Flow Vision licensing...................................................................................................
Flow Vision limitations and considerations Flow Vision limitations and considerations Beyond the individual feature-specific restrictions, the following restrictions and limitations apply to Flow Vision as a whole: • You cannot run Flow Vision and either Advanced Performance Monitor (APM) or Port Mirroring at the same time on a chassis (even across logical switches), as Flow Vision and Port Mirror connections are mutually exclusive.
Flow definitions FIGURE 1 Frame and port parameters Flow definitions To define a flow and configure Flow Vision to monitor that flow, you must provide a unique flow name and specify the flow parameters. These parameters identify the sets of related frames that compose the flow; these can either be explicitly defined or Flow Vision can learn them through observation. NOTE These flow definitions are stored on the switch on which the flow is created, and are not distributed across the fabric.
Duplicate flow definition support TABLE 3 Flow definition rules (Continued) Parameters Field names Rules Frame srcdev • At least one field must be specified. • Values for srcdev and dstdev can be explicit or "*" ("*" indicates learned flows). • Values for lun and frametype must be explicit. • On XISL monitors, the SFID and DFID values are mandatory but srcdev & dstdev are not. dstdev lun frametype NOTE Refer to Table 5 on page 19 for more information on frame types.
Supported port configurations for each application Supported port configurations for each application The following table lists the supported configurations for each Flow Vision feature that can be made using only the basic flow identification parameters (ingrport and srcdev, egrport and dstdev).
Numbers of flows supported TABLE 5 Supported frametype parameters (Continued) Frametype parameter Frames counted scsiwrite Only SCSI write command frames scsirw Both SCSI read and write command frames scsi2reserve Only SCSI 2 reserve command frames scsi3reserve Only SCSI 3 reserve command frames scsi2release Only SCSI 2 release command frames scsi3release Only SCSI 3 release command frames scsi2reserverelease Only SCSI 2 reserve-release command frames scsi3reserverelease Only SCSI 3 reserv
Flow learning NOTE A verification is done for each flow when it is created or activated to ensure that there is no identical flow active. Duplicate flows will not be created or activated when there is a identical flow already active. To create a new flow that duplicates an active flow, you must use the -noactivate keyword as part of the flow --create command. Refer to the “Creating an inactive flow” section of each feature for instructions on creating an inactive flow for that feature.
Viewing flows Viewing flows Flow Vision allows you to view the configuration parameters for each flow on a switch. • To display all Flow Vision flows, enter flow --show. • To display all flows for a specific feature, enter flow --show -feature feature_name. • To display the definition for a specific flow, enter flow --show flow_name -feature feature_name. When you enter flow --show with a flow name, only the flow definition for the specified flow is displayed.
Flow Vision Repeating a Flow Monitor flow The following example creates a Flow Monitor flow named “ag159_flow_2”, and then repeats the output two times: switch:admin> flow --create ag159_flow_2 -feature monitor -srcdev 10:05:00:11:0d:78:45:02 -dstdev 10:00:8c:7c:ff:43:c0:01 -ingrport 3/2 -bidir switch:admin> flow --show ag159_flow_2 -feature monitor -count 2 ======================================================================================================= Name : ag159_flow_2 Features: mon(Activated) n
Flow Vision Repeating a Flow Generator flow The following example creates a Flow Generator flow named “simflow_1”, and then repeats the output three times: switch:admin> flow --create simflow_1 -feature generator -srcdev 07f000 -dstdev 371400 -ingrport 12/16 switch:admin> flow --show simflow_1 -feature generator -count 3 ======================================================================================================= Name : simflow_1 Features: gen(Activated),mon(Activated) noConfig: Off Definition: I
Flow Vision Repeating a Flow Mirror flow The following example creates a bidirectional Flow Mirror flow named “fmcount_cfm” that is mirrored to the CPU, and repeats the output three times: switch:admin> flow --create fmcount_cfm -feature mirror -ingrport 10 -srcdev 010403 -dstdev 020504 bidir switch:admin> flow --show fmcount_cfm -fea mir -count 3 ======================================================================================================= Name : fmcount_cfm Features: mir(Activated) noConfig: Off
Sorting flow output ======================================================================================================= Name : fmcount_lfm Features: mir(Activated) noConfig: Off Definition: IngrPort(14),SrcDev(0x010e00),DstDev(0x010f00),MirPort(16) Flow Mirror (Activated): -------------------------------------------------------------------------------------------No of Mirrored Frames : 1267119, No of RX Mirrored Frames : 1267119, No of TX Mirrored Frames : 0 --------------------------------------------
Flow Vision Sorting a Flow Monitor flow Flow Monitor flows only would nee d sorting if they are a learned flow, as sorting with the dstdev and srcdev explicitly defined would not make sense because there would be only one line of data in the output. The table headings have been edited so that they will display more clearly in this document. The following example creates the Flow Monitor flow “neutrons”, and then shows the output sorted by column 4, the Destination ID.
Flow deletion Sorting a Flow Mirror flow The following example creates a Flow Mirror flow, and then shows the output sorted by column 3, the OXID.
Deleting all flows at one time 1. Connect to the switch and log in using an account with admin permissions. 2. Enter flow --delete flow_name. The named flow is immediately deleted and cannot be recovered. The following example deletes a Flow Monitor flow named “Flow1”. switch:admin> flow --delete Flow1 Deleting all flows at one time To delete all Flow Vision flows at one time, complete the following steps. 1. Connect to the switch and log in using an account with admin permissions. 2.
Clearing the statistics for a specific flow feature Clearing the statistics for a specific flow feature To clear the statistics for specified features of a flow, complete the following steps. 1. Connect to the switch and log in using an account with admin permissions. 2. Enter flow --reset flow_name -feature feature_list. Replace feature_list with either an individual feature or a comma-separated list of features (for example, “generator,monitor” or “mir,mon”). You will not be asked to confirm this action.
Firmware upgrade and downgrade considerations • When an E_Port or F_Port comes online (PORT_ONLINE), if the resources are available, any flows specifying that port will be installed in the ASIC and made active. If the resources are not available, the flow will stay deactivated. • When an E_Port is changed (EPORT_CHANGE), if the resources are available, any flows specifying that port will be installed in the ASIC and made active.
High Availability and Flow Vision Downgrade considerations The following items should be taken into consideration when downgrading to a version of Fabric OS earlier than 7.3.0: • All Flow Vision-related flows or simulation ports must be deleted prior to performing a downgrade to any version of Fabric OS prior to version 7.2.0; if they are not, the downgrade will be blocked and a warning message displayed.
Flow Monitor ● Overview of Flow Monitor ...............................................................................................33 ● Creating Flow Monitor flows............................................................................................34 ● Activating Flow Monitor flows..........................................................................................36 ● Deactivating Flow Monitor flows......................................................................................
Replicating APM monitors using Flow Monitor A sample use case would be to monitor throughput statistics for inbound traffic between a source device and a destination device. Monitoring LUN level statistics on page 52 provides an example of the command and the results for this use case. • Monitoring of various frame types at a switch port to provide deeper insights into storage I/O access patterns at a LUN, reservation conflicts, and I/O errors.
Parameter usage exceptions TABLE 7 Flow Monitor flow parameter combinations (Continued) Parameters Field names Description -bidir Adding this keyword makes the application monitor traffic in both directions. -noactivate Adding this keyword creates the flow without activating it. -noconfig Adding this keyword creates the flow without saving the flow to the configuration.
Activating Flow Monitor flows Activating Flow Monitor flows To activate an inactive Flow Monitor flow, enter flow --activate flowname -feature monitor. Activating a flow automatically clears all the flow statistics for that flow.
Viewing Flow Monitor flows Viewing Flow Monitor flows To display Flow Monitor flows, enter flow --show flowname -feature monitor.
Learning Flow creation on offline or slave ports To create a leaning flow in Flow Monitor, complete the following steps. 1. Connect to the switch and log in using an account with admin permissions. 2. Enter flow --create flow_name -feature monitor port_values , using an asterisk in quotes ("*") for those port and device values you want to be learned. The following example creates a Flow Monitor learning flow named “ingressTT” ingressing through port 30 (an E_Port).
Configuring Flow Monitor for a trunk group FIGURE 2 Learning support in a Fibre Channel Routing fabric The fixed parameters of a learning flow on an E_Port or an EX_Port should use the following combinations when defining flows using specific ingress or egress ports: • For flows using an ingress port (ingrport), the real source ID of the source device and the proxy ID of the destination device.
Monitoring Fibre Channel routed fabrics NOTE You cannot create a learned flow in a trunk group. 3. Enter flow --show flow_name -feature monitor to view the Flow Monitor statistical data for the entire trunk group. NOTE The accumulated Flow Monitor statistical data for the entire trunk group is stored on the master port. If the master port changes, the data is transferred to the new master port. To view this data, you must run the flow --show command on a flow that is defined using the master port.
Monitoring an edge-to-edge flow through an ingress port identified by a WWN FIGURE 3 A Fibre Channel router fabric The following figure provides the port WWN values for the physical devices and port WWNs.
Monitoring an edge-to-edge flow through an egress port identified by a WWN 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 e2e_src_dcx_wwn -feature monitor -ingrport 219 -srcdev 10:00:00:05:1e:e8:e2:00 -dstdev 20:00:00:11:0d:e4:18:00 DCX_Backbone128:admin>flow --show ---------------------------------------------
Monitoring a backbone-to-edge flow identified by WWNs -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 | ----------------------------------------------------------------------------\ ------------------
Monitoring an edge-to-backbone flow identified by WWNs \ -------------------------------------\ ||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(20:02:00:11:0d:51:00:00), DstDev(10:00:00:05:1e:e8:e2:00) Flow Monitor (Activated
Monitoring Fibre Channel router fabrics using proxy IDs Flow Monitor (Activated): Monitor time: | Mon Jul 17 15:59:58 UTC 2013 | -------------------------------------------------------------------------------------------------------------------------------------------------------| Rx Frames Count| Rx Frames per Sec.| Rx Bytes Count| Rx Throughput(Bps)| Avg Rx Frm Sz(Bytes)| -----------------------------------------------------------------------------------------------| 142.93M | 3.74M | 26.97G | 724.
Monitoring an edge-to-edge flow through an ingress port identified by a proxy ID Monitoring an edge-to-edge flow through an ingress port identified by a proxy ID In a network set up as shown in Figure 6 on page 45, for a flow passing from Device A to Device B that is ingressing through EX_Port1, the source device (srcdev) is Device A, the destination device (dstdev) is Device B′, and the ingress port (ingrport) is EX_Port1.
Monitoring an edge-to-edge flow through an egress port identified by a proxy ID | 2.85G | 8.44M | 387.88G | 1.
Monitoring a backbone-to-edge flow identified by proxy IDs | 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.
Monitoring an edge-to-backbone flow identified by proxy IDs | 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.
XISL and Backbone E_Port monitoring -----------------------------------------------------------------------------------------------| Rx Frames Count| Rx Frames per Sec.| Rx Bytes Count| Rx Throughput(Bps)| Avg Rx Frm Sz(Bytes)| -----------------------------------------------------------------------------------------------| 142.93M | 3.74M | 26.97G | 724.
Flow Monitor FIGURE 7 Monitoring fabric statistics on an XISL_Port TABLE 9 Learning support for XISL_Ports and Backbone E_Ports Learned traffic Backbone E_Ports XISL_Ports Intra-fabric traffic Only Backbone fabric traffic is learned. Logical fabric traffic is learned. Inter-fabric traffic Edge-to-edge, Backbone-to-edge, and edge-to-Backbone traffic is learned. Edge-to-edge traffic only is learned. The following figure shows fabric-based monitoring on a Backbone E_Port between BB1 and BB2.
Flow Monitor examples Flow Monitor examples The following examples display how to use the Flow Monitor feature. Monitoring LUN level statistics A common use of flow monitors is to monitor traffic flowing from a particular ingress port to a specified LUN. The following example creates a flow named “lunFlow11” that monitors traffic ingressing on port 5 between device 010502 and device 030700 using LUN 4, and then displays the results of that flow.
Monitoring flows using the learning functionality switch:admin> flow --show sumflow1 -feature monitor ===================================================================================================== Name : sumflow1 Features: mon(Active) noConfig: Off Definition: IngrPort(30),SrcDev(0x010000),DstDev(0x010100) Flow Monitor (Activated): Monitor time: | Tue Jul 16 22:06:32 CLT 2013 | ---------------------------------------------------------------------------------------------------------------------------
XISL_Port or Backbone E_Port flow examples ------------------------------------------------------------------------------------------------------|220200| 01f001 | 2.85G | 8.45M | 387.88G | 1.12G | 132 | ------------------------------------------------------------------------------------------------------|220200| 02f001 | 2.85G | 6.00M | 350.00G | 1.00G | 232 | ------------------------------------------------------------------------------------------------------| * | * | 5.60G | 14.45M | 737.88G | 2.
Legacy use case monitoring Legacy use case monitoring You can create monitoring flows in Flow Vision that provide similar functionality to those available through Advanced Performance Monitor (APM). The following examples cover creating Flow Monitor equivalents for an end-to-end monitor, a frame monitor, and an ingress or egress Top Talker monitor. Creating an end-to-end monitor equivalent You can use the -bidir keyword with the flow command to create the equivalent to an end-to-end monitor.
Creating an ingress or egress Top Talker monitor equivalent | 10.27M | 327.55k | ----------------------------------------=========================================================================== Creating an ingress or egress Top Talker monitor equivalent You can use the learning flow ("*") parameter to create the equivalent to a legacy Top Talker monitor. A Top Talker monitor is used to identify high-volume flows passing a port.
Flow Monitor and High Availability Flow Monitor and High Availability When a High Availability (HA) failover, High Availability reboot, or a power cycle occurs, all flows are deactivated, and statistics for all Flow Monitor flows are not retained. Flow Monitor will begin to gather statistics again when the standby control processor becomes active. After the device is back online, only the first 64 Flow Monitor sub-flows that can be learned are reactivated.
Flow Monitor • The calculated Rx and Tx frame size values displayed in the output are accurate within a range of -4 through +8 bytes. For example, a frame size value of 256 bytes may actually be anywhere from 252 to 260 bytes in size. • For Flow Monitor flows passing through the base switch in a VF-enabled fabric the source fabric ID (SFID) and destination fabric ID (DFID) values must be specified when the flow is defined.
Flow Generator ● Overview of Flow Generator .......................................................................................... 59 ● Creating Flow Generator flows........................................................................................63 ● Activating Flow Generator flows......................................................................................65 ● Learning in Flow Generator flows...................................................................................
Flow Generator setup Once you activate a Flow Generator flow, the flow will stay active until you deactivate the flow. The flow stays active even though the SID and DID SIM-ports are offline. As soon as SID and DID SIMports are online, traffic will start. Flow Generator setup Flow Generator offers several flow control options that you can configure, including the ability to specify both the frame size and the frame payload pattern.
Flow Generator • To run the test on all the ports on the local switch, set all the ports on the switch to SIM ports. • To run the test on one slot only, set only the ports of the slot to SIM ports. • To run the test on any other set of ports, set these specific ports to SIM ports. The frame payload size and pattern control parameters apply to sys_gen_all_simports. The control parameters can be the default, user-defined default, or specific to the sys_gen_all_simports flow.
Notes on predefined flows The following example shows the typical results of the flow -- show command when the sys_gen_all_simports flow is active: switch10:FID128:admin> flow --show ------------------------------------------------------------------------------------------------------Flow Name | Feature | SrcDev | DstDev |IngrPt|EgrPt |BiDir| LUN | FrameType| ------------------------------------------------------------------------------------------------------f1 |gen+,mon+ |* |||5 |no ||| sys_gen_all_simpo
Creating Flow Generator flows Refer to Notes on predefined flows for information on how sys_gen_all_simports behaves with HA and MAPS. Determining how long one pass of sys_gen_all_simports should take The following calculation can be used to estimate how long one full pass should take if all the possible pairings of Source ID and Destination ID are tested. • Flows per port = 4 • Time per iteration = 1 minute • Number of iterations for full run = Integer of ((number of SIM ports -1 ) / flows per port).
Parameter usage exceptions Parameter usage exceptions When you create a flow, it is automatically activated unless you use the -noactivate keyword for the flow --create command. Refer to Creating an inactive flow in Flow Generator on page 64 for an example. The following illustrated example creates a Flow Generator flow named “Flow11” and generates traffic using the ingress SIM port 1/1 from device 040100 (Domain 4) to device 050200 (Domain 5).
Activating Flow Generator flows Activating Flow Generator flows When a flow is activated, traffic is generated by the ingress port or source device for that flow and any sub-flows associated with it as soon as all SIM ports and devices defined in the flow are online. Activating a flow does not automatically clear the flow statistics for that flow; the existing statistic counters resume counting using the resumed flow data.
Viewing Flow Generator flows Viewing Flow Generator flows To display Flow Generator flows, enter flow --show flowname -feature generator. For root and static flows, this command shows the Source ID-Destination ID pairs and the cumulative frame count on the ingress or egress port specified in the flow definition. Displaying the status of a single Flow Generator flow The following example displays the status of the Flow Generator flow named “f2”.
Deactivating Flow Generator flows Deactivating Flow Generator flows You can deactivate Flow Generator flows without deleting them. This allows you to have a “library” of flows that you can activate as needed without having to recreate them. NOTE When a flow is deactivated, traffic stops for that flow and any sub-flows associated with it. When a flow is deactivated, the definition remains but Flow Generator does not populate it with traffic.
Frame payload pattern Frame payload pattern Flow Generator allows you to define the pattern to be used as the frame payload. The frame payload pattern must be an alphanumeric ASCII string between 1 and 32 characters in length. The default frame payload pattern value is 0, which produces a random pattern of alphanumeric ASCII characters with a variable string length between 1 and 32 characters.
Integrating Flow Generator with Flow Monitor The following example creates the flow as shown in the figure above. SIM port 1/1 is the source port and SIM port 1/2 is the destination device. The flow --show flowCase1 -feature generator command displays the SID frame count and then the DID frame count.
Commands related to Flow Generator ---------------------------------------------------------------------------------------------------| 10000| 75.84M | 482.95k | 1568G | 14.47M | 2080 | | 15000| 37.42M | 241.47k | 784.4G | 50.23M | 2080 | | 15100| 37.42M | 241.47k | 784.4G | 50.23M | 2080 | ---------------------------------------------------------------------------------------------------| * | 1.50G | 965.90k | 3137G | 1.
SIM port attributes and configuration switchshow Entering switchshow generates output showing which ports are set as simulation mode ports (SIM ports) and displays the WWN for each emulated device.
Identifying SIM ports ‐ EX_Port ‐ F_Port trunked ‐ Fastwrite port ‐ FCoE port ‐ ICL port ‐ L_Port ‐ M_Port (Mirror Port) ‐ VE port • If a port is configured with CSCTL_mode enabled, you can configure it as a SIM port. • If a port has an Ingress Rate Limit set, you can configure it as a SIM port. • If a port is configured as a SIM port: ‐ You cannot enable QoS. ‐ You cannot enable CSCTL_mode. ‐ You can set an Ingress Rate Limit.
Sending traffic using a Fabric Assigned WWN Permanent Port Name: 20:14:00:05:1e:57:dc:b3 Port Index: 20 Share Area: No Device Shared in Other AD: No Redirect: No Partial: No LSAN: No Port Properties: SIM Port <— Port Properties shows "SIM Port" (output truncated) Sending traffic using a Fabric Assigned WWN If you want to use a Fabric Assigned WWN (FA-WWN), you need to set the FA-WWN on the SIM port using the Dynamic Fabric Provisioning command, fapwwn -assign.
Flow Generator limitations and considerations Flow Generator traffic will also impact E_Ports; this may cause MAPS warnings for E_Port throughput levels. Refer to the Monitoring and Alerting Policy Suite Administrator's Guide for more information about working with MAPS. You can use the Monitoring and Alerting Policy Suite (MAPS) utility to monitor traffic in the sys_gen_all_simports flow using the same default and custom policies as used for F_Ports.
Flow Mirror ● Overview of Flow Mirror.................................................................................................. 75 ● Creating Flow Mirror flows.............................................................................................. 76 ● Activating Flow Mirror flows............................................................................................ 80 ● Viewing Flow Mirror flows..............................................................................................
Creating Flow Mirror flows A sample use case would be to mirror the traffic flow from a slow-draining F_Port to see what is causing this condition. Diagnosing a slow-draining F_Port on page 86 provides an example of this use case. The following figure provides a diagram of a flow that mirrors to the CPU the traffic ingressing through the ingrport. Flow Mirror can similarly mirror the egrport, but only one port (ingrport or egrport) can be mirrored per flow.
Flow Mirror limitations and restrictions TABLE 11 Flow Mirror-supported flow parameter combinations (Continued) Parameters Field names Description -noactivate Adding this keyword creates the flow without activating it. -noconfig Adding this keyword creates the flow without saving the flow to the configuration.
Local flow mirroring For example, on a fixed-port switch, if 500 frames meet the flow definition in the first second of the Flow Mirror operation, only the first 256 frames are mirrored. In the next second, frame mirroring will begin with the five-hundred-and-first frame that matches the flow definition. The intervening frames will not be mirrored, even though they match the flow definition. The following table shows the maximum frame rate and mirroring capacity for each platform type.
Flow Mirror switch:admin> flow --show -----------------------------------------------------------------------------------------------Flow Name |Feature| SrcDev | DstDev |IngrPt|EgrPt|BiDir|LUN|FrameType|SFID|DFID|MirPt| -----------------------------------------------------------------------------------------------sys_gen_all_simports|gen |* |* |* |* |no |- ||||| fmtest |mir+ |010e00 |010f00 |14 ||no |- ||||16 | -----------------------------------------------------------------------------------------------+
Creating an inactive flow in Flow Mirror Creating an inactive flow in Flow Mirror To create an inactive Flow Mirror flow, enter the flow --create flow_name -feature mirror flow_parameters -noactive command. The following example creates an inactive Flow Mirror flow named “mirroredflow120” from device 020a00 to device 01c000 ingressing through port 120.
Summary information view of a Flow Mirror flow Summary information view of a Flow Mirror flow To display the summary view of a Flow Mirror flow, enter flow --show flow_name -feature mirror. In the summary information view, the first output line lists the flow name and the flow features; the second line lists the source and destination devices and ports, and the flow’s directionality; the third line identifies the active features.
Viewing a Flow Mirror flow in time blocks -----------------------------------------------------------------------------------------------------| Jul 12 06:29:13:637 | Rx | SOFn3 | EOFn | Data | ---| 01040f00 00040200 08000008 … | | Jul 12 06:29:51:614 | Rx | SOFi3 | EOFt | PRLI | ---| 22fffc04 00040200 01290000 … | | Jul 12 06:29:51:622 | Rx | SOFi3 | EOFt | 01 | ---| 23fffc04 00040200 01990000 … | | Jul 12 06:29:51:625 | Rx | SOFi3 | EOFt | 01 | ---| 23fffc04 00040200 01990000 … | | Jul 12 06:30:10:951 |
Learning in Flow Mirror flows Flow Mirror (Activated): -------------------------------------------------------------------------------------| OXID | RXID | SOF | EOF | Frame_type | LUN(*) | Dir | Time-Stamp | -------------------------------------------------------------------------------------| 0001 | ffff | SOFn3 | EOFn | Data | ---| Tx | Jun 05 09:45:47:100 | | 0044 | ffff | SOFn3 | EOFn | Data | ---| Rx | Jun 05 09:45:47:100 | | 0001 | ffff | SOFn3 | EOFn | Data | ---| Tx | Jun 05 09:45:47:100 | (output
Deactivating Flow Mirror flows Deactivating Flow Mirror flows Flow Mirror flows can be deactivated without deleting them. This allows you to have a “library” of flows that you can activate as needed without having to create them repeatedly. To manually deactivate a Flow Mirror flow, enter flow --deactivate flow_name -feature mirror.
Mirroring traffic flowing to remote fabrics Mirroring traffic flowing to remote fabrics Flow Vision allows you to mirror traffic that is flowing to a remote fabric. To mirror traffic that is flowing to a remote fabric, in the flow definition you must specify the imported port ID or real PWWN of the device in the other fabric. The following illustration shows how such a mirroring situation might be constructed.
Troubleshooting using Flow Mirror + Denotes feature is currently activated for the flow switchP2:admin> flow --show fm_edge1_edge2 -feature mirror ======================================================================================================= Name : fm_edge1_edge2 Features: mir(Activated) noConfig: Off Definition: IngrPort(3/22),SrcDev(0x010000),DstDev(0x02f001),MirPort(3/43) Flow Mirror (Activated): -------------------------------------------------------------------------------------------No of Mi
Tracking SCSI commands 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(*)
Tracking latency between a host and all connected targets FIGURE 17 SCSI command tracking Tracking latency between a host and all connected targets In order to smooth out application performance, you may want to track the latency of SCSI InitiatorTarget pairs so that you can load balance them. The following examples capture all the SCSI commands and their status frames initiated by device H1 ingressing through port F1, as illustrated by the following figure.
Troubleshooting protocol errors Tracking latency using a CPU-mirrored flow To track the latency using a CPU-mirrored flow, you create the flow and then use the flow --show command to view the captured results. In this case, the latency is an approximate latency (best effort latency), because the latency is an approximate latency block completion time. You can use the time stamps on the appropriate frames and deduce the latency from those values.
Flow Mirror and High Availability switch:admin> flow --show fm_abts ======================================================================================================= = Name : fm_abts Features: mir(Activated) noConfig: Off Definition: IngrPort(3/4),SrcDev(*),DstDev(*),FrameType(abts) Flow Mirror (Activated): ------------------------------------------------------------------------------------------------------| SID(*) | DID(*) | OXID | RXID | SOF | EOF | Frame_type | LUN(*) | Dir | Time-Stamp | -------
