Flow vision features, Flow mirror, Limitations and prerequisites – Brocade Network Advisor SAN + IP User Manual v12.1.0 User Manual

Page 1650: Flow mirror 4, Flow vision features 4

Advertising
background image

1604

Brocade Network Advisor SAN + IP User Manual

53-1002949-01

Flow Vision features

44

Flow Vision features

This section provides detailed information on the Flow Generator, Flow Mirror, and Flow Monitor
features.

Flow Mirror

You can define flows with the feature enabled to select a traffic pattern and mirror this traffic
to the CPU. You can then monitor sub-flows resulting from the definition to listen or snoop on
traffic passing through a port.

Flow Mirror supports the following functions:

-

Sending mirrored frames to the CPU.

-

Mirroring frames in Layer 2 fabric.

-

Mirroring frames only on F_Ports.

-

In-depth analysis of flows of interest such as SCSI reservation frames, ABTS frames, flows
to bottlenecked devices, and frames during link bring-up.

Limitations and prerequisites

The following limitations and prerequisites apply specifically to the Flow Mirror feature.

Statistic counts displayed in the Flow Vision dialog box should not be inferred as accurate at
this time. Counts greater than zero do imply that the mirrored flow is functioning.

Mirrored frames are not displayed as with Fabric OS commands.

This feature is supported only on 16 Gbps-capable Fibre Channel platforms

You cannot enable Flow Mirror on more than one active flow definition per switch.

This feature requires a Fabric Vision license on the switch where you are enabling the feature.

This feature is not supported across Fibre Channel Routing (FCR).

N_Ports cannot be ingress or egress ports.

L_Ports cannot be ingress or egress ports.

Flow Mirroring is supported in VF mode.

Flow Mirror is not supported on the following ports:

-

DISL ports

-

E_Ports

-

EX_Ports

-

E_Port Trunks and F_Port trunks

-

XISL ports

-

Shared ports

Flow Mirroring is not supported in Access Gateway mode or across a Fibre Channel Router
backbone fabric.

If a 16-Gbps ingress port is specified when creating a flow, then the rate of outbound traffic
from that port may be reduced by as much as half. To prevent this, it is recommended that you
specify the ingress port and egress port values only when absolutely needed.

Advertising