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

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. However,
there will not be a check in MAPS for maximum throughput for SIM ports, as Flow Generator always
runs at maximum throughput.
Flow Generator limitations and considerations
The following limitations apply specifically to Flow Generator:
• If used on a live production system, Flow Generator traffic will compete with any existing traffic.
Consequently, E_Ports and FCIP links can become congested when using Flow Generator, leading
to throughput degradation. FCIP links are more prone to congestion than E_Ports.
• Only four active Flow Generator flows are allowed per ingress port.
• Flow Generator flows can only be mirrored at the ingress port; they cannot be mirrored at the
egress port.
• Flow Generator is not supported on Access Gateways or for Fibre Channel routers.
• Frame redirection is not supported for SIM ports.
• Zoning is not enforced. Sources and destinations can be in different zones.
• Flow Generator gathers source and destination pairs from the zoning database for learning flows
only at the time the flow is activated. Subsequent changes to this database will not be registered
until a flow is reactivated.
• If a SIM port configuration is deleted while the port is online, Flow Vision automatically stops all
Flow Generator flows, but the flows are not deactivated.
Flow Generator limitations and considerations
74 Flow Vision Administrators Guide
53-1003168-01