Brocade Flow Vision Administrators Guide (Supporting Fabric OS v7.3.0) - Manual (Page 77)

Flow Mirror-supported flow parameter combinations (Continued) TABLE 11
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.
The following example creates a Flow Mirror flow named “flowmirror14” that
mirrors traffic flowing from device “080e00 “ to device “080f00” ingressing
through the port 14 on the switch on which this command was run.
switch:admin> flow --create flowmirror14 -feature mirror -ingrport 14 -srcdev 080e00 -
dstdev 080f00
Mirror feature(s) have been activated.
Flow Mirror limitations and restrictions
The following limitations and restrictions apply specifically to Flow Mirror flows and flow mirroring:
• Flow Mirror is supported only on Gen 5 Fibre Channel platforms.
• Only one active Flow Mirror flow is supported per chassis or fixed-port switch.
• Active Flow Mirror flows are mutually exclusive with the In-Flight Encryption/Compression feature on
a blade or fixed-port switch. However, if Flow Mirror flows can exist on one blade and In-Flight
encryption/compression can be enabled on a different blade in the same chassis, then they can co-
exist.
• You cannot simultaneously mirror to a local port (LFM) and to the CPU (CFM). These are mutually
exclusive.
• A mirror port cannot be either an ingress or egress port of the flow definition.
• The flow --create enable_wrap and flow --create disable_wrap _wrap command are only
applicable to CPU flow mirroring.
• The mirror port should always be in the local domain.
• For bidirectional traffic, if the combined traffic rate exceeds the limit of the mirror port traffic limit, then
the Flow Mirror flow is not permitted. (For example, the combined rate of a bidirectional flow from a
16 Gbps port is 32 Gbps, and so cannot be mirrored to a 16 Gbps mirror port.)
• If a flow monitor flow defined using the “-frametype” keyword as part of the flow command is installed
on an ingress port, and a matching Flow Mirror flow is installed on an egress port, then traffic
egressing through the egress port is not mirrored.
• If a flow is created for both Flow Monitor and Flow Mirror that uses a combination of either the “-
frametype” and “-ingrport” keywords, or a combination of “-frametype”, “-egrport”, and “bidir”
keywords, frames matching these definitions will be monitored but will not be mirrored.
• If a Flow Monitor flow is created on a blade or fixed-port switch that uses a combination of either the
“-frametype” and “-ingrport” keywords, or a combination of “-frametype”, “-egrport”, and “bidir”
keywords, then Flow Mirror frames matching any flow definitions defined using the “-ingrport”
keyword that use ports on the same blade or fixed-port switch are not mirrored.
• Flow Mirror is not supported in Access Gateway mode or on SIM ports that are specified as ingress
or egress ports in the flow definition.
• Flow Mirror cannot mirror:
‐ Frames belonging to device-switch communication (for example, a FLOGI or PLOGI action)
‐ Link Primitives, discarded frames, frames from a remote Control Unit Port (CUP), Link
Control Frames, or frames containing domain controller addresses used as source IDs
• For flows mirrored to a CPU, only the first 256 frames are mirrored. If a greater number of frames that
match the flow definition within a second are identified, those later frames are not mirrored.
Flow Mirror limitations and restrictions
Flow Vision Administrators Guide 77
53-1003168-01