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

Differences between Fabric Watch and MAPS configurations
The monitoring and alerting configurations available in the MAPS are not as complex as those available
in Fabric Watch; as a consequence MAPS lacks some of the functionality available in Fabric Watch.
The following table shows the differences between Fabric Watch and MAPS configurations and
functionality.
Comparison of Fabric Watch and MAPS configurations and functionality TABLE 4
Configuration Fabric Watch behavior MAPS behavior
End-to-End monitoring
(Performance Monitor class) Supported Supported through flows.
Frame monitoring
(Performance Monitor class) Supported Supported through flows.
RX, TX monitoring Occurs at the individual physical
port level. Occurs at the trunk or port level as applicable.
Pause/Continue behavior Occurs at the element or counter
level. For example, monitoring
can be paused for CRC on one
port and for ITW on another port. Occurs at the element level. Monitoring can be
paused on a specific port, but not for a specific
counter on that port.
CPU/Memory polling interval Can configure the polling interval
as well as the repeat count.
This configuration can be migrated from Fabric
Watch, but cannot be changed.
E-mail notification
configuration Different e-mail addresses can be
configured for different classes. E-mail configuration supported globally.
Temperature sensor
monitoring Can monitor temperature values. Can monitor only if the sensor state is in or out
of range).
Differences between Fabric Watch and MAPS configurations
Monitoring and Alerting Policy Suite Administrator's Guide 17
53-1003147-01