Brocade Monitoring and Alerting Policy Suite Administrators Guide (Supporting Fabric OS v7.3.0) - Manual (Page 72)

‐ Number of SCSI I/O bytes read as recorded for the flow.
‐ Number of SCSI I/O bytes written as recorded for the flow.
For more information on Flow Vision, refer to the Flow Vision Administrator's Guide.
Statistics produced by the FV Flow Monitor feature are displayed in the MAPS dashboard in the
“Switch Health Report” section's Traffic Performance subsection. This data is not included in the
History Data section of the MAPS dashboard. Refer to the “MAPS Dashboard” portion of this guide for
examples and additional information.
Restrictions on Flow Vision flow monitoring
A Flow Vision flow can be imported and monitored using MAPS any time after it has been defined in
Flow Vision, subject to the following restrictions:
• It must be a flow created using the Flow Monitor feature.
• The flow must be active. In Fabric OS 7.3.0 and later, both static and learned flows (sub-flows
created using an asterisk (*)) can be imported and monitored.
• When importing a flow, the flow name must be specified. Once a flow is imported to MAPS, you can
define MAPS rules to monitor the flow. Each rule has a threshold criterion and alerting mechanism
defined. If the threshold criterion is met, then a configured alert is generated.
• MAPS monitoring starts after a flow has been both activated in Flow Vision and imported into
MAPS. Deactivating a flow causes monitoring to stop until it is reactivated. When the flow is
reactivated, monitoring automatically restarts.
• If you do not want to continue monitoring an imported flow, it can be removed (deimported) from
MAPS. Refer to Removing flows from MAPS on page 72 for more information.
Removing flows from MAPS
If you do not want to monitor a flow using MAPS, use the mapsConfig --deimport flow_name -force
command to remove the flow from MAPS.
You can only remove one flow at a time. Removing a flow only removes it from MAPS, it does not
affect the flow definition in Flow Vision. If you do not use the -force option, removing a flow will
succeed only if you have deleted all the rules associated with that flow.
To remove a flow from MAPS, complete the following steps.
1. Enter logicalGroup --show to see the list of flows imported into MAPS.
2. Identify the flows you want to remove from MAPS.
3. Enter mapsConfig --deimport flow_name -force.
The following example removes the flow named “myflow22” from MAPS.
switch:admin> mapsconfig --deimport myflow22 -force
If a flow is deleted in Flow Vision
If you delete a Flow Vision flow that has not been imported into MAPS, there is no change in MAPS. If
you delete a Flow Vision flow that has been imported into MAPS, the flow is marked as deleted, but
the group corresponding to the flow will remain. Groups are only removed if the flow --deimport
command is used.
If a flow is deleted in Flow Vision, MAPS will not automatically begin monitoring that flow if it is
recreated. If you try to import a flow with the same name as the deleted flow, the import will fail and a
Restrictions on Flow Vision flow monitoring
72 Monitoring and Alerting Policy Suite Administrator's Guide
53-1003147-01