Deployment Guide

The following example shows a typical RASLog entry for exceeding the
threshold for the number of Fibre Channel routers in the Backbone fabric:
2014/05/27-17:02:00, [MAPS-1003], 14816, SLOT 4 | FID 20, WARNING, switch_20,
Switch, Condition=SWITCH(BB_FCR_CNT>12), Current Value:[BB_FCR_CNT,13], RuleName=
defSWITCHBB_FCR_CNT_12, Dashboard Category=Fabric State Changes.
The following example shows a typical MAPS dashboard entry for exceeding
the threshold for the number of Fibre Channel routers in the Backbone fabric:
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 |No Errors |No Errors |
Fabric State Changes |Out of operating range |No Errors |
Switch Resource |In operating range |In operating range |
Traffic Performance |In operating range |In operating range |
FCIP Health |No Errors |No Errors |
Fabric Performance Impact|In operating range |In operating range |
3.2 Rules Affecting Health:
===========================
Category(RuleCount) |RptCount|Rule Name |Execution Time |Object|Triggered Value(Units)|
-----------------------------------------------------------------------------------------------------
Fabric State Changes|1 |defSWITCHBB_FCR_CNT_12|05/27/14 17:02:00|Switch|13 |
(1) | | | | | |
Zone configuration size monitoring
In Fabric OS 7.3.0 and later, MAPS can monitor zone configuration size. Based on the platform, a
switch supports either a maximum zone configuration size of 1 MB or 2 MB. The monitoring value is
calculated as a percentage of the zone configuration space used. If the configuration size reaches the
configured threshold limit, MAPS triggers the action configured for the rule and caches the data in the
dashboard. Refer to Default rules for scalability limit monitoring on page 91 for these limit values.
NOTE
MAPS zone configuration size monitoring is only for the default switch, as the total memory size is for
the chassis as a whole. The maximum available zone configuration limit is determined at the chassis
level and shared by all logical switches.
Scalability limit monitoring assumptions and dependencies
The following assumptions and dependencies should be kept in mind when considering scalability limit
monitoring.
• All the scalability limits are soft limits, not hard limits; the monitored value can be greater than 100
percent.
• The Backbone fabric can also have Layer 2 switches; these switches are not considered as part of
any of the scalability limit metrics.
• The number of device connections in an edge fabric or Backbone fabric also have scalability limits
themselves, and these cannot be monitored using MAPS.
• Scalability limit monitoring (using L2_DEVCNT_PER) occurs only at midnight. Therefor, if a switch
is moved from being a part of the Layer 2 fabric to being a part of the edge fabric, the device count
metrics (how many devices in the fabric) will not change until the next midnight.
Zone configuration size monitoring
90 Monitoring and Alerting Policy Suite Administrator's Guide
53-1003147-01