Brocade Network Advisor SAN User Manual v12.3.0 User Manual
Page 1212
1160
Brocade Network Advisor SAN User Manual
53-1003154-01
Flow Monitor
29
7. Enter the egress port data in Port (slot/port) or D,I (domain ID,port number) format in the
Egress field.
NOTE
You must enter the slot number and the port number. For Backbone chassis, the slot number
cannot be 0 (zero). For switches, you must enter 0 (zero) as the slot number. For logical (virtual)
switches, follow the rule for the physical chassis (either Backbone chassis or switch) from
which you created the logical switch.
8. Click OK.
The Flow Vision dialog box displays with the new flow definition highlighted.
9. Repeat
through
for each trunk port in the group.
10. Select OK to save the definition.
When the flow definition activates, the Flow Vision dialog box displays with the new flow
selected (highlighted) in the Flow Definitions table.
To view the Flow Monitor statistical data for the entire trunk group, select the master port flow
definition in the Flow Definitions table and click the right arrow button to display it in the Flows
table.
The accumulated Flow Monitor statistical data for the entire trunk group is stored on the
master port. If the master port changes, the data is transferred to the new master port.
You cannot display Flow statistics for slave trunk ports.
To review the sub-flow data for the selected flow, refer to
“Monitoring a Flow Monitor flow”
FC router fabrics Flow Monitor flow example procedures
You can create Flow Monitor flow definitions using port WWNs, port IDs, and fabric IDs (FC router).
When creating flow monitors on EX_Ports, you can use either a WWN or a port ID for the source
device and destination device or you can use the fabric ID for the FCR/XISL source fabric and
destination fabric. Inter-Fabric Link (IFL) flows can be monitored only on 16 Gbps-capable EX_Ports
in an FC router. IFL flows are not supported on E_Ports or F_Ports.
When monitoring an FC router fabric, you may find it simpler to use port WWNs rather than virtual
port IDs in your flow definitions. This is because you do not need to locate and map the virtual port
IDs for the actual source and destination devices.
Even though you always create a flow definition in the backbone fabric, the perspective of the flow
is from the edge fabric. In the following examples, the flow definitions are based on the perspective
of the Edge 1 fabric .