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

To create a leaning flow in Flow Monitor, complete the following steps.
1. Connect to the switch and log in using an account with admin permissions.
2. Enter flow --create flow_name -feature monitor port_values , using an asterisk in quotes ("*") for
those port and device values you want to be learned.
The following example creates a Flow Monitor learning flow named “ingressTT”
ingressing through port 30 (an E_Port).
switch:admin> flow --create ingressTT -feature monitor -ingrport 30 -srcdev "*" -
dstdev "*"
The following example creates a Flow Monitor learning flow named
“ex_lrn_ingr” which captures traffic ingressing through port 219 headed for
device 20:13:00:05:33:88:a3:90.
switch:admin> flow --create ex_lrn_ingr -feature monitor -ingrport 219 -srcdev "*" -
dstdev 20:13:00:05:33:88:a3:90
Learning Flow creation on offline or slave ports
Flows can be created that specify either an inactive or slave port in their definitions, but activation is
controlled not only by the port status, but by available resources and flow count limits.
• When a flow is created on an offline port, the flow is considered inactive until the port comes online.
However, the flow would only be installed in the ASIC and made active if the resources are
available. If the resources are not available the flow would remain deactivated.
• When a flow is created on a slave port, the flow is considered inactive until the port becomes the
master port. However, the flow would only be installed in the ASIC and made active if the resources
are available. If the resources are not available, the flow would remain deactivated.
Flow Monitor learning on E_Ports and EX_Ports
Flow Monitor supports learning and monitoring all the traffic passing through both E_Ports and
EX_Ports. The captured statistics are similar to the existing learning support provided for F_Ports.
As it is for F_Ports, learning is supported on trunked E_Ports and EX_Ports, and statistics are
gathered only on the flow associated with the master port. These statistics are the cumulative total
from all of the trunked ports. For this reason, you should create and use the same flow definition for
each of the ports in the trunk. You can use either a WWN or a PID value for the srcdev and dstdev
identifiers when creating learning flows.
While the source fabric ID to destination fabric ID option is allowed on any E_Port, it is needed only for
Backbone E_Ports and the XISL_Ports. If the source fabric ID to destination fabric ID combination is
configured on an edge E_Port learning flow, it will display the same source fabric ID to destination
fabric ID combination for all learned flows.
Learning Flow creation on offline or slave ports
38 Flow Vision Administrators Guide
53-1003168-01