Users Guide

Monitoring and Alerting Policy Suite Administrator’s Guide 35
53-1002933-02
Chapter
5
Monitoring flows using MAPS
In this chapter
•Flows and MAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
•Monitoring flows using MAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Flows and MAPS
MAPS can monitor only static flows created using Flow Vision and generates alert messages based
on user-defined rules. To monitor a flow, the flow must first be created in Flow Vision, and then
imported into MAPS. For information on working with Flow Vision, refer to the Fabric OS Flow Vision
Administrator’s Guide.
NOTE
Only the statistics monitoring functionality is supported in MAPS. The Flow Generator and
Flow Mirror features are not integrated with MAPS.
Importing flows
A flow can be imported any time after it has been defined in Flow Vision. Only static flows can be
imported into MAPS. Learned flows (those created using an asterisk (*)) cannot be imported or
monitored. When importing a flow, the flow name must be specified.
Only active flows can be monitored in MAPS. MAPS monitoring starts after a flow has both been
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.
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.
The following example imports an existing flow named “myflow22” into MAPS.
switch:admin> mapsconfig --import myflow22
Removing flows from MAPS
If you do not want to monitor a flow using MAPS, use mapsConfig --deimport flow name to remove
the flow from MAPS.
The following example removes the flow named “myflow22” from MAPS.
switch:admin> mapsconfig --deimport myflow22