Flow vision limitations and considerations, Roles and access in flow vision, Flow vision flows – Brocade Flow Vision Administrators Guide (Supporting Fabric OS v7.3.0) User Manual
Page 16: Roles and access in flow vision flow vision flows
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. This means that legacy Port Mirroring-related operations are
not allowed if any Flow Vision flow (active or defined) is present on a switch, and no Flow Vision
flows can be created or run if legacy Port Mirroring is enabled.
• Port swap functionality is not supported.
Roles and access in Flow Vision
Flow Vision can be accessed by users with the following roles: Admin, Switch Admin, or Fabric Admin.
Flow Vision 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). Only one can be
specified when defining a flow.
• Frame parameters: These are the following parameters: Source Device Identification (SID or
WWN), Destination Device Identification (DID or WWN), LUN, or frame type. At least one frame
parameter must be present to define a flow. Refer to
details on frame types.
• Direction: A direction is implicitly defined from an ingress port to an egress port, or a source device
(srcdev) to a destination device (dstdev). For example, srcdev=x, dstdev=y indicates traffic flowing
from x to y. The -bidir option causes the flow definition to be monitored in both directions. This
makes the following true:
‐
Entering srcdev=x dstdev=y specifies that only traffic flowing from x to y is the desired
flow.
‐
Entering srcdev=x dstdev=y -bidir specifies that traffic traveling from x to y and traffic
traveling from y to x are both desired flows.
The following figure illustrates how the frame and port parameters apply to a flow.
Flow Vision limitations and considerations
16
Flow Vision Administrators Guide
53-1003168-01