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

MAPS Fabric Performance Impact monitoring and legacy bottleneck
monitoring
The following conditions apply to MAPS Fabric Performance Impact (FPI) monitoring and legacy
bottleneck monitoring:
• MAPS FPI monitoring and the legacy bottleneck monitoring feature are mutually exclusive. If the
legacy bottleneck monitoring feature is not enabled on a switch, MAPS will automatically start
monitoring for impacts on fabric performance when the switch is restarted after upgrading to Fabric
OS 7.3.0. However, if the legacy bottleneck monitoring feature was enabled before the upgrade,
MAPS will not monitor for impacts on fabric performance. To use MAPS FPI monitoring, you will
need to both explicitly disable the legacy bottleneck monitoring feature and enable MAPS FPI
monitoring.
• Once the MAPS FPI monitoring feature is enabled, the legacy bottleneck monitoring feature cannot
be enabled.
• You cannot migrate the legacy bottleneck monitoring configurations to MAPS FPI monitoring. Once
MAPS FPI monitoring is enabled, all monitoring will be done using the predefined MAPS thresholds.
• Legacy bottleneck monitoring must be disabled on every logical switch before you can proceed with
configuring the netmon application using the mapsConfig command.
• Disabling legacy bottleneck monitoring only disables the latency and congestion features, it does
not disable stuck VC monitoring. This means that an AN-1010 RASLog message stating “Severe
latency detected” will still be posted if that condition occurs.
Scalability limit monitoring
MAPS monitors fabric level changes such as logged-in devices count in pure L2 fabric, LSAN devices
count, zone configuration size and number of Fiber Channel Router configurations. These fabric level
monitoring systems have scalability limits. MAPS supports default rules and actions such as RASLog,
SNMP and EMAIL. The results are captured in dashboard under “Fabric State Changes” category.
Using MAPS, user can also define rules with new threshold along with actions.
MAPS can monitor the following scalability limits:
• The number of logged-in device connections in a pure L2 fabric.
• The size of the zone configuration resource that is used.
• The number of Fiber Channel Router configurations.
• The number of imported Logical SAN (LSAN) device connections (this includes both edge fabric
and Backbone fabric device connections).
NOTE
MAPS does not monitor the individual device counts for edge and Backbone fabrics.
When a rule is triggered, the corresponding RASLogs appear in the summary section of the
dashboard. The following example shows two rules (LSan_Dev_Count and L2_Dev_Count) have been
triggered. The column headings in the example have been edited slightly so as to allow the example to
display clearly.
3.1 Summary Report:
===================
Category |Today |Last 7 days |
--------------------------------------------------------------------------------
Port Health |No Errors |No Errors |
Fru Health |In operating range |In operating range |
Security Violations |In operating range |No Errors |
MAPS Fabric Performance Impact monitoring and legacy bottleneck monitoring
88 Monitoring and Alerting Policy Suite Administrator's Guide
53-1003147-01