Users Guide

4 Monitoring and Alerting Policy Suite Administrator’s Guide
53-1002933-02
Migrating from Fabric Watch to MAPS
1
CAUTION
MAPS activation is a non-reversible process. Downgrading to Fabric OS 7.1 will enable Fabric
Watch with its last configured settings. When you upgrade back to Fabric OS 7.2, Fabric Watch
will continue to be enabled.
Differences between Fabric Watch and MAPS configurations
The MAPS monitoring and alerting configurations are not as complex as those available in
Fabric Watch; consequently MAPS does not have some functionality that was available in
Fabric Watch.
Table 1 shows differences between Fabric Watch and MAPS configurations.
TABLE 1 Differences between Fabric Watch and MAPS configurations
Configuration Fabric Watch behavior MAPS behavior
End-to-End monitoring
(Performance Monitor class)
Supported. Supported through flows. Refer to
“Monitoring end-to-end performance”
on page 37 for details.
Frame monitoring
(Performance Monitor class)
Supported. Supported through flows. Refer to
“Monitoring frames for a specified set
of criteria” on page 37 for details.
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 the states of the
sensors (In_Range or Out_of_range).