53-1002999-01 9 September 2013 Flow Vision Administrator’s Guide Supporting Fabric OS v7.2.
Copyright © 2013 Brocade Communications Systems, Inc. All Rights Reserved. ADX, AnyIO, Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS, ICX, MLX, MyBrocade, OpenScript, VCS, VDX, and Vyatta are registered trademarks, and HyperEdge, The Effortless Network, and The On-Demand Data Center are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. Other brands, products, or service names mentioned may be trademarks of their respective owners.
Contents About This Document In this chapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii Text formatting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii Command syntax conventions . . . . . . . . . . .
Chapter 2 Flow Monitor In this chapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 Overview of Flow Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 Flow Monitor management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 Creating Flow Monitor flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 Activating Flow Monitor flows . . . . . . . . . . . . . . . . . .
SIM-Port attributes and configuration . . . . . . . . . . . . . . . . . . . . . . . . . .41 Sending traffic using a Fabric Assigned WWN . . . . . . . . . . . . . . . . . . .42 Flow Generator and MAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 Flow Generator and High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . .43 Flow Generator limitations and considerations . . . . . . . . . . . . . . . . . .43 Chapter 4 Flow Mirror In this chapter. . . . . . . . . . . .
vi Flow Vision Administrator’s Guide 53-1002999-01
About This Document In this chapter • Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii • Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii • Brocade Flow Vision terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x • Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x • Additional information . . . . . . .
- 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 Backbone family: - Brocade DCX 8510-4 - Brocade DCX 8510-8 • Brocade blades: - Brocade FC8-32E - Brocade FC8-48E Document conventions This section describes text formatting conventions and important notice formats used in this document.
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 element. variable Variables are in italics. ... Repeat the previous element, for example “member[;member...]” value Fixed values following arguments are in plain font. For example, --show WWN | Boolean. Elements are exclusive.
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.
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, visit the Brocade Info Center and click the Resource Library location: http://www.brocade.com Release notes are available on the My Brocade website and are also bundled with the Fabric OS firmware. Other industry resources For additional resource information, visit the Technical Committee T11 website.
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 on the port side on the left • Brocade 5410, 5424, 5430, 5431, 5450, 5460, 5470, 5480—Serial number label attached to the module • Brocade 6510—On the pull-out tab on the front of the switch • Brocade DCX and DCX 8510-8—On the bottom right on the port side of the chassis • Brocade DCX-4S and DCX 8510-4—On t
Chapter 1 Flow Vision In this chapter • Overview of Flow Vision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Flow Vision features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Flow Vision references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Flows 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 one set of related frames or packets from a different set. These parameters are specified as part of the flow command, and include: • Port parameters: (also called the Point of Interest, or where the data you want to examine is from) This consists of an ingress port (ingrport) or an egress port (egrport).
Flows 1 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 flow --show flowname -feature mirror,generator Flow definition rules The rules listed in Table 1 identify what parameters can be used to define a flow.
1 Flows 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 8 Gbps-capable Fibre Channel platforms, possible frame monitoring flow classifiers include egrport, dstdev, and lun. On 16 Gbps-capable Fibre Channel platforms, including the Brocade FC8-32E and FC8-48E blades, possible frame monitoring flow classifiers include ingrport, egrport, dstdev, srcdev, and lun.
Flows 1 Numbers of flows supported Flow Vision supports a maximum of 512 flows on chassis-based platforms and a maximum of 128 flows on fixed-port platforms. However, there is a combined limit from all features of 64 flows (including static flows, root flows, and sub-flows, whether active or inactive) for any one port. In addition, there are individual limits for each Flow Vision feature; Table 4 lists these limits.
1 Flow Vision references The following example displays all the existing flows on the switch.
Flow Vision references 1 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 switch with Flow Vision installed will fail if any Flow Vision-related configurations are present on the switch being downgraded. 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.
1 8 Flow Vision references Flow Vision Administrator’s Guide 53-1002999-01
ChapterX 2 Flow Monitor In this chapter • Overview of Flow Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 • Flow Monitor management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 • Flow Monitor examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 • Monitoring Fibre Channel routed fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 • Flow Monitor references . . . . . . .
2 Flow Monitor management 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 --create flowname -feature monitor parameters command using the parameters in Table 5. Figure 1 on page 2 illustrates how the frame and port parameters apply to a flow. Table 5 shows the supported Flow Monitor flow parameter combinations.
Flow Monitor management 2 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 monitor flow_parameters -noactivate Refer to “Activating Flow Monitor flows” on page 11 for information on activating a Flow Monitor flow. The following example creates an inactive Flow Monitor flow named “sflow8” from device 020a00 to device 01c000 ingressing through port 10.
2 Flow Monitor management Viewing Flow Monitor flows To display Flow Monitor flows, enter flow --show flowname -feature monitor.
Flow Monitor examples 2 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 for the Flow Monitor flow named “Flow1”. switch:admin> flow --reset Flow1 -feature monitor Flow Monitor examples The following examples display how to use the Flow Monitor feature.
2 Flow Monitor examples | 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 | ------------------------------------------------------------------------------------------------| 44.92k/ 44.94k/ 89.85k| 2.00k/ 2.00k/ 4.01k| 5.88M/ 5.89M/ 11.77M| 2.62M/ 2.62M/ 5.
Flow Monitor examples 2 -------------------------------------------------------------------------------------\ --------------------------------------|IngrPt|EgrPt |BiDir| LUN | FrameType| |30 ||no ||| --------------------------------------+ Denotes feature is currently activated for the flow switch:admin> flow --show ingressTT -feature monitor =============================================================================================== Name : ingresstt Features: mon(Active) noConfig: Off Definition: Ing
2 Flow Monitor examples -------------------------------------------------------------------------------------------------\ | 65.11M/129.63M/194.75M|962.52k/653.84k/ 1.61M| 99.49G/185.44G/284.93G|958.32M/957.77M/ 1.87G \ -------------------------------------------------------------------------------------------------\ ------------------|Frame Size(Bytes)| | Tx / Rx | | 1632 / 1528 | ------------------------------------------------------------------------------------------------------------------| I/O Count
Flow Monitor examples 2 Ingress or egress Top Talker monitor You can use the learn flow (“*”) parameter to create the equivalent to a Top Talker monitor. A Top Talker monitor is used to identify high volume flows passing a port. This monitor is only supported on F_Ports. The following example creates both an ingress and an egress Top Talker monitor.
2 Flow Monitor examples switch:admin> flow --show egresstt ======================================================================================================== Name : egresstt Features: mon(Activated) noConfig: Off Definition: EgrPort(0/30),SrcDev(*),DstDev(*) Flow Monitor (Activated): Monitor time: | Fri Aug 30 23:25:35 UTC 2013 | ----------------------------------------------------------------------------------------------------------------------------------------------------\ |SID(*)|DID(*)| Tx Fra
Monitoring Fibre Channel routed fabrics 2 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 trunk group identified by the switchshow command.
2 Monitoring Fibre Channel routed fabrics 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 examples.
Monitoring Fibre Channel routed fabrics 2 Definition: IngrPort(219),SrcDev(10:00:00:05:1e:e8:e2:00),DstDev(20:00:00:11:0d:e4:18:00) Flow Monitor (Activated): Monitor time: | Mon Jun 17 14:59:58 UTC 2013 | ------------------------------------------------------------------------------------------------------------------------------------------------------------| Rx Frames Count | Rx Frames per Sec.
2 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 “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). The following example creates a flow that filters out frames passing from the backbone fabric to an edge fabric using a specific egress port.
Monitoring Fibre Channel routed fabrics 2 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 (dstdev) is “Port WWN c”, and the ingress port (ingrport) is EX_Port1 (Traffic is running from left to right). The following example creates a flow that filters out frames passing from an edge fabric to the backbone fabric using a specific ingress port.
2 Monitoring Fibre Channel routed fabrics Monitoring FC router fabrics using proxy IDs The following examples present flow definitions using deviceidmode set to PID mode. flow --control -deviceidmode pid FIGURE 5 An FC router fabric In Figure 5, the physical devices are A, B, and C. The proxy devices are Device A′, B′, C′, A″, B″, and C″, representing the physical devices A, B, and C, respectively. Figure 6 provides the PID, FID, and proxy PID values for the following examples.
Monitoring Fibre Channel routed fabrics 2 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 "Wasp_edge2" (fabric id = 50 )(Trunk master) 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 "Honeybee_edge1" (fabric id = 100 )(Trunk master) E-Port 50:00:51:e4:91:9e:0f:28 "fcr_xd_2_100" DCX_Backbone128:admin> fcrproxydevshow Prox
2 Monitoring Fibre Channel routed fabrics 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 destination device (dstdev) is Device A, and the egress port (egrport) is EX_Port1 (Traffic is running from right to left). The following example creates a flow that filters out frames passing from one edge fabric to another edge fabric using a specific egress port on the backbone.
Monitoring Fibre Channel routed fabrics 2 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) is Device A, and the egress port (egrport) is EX_Port1 (Traffic is running from right to left). The following example creates a flow that filters out frames passing from the backbone fabric to an edge fabric using a specific egress port.
2 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 Device A, the destination device (dstdev) is Device C′, and the ingress port (ingrport) is EX_Port1 (Traffic is running from left to right). The following example creates a flow that filters out frames passing from an edge fabric to the backbone fabric using a specific ingress port.
Flow Monitor references 2 Flow Monitor references The following sections provide additional information about Flow Monitor. Flow monitors and MAPS Flow Monitor statistics can be viewed using the Monitoring and Alerting Policy Suite (MAPS) service. This can help you identify critical administrative information such as traffic patterns, bottlenecks, and slow drains. Refer to the Monitoring and Alerting Policy Suite Administrator’s Guide for more details.
2 Flow Monitor references • Learning is supported on 16 Gbps F_Ports only. • Only one learned flow is supported per ASIC. • Flow Monitor can only monitor flows using EX_Ports on 16 Gbps-capable Fibre Channel platforms. • The frame type parameters scsiread, scsiwrite, and scsirdwr monitor only SCSI 6-, 10-, 12-, and 16-bit Read and Write values. Read Long and Write Long values are not monitored. • • • • • • • 30 Flow Monitor is not supported on ports with Encryption or Compression enabled.
Chapter 3 Flow Generator In this chapter • Overview of Flow Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Flow Generator management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Flow Generator examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Flow Generator references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 Flow Generator management Flow Generator flows are defined using a combination of the source device (srcdev), destination device (dstdev), ingress port (ingrport), and egress port (egrport) parameters.All of these must be SIM-Ports. The source device is the origination point of the test traffic. The destination device is the destination of the test traffic; for Flow Generator flows it may be remote from the switch.
Flow Generator management 3 Parameter usage exceptions • If the srcdev and ingrport parameters are both defined, they must both be local to the switch and refer to the same source. • If the dstdev and egrport parameters are both defined for the flow, they must both be local to the switch and represent the same destination.
3 Flow Generator management 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. The following example activates the Flow Generator flow named “Flow1”. switch:admin> flow --activate Flow1 -feature generator NOTE A flow can be activated with SIM-Ports that are offline or which have not been created.
Flow Generator management 3 Definition: IngrPort(1/9),SrcDev(0x010900),DstDev(0x01c100) Flow Generator (Activated): ----------------------| SrcDev | DstDev | ----------------------| 0x010900 | 0x01c100 | ----------------------Number of frames generated from IngrPort : 595.41M Note: More than 1 flow active on this port.
3 Flow Generator management Notes on displaying the status of a Flow Generator flow • If you want to see the per-flow frame count on a port with multiple flows, you must include the flow monitoring feature in the flow definition (flow --create flowname -feature generator, monitor). • If there is more than one static flow active on the port, Flow Generator will append a note stating such at the bottom of the output.
Flow Generator management 3 Resetting Flow Generator flow statistics To manually clear the frame count statistics for a Flow Generator flow, enter flow --reset flowname -feature generator. The following example clears the statistics for the Flow Generator flow named “Flow1”. switch:admin> flow --reset Flow1 -feature generator Customizing Flow Generator flows Flow Generator allows you to specify the frame payload size and pattern to be used for the Flow Generator flows by using the flow --control command.
3 Flow Generator examples Changing a flow frame payload pattern Assigning a frame payload pattern explicitly to a flow affects only that flow and overrides the existing frame payload pattern for that flow. Changing a payload pattern can only be done to an inactive flow. The following example sets the default payload pattern for the flow F2 to “a5a5a5”.
Flow Generator examples 3 -------|------|--------|-------------------------|--------------------|------------------| Addressing mode information Port Addressing Mode: index Device Addressing Mode: PID Flow Generator Information Size: 2048 Pattern: Random (Default) Flow mirror Information enable_wrap Integrating Flow Generator with Flow Monitor Flow Generator flows can be monitored using Flow Monitor.
3 Flow Generator references Flow Generator references The following sections provide additional information about Flow Generator. Commands related to Flow Generator The following commands affect or are affected by Flow Generator. portcfgshow Entering portcfgshow for a specified port shows the configuration of the SIM-Port. (Highlighted in red for illustration.) switch:admin> portcfgshow Area Number: Octet Speed Combo: Speed Level: AL_PA Offset 13: . . . . .
Flow Generator references 3 switchshow Entering switchshow generates output showing which ports are set as simulation mode ports (SIM-Ports) and displays the WWN for each emulated device.
3 Flow Generator references • SIM-Ports cannot be configured as any of the following port types; these restrictions also apply at the time a SIM-Port is enabled: - Any port running Encryption or Compression Any F_Port connected to a real device (unless the port is disabled) D_Port (Diagnostic Port) E_Port EX_Port F_Port trunked Fastwrite port FCoE port ICL port L_Port M_Port (Mirror Port) VE port • The following features of a SIM-Port are persistent across a reboot: - Each SIM-Port is assigned a PID an
Flow Generator references 3 Flow Generator and MAPS MAPS can be used to monitor SIM-Port traffic thresholds while Flow Generator flows are running. Because MAPS treats SIM-Ports as F_Ports, MAPS can issue warnings on these ports if threshold values are triggered. If you do not want to see MAPS warnings for SIM-Ports, disable MAPS monitoring for those ports. Flow Generator traffic will also impact E_Ports; this may cause MAPS warnings for E_Port throughput levels.
3 44 Flow Generator references Flow Vision Administrator’s Guide 53-1002999-01
Chapter 4 Flow Mirror In this chapter • Overview of Flow Mirror. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Flow Mirror management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Troubleshooting using Flow Mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Flow Mirror references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 Flow Mirror management Figure 10 provides a diagram of a mirrored flow with the ingrPort mirroring the traffic flow to the CPU. Flow Mirror can also mirror the egrPort, but only one port (ingrPort or egrPort) can be mirrored per flow. To mirror from one port in both flow directions (left to right and right to left), you must use the -bidir option. FIGURE 10 A flow being mirrored to the CPU Flow Mirror management The following sections describe how to work with Flow Mirror.
Flow Mirror management 4 The following example creates a Flow Mirror flow named “Flow1” that monitors all traffic flowing from device 010403 to device 020504 ingressing through port 10 on the switch on which this command was run. switch:admin> flow --create Flow1 -feature mirror -ingrport 10 -srcdev 010403 -dstdev 020504 When you create a flow, it is automatically activated unless you use the -noactivate keyword as part of the flow --create command.
4 Flow Mirror management Viewing Flow Mirror flows The following sections describe the different ways you can view Flow Mirror flows. Summary information view of a Flow Mirror flow To display the summary view of Flow Mirror flows, enter flow --show flowname -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.
Flow Mirror management 4 In the verbose 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. The following lines list for each frame the time stamp of the frame, the direction of the frame, the start of frame and end of frame values, the frame type, and the first 64 bytes (16 words) of the frame.
4 Flow Mirror management The following example shows the frame rates for the Flow Mirror flow named “fmshow” at 10-second intervals. In this output at the beginning of t (time), the frame rate is not displayed, but at t+10, t+20, and so on, the frame rate is displayed. This rate is based on the difference between the cumulative number of frames mirrored within the specified interval.
Flow Mirror management 4 | 040200 | 040f00 | 8058 | ffff | SOFi3 | EOFt | ELSframe | ---| Rx | Jul 12 06:32:11:091 | -------------------------------------------------------------------------------------------No of Mirrored Frames: 2, No of RX Mirrored Frames: 2, No of TX Mirrored Frames: 0 -------------------------------------------------------------------------------------------================================================================================================== [1]+ Stopped Repeating Flow
4 Flow Mirror management Deleting Flow Mirror flows To delete a Flow Mirror flow, enter flow --delete flowname. You do not need to include -feature mirror, as you can only delete the entire flow; you cannot delete an individual feature from a flow. Deleting a flow automatically clears all the flow statistics for that flow. Deleting an active flow automatically deactivates the flow before it is deleted. The following example deletes the Flow Mirror flow named “Flow1”.
Troubleshooting using Flow Mirror 4 Troubleshooting using Flow Mirror The following use cases describe how to use Flow Mirror to troubleshoot typical fabric performance problems. Using Flow Mirror to diagnose SCSI reserve and SCSI release performance If there is excessive SCSI reserve and release activity in a virtualized environment, you can use Flow Mirror to identify the affected LUNs.
4 Troubleshooting using Flow Mirror FIGURE 11 A Flow Mirror revealing a slow drain switch:admin> flow --create flow_slowdrain -feature mirror –egrport 15 –dstdev 0x040500 -srcdev 0x010200 -bidir switch:admin> flow --show flow_slowdrain -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
Flow Mirror references 4 Flow Mirror references The following sections provide additional information about Flow Mirror. Flow Mirror and High Availability On High Availability (HA) failover, HA reboot, or a power cycle, Flow Mirror will stop mirroring frames until the system recovers; at which point it will resume mirroring.
4 56 Flow Mirror references Flow Vision Administrator’s Guide 53-1002999-01
Index A Access Gateways, flow monitoring on, 29 activating Flow Generator flows, 33 Flow Mirror flows, 47 Flow Monitor flows, 11 asterisk (*) to indicate a learned flow, 5 B backward compatibility in Flow Monitor, 30 C command configdefault, 6 configdownload, 6 configupload, 6 fapwwn –assign, 42 flow --activate, 11, 33, 45, 47 --control, 37, 41, 52 --create, 10, 32, 33, 46, 47 --deactivate, 11, 36, 51 --delete, 12, 18, 36, 52 --reset, 13, 37, 40, 52 --show, 5, 12, 34, 35, 37, 48, 49, 51 --show -ctrlcfg,
creating Flow Generator flows, 32 Flow Mirror flows, 46 Flow Monitor flows, 10 customizing Flow Generator flows, 37 Flow Mirror flows, 52 deactivating Flow Generator flows, 36 Flow Mirror flows, 51 Flow Monitor flows, 11 defined, 2 deleting Flow Generator flows, 36 Flow Mirror flows, 52 Flow Monitor flows, 12 frametype parameters, 4 generating, 31–43 learned output, viewing, 35 learning Flow Generator flows, 34 Flow Mirror flows, 51 Flow Monitor flows, 12 Flow Vision flows, 5 mirroring, 45–56 monitor manage
supported functionality, 45 time block view, 49 viewing flows, 48–51 Flow Monitor, 9–30 backward compatibility, 30 creating inactive flows, 11 flow activation, 11 flow creation, 10 flow deactivation, 11 flow deletion, 12 flow learning, 12 flow parameter combinations, 10 High Availability, 29 limitations, 29 management, 10–13 MAPS and, 29 overview, 9 repeating output, 12 resetting flows, 13 sorting output, 12 viewing flows, 12 Flow Vision configuration database, 6 flow learning, 5 licensing, 6 Flow Vision in
M S MAPS Flow Generator and, 43 Flow Monitor and, 29 Flow Vision and, 6 SIM ports, 43 mirrored flows activating, 47 customizing, 52 deactivating, 51 deleting, 52 learning, 5, 51 resetting, 52 viewing, 48–51 mirroring flows, 45–56 monitor flows activating, 11 creating, 10 deactivating, 11 deleting, 12 learning, 12 resetting, 13 viewing, 12 Monitoring and Alerting Policy Suite. See: MAPS.
