Brocade Monitoring and Alerting Policy Suite ... · Supporting Fabric OS 7.3.0, Fabric OS 7.3.1, and Fabric OS 7.3.2 ADMINISTRATION GUIDE Brocade Monitoring and Alerting Policy Suite

Supporting Fabric OS 7.3.0, Fabric OS 7.3.1, and Fabric OS 7.3.2

ADMINISTRATION GUIDE

Brocade Monitoring and Alerting Policy SuiteAdministration Guide, 7.3.x

53-1003147-0720 October 2016

© 2016, Brocade Communications Systems, Inc. All Rights Reserved.

Brocade, the B-wing symbol, and MyBrocade are registered trademarks of Brocade Communications Systems, Inc., in the United States and in othercountries. Other brands, product names, or service names mentioned of Brocade Communications Systems, Inc. are listed at www.brocade.com/en/legal/brocade-Legal-intellectual-property/brocade-legal-trademarks.html. Other marks may belong to third parties.

Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any equipment,equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document at any time, withoutnotice, and assumes no responsibility for its use. This informational document describes features that may not be currently available. Contact a Brocadesales office for information on feature and product availability. Export of technical data contained in this document may require an export license from theUnited States government.

The authors and Brocade Communications Systems, Inc. assume no liability or responsibility to any person or entity with respect to the accuracy of thisdocument or any loss, cost, liability, or damages arising from the information contained herein or the computer programs that accompany it.

The product described by this document may contain open source software covered by the GNU General Public License or other open source licenseagreements. To find out which open source software is included in Brocade products, view the licensing terms applicable to the open source software, andobtain a copy of the programming source code, please visit http://www.brocade.com/support/oscd.

Brocade Monitoring and Alerting Policy Suite Administration Guide, 7.3.x2 53-1003147-07

http://www.brocade.com/en/legal/brocade-Legal-intellectual-property/brocade-legal-trademarks.html

http://www.brocade.com/en/legal/brocade-Legal-intellectual-property/brocade-legal-trademarks.html

http://www.brocade.com/support/oscd

ContentsPreface...................................................................................................................................................................................................................................7

Document conventions............................................................................................................................................................................................................................7Notes, cautions, and warnings.....................................................................................................................................................................................................7Text formatting conventions......................................................................................................................................................................................................... 7Command syntax conventions....................................................................................................................................................................................................8

Brocade resources.....................................................................................................................................................................................................................................8Document feedback..................................................................................................................................................................................................................................8Contacting Brocade Technical Support............................................................................................................................................................................................ 9

Brocade customers..........................................................................................................................................................................................................................9Brocade OEM customers............................................................................................................................................................................................................. 9

About This Document..................................................................................................................................................................................................... 11Supported hardware and software...................................................................................................................................................................................................11

Brocade Gen 4 platform (8-Gpbs) Fixed-port switches...............................................................................................................................................11Brocade Gen 5 platform (16-Gbps) Fixed-port switches............................................................................................................................................11Brocade Gen 4 platform (8-Gpbs) DCX Backbone family..........................................................................................................................................12Brocade Gen 5 platform (16-Gbps) DCX Backbone family.......................................................................................................................................12

What's new in this document............................................................................................................................................................................................................. 12Changes made for 53-1003147-01 (27 June 2014)...............................................................................................................................................12Changes made for 53-1003147-02 (15 August 2014)..........................................................................................................................................12Changes made for 53-1003147-03 (15 September 2014)..................................................................................................................................13Changes made for 53-1003147-04 (17 June 2015)...............................................................................................................................................13Changes made for 53-1003147-05 (24 July 2015)................................................................................................................................................ 13Changes made for 53-1003147-06 (16 February 2016)...................................................................................................................................... 13Changes made for 53-1003147-07 (20 October 2016)........................................................................................................................................14

Glossary...................................................................................................................................................................................................................................................... 15

Monitoring and Alerting Policy Suite Overview ........................................................................................................................................................ 17MAPS overview ...................................................................................................................................................................................................................................... 17MAPS license requirements............................................................................................................................................................................................................... 18MAPS configuration...............................................................................................................................................................................................................................18

Automated generation of default configuration................................................................................................................................................................ 18User-created configuration........................................................................................................................................................................................................18Deleting a user-created MAPS configuration....................................................................................................................................................................18

MAPS interaction with other Fabric OS features....................................................................................................................................................................... 18Restrictions on MAPS monitoring................................................................................................................................................................................................... 19Firmware upgrade and downgrade considerations for MAPS.............................................................................................................................................19

Firmware upgrade considerations.......................................................................................................................................................................................... 19Firmware downgrade considerations.................................................................................................................................................................................... 19

Fabric Watch to MAPS migration ....................................................................................................................................................................................................20Differences between Fabric Watch and MAPS configurations...................................................................................................................................20

MAPS Setup and Operation...........................................................................................................................................................................................21Initial MAPS setup.................................................................................................................................................................................................................................. 21

Enabling MAPS using Fabric Watch rules...........................................................................................................................................................................21Enabling MAPS without using Fabric Watch rules...........................................................................................................................................................22

Monitoring across different time windows....................................................................................................................................................................................23Setting the active MAPS policy to a default policy................................................................................................................................................................... 24

Brocade Monitoring and Alerting Policy Suite Administration Guide, 7.3.x53-1003147-07 3

Pausing MAPS monitoring................................................................................................................................................................................................................. 25Resuming MAPS monitoring.............................................................................................................................................................................................................25

MAPS Elements and Categories ..................................................................................................................................................................................27MAPS structural elements.................................................................................................................................................................................................................. 27MAPS monitoring categories ........................................................................................................................................................................................................... 27

Port Health........................................................................................................................................................................................................................................28FRU Health.......................................................................................................................................................................................................................................29Security Violations ........................................................................................................................................................................................................................29Fabric State Changes...................................................................................................................................................................................................................30Switch Resources ......................................................................................................................................................................................................................... 31Traffic Performance.......................................................................................................................................................................................................................31FCIP Health .................................................................................................................................................................................................................................... 32Fabric Performance Impact.......................................................................................................................................................................................................33Switch Status Policy......................................................................................................................................................................................................................34

MAPS Groups, Conditions, Rules, and Policies......................................................................................................................................................... 35MAPS groups overview........................................................................................................................................................................................................................35

Viewing group information ....................................................................................................................................................................................................... 35Predefined groups.........................................................................................................................................................................................................................36User-defined groups.................................................................................................................................................................................................................... 38Cloning a group.............................................................................................................................................................................................................................. 42Deleting groups.............................................................................................................................................................................................................................. 42

MAPS conditions.................................................................................................................................................................................................................................... 42Threshold values............................................................................................................................................................................................................................ 43Timebase...........................................................................................................................................................................................................................................43

MAPS rules overview............................................................................................................................................................................................................................ 45MAPS rule actions.........................................................................................................................................................................................................................46Working with MAPS rules and actions..................................................................................................................................................................................51

MAPS policies overview.......................................................................................................................................................................................................................58Viewing policy values................................................................................................................................................................................................................... 58Predefined policies........................................................................................................................................................................................................................59User-defined policies................................................................................................................................................................................................................... 60Fabric Watch legacy policies.....................................................................................................................................................................................................60Working with MAPS policies ....................................................................................................................................................................................................60

Port monitoring using MAPS.........................................................................................................................................................................................65Port monitoring and pausing..............................................................................................................................................................................................................65Monitoring groups of ports using the same conditions..........................................................................................................................................................65Port monitoring using port names...................................................................................................................................................................................................66Port monitoring using device WWNs ............................................................................................................................................................................................66Adding a port to an existing static group.......................................................................................................................................................................................66Adding missing ports to a dynamic group ..................................................................................................................................................................................67Removing ports from a group........................................................................................................................................................................................................... 68D_Port monitoring.................................................................................................................................................................................................................................. 68

Monitoring Flow Vision flows with MAPS...................................................................................................................................................................71Viewing Flow Vision Flow Monitor data with MAPS................................................................................................................................................................71

Flow Vision statistics supported by MAPS.........................................................................................................................................................................72Restrictions on Flow Vision flow monitoring......................................................................................................................................................................73Removing flows from MAPS....................................................................................................................................................................................................73Sub-flow monitoring and MAPS.............................................................................................................................................................................................74


Monitoring traffic performance..........................................................................................................................................................................................................74Monitoring end-to-end performance ...................................................................................................................................................................................74Monitoring frames for a specified set of criteria............................................................................................................................................................... 74

Monitoring learned flows......................................................................................................................................................................................................................75Excessive throughput notification........................................................................................................................................................................................... 75Possible bottleneck notification............................................................................................................................................................................................... 75

MAPS dashboard ............................................................................................................................................................................................................ 77MAPS dashboard overview................................................................................................................................................................................................................ 77

MAPS dashboard sections........................................................................................................................................................................................................77MAPS dashboard display options.......................................................................................................................................................................................... 80

Viewing the MAPS dashboard.......................................................................................................................................................................................................... 80Viewing a summary switch status report............................................................................................................................................................................. 81Viewing a detailed switch status report.................................................................................................................................................................................83Viewing historical data................................................................................................................................................................................................................. 85Viewing data for a specific time window .............................................................................................................................................................................86

Clearing MAPS dashboard data....................................................................................................................................................................................................... 88

Other MAPS monitoring capabilities........................................................................................................................................................................... 89Fabric performance impact monitoring using MAPS..............................................................................................................................................................89

Enabling MAPS Fabric Performance Impact monitoring............................................................................................................................................. 89Bottleneck detection with the MAPS dashboard ............................................................................................................................................................ 90MAPS Fabric Performance Impact monitoring and legacy bottleneck monitoring...........................................................................................91

Scalability limit monitoring.................................................................................................................................................................................................................. 91Layer 2 fabric device connection monitoring.................................................................................................................................................................... 92LSAN device connection monitoring in a metaSAN...................................................................................................................................................... 92Backbone fabric Fibre Channel router count monitoring..............................................................................................................................................93Zone configuration size monitoring....................................................................................................................................................................................... 93Scalability limit monitoring assumptions and dependencies...................................................................................................................................... 93Default rules for scalability limit monitoring........................................................................................................................................................................94Examples of scalability limit rules........................................................................................................................................................................................... 94

MAPS Service Availability Module...................................................................................................................................................................................................95MAPS monitoring for Extension platforms..................................................................................................................................................................................97

Brocade FCIP monitoring parameters and groups.........................................................................................................................................................97

Updating monitoring policy for 4 PSU devices......................................................................................................................................................... 99

MAPS Threshold Values...............................................................................................................................................................................................101Viewing monitoring thresholds.......................................................................................................................................................................................................101Fabric state change monitoring thresholds...............................................................................................................................................................................102Extension monitoring thresholds...................................................................................................................................................................................................102FRU state monitoring thresholds.................................................................................................................................................................................................. 103Port Health monitoring thresholds................................................................................................................................................................................................103

D_Port default Port Health monitoring thresholds....................................................................................................................................................... 103E_Port default Port Health monitoring thresholds....................................................................................................................................................... 104F_Port default Port Health monitoring thresholds........................................................................................................................................................105Non-F_Port default Port Health monitoring thresholds.............................................................................................................................................106

Resource monitoring thresholds....................................................................................................................................................................................................107Security monitoring thresholds...................................................................................................................................................................................................... 107SFP monitoring thresholds..............................................................................................................................................................................................................107

10 Gbps and 16 Gbps SFP monitoring threshold defaults.....................................................................................................................................108Quad SFPs and all other SFP monitoring threshold defaults................................................................................................................................. 108


Fabric Performance Impact thresholds.......................................................................................................................................................................................108Switch status policy monitoring thresholds...............................................................................................................................................................................109

Aggressive policy default Switch Status monitoring thresholds and actions ................................................................................................... 109Moderate policy default Switch Status monitoring thresholds and actions ...................................................................................................... 110Conservative policy default Switch Status monitoring thresholds and actions.................................................................................................111Base policy default Switch Status monitoring thresholds and actions.................................................................................................................112

Traffic Performance thresholds...................................................................................................................................................................................................... 113


Preface• Document conventions...................................................................................................................................................................................... 7• Brocade resources............................................................................................................................................................................................... 8• Document feedback............................................................................................................................................................................................ 8• Contacting Brocade Technical Support.......................................................................................................................................................9

Document conventionsThe document conventions describe text formatting conventions, command syntax conventions, and important notice formats used inBrocade technical documentation.

Notes, cautions, and warningsNotes, cautions, and warning statements may be used in this document. They are listed in the order of increasing severity of potential

hazards.

NOTEA Note provides a tip, guidance, or advice, emphasizes important information, or provides a reference to related information.

ATTENTIONAn Attention statement indicates a stronger note, for example, to alert you when traffic might be interrupted or the device mightreboot.

CAUTIONA Caution statement alerts you to situations that can be potentially hazardous to you or cause damage to hardware,firmware, software, or data.

DANGERA Danger statement indicates conditions or situations that can be potentially lethal or extremely hazardous to you. Safetylabels are also attached directly to products to warn of these conditions or situations.

Text formatting conventionsText formatting conventions such as boldface, italic, or Courier font may be used to highlight specific words or phrases.

Format Description

bold text Identifies command names.

Identifies keywords and operands.

Identifies the names of GUI elements.

Identifies text to enter in the GUI.

italic text Identifies emphasis.

Identifies variables.

Identifies document titles.

Courier font Identifies CLI output.

Identifies command syntax examples.


Command syntax conventionsBold and italic text identify command syntax components. Delimiters and operators define groupings of parameters and their logicalrelationships.

Convention Description

bold text Identifies command names, keywords, and command options.

italic text Identifies a variable.

value In Fibre Channel products, a fixed value provided as input to a command option is printed in plain text, forexample, --show WWN.

[ ] Syntax components displayed within square brackets are optional.

Default responses to system prompts are enclosed in square brackets.

{ x | y | z } A choice of required parameters is enclosed in curly brackets separated by vertical bars. You must selectone of the options.

In Fibre Channel products, square brackets may be used instead for this purpose.

x | y A vertical bar separates mutually exclusive elements.

< > Nonprinting characters, for example, passwords, are enclosed in angle brackets.

... Repeat the previous element, for example, member[member...].

\ Indicates a “soft” line break in command examples. If a backslash separates two lines of a commandinput, enter the entire command at the prompt without the backslash.

Brocade resourcesVisit the Brocade website to locate related documentation for your product and additional Brocade resources.

White papers, data sheets, and the most recent versions of Brocade software and hardware manuals are available at www.brocade.com.Product documentation for all supported releases is available to registered users at MyBrocade.Click the Support tab and select Document Library to access documentation on MyBrocade or www.brocade.com You can locatedocumentation by product or by operating system.

Release notes are bundled with software downloads on MyBrocade. Links to software downloads are available on the MyBrocade landingpage and in the Document Library.

Document feedbackQuality is our first concern at Brocade, and we have made every effort to ensure the accuracy and completeness of this document.However, if you find an error or an omission, or you think that a topic needs further development, we want to hear from you. You canprovide feedback in two ways:

• Through the online feedback form in the HTML documents posted on www.brocade.com

• By sending your feedback to [email protected]

Provide the publication title, part number, and as much detail as possible, including the topic heading and page number if applicable, aswell as your suggestions for improvement.

Brocade resources


http://www.brocade.com

http://my.Brocade.com





mailto:[email protected]

Contacting Brocade Technical SupportAs a Brocade customer, you can contact Brocade Technical Support 24x7 online, by telephone, or by e-mail. Brocade OEM customersshould contact their OEM/solution provider.

Brocade customersFor product support information and the latest information on contacting the Technical Assistance Center, go to www.brocade.com andselect Support.

If you have purchased Brocade product support directly from Brocade, use one of the following methods to contact the BrocadeTechnical Assistance Center 24x7.

Online Telephone E-mail

Preferred method of contact for non-urgentissues:

• Case management through the MyBrocade portal.

• Quick Access links to KnowledgeBase, Community, Document Library,Software Downloads and Licensingtools

Required for Sev 1-Critical and Sev 2-Highissues:

• Continental US: 1-800-752-8061

• Europe, Middle East, Africa, and AsiaPacific: +800-AT FIBREE (+800 2834 27 33)

• Toll-free numbers are available inmany countries.

• For areas unable to access a toll-freenumber: +1-408-333-6061

[email protected]

Please include:

• Problem summary

• Serial number

• Installation details

• Environment description

Brocade OEM customersIf you have purchased Brocade product support from a Brocade OEM/solution provider, contact your OEM/solution provider for all ofyour product support needs.

• OEM/solution providers are trained and certified by Brocade to support Brocade® products.

• Brocade provides backline support for issues that cannot be resolved by the OEM/solution provider.

• Brocade Supplemental Support augments your existing OEM support contract, providing direct access to Brocade expertise.For more information, contact Brocade or your OEM.

• For questions regarding service levels and response times, contact your OEM/solution provider.

Contacting Brocade Technical Support


https://www.brocade.com

https://login.brocade.com/

http://www.brocade.com/services-support/international_telephone_numbers/index.page

mailto:[email protected]


About This Document• Supported hardware and software..............................................................................................................................................................11• What's new in this document........................................................................................................................................................................12• Glossary.................................................................................................................................................................................................................15

Supported hardware and softwareIn those instances in which procedures or parts of procedures documented here apply to some switches but not to others, this listidentifies exactly which switches are supported and which are not.

Certain versions of Fabric OS software support connections to the Brocade Analytics Monitoring Platform. For more information aboutthe Brocade Analytics Monitoring Platform, including which versions of Fabric OS can interact with it, refer to the Brocade AnalyticsMonitoring Platform Release Notes.

Although many different software and hardware configurations are tested and supported by Brocade Communications Systems, Inc. forFabric OS 7.3.2, documenting all possible configurations and scenarios is beyond the scope of this document.

The following hardware platforms are supported by this release of Fabric OS:

Brocade Gen 4 platform (8-Gpbs) Fixed-port switches• Brocade 300 switch

• Brocade 5100 switch


• Brocade 5410 blade server SAN I/O module









• Brocade NC-5480 blade server SAN I/O module

• Brocade 7800 extension switch

• Brocade VA-40FC switch

• Brocade Encryption Switch

Brocade Gen 5 platform (16-Gbps) Fixed-port switches• Brocade 6505 switch

• Brocade M6505 blade server SAN I/O module






• Brocade 7840 extension switch

Brocade Gen 4 platform (8-Gpbs) DCX Backbone family• Brocade DCX

• Brocade DCX-4S

Brocade Gen 5 platform (16-Gbps) DCX Backbone family• Brocade DCX 8510-4

• Brocade DCX 8510-8

What's new in this document

Changes made for 53-1003147-01 (27 June 2014)The following content is new or significantly revised for the first release of this document:

• Added new options in mapsSam --show command to show specific detail.

• Added new options in mapsRule and logicalGroup commands to force changes.

• Added new options in mapsConfig command to send test e-mails.

• Enhanced D_Port monitoring.

• Added new default monitoring groups.

• Added new “Port Decommissioning” action.

• Added new dynamic user-defined groups and sub-flow monitoring.

• Added ability to monitor throughput degradation.

• Added ability to monitor device connection scalability limits.

• Added ability to monitor switch Ethernet management ports.

• Added ability to monitor Brocade 7840 device for tunnel-level QoS.

• Added ability to monitor Brocade 7840 device using tunnel-level and circuit parameters.

• Revised MAPS and Fabric Performance Impact (bottleneck) monitoring.

Changes made for 53-1003147-02 (15 August 2014)The following content is new or significantly revised for the second release of this document:

• In Port Health on page 28, added note describing what is included in the ITW counter to the table.

• Updated Port fencing and port decommissioning on page 48.



Changes made for 53-1003147-03 (15 September 2014)The following content is new or significantly revised for the third release of this document:

• In Predefined groups on page 36, added “ALL_2K_QSFP” row to table.

Changes made for 53-1003147-04 (17 June 2015)The following content is new or significantly revised for the fourth release of this document:

• Globally, corrected examples to use “-timebase” instead of “-t”.

• In the following topics, corrected examples to use two hyphens rather than one (for example “-create” should be “--create”.

– Creating a static user-defined group on page 38– Creating a dynamic user-defined group on page 39– Port monitoring using device WWNs on page 66– Monitoring learned flows on page 75

• In Monitoring end-to-end performance on page 74, added line to examples that enables the policy, and added note.

• In Viewing Flow Vision Flow Monitor data with MAPS on page 71, updated steps and example to include enabling the policywith the new flow and rule.

• In Flow Vision statistics supported by MAPS on page 72, added MAPS elements to list .

• Added Updating monitoring policy for 4 PSU devices on page 99.

Changes made for 53-1003147-05 (24 July 2015)The following content is new or significantly revised for the fifth release of this document:

• Added content for "Rule for zone configuration size" in Examples of scalability limit rules on page 94.

• Modified "Zone Configuration size" value in Timebase on page 43.

Changes made for 53-1003147-06 (16 February 2016)The following content is new or significantly revised for the sixth release of this document:

• A statement was added in Supported hardware and software on page 11 that helps readers find more information about theBrocade Analytics Monitoring Platform.

• A Glossary on page 15 was added.

• The following topics were revised for accuracy and clarity:

– MAPS configuration on page 18 (previously titled "MAPS configuration files")– Restrictions on MAPS monitoring on page 19– Pausing MAPS monitoring on page 25– MAPS structural elements on page 27– Switch Status Policy on page 34– MAPS groups overview on page 35– Viewing group information on page 35– Predefined groups on page 36– User-defined groups on page 38– Deleting groups on page 42– Viewing policy information on page 61– MAPS conditions on page 42– Threshold values on page 43



– Timebase on page 43– MAPS rules overview on page 45– MAPS rule actions on page 46– E-mail alerts on page 46– Port fencing and port decommissioning on page 48– Configuring port decommissioning on page 49– MAPS SNMP traps on page 47 (previously titled "SNMP traps")– Modifying a MAPS rule on page 53 (previously titled "Modify a MAPS policy rule")– Rule deletion on page 55– E-mail alert testing on page 56– Monitoring groups of ports using the same conditions on page 65 (previously titled "Monitoring similar ports using the

same rules)– Port monitoring using device WWNs on page 66– Adding a port to an existing static group on page 66 (previously titled "Adding a port to an existing group")– Adding missing ports to a dynamic group on page 67 (previous titled "Adding missing ports to a group")– Removing ports from a group on page 68– MAPS dashboard display options on page 80– Summary Report section on page 77– Viewing a summary switch status report on page 81

Changes made for 53-1003147-07 (20 October 2016)To be consistent with changes made within MyBrocade.com, the title of this document has been changed to Brocade Monitoring andAlerting Policy Suite Administration Guide. The following content is new or significantly revised for the seventh release of this document:

• Added information to MAPS configuration on page 18.

• Updated the content in Setting the active MAPS policy to a default policy on page 24.

• Added information to MAPS structural elements on page 27.

• Updated information in Port Health on page 28.

• Added information to FRU Health on page 29.

• Restructured and updated information in Fabric State Changes on page 30.

• Added information to Switch Resources on page 31.

• Updated information in FCIP Health on page 32.

• Updated information in Fabric Performance Impact on page 33.

• Updated information in Switch Status Policy on page 34.

• Updated information in Modifying a dynamic user-defined group on page 40.

• Corrected the heading of Restoring a group to its default membership on page 41.

• Corrected information in Threshold values on page 43.

• Removed inaccurate example in Timebase on page 43.

• Corrected the examples in Enabling or disabling rule actions at a global level on page 46.

• Updated information in MAPS SNMP traps on page 47.

• Updated information in Port fencing and port decommissioning on page 48.

• Added clarifying information to SFP marginal on page 50.

• Added information to RASLog messages on page 51.

• Updated information in Viewing MAPS rules on page 51.



• Updated information in Creating a rule on page 52.

• Included new procedure in Sending alerts using e-mail on page 56.

• Added information to MAPS policies overview on page 58.

• Updated information in Predefined policies on page 59.

• Added information to Fabric Watch legacy policies on page 60.

• Updated examples in Viewing policy information on page 61.

• Added information to Adding missing ports to a dynamic group on page 67.

• Corrected information in D_Port monitoring on page 68.

• Updated information in Switch Health Report section on page 77.

• Updated information in Notes on dashboard data on page 79.

• Updated information in Enabling MAPS Fabric Performance Impact monitoring on page 89.

• Updated examples in Scalability limit monitoring on page 91.

• Updated information in Default rules for scalability limit monitoring on page 94.

• Added information in MAPS Service Availability Module on page 95.

• Updated information in MAPS monitoring for Extension platforms on page 97.

• Added information toFabric state change monitoring thresholds on page 102.

• Added and updated information in Extension monitoring thresholds on page 102.

• Updated information in FRU state monitoring thresholds on page 103.

• Updated information in Port Health monitoring thresholds on page 103, and sub-sections.

• Updated information inResource monitoring thresholds on page 107.

• Added information to Security monitoring thresholds on page 107.

• Updated information in SFP monitoring thresholds on page 107.

• Updated information in Switch status policy monitoring thresholds on page 109.

• Updated information in Traffic Performance thresholds on page 113.

GlossaryThe following terminology, acronyms, and abbreviations are used in this document.

TABLE 1 MAPS-related terminology

Term Description

Action An activity, such as RASlog, performed by MAPS if a condition defined in a rule evaluates to true.

ASIC Application-Specific Integrated Circuit; the chip within a switch or blade that controls its operation, including packet switchingand routing.

Back-end port Port that connects a core switching blade to a port or application blade (and vice versa).

Condition Combination of monitoring system , timebase, threshold value, and the logical operation (examples: ==, >, <, >=) that needs tobe evaluated; for example: CRC/MIN > 10.

Congestion A circumstance in which the offered traffic load exceeds the capacity to transmit on the link. This could occur because theoffered or incoming traffic exceeds the capacity of the link or the receiver of the traffic is receiving slower than the incomingtraffic.

CRC Cyclic redundancy check; an error-detecting code used to detect accidental changes to raw data.

Flow A set of Fibre Channel frames that share similar traits.

Glossary


TABLE 1 MAPS-related terminology (continued)

Term Description

Flow Monitor A Flow Vision application that can monitor all the traffic passing through E_Ports, EX_Ports, F_Ports, and XISL_Ports. Referto the Flow Vision Administrator's Guide for details.

Front-end port Port that connects a switch to another switch, host, or target device, such as a storage unit.

FRU Field-Replaceable Unit; Power supply or other physical element of a device that can be replaced by an end-user.

HBA Host Bus Adapter; Fibre Channel interface that allows a host system to connect to other network or storage devices.

ISL Inter-Switch Link; a link joining two Fibre Channel switches using E_Ports.

ITW Invalid transmission word; if a data word does not transmit successfully, encoding errors may result.

Logical group A collection of similar objects.

NPIV N_Port ID Virtualization; a feature permitting multiple Fibre Channel node port (N_Port) IDs to share a single physical N_Port.

Policy Set of rules which are activated at the same time.

Rule Setting that associates a condition with actions that need to be triggered when the specified condition is evaluated to true.

QoS Quality of Service; mechanism for assigning priorities to data flows. See Traffic Management.

RSCN Registered State Change Notification; a Fibre Channel fabric notification sent to all specified switches and nodes identifyingsignificant fabric changes.

SAN Storage Area Network; a dedicated network that provides access to consolidated, block level data storage.

Slow-drain(ing) device Device that does not process frames at the rate generated by the source.

Static flow Flow created when learning is not used and all the parameters required are contained in the flow definition.

Sub-flow System auto-created flow based on a root flow. A root flow can have more than one sub-flow.

Threshold Value used in evaluating a condition.

Timebase The time period across which the change in a counter is to be monitored.

Traffic management Fabric OS mechanism that assigns high, medium, or low priority to data flows.

VC Virtual Circuit; a mechanism in a Brocade switch for creating multiple logical data paths across a single physical link orconnection.

Virtual channel Synonym for Virtual Circuit.

XISL An eXtended ISL; a type of ISL connection that carries traffic for multiple logical fabrics on the same physical link whilemaintaining fabric isolation.

Glossary


Monitoring and Alerting Policy SuiteOverview

• MAPS overview .................................................................................................................................................................................................17• MAPS license requirements..........................................................................................................................................................................18• MAPS configuration......................................................................................................................................................................................... 18• MAPS interaction with other Fabric OS features..................................................................................................................................18• Restrictions on MAPS monitoring..............................................................................................................................................................19• Firmware upgrade and downgrade considerations for MAPS....................................................................................................... 19• Fabric Watch to MAPS migration .............................................................................................................................................................. 20

MAPS overviewThe Monitoring and Alerting Policy Suite (MAPS) is an optional storage area network (SAN) health monitor supported on all switchesrunning Fabric OS 7.2.0 or later that allows you to enable each switch to constantly monitor itself for potential faults and automaticallyalerts you to problems before they become costly failures.

MAPS tracks a variety of SAN fabric metrics and events. Monitoring fabric-wide events, ports, and environmental parameters enablesearly fault detection and isolation as well as performance measurements.

MAPS provides a set of predefined monitoring policies that allow you to immediately use MAPS on activation. Refer to Predefinedpolicies on page 59 for information on using these policies.

In addition, MAPS provides customizable monitoring thresholds. These allow you to configure specific groups of ports or other elementsso that they share a common threshold value. You can configure MAPS to provide notifications before problems arise, for example, whennetwork traffic through a port is approaching the bandwidth limit. MAPS lets you define how often to check each switch and fabricmeasure and specify notification thresholds. Whenever fabric measures exceed these thresholds, MAPS automatically providesnotification using several methods, including e-mail messages, SNMP traps, and log entries. Refer to MAPS groups overview on page35, MAPS rules overview on page 45, and MAPS policies overview on page 58 for information on using these features.

The MAPS dashboard provides you with the ability to view in a quick glance what is happening on the switch, and helps administratorsdig deeper to see details of exactly what is happening on the switch (for example, the kinds of errors, the error count, and so on). Refer to MAPS dashboard overview on page 77 for more information.

MAPS provides a seamless migration of all customized Fabric Watch thresholds to MAPS, thus allowing you to take advantage of theadvanced capabilities of MAPS. MAPS provides additional advanced monitoring, such as monitoring for the same error counters acrossdifferent time periods, or having more than two thresholds for any error counters. MAPS also provides support for you to monitor thestatistics provided by the Flow Monitor feature of Flow Vision. Refer to Differences between Fabric Watch and MAPS configurations onpage 20 and Fabric Watch to MAPS migration on page 20 for details.

Activating MAPS is a chassis-specific process, and you can activate only one chassis at a time. On a given chassis there can be multiplelogical switches. Activating MAPS enables it for all logical switches in the chassis, however each logical switch can have its own MAPSconfiguration.

CAUTIONMAPS activation is a non-reversible process. Downgrading the switch firmware to an earlier version of Fabric OS will enableFabric Watch with its last configured settings. If you then re-upgrade the switch firmware back to the later version (such asFabric OS 7.3.0), Fabric Watch will continue to be enabled.


MAPS automatically monitors the management port (Eth0 or Bond0), as the rule for Ethernet port monitoring is present in all threedefault policies. While these cannot be modified, the management port monitoring rules can be removed from cloned policies. Refer to Predefined policies on page 59 for more information.

MAPS license requirementsThe Monitoring and Alerting Policy Suite (MAPS) is an optional licensed Fabric OS feature.

In order to provide full functionality, MAPS requires an active and valid Fabric Vision license. Alternatively if you are upgrading andalready have a license for Fabric Watch plus a license for Advanced Performance Monitoring, you will automatically get MAPSfunctionality without having to obtain a separate license. Refer to the Fabric OS Software Licensing Guide for more information aboutlicensing and how to obtain the necessary license keys. If you only have one of these licenses you will need to acquire the other in orderto use all the MAPS features. Without the correct licenses, neither converting Fabric Watch custom policies to MAPS nor migrating toMAPS is allowed.

MAPS configurationMAPS automatically generates one configuration for each platform, called the default configuration. You can add rules, groups, andpolicies to create a user-created configuration.

NOTEOn a reboot or HA failover, MAPS remains in the same state as it was before the event.

Automated generation of default configurationWhen MAPS generates a configuration for a particular platform, it includes only those rules that are applicable to that platform. Forexample, FCIP monitoring rules are not included in the automatic generation of the configuration for platforms that do not support FCIP.Also, some rules are replaced with others, because they have been deprecated for a particular platform. The deprecated rules exist insome policies to support backward compatibility.

User-created configurationA MAPS user-created configuration is persistent across reboot and can be uploaded or downloaded. A configuration upload or downloadaffects only the user-created configuration. You cannot upload or download the default MAPS configuration.

Deleting a user-created MAPS configurationTo remove the entire user-created MAPS configuration, complete the following steps.

1. Connect to the switch and log in using an account with admin permissions.

2. Enter mapsconfig --purge.For more information on this command, refer to the Fabric OS Command Reference.

MAPS interaction with other Fabric OS featuresMAPS interacts in different ways with different Fabric OS features, including Admin Domains, High Availability, and Virtual Fabrics.

The following table outlines how MAPS interacts with specific features in Fabric OS.

MAPS license requirements


TABLE 2 Interactions between Fabric OS features and MAPS

Feature MAPS interaction

AdminDomains

MAPS is supported on switches that have Admin Domains. There can only be one MAPS configuration that is common to all theAdmin Domains on the chassis. Users with Administrator privileges can modify the MAPS configuration from any Admin Domain.

ATTENTIONIf MAPS is enabled, do not download configuration files that have Admin Domains defined in them, as this may causeunpredictable behavior.

High Availability MAPS configuration settings are maintained across a High Availability (HA) failover or HA reboot; however, MAPS will restartmonitoring after a HA failover or HA reboot and the cached MAPS statistics are not retained.

Virtual Fabrics When using Virtual Fabrics, different logical switches in a chassis can have different MAPS configurations.

Restrictions on MAPS monitoringThe following restrictions apply globally to MAPS monitoring:

• Small form-factor pluggable (SFP) transceivers on simulated mode (SIM) ports cannot be monitored using MAPS.

• If an event occurs before the dashboard starts monitoring (such as an SCN or an alert), then the event might not be shown inthe dashboard.

Refer to Viewing Flow Vision Flow Monitor data with MAPS on page 71 for additional details about monitoring Flow Vision flows.

Firmware upgrade and downgrade considerations for MAPSThe following firmware upgrade and downgrade considerations apply to the Monitoring and Alerting Policy Suite (MAPS) in Fabric OS7.3.0.

Firmware upgrade considerationsThere are no direct upgrade considerations. However, MAPS Fabric Performance Impact monitoring and the legacy bottleneckmonitoring feature are mutually exclusive. If the legacy bottleneck monitoring feature was enabled before the upgrade, MAPS will notmonitor fabric performance. Refer to Fabric performance impact monitoring using MAPS on page 89 for additional information.

Firmware downgrade considerationsWhen downgrading from Fabric OS 7.3.0 to any previous version of the operating system, the following MAPS-related behaviors shouldbe expected:

• When an active Command Processor (CP) is running Fabric OS 7.3.0 or 7.2.0 with MAPS disabled, and the standby device hasan earlier version of Fabric OS, High Availability will be synchronized, but MAPS will not be allowed to be enabled until thefirmware on the standby device is upgraded. The mapsConfig --enablemaps command fails and an error message isdisplayed.

• When an active CP is running Fabric OS 7.3.0 or 7.2.0 and MAPS is enabled, but the standby device is running Fabric OS7.1.0 or earlier, then High Availability will not be synchronized until the standby CP is upgraded to Fabric OS 7.3.0 or 7.2.0.

• On devices with a single CP, there is no change in behavior when downgrading to an earlier version of Fabric OS.

• Downgrading to versions of Fabric OS prior to version 7.3.0 will fail if some features are not supported in the earlier firmwareand their loss could impact MAPS functionality. In this case, MAPS provides instructions on how to disable these featuresbefore firmware downgrade. An example of this is if either MAPS actions or rules include Fabric Performance Impact

Firmware upgrade and downgrade considerations for MAPS


monitoring or port decommissioning. Refer to Port decommissioning and firmware downgrades on page 48 for additionalinformation.

• Downgrading to versions of Fabric OS prior to version 7.3.0 will trigger a warning message if any feature is not supported in theearlier firmware and keeping the feature configuration is harmless. In this case, MAPS provides a warning message similar tothe following, but does not block the downgrade.

WARNING: <A>, <B>, <C> feature(s) is/are enabled. These features are not available in FOS <a.b.c> release.Do you want to continue?

Examples of this condition include MAPS having any user-created rules pertaining to monitoring the following: D_Ports,L2_DEVCNT_PER, LSAN_DEVCNT_PER, ZONE_CFGSZ_PER, BB_FCR_CNT, or ETH_MGMT_PORT.

• Downgrading to versions of Fabric OS prior to version 7.3.0 is not allowed if the MAPS “Fabric Performance Impactmonitoring” feature is enabled. You must disable FPI using the mapsConfig –disablefpimon command before starting thefirmware downgrade.

Fabric Watch to MAPS migrationFabric Watch and MAPS cannot coexist on a switch. To use MAPS, you must migrate from Fabric Watch to MAPS.

On a switch running Fabric OS 7.2.0 or later, or when you upgrade your existing switch to a later version, Fabric Watch is enabled bydefault. On an upgraded switch, Fabric Watch continues to monitor as in Fabric OS 7.1.0 until MAPS is activated.

When you start MAPS for the first time, it can automatically convert the Fabric Watch configurations to ones that are compatible withMAPS so you do not need to recreate all of the thresholds and rules. However if you do not make the conversion as part of the initialmigration, you will need to configure the rules manually.

Refer to Enabling MAPS using Fabric Watch rules on page 21 for instructions on starting MAPS using your existing Fabric Watchrules.

Differences between Fabric Watch and MAPS configurationsThe monitoring and alerting configurations available in the MAPS are not as complex as those available in Fabric Watch; as aconsequence MAPS lacks some of the functionality available in Fabric Watch.

The following table shows the differences between Fabric Watch and MAPS configurations and functionality.

TABLE 3 Comparison of Fabric Watch and MAPS configurations and functionality

Configuration Fabric Watch behavior MAPS behavior

End-to-End monitoring(Performance Monitor class)

Supported Supported through flows.

Frame monitoring (PerformanceMonitor 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. Forexample, monitoring can be paused for CRCon one port and for ITW on another port.

Occurs at the element level. Monitoring can be paused on aspecific port, but not for a specific counter on that port.

CPU/Memory polling interval Can configure the polling interval as well asthe repeat count.

This configuration can be migrated from Fabric Watch, butcannot be changed.

E-mail notification configuration Different e-mail addresses can beconfigured 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.

Fabric Watch to MAPS migration


MAPS Setup and Operation• Initial MAPS setup.............................................................................................................................................................................................21• Monitoring across different time windows...............................................................................................................................................23• Setting the active MAPS policy to a default policy..............................................................................................................................24• Pausing MAPS monitoring............................................................................................................................................................................25• Resuming MAPS monitoring....................................................................................................................................................................... 25

Initial MAPS setupThe Monitoring and Alerting Policy Suite (MAPS) is not enabled by default.

If you want to use the existing Fabric Watch rules in MAPS, you must convert them before enabling MAPS. Once you have done this,you can enable and configure MAPS.

Enabling MAPS using Fabric Watch rulesIf you are already using Fabric Watch and would like MAPS to use the same thresholds, you can convert the Fabric Watch policies intoMAPS policies and then enable MAPS using the policy named “fw_active_policy”. This provides the same monitoring functionality asFabric Watch.

You can monitor your switch for a while using the MAPS policy, and then fine-tune the policy as necessary to fit your environment. Whenyou are satisfied with the configuration settings, you can specify the actions you want to occur when thresholds are crossed.

To monitor a switch in this manner, complete the following steps.

1. Migrate from Fabric Watch by entering mapsConfig --fwconvert to import the Fabric Watch rules.

2. Enable MAPS by entering mapsConfig --enablemaps -policy fw_active_policy.

Upon successful completion of this command, the following happens:

• The Fabric Watch configurations are converted to MAPS policies.

• Fabric Watch monitoring and commands are disabled.

• MAPS commands are enabled.

• The MAPS “fw_active_policy” policy is enabled.

3. Set global actions on the switch to “none” by entering mapsConfig --actions none.

Setting the global actions to “none” allows you to test the configured thresholds before enabling the actions.

4. Monitor the switch by entering mapsDb --show or mapsDb --show all.

5. Fine-tune the rules used by the policy as necessary.

6. Set global actions on the switch to the allowed actions by using mapsConfig --actions and specifying all of the actions that youwant to allow on the switch.


The following example enables MAPS, loads the policy “dflt_conservative_policy”, sets the actions to “none”, and then sets approvedactions.

switch:admin> mapsconfig --fwconvert switch:admin> mapsconfig --enablemaps -policy dflt_conservative_policy

WARNING:This command enables MAPS and replaces all Fabric Watch configurations and monitoring. Once MAPS is enabled, the Fabric Watch configuration can't be converted to MAPS. If you wish to convert your Fabric Watch configuration into MAPS policies, select NO to this prompt and first issue the "mapsconfig --fwconvert" command. Once the Fabric Watch configuration is concerted into MAPS policies, you may reissue the "mapsconfig --enablemaps" command to continue this process. If you do not use Fabric Watch or need the configuration, then select YES to enable MAPS now.Do you want to continue? (yes, y, no, n): [no] yes ...MAPS is enabled.

switch:admin> mapsconfig --actions none

switch:admin> mapsconfig --actions raslog,fence,snmp,email,sw_marginal

Enabling MAPS without using Fabric Watch rulesIf you are not already using Fabric Watch, or do not wish to continue using the Fabric Watch policies, you can quickly start monitoringyour switch using MAPS with one of the predefined policies delivered with MAPS.

ATTENTIONIf you follow these instructions, the Fabric Watch configurations are not converted to MAPS policies as part of the migration,Fabric Watch commands are disabled, and MAPS commands are enabled.


2. Enter mapsPolicy --enable -policy followed by the name of the policy you want to enable. The default policies are:

• dflt_conservative_policy

• dflt_aggressive_policy

• dflt_moderate_policy

NOTEYou must include an existing policy name in this command to enable MAPS.

3. Set global actions on the switch to “none” by entering mapsConfig --actions none.

Setting the global actions to “none” allows you to test the configured thresholds before enabling the actions.

4. Monitor the switch by entering mapsDb --show or mapsDb --show all.

5. Fine-tune the rules used by the policy as necessary.

6. Set global actions on the switch to the allowed actions by using mapsConfig --actions and specifying all of the actions that youwant to allow on the switch.

Initial MAPS setup


The following example enables MAPS, loads the policy “fw_aggressive_policy”, sets the actions to “none”, and then sets approvedactions.

switch:admin> mapsconfig --enablemaps -policy fw_aggressive_policy

WARNING:This command enables MAPS and replaces all Fabric Watch configurations and monitoring. Once MAPS is enabled, the Fabric Watch configuration can't be converted to MAPS. If you wish to convert your Fabric Watch configuration into MAPS policies, select NO to this prompt and first issue the "mapsconfig --fwconvert" command. Once the Fabric Watch configuration is concerted into MAPS policies, you may reissue the "mapsconfig --enablemaps" command to continue this process. If you do not use Fabric Watch or need the configuration, then select YES to enable MAPS now.Do you want to continue? (yes, y, no, n): [no] yes ...MAPS is enabled.

switch:admin> mapsconfig --actions none

switch:admin> mapsconfig --actions raslog,fence,snmp,email,sw_marginal

For additional information refer to the following links.

Refer to Predefined policies on page 59 for details on the default MAPS policies.

Refer to Viewing the MAPS dashboard on page 80 for details on the mapsDb command output.

Refer to MAPS rule actions on page 46 for details on configuring MAPS rule actions.

Monitoring across different time windowsYou can create rules that monitor across multiple time windows or timebases.

For example, if you want to monitor both for severe conditions and separately for non-critical but persistent conditions, you wouldconstruct rules similar to the following.

1. Enter mapsrule --create severe_rule_name -monitor monitor_name -group group_name -timebase time_base -op operator-value time -action action_1, action_2, …

2. Enter mapsrule --create persistent_rule_name -monitor monitor_name -group group_name -timebase time_base -opoperator -value time -action action_1, action_2, …

3. Enter mapsrule --show severe_rule_name to confirm the rule values.

4. Enter mapsrule --show persistent_rule_name to confirm the rule values.

Monitoring across different time windows


Both of the following cases could indicate potential issues in the fabric. Configuring rules to monitor these conditions allows you tocorrect issues before they become critical.

In the following example, the definition for crc_severe specifies that if the change in the CRC counter in the last minute is greater than 5, itmust trigger an e-mail alert and SNMP trap. This rule monitors for the severe condition. It monitors sudden spikes in the CRC errorcounter over a period of one minute. The definition for crc_persistent specifies that if the change in the CRC counter in the last day isgreater than 20, it must trigger a RASLog message and e-mail alert. This rule monitors for slow occurrences of CRC errors that couldaccumulate to a bigger number over the period of a day.

switch1234:admin> mapsrule --create crc_severe -monitor crc -group ALL_PORTS -t min -op g -value 5 -action email,snmp

switch1234:admin> mapsrule --create crc_persistent -monitor crc -group ALL_PORTS -t day -op g -value 20 -action raslog,email

switch1234:admin> mapsrule --show crc_severe Rule Data:----------RuleName: crc_severeCondition: ALL_PORTS(crc/min>5)Actions: email,snmpPolicies Associated: none

switch1234:admin> mapsrule --show crc_persistent Rule Data:----------RuleName: crc_persistentCondition: ALL_PORTS(crc/day>20)Actions: raslog,emailPolicies Associated: none

Setting the active MAPS policy to a default policyMAPS allows you to easily set the active MAPS policy to one of the default policies.

To set the active MAPS policy, complete the following steps.


2. Enter mapspolicy --enable followed by the name of the policy you want to enable. The default policies are:




• dflt_base_policy

NOTEIf you have installed a Fabric Vision license, then you should use the conservative, aggressive, or moderate policies.Use the base policy only for basic monitoring, similar to using MAPS without a license. Refer to Feature monitors notrequiring a license for details.

3. Enter mapspolicy --show -summary to confirm that the policy you specified is active.

Setting the active MAPS policy to a default policy


The following example sets “dflt_moderate_policy” as the active MAPS policy, and then displays the list of policies and names the activepolicy.

switch:admin> mapspolicy --enable dflt_moderate_policyswitch:admin> mapspolicy --show -summary Policy Name Number of Rules------------------------------------------------------------dflt_aggressive_policy : 196dflt_conservative_policy : 198dflt_moderate_policy : 198dflt_base_policy : 20fw_default_policy : 109fw_custom_policy : 109fw_active_policy : 109Active Policy is 'dflt_moderate_policy'.

For more information, refer to Predefined policies on page 59.

Pausing MAPS monitoringYou can stop monitoring ports, FCIP circuits, or SFPs in MAPS. You might do this during maintenance operations, such as device orserver upgrades.

To temporarily stop monitoring an element in MAPS, complete the following steps. This suspends MAPS monitoring for the specifiedelement member.


2. Enter mapsConfig --config pause followed by both the element type and the specific members for which you want monitoringpaused.

You must specify both the type and the member information in the command; you specify multiple members by separatingthem with a comma for individual members, or a hyphen for a range of members.

The following example pauses MAPS monitoring for ports 5 and 7.

switch:admin> mapsConfig --config pause -type port -members 5,7

Resuming MAPS monitoringOnce you have paused monitoring, you can resume monitoring at any time.

To resume monitoring a paused port or other element in MAPS, complete the following steps. This resumes MAPS monitoring for thespecified element member.


2. Enter mapsConfig --config continue followed by both the element type and the specific members for which you wantmonitoring resumed.

You must specify both the type and the member information in the command; you specify multiple members by separatingthem with a comma for individual members, or a hyphen for a range of members.

The following example resumes MAPS monitoring for port 5.

switch:admin> mapsConfig --config continue -type port -members 5

Resuming MAPS monitoring



MAPS Elements and Categories• MAPS structural elements.............................................................................................................................................................................27• MAPS monitoring categories ......................................................................................................................................................................27

MAPS structural elementsThe Monitoring and Alerting Policy Suite (MAPS) comprises various structural elements.

The following table provides a brief description of each structural element in MAPS.

TABLE 4 MAPS structural elements

Element Description

Action The activity performed by MAPS if a condition defined in a rule evaluates to true. For more information, refer to Working with MAPSrules and actions on page 51.

Category A grouping of similar elements that can be monitored (for example, "Security Violations"). For more information, refer to MAPSmonitoring categories on page 27.

Condition An arithmetic or logical expression using either (1) a timebase and a threshold value with a relational operator or (2) a monitor value anda state with a boolean operator. For more information, refer to MAPS conditions on page 42.

Group A collection of similar objects that you can monitor as a single entity. For example, a collection of ports can be assembled as a group.For more information, refer to MAPS groups overview on page 35.

Dashboard A summary view of the switch health status that allows you to easily determine whether everything is working according to policy orwhether you need to investigate further. For more information, refer to MAPS dashboard overview on page 77.

Monitoringsystem

A value (measure or statistic) that can be monitored. For more information, refer to MAPS monitoring categories on page 27.

Rule A direction associating a condition with one or more actions that must occur when the specified condition is evaluated to be true. Formore information, refer to MAPS rules overview on page 45.

Policy A set of rules defining thresholds for triggering actions MAPS is to take when that threshold is triggered. When a policy is enabled, all ofthe rules in the policy are in effect. For more information, refer to MAPS policies overview on page 58.

MAPS monitoring categoriesWhen you create a rule, you must specify a category to be monitored.

MAPS provides you with the following monitorable categories:

• Switch Status Policy on page 34

• Port Health on page 28

• FRU Health on page 29

• Security Violations on page 29

• Fabric State Changes on page 30

• Switch Resources on page 31

• Traffic Performance on page 31

• FCIP Health on page 32

• Fabric Performance Impact on page 33


In addition to being able to set alerts and other actions based on these categories, the MAPS dashboard displays their status. Refer to MAPS dashboard overview on page 77 for information on using the MAPS dashboard.

Port HealthThe Port Health category monitors port statistics and takes action based on the configured thresholds and actions. You can configurethresholds per port type and apply the configuration to all ports of the specified type. Ports whose thresholds can be monitored includephysical ports, D_Ports, E_Ports, and F_Ports. The Port Health category also monitors the physical aspects of a small form-factorpluggable (SFP) transceiver, such as voltage, current, receive power (RXP), transmit power (TXP), and state changes in physical ports,D_Ports, E_Ports, and F_Ports.

The following table describes the monitored parameters in this category. In the “Monitored parameter” column, the value in parenthesesis the parameter name you specify in mapsrule -monitor command.

TABLE 5 Port Health category parameters

Monitored parameter Description

Cyclic redundancy check (CRCwith good EOF (crc g_eof)markers)

The number of times an invalid cyclic redundancy check error occurs on a port or a frame that computes to aninvalid CRC. Invalid CRCs can represent noise on the network. Such frames are recoverable by retransmission.Invalid CRCs can indicate a potential hardware problem.

Invalid transmission words (ITW) The number of times an invalid transmission word error occurs on a port. A word did not transmit successfully,resulting in encoding errors. Invalid word messages usually indicate a hardware problem.

NOTEThe ITW counter includes any physical coding sub-layer (PCS) violations. ITW violations can occur dueto an “encoding in” or “encoding out” violation, a PCS violation, or all of these. Encoding violations occuronly at slow (8 Gbps or lower) speeds, and PCS violations occur only at high (10 Gbps or higher)speeds.

Sync loss (LOSS_SYNC) The number of times a synchronization error occurs on the port. Two devices failed to communicate at the samespeed. Synchronization errors are always accompanied by a link failure. Loss of synchronization errors frequentlyoccur due to a faulty SFP transceiver or cable.

Link failure (LF) The number of times a link failure occurs on a port or sends or receives the Not Operational Primitive Sequence(NOPS). Both physical and hardware problems can cause link failures. Link failures also frequently occur due to aloss of synchronization or a loss of signal.

Signal loss (LOSS_SIGNAL) The number of times that a signal loss occurs in a port. Signal loss indicates that no data is moving through theport. A loss of signal usually indicates a hardware problem.

Protocol errors (PE) The number of times a protocol error occurs on a port. Occasionally, protocol errors occur due to software glitches.Persistent errors generally occur due to hardware problems.

Power-on time (PWR_HRS) The number of hours that an SFP transceiver has been powered up.

NPIV logins(DEV_NPIV_LOGINS)

The number of NPIV logins to the device. Refer to Monitoring NPIV logins to F_Ports for details.

Link reset (LR) The ports on which the number of link resets exceed the specified threshold value.

Class 3 timeouts (C3TXTO) The number of Class 3 discard frames because of timeouts.

State changes (STATE_CHG) The state of the port has changed for one of the following reasons:

• The port has gone offline.

• The port has come online.

• The port is faulty.

SFP current (CURRENT) The amperage supplied to the SFP transceiver in milliamps (mA). Current area events indicate hardware failures.

SFP receive power (RXP) The power of the incoming laser in microwatts (µW). This is used to help determine if the SFP transceiver is in goodworking condition. If the counter often exceeds the threshold, the SFP transceiver is deteriorating.

SFP transmit power (TXP) The power of the outgoing laser in microwatts (µW). This is used to help determine if the SFP transceiver is in goodworking condition. If the counter often exceeds the threshold, the SFP transceiver is deteriorating.

MAPS monitoring categories


TABLE 5 Port Health category parameters (continued)


SFP voltage (VOLTAGE) The voltage supplied to the SFP transceiver in millivolts (mV). If this value exceeds the threshold, the SFPtransceiver is deteriorating.

SFP temperature (SFP_TEMP) The temperature of the SFP transceiver in degrees Celsius. A high temperature indicates that the SFP transceivermay be in danger of damage.

Port health and CRC monitoringThere are two types of CRC errors that can be logged on a switch; taken together they can assist in determining which link introduced theerror into the fabric. The two types are plain CRCs, which have bad end-of-frame (EOF) markers and CRCs with good EOF (crc g_eof)markers. When a crc g_eof error is detected on a port, it indicates that the transmitter or path from the sending side may be a possiblesource. When a complete frame containing a CRC error is first detected, the error is logged, and the good EOF (EOFn) is replaced with abad EOF marker (EOFni). Because Brocade switches forward all packets to their endpoints, changing the EOF marker allows the packetto continue but not be counted.

For thresholding and fencing purposes, only frames with CRC errors and good end-of-frame markers are counted. This enables you toknow exactly how many errors were originated in a specific link.

FRU HealthThe FRU Health category enables you to define rules for field-replaceable units (FRUs).

The following table lists the monitored parameters in this category.

TABLE 6 FRU Health category parameters

Monitored parameter Description Data type Range of data

PS_STATE The state of a power supply (PS) has changed. enum OUT, ON, FAULTY

FAN_STATE The state of a fan has changed. enum OUT, ON, FAULTY

BLADE_STATE The state of a slot (blade) has changed. enum FAULTY, OFF, ON, OUT

SFP_STATE The state of the SFP transceiver has changed. enum IN, OUT, FAULTY

WWN_STATE The state of a WWN card has changed. enum OUT, ON, FAULTY

Security ViolationsThe Security Violations category monitors different security violations on the switch and takes action based on the configured thresholdsand their actions.


TABLE 7 Security Violations category parameters


DCC violations (SEC_DCC) An unauthorized device attempts to log in to a secure fabric.

HTTP violations (SEC_HTTP) A browser access request reaches a secure switch from an unauthorized IP address.

Illegal command (SEC_CMD) Commands permitted only to the primary Fibre Channel Switch (FCS) are executed on another switch.

Incompatible security DB (SEC_IDB) Secure switches with different version stamps have been detected.

Login violations (SEC_LV) Login violations which occur when a secure fabric detects a login failure.

Invalid Certifications (SEC_CERT) Certificates are not valid.

No-FCS (SEC_FCS) The switch has lost contact with the primary FCS.



TABLE 7 Security Violations category parameters (continued)


SCC violations (SEC_SCC) SCC violations which occur when an unauthorized switch tries to join a secure fabric. The WWN of theunauthorized switch appears in the ERRLOG.

SLAP failures (SEC_AUTH_FAIL) SLAP failures which occur when packets try to pass from a non-secure switch to a secure fabric.

Telnet violations (SEC_TELNET) Telnet violations which occur when a Telnet connection request reaches a secure switch from an unauthorizedIP address.

TS out of sync (SEC_TS) Time Server (TS) violations, which occur when an out-of-synchronization error has been detected.

Fabric State ChangesThe Fabric State Changes category contains areas of potential inter-device problems, such as zone changes, fabric segmentation,E_Port down, fabric reconfiguration, domain ID changes, and fabric logins.

The following table lists all the monitored parameters in this category.

TABLE 8 Fabric State Changes category parameters

Parameter name Description Data type Range of data

BB_FCR_CNT) Monitors the number (count) of Fibre Channel routers (FCR)configured in a backbone (BB) fabric.

Uint32 0 - 999999999

DID_CHG Monitors the number of forced domain ID (DID) changes. Theseoccur when there is a conflict of domain IDs in a single fabric and theprincipal switch must assign another domain ID to a switch.

Uint32 0 - 999999999

EPORT_DOWN Tracks the number of times that an E_Port or VE_Port goes down.E_Ports and VE_Ports go down each time you remove a cable or anSFP transceiver (where there are SFP transceiver failures or transienterrors).

Uint32 0 - 999999999

FAB_CFG Tracks the number of fabric reconfigurations. These occur when thefollowing events happen:

• Two fabrics with the same domain ID are connected

• Two fabrics are joined

• An E_Port or VE_Port goes offline

• A principal link segments from the fabric

Uint32 0 - 999999999

FAB_SEG Tracks the cumulative number of segmentation changes.Segmentation changes occur because of one of the following eventsoccurs:

• Zone conflicts

• Domain conflicts

• Incompatible link parameters

During E_Port and VE_Port initialization, ports exchangelink parameters, and incompatible parameters(uncommon) result in segmentation.

• Segmentation of the principal link between two switches

Uint32 0 - 999999999

FLOGI Activates when ports and devices initialize with the fabric (fabriclogins).

Uint32 0 - 999999999

L2_DEVCNT_PER Monitors the percentage of imported devices in a Fibre Channelfabric relative to the total number of devices supported in the fabric,whether they are active or not (Layer 2 device count percentage). Theswitches in a pure Layer 2 fabric do not participate in the metaSAN.

Float 0 - 100

LSAN_DEVCNT_PER Monitors the percentage of active devices in a Fibre Channel router-enabled backbone fabric relative to the maximum number of devicespermitted in the metaSAN (LSAN device count percentage). This

Float 0 - 100



TABLE 8 Fabric State Changes category parameters (continued)


percentage includes devices imported from any attached edgefabrics.

ZONE_CFGSZ_PER Monitors the “used zone configuration” size relative to the maximumzone configuration size on the switch.

Float 0 - 100

ZONE_CHG Tracks the number of zone changes. Because zoning is a securityprovision, frequent zone changes could indicate a security breach orweakness. Zone change messages occur whenever there is achange in zone configurations.

Uint32 0 - 999999999

Switch ResourcesSwitch Resource monitoring enables you to monitor your system’s temperature, flash usage, memory usage, and CPU usage.

You can use Switch Resources monitors to perform the following tasks:

• Configure thresholds for MAPS event monitoring and reporting for the environment and resource classes. Environmentthresholds enable temperature monitoring, and resource thresholds enable monitoring of flash memory.

• Configure memory or CPU usage parameters on the switch or display memory or CPU usage. Configuration options includesetting usage thresholds which, if exceeded, trigger a set of specified MAPS alerts. You can set up the system monitor to poll atcertain intervals and specify the number of retries required before MAPS takes action.


TABLE 9 Switch Resources category parameters


CPU The percentage of CPU available, calculated by comparing thepercentage of CPU consumed with the configured threshold value.

Float 0 - 100

ETH_MGMT_PORT_STAT The status of the Ethernet management port (Bond0). enum UP, DOWN

FLASH_USAGE The available compact flash space, calculated by comparing thepercentage of flash space consumed with the configured highthreshold value.

Float 0 - 100

MEMORY_USAGE The available memory, calculated by comparing the percentage ofmemory consumed with the configured threshold value.

Float 0 - 100

TEMP The ambient temperature inside the switch in degrees Celsius.Temperature sensors monitor the switch in case the temperature risesto levels at which damage to the switch might occur.

enum IN_RANGE,OUT_OF_RANGE

Traffic PerformanceThe Traffic Performance category groups areas that track the source and destination of traffic. You can use traffic thresholds and alarmsto determine traffic load and flow and to reallocate resources appropriately.


TABLE 10 Traffic Performance category parameters


Receive bandwidth usagepercentage (RX)

The percentage of port bandwidth being used by RX traffic. For example, if the port speed is 10 Gbps and the portreceives 5 Gb of data in one second, then the percentage of RX utilization is 50 percent (5 Gb*100/(10 Gb*1second)). For a master trunk port, this indicates the RX percentage for the entire trunk.



TABLE 10 Traffic Performance category parameters (continued)


Transmit bandwidth usagepercentage (TX)

The percentage of port bandwidth being used by TX traffic. For example, if the port speed is 10 Gbps and the portsends 5 Gb of data in one second, then the percentage of TX utilization is 50 percent (5 Gb*100/(10 Gb*1 second)).For a master trunk port, this indicates the TX percentage for the entire trunk.

Utilization (UTIL) The percentage of individual port (or trunk) bandwidth being used at the time of the most recent poll.

Transmitted frame count(TX_FCNT)

The number of frames transmitted from the flow source.

Received frame count(RX_FCNT)

The number of frames received by the flow destination.

Transmitted throughput(TX_THPUT)

The number of megabytes (MB) transmitted per second by the flow source.

Received throughput(RX_THPUT)

The number of megabytes (MB) received per second by the flow destination.

SCSI frames read (IO_RD) The number of SCSI I/O read command frames recorded for the flow.

SCSI frames written (IO_WR) The number of SCSI I/O write command frames recorded for the flow.

SCSI frames read(IO_RD_BYTES)

The number of SCSI I/O bytes read as recorded for the flow.

SCSI frames written(IO_WR_BYTES)

The number of SCSI I/O bytes written as recorded for the flow.

FCIP HealthThe FCIP Health category enables you to define rules for FCIP health, including circuit state changes, circuit state utilization, and packetloss.

The following tables list the monitored parameters in this category. The first table lists those FCIP Health parameters monitored on allBrocade platforms.

TABLE 11 FCIP Health category parameters


FCIP circuit state changes (CIR_STATE) The state of the circuit has changed for one of the following reasons:

• The circuit has gone offline.

• The circuit has come online.

• The circuit is faulty.

FCIP circuit utilization (CIR_UTIL) The percentage of circuit utilization in the configured time period (this can be minute, hour, or day).

FCIP circuit packet loss (CIR_PKTLOSS) The percentage of the total number of packets that have had to be retransmitted.

The following FCIP parameters are only monitored on the Brocade 7840 extension switch. These parameters are in addition to the oneslisted in the previous table.

TABLE 12 Brocade 7840 FCIP Health category parameters


FCIP packet loss (PKTLOSS) The percentage of the total number of packets that have had to be retransmitted in each QoS level.This applies to each FCIP QoS group only.

FCIP tunnel state change (STATE_CHG) The count of FCIP tunnel state changes. This applies to the tunnel group only.

FCIP tunnel or QoS utilization (UTIL) The percentage of FCIP utilization. This applies to both the tunnel and the QoS groups.

FCIP circuit round trip time (RTT) The circuit round-trip latency. This is an absolute value, and only applies to the circuit group.



TABLE 12 Brocade 7840 FCIP Health category parameters (continued)


FCIP circuit jitter (JITTER) The amount of jitter in a circuit. This is a calculated percentage, and only applies to the circuit group.

Refer to the Extension monitoring thresholds on page 102 for the default values.

Fabric Performance ImpactThe Fabric Performance Impact category monitors the current condition of the latency seen on E_Ports and F_Ports over different timewindows and uses that to determine the performance impact to the fabric and network. MAPS generates alerts when either thecongestion levels or port latencies meet or exceed the specified thresholds. To achieve this, MAPS monitors ports for bandwidthutilization and the IO_PERF_IMPACT and IO_FRAME_LOSS bottleneck states. MAPS uses the IO_LATENCY_CLEAR state to showthat one of the latency rules was triggered, but the latency has been cleared from the port.

NOTEWhenever IO_PERF_IMPACT is used, IO_LATENCY_CLEAR must also be included in the active policy to clear the latencyrecord.


TABLE 13 Fabric Performance Impact category parameters


BE_LATENCY_IMPACT In all fabric edge switches connecting to Brocade Analytics MonitoringPlatform with active VTAP flows, MAPS monitors the tim_txcrd_z back-end port on a mirrored traffic path.

enum IO_PERF_IMPACT

DEV_LATENCY_IMPACT When a port does not quickly clear the frames sent through it, this cancause a backup in the fabric. When MAPS detects that the backpressurefrom such a condition is significant enough, the bottleneck state of thatport is changed to IO_PERF_IMPACT.

When a timeout is seen on a port, the bottleneck state of that port ischanged to IO_FRAME_LOSS. This state will also be set if the Inter-Frame-Time (IFT) or Average R_RDY_DELAY is greater than or equal to80ms.

enum IO_PERF_IMPACT,IO_FRAME_LOSS

IO_LATENCY_CLEAR Once the device latency is cleared from an F_Port, MAPS clears thelatency record and sets the state of the port to “IO_LATENCY_CLEAR”.This allows the system to resume monitoring for latency.

enum IO_LATENCY_CLEAR

IT_FLOW The number of zoned online devices that have exceeded the zoned deviceratio threshold.

Uint32 0 - 999999999

RX The percentage of port bandwidth being used by received, incoming (RX)traffic. For example, if the port speed is 10 Gbps and the port receives 5Gb of data in one second, then the percentage of RX utilization is 50percent (5 Gb*100/(10 Gb*1 second)). For a master trunk port, thisindicates the RX percentage for the entire trunk.

Float 0 - 100

TX The percentage of port bandwidth being used by transmitted, outgoing(TX) traffic. For example, if the port speed is 10 Gbps and the port sends5 Gb of data in one second, then the percentage of TX utilization is 50percent (5 Gb*100/(10 Gb*1 second)). For a master trunk port, thisindicates the TX percentage for the entire trunk.

Float 0 - 100

UTIL The percentage of individual port (or trunk) bandwidth being used at thetime of the most recent poll.

Float 0 - 100



For more information on Fabric Performance Impact monitoring, refer to Fabric performance impact monitoring using MAPS on page89.

Switch Status PolicyThe Switch Status Policy category lets you monitor the health of the switch by defining the number of types of errors that transition theoverall switch state into a state that is not healthy. For example, you can specify a switch status policy so that if a switch has two powersupply failures, it is considered to be in a marginal state, or if it has two failures, it is in a critical (down) state.

The following table lists the monitored parameters in this category and identifies the factors that affect their health.

NOTENot all switches support all monitors. Also, MAPS does not monitor CPU or memory usage with switch status policies, and youcannot configure this monitoring.

TABLE 14 Switch Status Policy category parameters

Parameter name Description

BAD_FAN The number of problematic fans, including missing fans and faulty fans. Uint32 0 - 999999999

BAD_PWR The number of times a power (PWR) supply threshold detected absent orfailed power supplies, and power supplies that were not in the correct slotfor redundancy.

Uint32 0 - 999999999

BAD_TEMP The number of time temperature thresholds detected faulty temperaturesensors.

Uint32 0 - 999999999

DOWN_CORE The number of faulty (down) core blades (applies to modular switchesonly).

Uint32 0 - 999999999

ERR_PORTS The percentage of ports with errors. Float 0 - 100

FAULTY_BLADE The number of faulty (down) blades (applies to modular switches only). Uint32 0 - 999999999

FAULTY_PORTS The percentage of hardware-related port faults. Float 0 - 100

FLASH_USAGE The percentage of flash usage by the system. Float 0 - 100

HA_SYNC Indicates whether the system is in or out of sync. Uint32 0 - 1

MARG_PORTS The percentage of physical ports, E_Ports, and F_Ports (both optical andcopper) that exceed threshold settings. Whenever these thresholds arepersistently high, the port is marginal.

Float 0 - 100

MISSING_SFP The percentage of ports that are missing SFP media. Float 0 - 100

WWN_DOWN The number of faulty (down) WWN cards (applies to modular switchesonly).

Uint32 0 - 999999999

NOTEMarginal ports, faulty ports, error ports, and missing SFP transceivers are calculated as a percentage of the physical ports (thiscalculation excludes logical ports, FCoE_Ports, and VE_Ports).



MAPS Groups, Conditions, Rules, andPolicies

• MAPS groups overview.................................................................................................................................................................................. 35• MAPS conditions...............................................................................................................................................................................................42• MAPS rules overview.......................................................................................................................................................................................45• MAPS policies overview................................................................................................................................................................................. 58

MAPS groups overviewA MAPS group is a collection of similar objects that you can then monitor using a common threshold.

MAPS provides predefined groups, or you can create a user-defined group and then use that group in rules, thus simplifying ruleconfiguration and management. For example, you can create a group of UNIX ports, and then create specific rules for monitoring thisgroup. As another example, to monitor your network, you can define Flow Vision flows on a switch that have different feature sets, andthen import them into MAPS as groups.

Viewing group informationMAPS allows you to view the information for all logical groups collectively, or for a single specific group.

To view a summary of all the logical groups on a switch, enter logicalgroup --show. This command returns the group name, and whetherthe group is predefined. The output presents a table with columns that list characteristics for each group:

• The name of the group

• Whether it is a predefined group

• The type of items in the group (port, SFP, power supply, and so on)

• A list of all of the current members

The following example shows the output of logicalgroup --show.

switch:admin> logicalgroup --show

-----------------------------------------------------------------------------------Group Name |Predefined |Type |Member Count |Members-----------------------------------------------------------------------------------ALL_100M_16GSWL_QSFP |Yes |Sfp |4 |52-55ALL_32GSWL_QSFP |Yes |Sfp |0 |ALL_TARGET_PORTS |Yes |Port |4 |10-11,26-27ALL_ASICS |Yes |Asic |0 |ALL_16GLWL_SFP |Yes |Sfp |0 |ALL_HOST_PORTS |Yes |Port |7 |16-18,21-22,38-39ALL_SFP |Yes |Sfp |27 |0,2-3,7,9-12,16-23NON_E_F_PORTS |Yes |Port |43 |1,4-6,8,13-15,28-31ALL_10GSWL_SFP |Yes |Sfp |0 |SWITCH |Yes | |1 |0CHASSIS |Yes | |1 |0ALL_10GLWL_SFP |Yes |Sfp |0 |ALL_TS |Yes |Temp. sensor|7 |0-6ALL_F_PORTS |Yes |Port |12 |10-12,26-27,38-39ALL_FAN |Yes |Fan |2 |1-2ALL_QUARANTINED_PORTS |Yes |Port |0 |ALL_16GSWL_SFP |Yes |Sfp |21 |0,2,7,9-11,38-39,46ALL_QSFP |Yes |Sfp |0 |ALL_CERTS |Yes |Certificate |0 |


ALL_OTHER_F_PORTS |Yes |Port |1 |12ALL_E_PORTS |Yes |Port |9 |0,2-3,7,9,32,52,54-55ALL_WWN |Yes |WWN |1 |1ALL_PORTS |Yes |Port |64 |0-63ALL_D_PORTS |Yes |Port |0 |ALL_OTHER_SFP |Yes |Sfp |1 |12ALL_PS |Yes |Power Supply|2 |1-2ALL_FLASH |Yes |Flash |1 |0ALL_PIDS |Yes |Pid |12 |All Pids monitoredALL_25Km_16GLWL_SFP |Yes |Sfp |0 |ALL_32GSWL_SFP |Yes |Sfp |1 |3ALL_32GLWL_SFP |Yes |Sfp |0 |ALL_32GSWL_QSFP |Yes |Sfp |0 |io_mon_ |No |Flow |1 |Monitored Flow

To view details of a specific logical group on a switch, enter logicalgroup --show group_name. This provides exactly same informationas that of logicalgroup --show but for the specified group only. The following example shows the output of logicalgroup --showALL_TS.

switch:admin> logicalgroup --show ALL_TS -------------------------------------------------------------------------------Group Name |Predefined |Type |Member Count |Members-------------------------------------------------------------------------------ALL_TS Yes Temp Sensor 4 0-3

You can also use this command to display the state of flows from a MAPS perspective. The state of a flow is shown in the output in the“Members” column. The following example shows the output of logicalgroup --show fpm1 for the active Flow Vision flow “fpm1” thathas been imported into, and being monitored through, MAPS.

switch:admin> logicalgroup -show fpm1 -------------------------------------------------------------------------------Group Name |Predefined |Type |Member Count |Members-------------------------------------------------------------------------------fpm1 No Flow 1 Monitored Flow

The following example shows the output of logicalgroup --show fpm2. In this example, the flow “fpm2” was imported into MAPS, butwas subsequently deleted in Flow Vision. MAPS is not monitoring this flow, but it is maintained as a zero member group. If the flow isrecreated in Flow Vision and you want to resume monitoring this flow, you must reimport the flow using the mapsconfig --importflow_name -force command. Refer to the Fabric OS Command Reference for more information on using the mapsconfig orlogicalgroup commands.

switch:admin> logicalgroup --show fpm2 -------------------------------------------------------------------------------Group Name |Predefined |Type |Member Count|Members-------------------------------------------------------------------------------fpm2 No Flow 0 Not Monitored (Stale Flow)

Predefined groupsMAPS provides several predefined groups. You cannot delete any of these groups. You can add and remove members from the“PORTS” groups, and you can change the pre-defined threshold values for any predefined group.

NOTEOn switches configured as Access Gateways, F_Ports are categorized and displayed only in the ALL_F_PORT group. They arenot categorized in the ALL_HOST_PORTS, ALL_TARGET_PORTS, or ALL_OTHER_F_PORTS groups.

MAPS groups overview


The following table lists these predefined groups organized by object type.

TABLE 15 Predefined MAPS groups

Predefined group name Object type Description

ALL_PORTS FC Port All ports in the logical switch.

ALL_D_PORTS FC Port All D_Ports in the logical switch.

ALL_E_PORTS FC Port All E_Ports and EX_Ports in the logical switch. This includes all the ports in E_Portand EX_Port trunks as well.

ALL_F_PORTS FC Port All F_Ports in the logical switch. This includes all the ports in F_Port trunks as well.

ALL_HOST_PORTS FC Port All ports in the logical switch connected to hosts. MAPS automatically detects if adevice connected on this port is a server device and adds it to this set.

ALL_TARGET_PORTS FC Port All logical switch ports connected to targets. MAPS automatically detects if adevice connected on this port is a target device and adds it to this set. If the deviceconnected to the port is identified as both a Host and a Target device, MAPS treatsthe port as a Target port.

ALL_OTHER_F_PORTS FC Port All F_Ports in the logical switch which are neither Host nor Target ports.

NON_E_F_PORTS FC Port All ports in the logical switch which are neither E_Ports nor F_Ports.

ALL_TUNNELS Tunnel All FCIP tunnels in the switch. This is supported on the Brocade 7840 switch only.

ALL_SFP SFP All small form-factor pluggable (SFP) transceivers.

ALL_10GSWL_SFP SFP All 10-Gbps Short Wavelength (SWL) SFP transceivers on FC Ports in the logicalswitch.

ALL_10GLWL_SFP SFP All 10-Gbps Long Wavelength (LWL) SFP transceivers on FC Ports in the logicalswitch.

ALL_16GSWL_SFP SFP All 16-Gbps SWL SFP transceivers in the logical switch.

ALL_16GLWL_SFP SFP All 16-Gbps LWL SFP transceivers in the logical switch.

ALL_OTHER_SFP SFP All SFP transceivers that do not belong to one of the following groups:

• ALL_100M_16GSWL_QSFP

• ALL_10GSWL_SFP

• ALL_10GLWL_SFP

• ALL_16GSWL_SFP

• ALL_16GLWL_SFP

• ALL_QSFP

ALL_QSFP SFP All quad small form-factor pluggable (QSFP) transceivers in the logical switch.

ALL_2K_QSFP SFP All 2 Kilometre-capable quad small form-factor pluggable (QSFP) transceivers inthe logical switch.

ALL_SLOTS Slot All slots present in the chassis.

ALL_SW_BLADES Blade All port and application blades in the chassis.

ALL_CORE_BLADES Blade All core blades in the chassis.

ALL_CIRCUITS Circuit All Fibre Channel over Internet Protocol (FCIP) circuits in the logical switch.

ALL_FAN Fan All fans in the system.

ALL_FLASH Flash The flash memory card in the system.

ALL_PS Power Supply All power supplies in the system.

ALL_TS Temperature Sensor All temperature sensors in the system.

ALL_WWN WWN All WWN cards in the chassis.

ALL_TUNNEL_HIGH_QOS QoS These are available for Brocade 7840 devices only.

ALL_TUNNEL_MED_QOS QoS

ALL_TUNNEL_LOW_QOS QoS



TABLE 15 Predefined MAPS groups (continued)

Predefined group name Object type Description

ALL_TUNNEL_F_QOS QoS monitoring based on pre-defined QoS priorities is done only at the tunnellevel, and the groups correspond to the tunnels on Brocade 7840 devices.Attributes monitored for QoS are throughput and lost packets.

QoS

SWITCH Switch Default group used for defining rules on parameters that are global for the wholeswitch level, for example, security violations or fabric health.

CHASSIS Chassis Default group used for defining rules on parameters that are global for the wholechassis, for example, CPU or flash.

For more information on groups, refer to:

• MAPS groups overview on page 35

• User-defined groups on page 38

User-defined groupsUser-defined groups allow you to specify groups defined by characteristics you select.

In many cases, you may need groups of elements that are more suited for your environment than the predefined groups. For example,small form-factor pluggable (SFP) transceivers from a specific vendor can have different specifications than SFP transceivers fromanother vendor. When monitoring the transceivers, you may want to create a separate group of SFP transceivers for each vendor. Inanother scenario, some ports may be more critical than others, and so can be monitored using different thresholds than other ports.

You can define membership in a group either statically or dynamically. For a group using a static definition, the membership is explicitand only changes if you redefine the group. For a group using a dynamic definition, membership is determined by meeting a filter value.When the value is met, the port or device is added to the group, and is included in any monitoring. When the value is not met, the port ordevice is removed from the group, and is not included in any monitoring data for that group.

The following items should be kept in mind when working with user-defined groups:

• Dynamic groups are only used to group ports.

• The device node WWN information is fetched from the FDMI database, group membership is validated against this database.

• On an Access Gateway device, if you create a group with the feature specified as "device node WWN", then the ports to whichthe devices are connected will be part of the group.

• On a switch connected to Access Gateway, the ports connected to Access Gateway are not grouped in a user-defined group.

• A port or device can be a member of multiple groups.

• A maximum of 64 user-defined groups and imported flows combined is permitted per logical switch.

• All operations on a dynamic group are similar to those for static groups.

• Group names are not case sensitive; My_Group and my_group are considered to be the same.

Creating a static user-defined groupMAPS allows you to create a monitorable group defined using a static definition, in which the membership is explicit and only changes ifyou redefine the group.

As an example of a static definition, you could define a group called MY_CRITICAL_PORTS and specify its members as“2/1-10,2/15,3/1-20”. In this case, the group has a fixed membership, and to add or remove a member from the group you wouldhave to use the logicalGroup command and specify what you want to do (add or remove a member).



To create a static group containing a specific set of ports, complete the following steps.


2. Enter logicalGroup --create group_name -type port -members "member_list".

You can specify either a single port, or specify multiple ports as either individual IDs separated by commas, or a range wherethe IDs are separated by a hyphen.

3. Optional: Enter logicalGroup --show group_name -details to view the group membership.

The following example creates a group named MY_CRITICAL_PORTS whose membership is defined as the ports2/1-10,2/15,3/1-20.

switch:admin> logicalgroup --create MY_CRITICAL_PORTS -type port -members "2/1-10,2/15,3/1-20"

For more information on the logicalGroup command, refer to the Fabric OS Command Reference.

Modifying a static user-defined groupMAPS allows you to modify the membership of a static user-defined group (that is, one with a fixed membership).

To change which ports are in a static user-defined group, complete the following steps.


2. Use the following commands to add or delete specific ports from the group.

• To explicitly add ports to the group, enter logicalGroup --addmember group_name -members member_list.

• To explicitly remove ports from the group, enter logicalGroup --delmember group_name -members member_list.

You need to specify every element in the command. When adding or removing ports, you can specify either a single port(2/15), or specify multiple ports as either individual IDs separated by commas (2/15, 5/16), or a range of ports with the IDsseparated by hyphens (2/15-16/15).


The following example removes the port 2/15 from the MY_CRITICAL_PORTS group:

switch:admin> logicalgroup --delmember MY_CRITICAL_PORTS -members 2/15


Creating a dynamic user-defined groupBy using a dynamic definition, you can create a group that can be monitored, with membership determined by meeting a filter value.When the value is matched, the port or device is added to the group, and it is included in any monitoring. When the value is not matched,the port or device is removed from the group, and it is not included in any monitoring data for that group.

As an example of a dynamic definition, you could specify a port name or an attached device node WWN, and all ports which match theport name or device node WWN will be automatically included in this group. As soon as a port meets the criteria, it is automaticallyadded to the group. As soon as it ceases to meet the criteria, it is removed from the group. The characters in the following table are usedto identify the feature characteristics (port name or device node WWN) that you want to specify to identify the group.

TABLE 16 Group-definition operators

Character Meaning Explanation

* Match any set of characters in the position indicated by the asterisk. Defining the port name as brcdhost* will include any portname starting with brcdhost, such as brcdhost1,brcdhostnew, and so on.



TABLE 16 Group-definition operators (continued)

Character Meaning Explanation

? Match any single character in the position indicated by the questionmark.

Defining the port name as brcdhost? will include any portname that has exactly one character following "brcdhost,"such as brcdhost1, brcdhostn, and so on. However,brcdhostnew will not match this criterion.

[expression] Match any character defined by the expression inside the squarebrackets; that is, one character from the set specified in theexpression. For example, [1-4] will match for values of 1, 2, 3, or 4.

Defining the port name as brcdhost[1-3] will include only theport names brcdhost1, brcdhost2, and brcdhost3.

! Match the string following, and exclude any ports that match. Youmust include the entire term in single quotation marks (').

Defining the port name as '!brcdhost' will include all the portnames except for those that begin with brcdhost.

To create a dynamic group of all the ports that are connected to devices that have a node WWN starting with 30:08:00:05, complete thefollowing steps.


2. Enter logicalgroup --create group_name -type type -feature feature_type -pattern pattern.

For feature_type, either port names or WWNs can be used, not both. Quotation marks around the pattern value are required. If !is specified in the pattern it must be within single quotation marks ('!'). You can only specify one feature as part of a groupdefinition.

3. Optional: Enter logicalgroup --show group_name -details to view the group membership.

The following example creates a group named “GroupWithWwn_30:08:00:05” that has a membership defined as ports connected to adevice with a node WWN that starts with 30:08:00:05.

switch:admin> logicalgroup --create GroupWithWwn_30:08:00:05 -type port -feature nodewwn -pattern "30:08:00:05*"

Alternatively, the following example creates a group that has a membership defined as ports with a port name that begins with "brcdhost."The only difference from the previous example is that the feature is defined as “portname” rather than “nodewwn”.

switch:admin> logicalgroup --create GroupWithNode_brcdhost -type port -feature portname -pattern "brcdhost*"

For more information on the logicalgroup command, refer to the Fabric OS Command Reference.

Modifying a dynamic user-defined groupMAPS allows you to change the definition pattern used to specify a dynamic user-defined group after you have created it.

To modify a dynamic user-defined group after you have created it, complete the following steps.


2. Enter logicalGroup --update group_name -feature feature_name -pattern pattern.

NOTEThe values for group_name and feature_name must match existing group and feature names. You can only specifyone feature as part of a group definition.



3. Use the following commands to add or delete specific ports from the group. (You can also use this command to modify thegroup membership of pre-defined groups.)

• To explicitly add ports to the group, enter logicalGroup --addmember group_name -members member_list.

• To explicitly remove ports from the group, enter logicalGroup --delmember group_name -members member_list.

You need to specify every element in the command. When adding or removing ports, you can specify either a single port(2/15), or specify multiple ports as either individual IDs separated by commas (2/15, 2/16, 3/15), or a range of ports with theIDs separated by hyphens (2/15-16, 3/15).


The following example changes the node WWN of the attached devices in Group_001 to start with 30:08:01.

switch:admin> logicalgroup --update Group_001 -feature nodewwn -pattern "30:08:01*"


Restoring a group to its default membershipMAPS allows you to restore the membership of any modified MAPS group back to its default. This can be done to predefined groupsand dynamic user-defined groups. This command does not work on groups with a static definition.

To restore the membership of a modified MAPS group, complete the following steps.


2. Enter logicalgroup --restore group_name. This restores the group membership to its default.

3. Optional: Enter logicalgroup --show group_name -details to view the group membership.

The following example restores all the deleted members and removes the added members of the GOBLIN_PORTS group. First it showsthe detailed view of the modified GOBLIN_PORTS group, then restores the membership of the group and then it shows the post-restore group details. Notice the changes in the MemberCount, Members, Added Members, and Deleted Members fields between thetwo listings.

switch:admin> logicalgroup --show GOBLIN_PORTS -detail

GroupName : GOBLIN_PORTSPredefined : NoType : PortMemberCount : 11Members : 1-2,12-20Added Members : 2,20Deleted Members : 10-11Feature : PORTNAMEPattern : port1*

switch:admin> logicalgroup --restore GOBLIN_PORTS

switch:admin> logicalgroup --show GOBLIN_PORTS -detail

GroupName : GOBLIN_PORTSPredefined : NoType : PortMemberCount : 11Members : 1,10-19Added Members :Deleted Members :Feature : PORTNAMEPattern : port1*



Cloning a groupMAPS allows you to clone any predefined, static, or dynamic user-defined group.

To clone a group, complete the following steps.


2. Enter logicalgroup --clone existing_group_name -name new_group_name.You can now modify the new group.

The following example clones the predefined group “ALL_TARGET_PORTS” as “ALL_TARGET_PORTS-LR_5”.

switch:admin> logicalgroup --clone ALL_TARGET_PORTS -name ALL_TARGET_PORTS-LR_5

Deleting groupsThe logicalgroup --delete group_name command allows you to remove any logical group other than the predefined groups.

You cannot delete a group that is used by any rules. Adding the -force option to this command overrides the default behavior and forcesthe deletion all the rules that are configured with the given group and then deletes the group. If a logical group is present in user-definedrules, the -force option deletes all the rules that are configured with the given group and then deletes the group.

The following example shows that the user-defined group GOBLIN_PORTS exists, deletes the group, and then shows that the group hasbeen deleted.

switch:admin> logicalgroup --show -------------------------------------------------------------------------------------Group Name |Predefined |Type |Member Count |Members-------------------------------------------------------------------------------------ALL_PORTS Yes Port 48 6/0-15,7/0-31ALL_SFP Yes SFP 11 7/8-14,7/24-27ALL_PS Yes PowerSupply 2 0-1 : : : : : : : : : :GOBLIN_PORTS No Port 10 1/1-5,3/7-9,3/12SFPGroup No SFP 10 1/1-5,3/7-9,3/12

switch:admin> logicalgroup --delete GOBLIN_PORTS

switch:admin> logicalgroup --show -------------------------------------------------------------------------------------Group Name |Predefined |Type |Member Count |Members-------------------------------------------------------------------------------------ALL_PORTS Yes Port 48 6/0-15,7/0-31ALL_SFP Yes SFP 11 7/8-14,7/24-27ALL_PS Yes PowerSupply 2 0-1 : : : : : : : : : :SFPGroup No SFP 10 1/1-5,3/7-9,3/12

MAPS conditionsA MAPS condition includes a monitoring system, a timebase, and a threshold. If the condition is evaluated as true, the actions specifiedin the rule are triggered. The condition depends on the element that is to be monitored.

For example, if you specified that a rule should be triggered if the CRC counter increment in the last minute is greater than 10, then thethreshold value is 10 and the timebase is the preceding minute. In this rule, the condition is the combination of the two; that is, the CRCvalue must be greater than the threshold value of 10 AND this threshold must be exceeded during the minute timebase. If the counterreaches 11 within that minute, the rule would trigger.

MAPS conditions


NOTEMAPS conditions are applied on a per-port basis, not switch- or fabric-wide. For example, 20 ports that each get 1 CRCcounter would not trigger a “greater than 10” rule.

Threshold valuesThresholds are the values at which potential problems might occur. When configuring a rule using mapsrule --config, or creating a ruleusing mapsrule --create, you can use the --value option to specify a threshold value that, when exceeded, triggers specified actions.

For example, you could create a rule that monitors loss-of-signal errors on all host ports, and triggers actions when the counter is greaterthan 14. Then, when the counter reaches 15, the rule triggers the actions. The following is an example of such a rule:

switch:admin> mapsrule --create LoS_greater_than_14 -monitor LOSS_SIGNAL -group ALL_HOST_PORTS -timebase day -op ge -value 14 -action raslog,email,snmp

TimebaseThe -timebase value specifies the time interval between samples, and affects the comparison of sensor-based data with user-definedthreshold values.

You can set the timebase to the following durations:

TABLE 17 Timebase durations

Duration Description How often samples are compared

day Samples used for comparison are one day apart. Once a day.

hour Samples used for comparison are one hour apart. Once every hour.

minute Samples used for comparison are one minute apart. Once every minute.

none A comparison is made between the real-time value and theconfigured threshold value.

N/A.

Supported timebasesThe following table identifies which monitors support which timebases.

TABLE 18 Monitors and supported timebases

Monitor Name Day Hour Minute None

Domain ID change Yes Yes Yes No

Fabric logins Yes Yes Yes No

Fabric reconfigurations Yes Yes Yes No

E_Ports down Yes Yes Yes No

Segmentation changes Yes Yes Yes No

Zone changes Yes Yes Yes No

L2 Device Count Yes Yes Yes No

LSAN Device Count Yes Yes Yes No

Zone Configuration size No No No Yes

FCR Count Yes Yes Yes No

Tunnel (STATE_CHG) Yes Yes Yes No

Tunnel QoS (UTIL) Yes Yes Yes No

MAPS conditions


TABLE 18 Monitors and supported timebases (continued)


QoS packet loss percentage (PKTLOSS) Yes Yes Yes No

Circuit state (CIR_STATE) Yes Yes Yes No

Circuit utilization percentage (CIR_UTIL) Yes Yes Yes No

Circuit packet loss percentage (CIR_PKTLOSS) Yes Yes Yes No

Circuit round-trip times (RTT) Yes Yes Yes No

Circuit jitter (JITTER) Yes Yes Yes No

Power Supply (PS_STATE) No No No No

Fan (FAN_STATE) No No No No

Blade (BLADE_STATE) No No No No

SFP (SFP_STATE) No No No No

WWN (WWN) No No No No

CRC Errors Yes Yes Yes No

Invalid Transmit Words Yes Yes Yes No

Sync Loss Yes Yes Yes No

Link Failure Yes Yes Yes No

Loss of Signal Yes Yes Yes No

Protocol Errors Yes Yes Yes No

Link Reset Yes Yes Yes No

C3 Time outs Yes Yes Yes No

State change Yes Yes Yes No

SFP Current No No No Yes

SFP Receive Power No No No Yes

SFP Transmit Power No No No Yes

SFP Voltage No No No Yes

SFP Temperature No No No Yes

SFP Power On Hours No No No Yes

Flash memory percentage used (FLASH_USAGE) No No No Yes

CPU percentage used (CPU) No No No Yes

Memory percentage used (MEMORY_USAGE) No No No Yes

Ethernet management port state (ETH_MGMT_PORT_STATE) No No No Yes

Temperature Sensor (TEMP) No No No Yes

DCC violations Yes Yes Yes No

HTTP violation Yes Yes Yes No

Illegal command Yes Yes Yes No

Incompatible security DB Yes Yes Yes No

Login violations Yes Yes Yes No

Invalid certifications Yes Yes Yes No

No-FCS Yes Yes Yes No

SCC violations Yes Yes Yes No

SLAP failures Yes Yes Yes No

Telnet violations Yes Yes Yes No

MAPS conditions


TABLE 18 Monitors and supported timebases (continued)


TS out of sync Yes Yes Yes No

Current (CURRENT) No No No No

Receive Power (RXP) No No No No

Transmit Power (TXP) No No No No

Voltage (VOLTAGE) No No No No

Temperature (TEMP) No No No No

Fabric Performance Impact (DEV_LATENCY_IMPACT) No No No Yes

Receive Bandwidth usage percentage (RX) Yes Yes Yes No

Transmit Bandwidth usage percentage (TX) Yes Yes Yes No

Trunk Utilization percentage (UTIL) Yes Yes Yes No

Absent or faulty power supply (BAD_PWR) No No No Yes

Temperature sensors outside range (BAD_TEMP) No No No Yes

Absent or faulty fans (BAD_FAN) No No No Yes

Flash usage (FLASH_USAGE) No No No Yes

Percentage of marginal ports (MARG_PORTS) No No No Yes

Percentage of error ports (ERR_PORTS) No No No Yes

Percentage of faulty ports (FAULTY_PORTS) No No No Yes

Faulty blades (FAULTY_BLADE) No No No Yes

Faulty WWN (WWN_DOWN) No No No Yes

Core blade monitoring (DOWN_CORE) No No No Yes

HA Sync (HA_SYNC) No No No Yes

Receive throughput Yes Yes Yes No

Transmit Frame Count Yes Yes Yes No

Receive Frame Count Yes Yes Yes No

Transmit throughput Yes Yes Yes No

IO Read Command Count Yes Yes Yes No

IO Write Command Count Yes Yes Yes No

IO Read Data Yes Yes Yes No

IO Write Data Yes Yes Yes No

Throughput Degradation Yes Yes Yes Yes

MAPS rules overviewA MAPS rule associates a condition with actions that need to be taken when the condition is evaluated to be true and the specified rule istriggered. A MAPS rule can exist outside of a MAPS policy, but are only evaluated by MAPS when the rule is part of the active policy.

Each rule specifies the following items:

• A group of objects to be evaluated. Refer to MAPS groups overview on page 35 for additional information.

• The condition being monitored. Each rule specifies a single condition. A condition includes a timebase and a threshold. Refer to MAPS conditions on page 42 for additional information.

• The actions to take if the condition is evaluated to be true. Refer to MAPS rule actions on page 46 for additional information.

The combination of actions, conditions, and groups allows you to create a rule for almost any scenario required for your environment.

MAPS rules overview


MAPS rule actionsWhen you create a rule, you associate an action for MAPS to take if the condition defined in the rule evaluates to true. Each rule can haveone or more actions associated with it. For example, you can configure a rule to log a RASLog message and fence the port if the numberof CRC errors on any E_Port is greater than 20 per minute.

The global action settings on the switch take precedence over the actions defined in the rules. For example, if the global action settingsallow RASLog alerts, but do not allow port fencing, then in the example given in the previous paragraph, if the CRC threshold is reached aRASLog message would be logged but the port would not be fenced. To enable global actions, use the mapsConfig --actionscommands. For more details, refer to Enabling or disabling rule actions at a global level on page 46. Refer to the Fabric OS CommandReference for further details on using the mapsConfig command.

MAPS provides the following actions for rules:

• RASLog messages on page 51

• MAPS SNMP traps on page 47

• E-mail alerts on page 46

• Port fencing and port decommissioning on page 48

• Switch critical on page 50

• Switch marginal on page 50

• SFP marginal on page 50

E-mail alertsAn e-mail alert action sends information about the event to one or more specified e-mail addresses. The e-mail alert specifies thethreshold and describes the event, much like an error message.

To configure the e-mail recipients, use the mapsConfig --emailcfg command. Multiple destination e-mail addresses are possible; theymust be separated using a comma between each individual address and each address must be a complete e-mail address. For example,[email protected] is a valid e-mail address; abc@brocade is not. Refer to Sending alerts using e-mail on page 56 for moreinformation.

To clear all configured email address(es), enter mapsconfig --emailcfg -address none. All configured email addresses will be erased.

Enabling or disabling rule actions at a global levelAllowable actions on a switch can be specified globally, and supersede any actions specified in individual rules. Enabling and disablingactions at a global level allows you to configure rules with stricter actions, such as port fencing, but disable the action globally until youcan test the configured thresholds. After validating the thresholds, you can enable an action (such as port decommissioning) globallywithout having to change all of the rules.

ATTENTIONFor MAPS to trigger an action, the action must be explicitly enabled using the mapsconfig --actions command.

To enable or disable actions at a global level, complete the following steps.

1. Enter mapsconfig --show to display the actions that are currently allowed on the switch.

MAPS rules overview


2. Enter mapsconfig --actions and specify all of the actions that you want to allow on the switch, for example, mapsconfig --actions action1, action2, action3 ... (up to the complete set of actions).

NOTEIf you are changing the list of active actions, you need to specify all the actions to be active. For example, if you areadding RASLog notifications to a switch that already has e-mail notifications enabled, you must specify both “email”and “RASLog” as actions in the mapsconfig command.

To disable all actions, enter mapsconfig --actions none. The keyword none cannot be combined with any other action.

The following example shows that RASLog notification (raslog) is not an active action on the switch, and then adds it to the list of allowedactions.

switch:admin> mapsconfig --show Configured Notifications: EMAIL,DECOM,FENCEMail Recipient: [email protected] members :PORT : CIRCUIT :SFP :

switch:admin> mapsconfig --actions raslog,email,decom,fence

switch:admin> mapsconfig --show Configured Notifications: RASLOG,EMAIL,DECOM,FENCEMail Recipient: [email protected] members :PORT : CIRCUIT :SFP :

MAPS SNMP trapsWhen specific events occur on a switch, SNMP generates a message (called a “trap”) that notifies a management station.

A MAPS SNMP trap forwards the following information to an SNMP management station:

• Name of the element whose counter registered an event

• Area and index number of the threshold that the counter crossed

• Event type

• Value of the counter that exceeded the threshold

• State of the element that triggered the alarm

• Source of the trap

In environments where you have a high number of messages coming from a variety of switches, you might want to receive them in asingle location and view them using a graphical user interface (GUI). In this type of scenario, Simple Network Management Protocol(SNMP) notifications could be the most efficient notification method, because you can avoid having to log in to each switch individuallyas you would have to do for error log notifications.

In order to get the event notifications, you must configure the SNMP software to receive the trap information from the network device,and you must configure the SNMP agent's IP address on the switch to send the trap to the management station. You can configureSNMP traps receiver using the snmpconfig command. For additional information on configuring the SNMP agent using snmpconfig,refer to the Fabric OS Command Reference.

SNMP MIB supportMAPS requires SNMP management information base (MIB) support on the device for management information collection. Foradditional information on SNMP MIB support, refer to the MIB Reference Manual.

MAPS rules overview


Port fencing and port decommissioningMAPS supports port fencing for both E_Ports and F_Ports. MAPS also supports port decommissioning for E_Ports. However,decommissioning for F_Ports can only be done with MAPS in conjunction with Brocade Network Advisor. These actions automaticallytake ports offline when configured thresholds in a given rule are exceeded. Port fencing immediately takes ports offline, which mightcause loss of traffic. Port decommissioning takes a port offline without loss of traffic. Both are disabled by default. Port decommissioningand port fencing can only be configured for the port health monitoring systems for which decommissioning is supported.

Port decommissioning cannot be configured by itself in a MAPS rule or action. It requires port fencing to be enabled in the same rule. Ifyou attempt to create a MAPS rule or action that has port decommissioning without port fencing, the rule or action will be rejected.MAPS can be configured to have only port fencing enabled in a rule; if this is the case, the port will be taken offline immediately.

MAPS supports port fencing and port decommissioning actions for rules that monitor CRC, ITW, PE, LR, STATE_CHG, or C3TXTOerrors from physical ports, such as E_Ports, F_Ports, or U_Ports. Otherwise, for circuits, MAPS supports only port fencing actions forrules that monitor changes of state (STATE_CHG). Refer to the Port Health monitoring thresholds on page 103 tables for these rules.

Be aware that if multiple rules for the same counter are configured with different thresholds, then both port fencing and portdecommissioning should be configured for the rule with the highest threshold monitored. For example, if you configure one rule with aCRC threshold value “greater than 10 per minute” and you configure a second rule with a CRC threshold value “greater than 20 perminute,” you should configure port fencing and port decommissioning as the action for the rule with the 20-per-minute threshold,because configuring it for the 10-per-minute rule will block the other rule from being triggered.

Port decommissioning for E_Ports and F_PortsFor E_Ports, if port decommissioning fails, MAPS will fence the port. Switches themselves can decommission E_Ports through MAPS.In this case, when port decommissioning is triggered on an E_Port, the neighboring switches will perform a handshake so that traffic isre-routed before the port is disabled. Be aware that there are multiple reasons that the port-decommissioning operation between twoE_Ports could fail; for example, if the link that fails is the last link between the two switches. To see which parameters can trigger portfencing and port decommissioning, refer to Port Health monitoring thresholds on page 103.

For F_Ports, port decommissioning will only work if Brocade Network Advisor is actively monitoring the switch. Brocade NetworkAdvisor can decommission F_Ports based on specified criteria (refer to Port Health monitoring thresholds on page 103.) MAPSnotifications are integrated with Brocade Network Advisor, which in turn must coordinate with the switch and the end device toorchestrate the port decommissioning. If Brocade Network Advisor is not configured on a switch, MAPS will fence the F_Port.

For more information on port fencing, port decommissioning, and related failure codes, refer to the Fabric OS Administrator's Guide.

Port decommissioning and firmware downgrades• If the port decommissioning (decom) configuration is in any of the logical switches, the firmwareDownload operation from

Fabric OS 7.3.0 to a previous version will fail with one of the following messages:

– If the decom action is configured in the MAPS actions, the following error message is displayed.

Downgrade is not allowed, because port decommmission(decom) actions are enabled in some logical switches.Please delete decom action from the FID(S) <fid1>, <fid2> …

– If any of the MAPS rules have the decom action configured, the following error message is displayed.

Downgrade is not allowed, because port decommission(decom) actions are configured in user defined rules in some logical switches. Please delete decom action from all user defined rules in the FID(S) <fid1>,<fid2> …

• If there are any default policy rules present with port decommissioning configured, the firmware downgrade is not blocked as inthis case, the decommissioning rules are mapped to Fabric OS 7.2.x port fencing rules. That is, a default Fabric OS 7.3.0

MAPS rules overview


MAPS rule with port commissioning specified will remain mapped to the same rule, but without port decommissioning as anaction, when the switch is downgraded to version Fabric OS 7.2.x.

• Currently the decommission action is present for the port monitoring rules in dflt_aggressive_policy. When the switch isrebooted using version Fabric OS 7.2.x, the default rules in dflt_aggressive_policy which had port decommissioning specifiedwill have port fencing specified.

• User-defined rules in the active policy are not checked to see if they have port decommissioning configured, as user-definedrules in the active policy are present only in memory and are erased as soon as a different policy is enabled, whether in FabricOS 7.3.0 or any earlier version.

Configuring port decommissioningPort decommissioning is a two-part process. You configure port decommissioning along with port fencing in the MAPS actionsconfiguration, and then you configure it as an action in a MAPS rule.

To enable port decommissioning, complete the following steps.


2. Create a rule or action as follows:

• Enter mapsconfig --actions fence,decom to create an action for the entire switch.

• Use the mapsrule --create new_rule_name -group group_name -monitor monitor_value -timebase time_unit -opcomparison_operator -value comp_op_value -action fence,decom command to create a rule.

The following example enables port fencing and port decommissioning for a switch and then displays the confirmation.

switch246:FID128:admin> mapsconfig --actions fence,decomswitch246:admin> mapsconfig --showConfigured Notifications: FENCE,DECOMMail Recipient: Not ConfiguredPaused members :===============PORT :CIRCUIT :SFP :

The following example makes port fencing and port decommissioning part of a rule and then displays the confirmation.

switch246:FID128:admin> mapsrule --create crc_decom -group ALL_E_PORTS -monitor CRC -timebase min -op g -value 3 -action raslog,fence,decom switch246:admin> mapsrule --show crc_decomRule Data:----------RuleName: crc_decomCondition: ALL_E_PORTS(CRC/min>3)Actions: raslog,fence,decomAssociated Policies:

Enabling port fencingPort fencing in MAPS can be either an action that is part of the overall switch configuration, or part of a specific rule. If it is part of theoverall switch configuration, it will happen any time the port fails, while if it is part of a rule, the port will be fenced if that rule is triggered.Multiple rules can have port fencing as an action; it will happen if any of them are triggered.

To enable port fencing, complete the following steps.


MAPS rules overview


2. Create a rule or action as follows:

• To set up a port fencing action for the entire switch, enter mapsConfig --actions fence.

• To create a rule for port fencing, enter mapsRule --create new_rule_name -group group_name -monitor monitor_value -timebase time_unit -op comparison_operator -value comp_op_value -action fence.

The following example enables port fencing on a switch and then displays the confirmation.

switch1234:admin> mapsconfig --actions raslog,fenceswitch1234:admin> mapsconfig --show

Configured Notifications: RASLOG,FENCEMail Recipient: Not ConfiguredPaused members :===============PORT :CIRCUIT :SFP :

The following example makes port fencing part of a rule and then displays the confirmation.

switch1234:admin> mapsrule --create crc_fence_Eport -group ALL_E_PORTS -monitor CRC -timebase min -op g -value 3 -action raslog,fence switch:admin> mapsrule --show crc_fence_Eport

Rule Data:----------RuleName: crc_fence_EportCondition: ALL_E_PORTS(CRC/min>3)Actions: raslog,fence Associated Policies:

SFP marginalThe SPF_MARGINAL action sets the state of the affected small form-factor SPF_MARGINAL pluggable (SFP) transceiver in the MAPSdashboard to "Green“ or "Yellow.” The word "Green" indicates that the transceiver is operating normally; the word "Yellow" indicates it isoperating outside the normal range.

This action is valid only in the context of Advanced SFP groups.

NOTEThis applies only to Brocade-branded SFPs having speeds greater than or equal to 10G.

Switch criticalThe “switch critical” action sets the state of the affected switch in the MAPS dashboard display to SW_CRITICAL. This action does notbring the switch down, but only affects what is displayed in the dashboard. This action is valid only in the context of Switch Status Policy-related rules.

Switch marginalThe “switch marginal” action sets the state of the affected switch in the MAPS dashboard to SW_MARGINAL. This action does not affectthe actual state of the switch, but only affects what is displayed in the dashboard. This action is valid only in the context of Switch StatusPolicy-related rules.

MAPS rules overview


RASLog messagesFollowing an event, MAPS adds an entry to the switch event log for an individual switch. The RASLog stores event information but doesnot actively send alerts. You can use the errShow command to view the RASLog.

MAPS triggers RASLog messages MAPS-1001 to MAPS-1004 when the condition in a rule is true for regular counters or when theerrors are above the threshold value. Depending on the state and the condition set, RASLog generates INFO, WARNING, CRITICAL, orERROR messages.

TABLE 19 RASLog message category for non-state-based monitoring systems

Condition description RASLog message category Example

A rule with “>”, “>=” or “==” condition Generates a WARNING (MAPS-1003)message.

LOSS_SIGNAL monitoring system

Exception:

Class 3 Transmission Timeouts (C3TX_TO), where the “>” and“>=” condition generates an ERROR (MAPS-1002) messageand a “ ==” condition generates a WARNING (MAPS-1003)message.

A rule with “<” or “<=” condition Generates an INFO (MAPS-1004)message.

TABLE 20 RASLog message category for state-based monitoring systems

Condition description RASLog message category Example

A rule with “ ==” or “!=” condition Generates a WARNING (MAPS-1003)message.

LOSS_SIGNAL monitoring system

Exception:

FPI monitoring for the IO_PERF_IMPACT state, where the “==”and “!=” generates a WARNING (MAPS-1003) message and a“==” for IO_FRAME_LOSS state generates a CRITICAL(MAPS-1001) message.

In Fabric OS 8.0.1 release, MAPS provides the port name information as part of RASLog.

2015/06/25-21:11:43, [MAPS-1003], 239, FID 128, WARNING, odin82, PortName, F-Port 0,Condition=ALL_OTHER_F_PORTS(LF/min>5), Current Value:[LF,100], RuleName=defALL_OTHER_F_PORTSLF_5,Dashboard Category=Port Health.Refer to the Fabric OS Message Reference for a complete listing and explanation of MAPS-related RASLog messages.

Working with MAPS rules and actionsMAPS allows you to view, create, modify, and delete rules, and enable or disable actions.

Viewing MAPS rulesMAPS allows you to see all the MAPS rules on a switch, or the details of a single MAPS rule.

To view the MAPS rules on a switch, complete the following steps.


MAPS rules overview


2. Choose from the following options:

• To view all the MAPS rules on the switch, enter mapsRule --show -all. This displays all the rules on the switch, listing therule name, the actions in the rule, and the threshold condition that triggers the rule.

• To view the details of a MAPS rule on the switch, enter mapsRule --show rule_name. This displays the rule name, theactions in the rule, the threshold condition that triggers the rule, and the names of any policies associated with the rule. Ifthe rule is not associated with any policies, nothing is shown for the associated policies.

The following example shows all rules on the switch. Notice that the policies are not shown in the output.

switch:admin> mapsrule --show -all -------------------------------------------------------------------RuleName Action Condition -------------------------------------------------------------------Rule1 Raslog, Fence, SNMP Switch(SEC_IDB/Min>0) Rule2 Raslog Switch(SEC_IDB/Hour>1) NewRule1 Raslog, Fence, SNMP Switch(SEC_IDB/Min>0) NewRule2 Raslog, Fence, SNMP Switch(SEC_IDB/Hour>1)

The following example shows the policy names associated with the rule name “Rule1”.

switch:admin> mapsrule --show Rule1 RuleName: Rule1Action: Raslog, Fence, SNMPCondition: Switch(SEC_IDB/Min>0) Policies Associated: daily_policy, crc_policy

Creating a ruleEach MAPS rule monitors a single condition. When you create a rule, you can choose to add it to a policy.

To create a policy rule, complete the following steps.

1. Enter mapsrule --create rule_name followed by the rule parameters, and optionally the policy you want to assign it to. Rulenames are not case sensitive; My_Rule and my_rule are considered to be the same. Rule names are limited to a length of 72characters.

2. Optional: Enter mapsrule --show rule_name to display the rule.

3. Optional: If you added the rule to the active policy, you must re-enable the policy for the rule to take effect by enteringmapspolicy --enable policy policy_name.

NOTEIf you are specifying a group, the group must already exist.

Example of creating a rule to generate a RASLog messageThe following example creates a rule to generate a RASLog message if the CRC counter for a group of critical ports is greater than 10 inan hour. This rule is added to the daily_policy, and the daily_policy is re-enabled for the rule to take effect.

switch:admin> mapsrule --create check_crc -monitor crc -group critical_ports -timebase hour -op g -value 10 -action raslog -policy daily_policyswitch:admin> mapsrule --show check_crc

Rule Data:----------RuleName: check_crcCondition: critical_ports(crc/hour>10)Actions: raslogPolicies Associated: daily_policy

switch:admin> mapspolicy --enable daily_policy

MAPS rules overview


Example of creating a rule for a flowTo accommodate creating a rule for a flow, mapsrule accepts a flow name as a value for the -group parameter. The following exampleillustrates the structure.

switch:admin> mapsrule --create check_crc2 -monitor crc -group MyFlow -timebase min -op g -value 15 -action raslog -policy daily_policy2

NOTEBefore you can create a rule for a flow, you must import it using the mapsconfig --importcommand.

Modifying a MAPS ruleYou can modify only user-defined MAPS rules. You cannot modify the default MAPS rules.

To modify a user-defined MAPS rule, complete the following steps.

1. Enter mapsrule --show rule_name to display the rules, so you can identify the rule you want to modify.

2. Enter mapsrule --config followed by the parameters you are changing to modify the rule.

NOTEYou only need to specify the parameters you are changing. Any parameters you do not specify are not changed.

3. Optional: Enter mapsrule --show to display the updated rule.

4. If the rule is included in the active policy you must re-enable the policy using mapspolicy --enable policy policy_name for themodified rule to take effect.

Changing one parameterThe following example changes the timebase for a rule from minutes to hours.

switch:admin> mapsrule --show check_crc Rule Data:----------RuleName: check_crcCondition: critical_ports(crc/minute>5)Actions: raslogPolicies Associated: daily_policy

switch:admin> mapsrule --config check_crc -timebase hour

switch:admin> mapsrule --show check_crc Rule Data:----------RuleName: check_crcCondition: critical_ports(crc/hour>5)Actions: raslogPolicies Associated: daily_policy

MAPS rules overview


Changing multiple parametersThe following example modifies the rule “check_crc2” to generate a RASLog message and an e-mail message if the CRC counter for agroup of critical ports is greater than 15 in an hour (rather than 10 in a minute). This rule is part of the active policy, so the policy is re-enabled for the change to take effect.

switch:admin> mapsrule --show check_crc2 Rule Data:----------RuleName: check_crc2Condition: critical_ports(crc/minute>10)Actions: RASLOG Policies Associated: daily_policy

switch:admin> mapsrule --config check_crc2 -timebase hour -op g -value 15 -action raslog,email -policy daily_policy

switch:admin> mapsrule --show check_crc2 Rule Data:----------RuleName: check_crc2 Condition: critical_ports(crc/hour>15)Actions: RASLOG, EMAILMail Recipient: [email protected] Associated: daily_policy


Cloning a ruleYou can clone both default and user-defined MAPS rules.

To clone a MAPS rule, complete the following steps.

1. Use the mapsrule --show rule_name command to display the rule you want to clone.

2. Use the mapsrule --clone oldRuleName -rulename newRuleName command to duplicate the rule.

NOTEIf no parameters other than --clone oldRuleName -rulename newRuleName are specified, an exact copy of theoriginal rule is created.

For more information on this command and all its parameters, refer to the Fabric OS Command Reference.

Creating an exact cloneThe following example shows the existing rule (“old_rule” ), creates an exact clone of that rule and names it “new_rule”, and then displaysthe cloned rule.

switch:admin> mapsrule --show old_rule RuleName: old_ruleAction: Raslog, Fence, SNMPCondition: Switch(SEC_IDB/Min>0) Policies Associated: none

switch:admin> mapsrule --clone old_rule -rulename new_rule

switch:admin> mapsrule --show new_rule RuleName: new_ruleAction: Raslog, Fence, SNMPCondition: Switch(SEC_IDB/Min>0) Policies Associated: none

MAPS rules overview


Cloning a rule and changing its valuesWhen you clone a rule, you can also specify the parameters you want to be different from the old rule in the new rule. To modify the rule,use the --config keyword. The following example clones “myOldRule” as “myNewRule” and changes the flow that is being monitored to“flow2” and assigns it the monitor “monitor2”. It then displays the rule.

switch:admin> mapsrule --clone myOldRule -rulename myNewRule

switch:admin> mapsrule --config -group flow2 -monitor monitor2

admin> mapsrule --show myNewRule RuleName: myNewRuleAction: Raslog, Fence, DecomCondition: Switch(SEC_IDB/Hour>10) Policies Associated: slow_monitor2

Cloning a rule and changing its timebaseThe following example creates a clone of “Rule1” with a timebase of an hour, and then displays the rule.

switch:admin> mapsrule --clone Rule1 -rulename NewRule2 -timebase hour

switch:admin> mapsrule --show NewRule2 RuleName: NewRule2Action: Raslog, Fence, SNMPCondition: Switch(SEC_IDB/Hour>0) Policies Associated: none

Rule deletionA rule must be removed from every policy that references it before it can be deleted.

Although you can use the mapsrule --delete rule_name command to delete individual instances of a user-defined rule, you mustremove the rule individually from every policy that uses the rule before you can finally delete the rule itself. This could require a lot oftedious work if the rule has been added to many policies. To simplify the process, adding the -force keyword to the command allows youto delete the named user-defined rule from every policy that uses the rule before deleting the rule itself.

NOTEThere is a difference between using the -force keyword to delete a rule and using it to delete a group. When you delete a ruleusing this option, the rule is first removed from all policies, and then the rule itself is deleted. When you delete a group, first therule referencing the specified group is deleted and, if the rule is part of any policies, it is deleted from those policies). Then thegroup is deleted. Refer to Deleting groups on page 42 for information on deleting groups.

The following example shows that the rule port_test_rule35 exists in test_policy_1. The examples show the rule being deleted from thatpolicy using the -force keyword, and then it shows a verification that the rule has been deleted from the policy.

switch:admin> mapspolicy --show test_policy_1 Policy Name: xyz_test60Rule List Action Condition---------------------------------------------------------------------def_port_test_rule35 RASLOG ALL_PORTS(CRC/min>300)def_port_test_rule50 RASLOG ALL_PORTS(CRC/min>650) def_port_test_rule80 RASLOG ALL_PORTS(CRC/min>850) Active Policy is 'dflt_conservative_policy'.

switch:admin> mapsrule --delete port_test_rule35 -force Execution is successful.2014/02/02-17:55:38, [MAPS-1101], 255, FID 128, INFO, sw0, Rule port_test_35 is deleted.

switch:admin> mapspolicy --show test_policy_1 Policy Name: xyz_test60Rule List Action Conditionport_test_rule50 RASLOG ALL_PORTS(CRC/min>650) port_test_rule80 RASLOG ALL_PORTS(CRC/min>850)

MAPS rules overview


Sending alerts using e-mailE-mail alerts allow you to be notified immediately when MAPS detects that an error has occurred. There is a limit of five e-mailaddresses per alert, and the maximum length for each individual e-mail address is 128 characters.

To configure MAPS to send an alert using e-mail, complete the following steps.

1. Configure and validate the e-mail server. Refer to Configuring e-mail server information on page 57 for information onspecifying the e-mail server to be used.

2. Enter the mapsconfig --emailcfg command to set the e-mail parameters.

To send an alert to multiple e-mail addresses, separate the addresses using a comma.

NOTEYou can also send a test e-mail alert. Refer to E-mail alert testing on page 56 for additional information.

Specifying e-mail address for alertsThe following example specifies the e-mail address for e-mail alerts on the switch, and then displays the settings. It assumes that youhave already correctly configured and validated the e-mail server.

switch:admin> mapsconfig --emailcfg -address [email protected]

switch:admin> mapsconfig --show Configured Notifications: RASLOG,EMAIL,FENCE,SW_CRITICAL,SW_MARGINALMail Recipient: [email protected] Monitoring: EnabledPaused members :===============PORT :CIRCUIT :SFP :

Specifying multiple e-mail addresses for alertsThe following example specifies multiple e-mail addresses for e-mail alerts on the switch, and then displays the settings. It assumes thatyou have already correctly configured and validated the e-mail server.

switch:admin> mapsconfig --emailcfg -address [email protected], [email protected]

switch:admin> mapsconfig --show Configured Notifications: RASLOG,EMAIL,FENCE,SW_CRITICALMail Recipient: [email protected], [email protected] members :PORT : CIRCUIT :SFP :

Clearing the configured e-mail addressTo clear the configured e-mail addresses, enter mapsconfig --emailcfg -address none. All configured e-mail addresses will be erased.

E-mail alert testingYou can send a test e-mail message to check that you have the correct e-mail server configuration. You can use any combination ofdefault and custom subject or message for your test e-mail message.

To verify that the MAPS e-mail feature is correctly configured, enter mapsConfig --testmail optional_customizations command. Youcan customize the subject and message as described in the following table.

MAPS rules overview


TABLE 21 Test e-mail command parameters

Command option Details

--testmail MAPS sends the default test e-mail with the default subject “MAPS Welcome mail” and message text“Test mail from switch”.

--testmail –subject subject MAPS sends the test e-mail with the subject you provided and the default message text.

--testmail -message message MAPS sends the test e-mail with the default subject and the message text you provided.

--testmail –subject subject -messagemessage

MAPS sends the test e-mail with the subject and message text you provided.

For more information on this command, refer to the Fabric OS Command Reference.

Configuring e-mail server informationFabric OS allows you to specify the e-mail server used to send e-mail alerts. The e-mail configuration is global at the chassis level and iscommon for all logical switches in the chassis.

NOTETo send e-mail, the domain name system (DNS) server configuration has to be specified. Refer to the Fabric OS CommandReference for information on using the dnsconfig command.

The relay host is a smart relay server which is used to filter e-mail messages coming from outside world to the switch. If the relay host isnot configured, all the e-mails from and to the switch will be handled by the DNS mail server. If a relay host is configured all the e-mailsare routed through the relay host to the switch, reducing the load on the DNS mail server.

To specify the e-mail server used to send e-mail alerts, complete the following steps.


2. Enter relayconfig --config -rla_ip relay IP address -rla_dname “relay domain name”. The quotation marks are required.There is no confirmation of this action.

3. Optional: Enter relayconfig --show.This displays the configured e-mail server host address and domain name.

The following example configures the relay host address and relay domain name for the switch, and then displays it.

switch:admin> relayconfig --config -rla_ip 10.70.212.168 -rla_dname "mail.my-company.com"

switch:admin> relayconfig --show Relay Host: 10.70.212.168 Relay Domain Name: mail.my-company.com

For additional information on the relay host and the relayconfig command, refer to the Fabric OS Command Reference.

Viewing configured e-mail server informationFabric OS allows you to view the e-mail server host address and domain name configured for MAPS.

To view the e-mail server host address and domain name configured for MAPS, complete the following steps.


2. Optional: Enter relayConfig --show.This displays the configured e-mail server host address and domain name.

MAPS rules overview


The following example displays the configured relay host address and relay domain name for the switch.

switch:admin> relayconfig --show Relay Host: 10.70.212.168 Relay Domain Name: mail.my-company.com

For additional information on the relay host and the relayConfig command, refer to the Fabric OS Command Reference.

Deleting e-mail server configurationFabric OS allows you to remove the e-mail server configuration used by MAPS.

To remove the e-mail server host address and domain name configured for MAPS, complete the following steps.


2. Enter relayConfig --delete.There is no confirmation of this action.

3. Optional: Enter relayConfig --show to confirm the deletion.

The following example deletes the configured relay host address and relay domain name for the switch, and then shows that these itemshave been deleted.

switch:admin> relayconfig --delete

switch:admin> relayconfig --show Relay Host: Relay Domain Name:

For additional information on the relay host and the relayConfig command, refer to the Fabric OS Command Reference.

MAPS policies overviewA MAPS policy is a set of rules. When you enable a policy, all of the rules in the policy are in effect. Refer to MAPS rules overview onpage 45 for more information about MAPS rules.

A switch can have multiple policies. For example, you can have a policy for everyday use and you can have another policy for when youare running backups or performing switch maintenance.

The following restrictions apply to policies:

• Only one policy can be active at a time.

• When you enable a policy, it becomes the active policy and the rules in the active policy take effect.

• One policy must always be active on the switch.

– You can have an active policy with no rules, but you must have an active policy.

NOTEIt is recommended that you avoid using policies that have no rules.

– You cannot disable the active policy. You can only change the active policy by enabling a different policy.

Viewing policy valuesYou can display the values for a policy by using the mapspolicy --show policy_name |grep group_name command.

MAPS policies overview


The following example displays all the thresholds for host ports in the My_all_hosts_policy.

switch:admin> mapspolicy --show My_all_hosts_policy | grep HOSTdefALL_HOST_PORTSC3TXTO_10 |ALL_HOST_PORTS(C3TXTO/MIN>10) |FENCE,SNMP,EMAIL |defALL_HOST_PORTSC3TXTO_3 |ALL_HOST_PORTS(C3TXTO/MIN>3) |RASLOG,SNMP,EMAIL|defALL_HOST_PORTSCRC_10 |ALL_HOST_PORTS(CRC/MIN>10) |RASLOG,SNMP,EMAIL|defALL_HOST_PORTSCRC_20 |ALL_HOST_PORTS(CRC/MIN>20) |FENCE,DECOM,SNMP |defALL_HOST_PORTSITW_21 |ALL_HOST_PORTS(ITW/MIN>21) |RASLOG,SNMP,EMAIL|defALL_HOST_PORTSITW_40 |ALL_HOST_PORTS(ITW/MIN>40) |DECOM,SNMP,EMAIL |defALL_HOST_PORTSLF_3 |ALL_HOST_PORTS(LF/MIN>3) |RASLOG,SNMP,EMAIL|defALL_HOST_PORTSLOSS_SIGNAL_3 |ALL_HOST_PORTS(LOSS_SIGNAL/MIN>3) |RASLOG,SNMP,EMAIL|defALL_HOST_PORTSLOSS_SYNC_3 |ALL_HOST_PORTS(LOSS_SYNC/MIN>3) |RASLOG,SNMP,EMAIL|defALL_HOST_PORTSLR_10 |ALL_HOST_PORTS(LR/MIN>10) |FENCE,DECOM,SNMP |defALL_HOST_PORTSLR_5 |ALL_HOST_PORTS(LR/MIN>5) |RASLOG,SNMP,EMAIL|defALL_HOST_PORTSPE_3 |ALL_HOST_PORTS(PE/MIN>3) |RASLOG,SNMP,EMAIL|defALL_HOST_PORTSPE_7 |ALL_HOST_PORTS(PE/MIN>7) |FENCE,DECOM,SNMP |defALL_HOST_PORTSRX_75 |ALL_HOST_PORTS(RX/HOUR>75) |RASLOG,SNMP,EMAIL|defALL_HOST_PORTSSTATE_CHG_10 |ALL_HOST_PORTS(STATE_CHG/MIN>10) |FENCE,DECOM,SNMP |defALL_HOST_PORTSSTATE_CHG_5 |ALL_HOST_PORTS(STATE_CHG/MIN>5) |RASLOG,SNMP,EMAIL|defALL_HOST_PORTSTX_75 |ALL_HOST_PORTS(TX/HOUR>75) |RASLOG,SNMP,EMAIL|defALL_HOST_PORTSUTIL_75 |ALL_HOST_PORTS(UTIL/HOUR>75) |RASLOG,SNMP,EMAIL|

Predefined policiesMAPS provides four predefined policies that you can neither modify nor delete.

The four predefined policies are as follows:


This policy contains rules with more lenient thresholds that allow a buffer and do not immediately trigger actions. Use this policyin environments where the elements are resilient and can accommodate errors.


This policy contains rules with thresholds values between the aggressive and conservative policies.


This policy contains rules with very strict thresholds. Use this policy if you need a pristine fabric (for example, FICON fabrics).

• dflt_base_policy

This policy contains rules that monitor the unlicensed features which were made available earlier through Fabric Watch. Refer to Unlicenced feature monitoring for a description of these features.

Although you cannot modify these predefined policies, you can create a policy based on these policies that you can modify. For moreinformation, refer to the following links.

• Modifying a default policy on page 64

• Creating a policy on page 62

• User-defined policies on page 60

MAPS automatically monitors the management port (Eth0 or Bond0), as the rule for Ethernet port monitoring is present in all fourdefault policies. While these cannot be modified, the management port monitoring rules can be removed from cloned policies.

For System z and FICON environments, Brocade recommends that you start with the Aggressive policy. For Open Systemsenvironments and other environments, Brocade recommends that you start with the Moderate policy.

Default MAPS policy rulesEach of the predefined default policies has its own rule set.

To view the rules for a policy, enter mapsPolicy --show followed by the name of the policy.



User-defined policiesMAPS allows you to define your own policies. You can create a policy and add rules to it, or you can clone one of the default policies andmodify the cloned policy.

Refer to Working with MAPS policies on page 60 for information on working with user-defined policies.

Fabric Watch legacy policiesWhen you migrate from Fabric Watch to MAPS, the following three policies are automatically created if you have used mapsConfig --fwconvert. If you do not use this command, then these policies are not created.

• fw_custom_policy

This policy contains all of the monitoring rules based on the custom thresholds configured in Fabric Watch.

• fw_default_policy

This policy contains all of the monitoring rules based on the default thresholds configured in Fabric Watch.

• fw_active_policy

This policy contains all of the monitoring rules based on the active thresholds in Fabric Watch at the time of the conversion.

These policies are treated as user-defined policies. You can modify them by adding and deleting rules, and you can delete them.

The following factors also apply to Fabric Watch conversions:

• Converted active Fabric Watch policies reference either custom or default Fabric Watch rules.

• No custom rules are created if the "custom" thresholds are the same as the default thresholds. Instead, the default Fabric Watchrule will be referenced in the fw_custom_policy.

• Converted rules are prefixed with “fw_def_name” or “fw_cust_name”. The value for name is a string based on the Fabric Watchclass, the area, threshold criteria (above high or below low), and the threshold number. This is the same pattern that MAPS rulesuse.

Changes to threshold behaviors after conversionMAPS has inherent design differences from Fabric Watch when it handles thresholds. During conversion, the following changes occur inthreshold behavior:

• Above-High is converted for all the thresholds, because they always indicate an error.

• Above-Low is converted for port-related classes: PORT, E_PORT, F_PORT, etc.

• Below-Low is converted for SFP parameters, where a Below-Low event for voltage or current indicates an error state.

• Below-High is ignored during conversion for all classes.

NOTEIf you still want to configure any unconverted rules, given the above behavioral changes, you can create rules manually using the--op option of the mapsrule command to add them to the policy.

Working with MAPS policiesThe following sections discuss viewing, creating, enabling, and modifying MAPS policies.



Viewing policy informationMAPS allows you to view the policies on a switch. You can use this command to show all policies, only a particular policy, or a summary.

To view the MAPS policies on a switch, complete the following steps.


2. Choose from the following options:

• To view a summary of all the policies on the switch, enter mapsPolicy --show -summary.

• To view the features of all the policies on the switch, enter mapsPolicy --show -all.

• To view the features of a specific policy on the switch, enter mapsPolicy --show policy_name.

The following example shows the result of using the --show -summary option.

switch:admin> mapsPolicy --show -summary

Policy Name Number of Rules------------------------------------------------------------dflt_aggressive_policy : 196dflt_conservative_policy : 198dflt_moderate_policy : 198fw_default_policy : 109fw_custom_policy : 109fw_active_policy : 109Active Policy is 'dflt_moderate_policy'.

The following example shows an excerpted result of using the --show policy_name option for the fw_default_policy. The entire listing istoo long (over 100 lines) to include.

switch:admin> mapsPolicy --show fw_default_policy

Policy Name: fw_default_policy Rule List Action Condition--------------------------------------------------------------------------------------------- fw_def_ALL_OTHER_SFPSFP_TEMP_AH_85 RASLOG ALL_OTHER_SFP(SFP_TEMP/none>85) fw_def_ALL_OTHER_SFPSFP_TEMP_BL_n10 RASLOG ALL_OTHER_SFP(SFP_TEMP/none<-10)… fw_def_ALL_PORTSLF_AH_500 NONE ALL_PORTS(LF/min>500) fw_def_ALL_PORTSLOSS_SYNC_AH_500 NONE ALL_PORTS(LOSS_SYNC/min>500)… fw_def_ALL_E_PORTSLF_AH_500 NONE ALL_E_PORTS(LF/min>500) fw_def_ALL_E_PORTSLF_AL_50 NONE ALL_E_PORTS(LF/min>50)… fw_def_ALL_F_PORTSLOSS_SYNC_AH_500 NONE ALL_F_PORTS(LOSS_SYNC/min>500) fw_def_ALL_F_PORTSLOSS_SYNC_AL_50 NONE ALL_F_PORTS(LOSS_SYNC/min>50)… fw_def_SWITCHSEC_TELNET_AH_2 RASLOG,SNMP SWITCH(SEC_TELNET/min>2) fw_def_SWITCHSEC_HTTP_AH_2 RASLOG,SNMP SWITCH(SEC_HTTP/min>2)… fw_SWITCHFAULTY_PORTSMarg_10 SW_MARGINAL SWITCH(FAULTY_PORTS/none>=10.00) fw_SWITCHFAULTY_PORTSCrit_25 SW_CRITICAL SWITCH(FAULTY_PORTS/none>=25.00)Active Policy is 'dflt_moderate_policy'.



The following example shows an excerpted result of using the --show -all option. The entire listing is too long (over 930 lines) to include.

switch:admin> mapsPolicy --show -all Rule List Action Condition-------------------------------------------------------------------------------------- dflt_aggressive_policy: defNON_E_F_PORTSCRC_0 RASLOG,SNMP,EMAIL NON_E_F_PORTS(CRC/MIN>0) defNON_E_F_PORTSCRC_2 FENCE,SNMP,EMAIL NON_E_F_PORTS(CRC/MIN>2) defNON_E_F_PORTSITW_15 RASLOG,SNMP,EMAIL NON_E_F_PORTS(ITW/MIN>15)… [193 lines]

dflt_conservative_policy: defNON_E_F_PORTSCRC_21 RASLOG,SNMP,EMAIL NON_E_F_PORTS(CRC/MIN>21) defNON_E_F_PORTSCRC_40 FENCE,SNMP,EMAIL NON_E_F_PORTS(CRC/MIN>40) defNON_E_F_PORTSITW_41 RASLOG,SNMP,EMAIL NON_E_F_PORTS(ITW/MIN>41)… [195 lines]

dflt_moderate_policy: defNON_E_F_PORTSCRC_10 RASLOG,SNMP,EMAIL NON_E_F_PORTS(CRC/MIN>10) defNON_E_F_PORTSCRC_20 FENCE,SNMP,EMAIL NON_E_F_PORTS(CRC/MIN>20) defNON_E_F_PORTSITW_21 RASLOG,SNMP,EMAIL NON_E_F_PORTS(ITW/MIN>21)… [195 lines]

fw_default_policy: fw_def_ALL_OTHER_SFPSFP_TEMP_AH_85 RASLOG ALL_OTHER_SFP(SFP_TEMP/none>85) fw_def_ALL_OTHER_SFPSFP_TEMP_BL_n10 RASLOG ALL_OTHER_SFP(SFP_TEMP/none<-10) fw_def_ALL_OTHER_SFPRXP_AH_5000 RASLOG ALL_OTHER_SFP(RXP/none>5000)… [106 lines]

fw_custom_policy: fw_def_ALL_OTHER_SFPSFP_TEMP_AH_85 RASLOG ALL_OTHER_SFP(SFP_TEMP/none>85) fw_def_ALL_OTHER_SFPSFP_TEMP_BL_n10 RASLOG ALL_OTHER_SFP(SFP_TEMP/none<-10) fw_def_ALL_OTHER_SFPRXP_AH_5000 RASLOG ALL_OTHER_SFP(RXP/none>5000)… [106 lines]

fw_active_policy: fw_def_ALL_OTHER_SFPSFP_TEMP_AH_85 RASLOG ALL_OTHER_SFP(SFP_TEMP/none>85) fw_def_ALL_OTHER_SFPSFP_TEMP_BL_n10 RASLOG ALL_OTHER_SFP(SFP_TEMP/none<-10) fw_def_ALL_OTHER_SFPRXP_AH_5000 RASLOG ALL_OTHER_SFP(RXP/none>5000)… [106 lines]

Active Policy is 'dflt_moderate_policy'.

Creating a policyIn many cases, you might have multiple different policies available. For example, you could apply a different set of rules whenmaintenance operations are in progress from those that are in place for normal operations. Fabric OS allows you to create multiplepolicies beforehand and then easily switch between policies when necessary.

NOTEWhen you create a policy, the policy is automatically saved, but not enabled. The policy is not enabled unless you explicitlyenable it. Policy names are not case-sensitive; My_Policy and my_policy are considered to be the same.

To create policies and then add rules to them, complete the following steps.

1. Create a new policy or clone a policy from one of your existing policies.

• To create a new policy, enter mapsPolicy --create policy_name to create a policy.

• To clone an existing policy, enter mapsPolicy --clone policy_name -name clone_policy_name.



2. Create or modify rules to configure the required thresholds in the new policy.

• To create a rule, enter mapsRule --create rule_name -group group_name -monitor ms name -timebase timebase -opop_value -value value -action action -policy policy_name.

• To clone an existing rule, enter mapsRule --clone rule_name -name clone_rule_name.

• To modify existing rules, enter mapsRule --config rule_name parameters.

The following example creates a policy by cloning another policy, and then adds a rule to the new policy.

switch:admin> mapspolicy --clone defpol -name backup_pol switch:admin> mapsrule --create chassiscpu -monitor CPU -group chassis -op ge -value 70 -action raslog -policy backup_pol

Enabling a policyOnly one policy can be enabled at a time, and it must be enabled before it takes effect.

NOTEIf the active policy is changed, or if the rules in the active policy are changed, the active policy must be re-enabled for thechanges to take effect.

To enable a policy, complete the following steps.


2. Enter mapspolicy --enable followed by the name of the policy you want to enable.The previously enabled policy is automatically disabled and the specified policy is then enabled. There is no confirmation of thechange.

The following example enables the “dflt_aggressive_policy” policy.

switch:admin> mapspolicy --enable dflt_aggressive_policy

Modifying a user-defined policyYou can modify existing user-defined policies. For example, you might need to modify a policy if elements in the fabric change or ifthreshold configurations need to be modified to catch certain error conditions.

To modify a user-defined policy and its associated rules, perform the following steps.

1. Modify the rules in the policy based on your requirements.

You cannot modify the default rules, but you can add rules to and delete rules from the policy, and you can create rules and addthem to the policy.

• Use mapspolicy to add rules to and delete rules from the policy.

• Use mapsrule to modify rules or to create rules and add them to the policy.

2. Optional: Even if the policy is the active policy, you must re-enable the policy using the mapspolicy --enable policy_namecommand for the changes to take effect. Adding a new rule or changing an existing rule in the active policy does not take effectuntil you re-enable the policy.



The following example adds a rule to the policy named "daily_policy," displays the policy, and then re-enables the policy so the changecan become active.

switch:admin> mapspolicy --addrule daily_policy -rulename check_crc

switch:admin> mapspolicy --show daily_policy

Policy Name: daily_policyRule List : check_crc defALL_E_PORTSITW_21 defALL_E_PORTSITW_40 myCHASSISFLASH_USAGE_90Active Policy is ’daily_policy’


Modifying a default policyYou cannot modify any of the predefined MAPS policies, but you can clone one to create a new policy, and then modify that new policy.

To create and activate a modified version of a default policy, complete the following steps.

1. Create a copy of the default policy.

switch:admin> mapspolicy --clone dflt_conservative_policy -name my_policy

2. Modify the rules in the policy based on your requirements.

You cannot modify the default rules, but you can add rules to and delete rules from the policy, and you can create or clone rulesand add them to the policy.

Use mapsPolicy to add and delete rules to and from the policy. Use mapsRule to create rules and add them to the policy.

3. Enable the policy.

switch:admin> mapspolicy --enable my_policy

The previously enabled policy is disabled, and the specified policy is enabled.

The following example clones the default policy, deletes two rules, and modifies a rule to send an e-mail message in addition to aRASLog entry.

switch:admin> mapspolicy --clone dflt_conservative_policy -name rule_policy

switch:admin> mapspolicy --delrule rule_policy -rulename defCHASSISFLASH_USAGE_90

switch:admin> mapspolicy --delrule rule_policy -rulename defCHASSISMEMORY_USAGE_75

switch:admin> mapsrule --clone myCHASSISFLASH_USAGE_90 -monitor flash_usage -group chassis -timebase none -op ge -value 90 -action raslog,email -policy rule_policy

switch:admin> mapspolicy --enable rule_policy



Port monitoring using MAPS• Port monitoring and pausing........................................................................................................................................................................ 65• Monitoring groups of ports using the same conditions.....................................................................................................................65• Port monitoring using port names............................................................................................................................................................. 66• Port monitoring using device WWNs .......................................................................................................................................................66• Adding a port to an existing static group................................................................................................................................................. 66• Adding missing ports to a dynamic group .............................................................................................................................................67• Removing ports from a group......................................................................................................................................................................68• D_Port monitoring.............................................................................................................................................................................................68

Port monitoring and pausingPausing operations on a port does not affect flow monitoring. Flow monitoring is done at the flow level and the details of the flow passingthrough a particular port is transparent to MAPS.

Monitoring groups of ports using the same conditionsYou can create groups of ports that need to be modified using the same conditions. Then, you can use these groups to easily monitorthe ports using a single set of rules and thresholds. MAPS refers to these as “logical groups.”

Often on a switch there are sets of ports that behave in a similar manner and have a different behavior from other sets of ports. Forexample, the behavior of ports connected to UNIX hosts and servers is different from the behavior of ports connected to Windows hostsand servers. To easily monitor these similar sets of ports using the same rules, you can create a group and apply rules to the group.

To create a group and apply rules to the group, complete the following steps.

1. Create a logical group of similar ports.

2. Create rules using this logical group and add them to the active policy.

3. Enable the policy.

NOTEYou must enable the policy even if it is the active policy. Adding a rule to the active policy does not take effect until youre-enable the policy.

The following example creates the logical group “unix_ports” in the first line, creates a rule “unixHiCrc” using this logical group and addsthem to the active policy “my_policy” in the second, and enables the policy in the third.

switch:FID6:admin> logicalgroup --create unix_ports -type port -members "1,3,17,21" switch:FID6:admin> mapsrule --create unixHiCrc -monitor crc -group unix_ports -timebase min -op g -value 50 -action raslog -policy my_policyswitch:FID6:admin> mapspolicy --enable my_policy


Port monitoring using port namesFabric OS allows you to monitor ports based on their assigned names.

Because the port name is an editable attribute of a port, you can name ports based on the device to which they are connected. You canthen group the ports based on their port names. For example, if ports 1 to 10 are connected to devices from the ABC organization, youcan name these ports ABC_port1, ABC_port2, and so on through ABC_port10. You can then define a group named “ABC_Ports” witha membership determined by having a port name that begins with “ABC_port”. The following example defines a group based on this portname pattern. There is no limit on the number of ports that can be in a group.

switch246:FID128:admin> logicalgroup --create ABC_Ports -type port -feature portName -pattern ABC_port*

For more information on creating dynamic user-defined groups, refer to User-defined groups on page 38.

Port monitoring using device WWNsFabric OS allows you to monitor ports that are connected to a device that has device World Wide Name (WWN) that follows a certainpattern. This WWN pattern can then be used as part of the criteria for identifying a group. There is no limit on the number of ports thatcan be in a group.

One use of this might be for monitoring all ports on devices from a specific manufacturer. Because the WWN of a device containsinformation about the vendor, you can use this information to group devices based on this information, and then monitor them as adistinct group. For example, if you have a set of devices from vendor WXYZ with a WWN beginning 30:08:00:05, you can define agroup named “WXYZ_Devs” with a membership determined by having a WWN that begins with “30:08:00:05”.

NOTEThe device node WWN information is fetched from the FDMI database, and group membership is validated against thisdatabase.

The following example defines a group based on this device WWN pattern.

switch1246:FID128:admin> logicalgroup --create WXYZ_Devs -type port -feature nodewwn -pattern 30:08:00:05*

For further information on creating dynamic user-defined groups, refer to User-defined groups on page 38.

Adding a port to an existing static groupIf a new element, such as a host, target, or small form-factor pluggable (SFP) transceiver is added to the switch , you can monitor theports in that element using existing rules for similar elements by adding it to an existing group, or creating a new group that uses anexisting rule.

A port can be added to a static group or to dynamic groups, both user-defined and predefined.

For this type of monitoring, elements that are added manually to a group remain in the group whether they are online or offline.

To add a port to an existing group, complete the following steps. The added element is automatically monitored using the existing rulesthat have been set up for the group as long as the rules are in the active policy. You do not need to re-enable the active policy.


2. Enter logicalgroup --addmember group_name -member member_list

The element you want to add must be the same type as those already in the group (port, circuit, or SFP transceiver).


Port monitoring using port names


3. Optional: Enter logicalgroup --show group_name to see the members of the named group.

The following example adds the ports 31 and 41 to the critical_ports group.

switch:admin> logicalgroup --addmember critical_ports -members "31,41"

Listing this group produces the following output.

switch:admin> logicalgroup --show critical_ports---------------------------------------------------------------------Group Name |Predefined |Type |Member Count |Members---------------------------------------------------------------------critical_ports |No |Port |5 |10,15,25,31,41

Adding missing ports to a dynamic groupYou can add ports to a predefined group (for example, ALL_HOST or ALL_TARGET) or user-defined dynamic group that might nothave been included automatically.

For dynamic groups, you can specify any of the following:

• A single port

• Multiple ports separated by commas

• A range in which the IDs are separated by commas

You can create dynamic groups using either port names or WWNs, but you cannot use both in a single group definition. After a dynamicgroup is created, you can add ports to the same group using the same patterns as when the group was created. Quotation marks aroundthe member_list value are optional. The operation is very similar to adding ports to a static group. However, the following items should bekept in mind for this monitoring:

• There is no validation of manual additions to a group; for example, if you add port 17 as part of an F_Port group, that port isadded to the group even if it is not actually an F_Port.

• You can add a port to a predefined port group, but not to the group ALL_QUARANTINED_PORTS.

NOTEThe same restrictions as described in Adding a port to an existing static group on page 66 apply.

1. Enter logicalgroup --show group_name.

2. Enter logicalgroup --addmember group_name -member member_list to add the specified port to the named group.

3. Optional: Enter logicalgroup --show group_name to confirm the addition.

The following example shows these steps for the group ALL_HOST_PORTS, first showing that port 5 is not part of the group, thenadding it to the group, then showing that it has been added to the group.

switch:admin> logicalgroup --show ALL_HOST_PORTS---------------------------------------------------------------------Group Name |Predefined |Type |Member Count |Members--------------------------------------------------------------------- ALL_HOST_PORTS |Yes |Port |2 |0,15

switch:admin> logicalgroup --addmember ALL_HOST_PORTS -mem 5

switch:admin> logicalgroup --show ALL_HOST_PORTS-------------------------------------------------------------------- Group Name |Predefined |Type |Member Count |Members-------------------------------------------------------------------- ALL_HOST_PORTS |Yes |Port |3 |0,5,15

Adding missing ports to a dynamic group


Removing ports from a groupIn a similar way that you would add ports to either predefined or user-defined dynamic groups, you can also remove the ports from eithergroup type. This is useful for devices that erroneously identify themselves as both host and target or for one-off exceptions when youwant to remove a port that satisfies the specified pattern used for a user-defined dynamic group but you do no want it to be part of thegroup. .

To remove a port from a group, complete the following steps.


2. Enter logicalGroup --delmember group_name -members member_list.


3. Optional: Enter logicalGroup --show group_name to confirm that the named ports are no longer part of the group.

The following example removes port 5 from the ALL_TARGET_PORTS group, and then shows that it is no longer a member of thatgroup.

switch:admin> logicalgroup --delmember ALL_TARGET_PORTS -members "5"

switch:admin> logicalgroup --show ALL_TARGET_PORTS------------------------------------------------------------------------------------Group Name |Predefined |Type |Member Count |Members------------------------------------------------------------------------------------ALL_TARGET_PORTS |Yes |Port |5 |1,11,22,32,44

D_Port monitoringIn Fabric OS 7.3.0, D_Ports can be monitored by MAPS using the group ALL_D_PORTS.

You can either configure a port as a D_Port using the CLI, or Fabric OS can dynamically convert a port to a D_Port. Refer to the FabricOS Administrator's Guide for information on enabling the dynamic conversion. When a port is configured as a D_Port, MAPSautomatically adds the port to the ALL_D_PORTS group, and starts monitoring the port.

Rules based on the ALL_D_PORTS group are part of the default policies, and have error thresholds spanning multiple time windows ortimebases. If any of the rules are triggered, MAPS triggers the action configured for the rule, alerts the fabric service module ifappropriate, and caches the data in the dashboard.

The D_Port diagnostic output classifies the error conditions into the following states:

• Errors within operating range

• Errors outside of operating range

D_Port monitoring monitors all D_Port errors; however, the fabric service module is only notified for the following errors:

• CRC

• ITW — for the enc_out and enc_in invalid transmission words only

• LF

• LOSS_SYNC

The D_Port monitoring feature is only supported for 10 Gbps and 16 Gbps SFPs and 8Gbps LWL and ELWL ports on the followingblades: CR16-4, CR16-8, FC8-32E, FC8-48E, FC16-32, FC16-48, and FC16-64.

NOTEIn versions of Fabric OS prior to 7.3, MAPS monitored D_Ports using the NON_E_F_PORTS group, but the default rules forthis group did not provide the flexibility now available through the ALL_D_PORTS group.

Removing ports from a group


The mapsrule command accepts the ALL_D_PORTS group, which can be used as shown in the following example.

mapsrule --create d_port_mon -group ALL_D_PORTS -monitor CRC -timebase min -op ge -value 1 -action raslog -policy nil

Using the mapsdb --show command shows any error or rule violation during diagnostics tests on a D_Port.

switch:admin> mapsdb --show1 Dashboard Information:=======================DB start time: Wed Mar 26 10:02:38 2014Active policy: dflt_moderate_policyConfigured Notifications: SW_CRITICAL,SW_MARGINALFenced Ports : NoneDecommissioned Ports : None

2 Switch Health Report:=======================Current Switch Policy Status: MARGINALContributing Factors:---------------------*BAD_PWR (MARGINAL).

3.1 Summary Report:===================Category |Today |Last 7 days |-------------------------------------------------------------------------Port Health |Out of operating range |In operating range |Fru Health |In operating range |In operating range |Security Violations |No Errors |No Errors |Fabric State Changes |Out of operating range |In operating range |Switch Resource |In operating range |In operating range |Traffic Performance |In operating range |In operating range |FCIP Health |Not applicable |Not applicable |Fabric Performance Impact|In operating range |In operating range |

3.2 Rules Affecting Health:===========================Category(Rule Count)|RptCount|Rule Name |Execution Time |Object |Triggered Value(Units)|----------------------------------------------------------------------------------------------------Port Health(5) |1 |defALL_D_PORTSCRC_1 |05/07/14 08:43:32|D_Port 20|300 Errors | |4 |defNON_E_F_PORTSLF_0|05/07/14 08:42:56|D_Port 7 |6 | | | | |D_Port 7 |6 | | | | |D_Port 7 |6 | | | | |D_Port 7 |7 |

You can also run the portdporttest --show port_number command to see details of an individual port. The following example shows theresults for port 28.

switch:admin> portdporttest --show 28D-Port Information:===================Port: 28Remote WWNN: 10:00:00:05:1e:e5:e4:00Remote port: 164Mode: ManualStart time: Thu Nov 7 13:43:26 2013End time: Thu Nov 7 13:53:43 2013Status: PASSED*

Refer to the Fabric OS Command Reference for additional information on these commands.

D_Port monitoring



Monitoring Flow Vision flows with MAPS• Viewing Flow Vision Flow Monitor data with MAPS...........................................................................................................................71• Monitoring traffic performance.................................................................................................................................................................... 74• Monitoring learned flows................................................................................................................................................................................ 75

Viewing Flow Vision Flow Monitor data with MAPSThe Monitoring and Alerting Policy Suite (MAPS) can monitor flows created using the Flow Monitor feature of Flow Vision. Flows createdby the Flow Vision Flow Generator and Flow Mirror features cannot be monitored using MAPS.

For details on flows and Flow Vision, refer to the Flow Monitor section of the Flow Vision Administrator's Guide.

To monitor flows using MAPS, complete the following steps.

1. Create the flow in Flow Vision using the flow --create command.

2. Import the flow into MAPS using the mapsconfig --import command.

3. Enter logicalgroup --show to confirm that the flow was correctly imported into MAPS. The imported flow name indicates thegroups which can be monitored.

4. Define a MAPS rule using the mapsrule --create command.

Refer to MAPS rules overview on page 45 for information on creating and using rules.

5. Enter mapspolicy --enablepolicy policy_name to activate the flow.

6. Optional: Enter mapsdb --show to view the flow data.

For a discussion of the output of this command, refer to MAPS dashboard overview on page 77.


The following example illustrates these flow monitoring steps. The first command line creates the flow, the second command line importsit, and the third command line displays the members of the logical groups, with the imported flow in bold (only for the example). Thefourth command line creates a rule for the group, the fifth command line enables the flow with the new rule active, and the sixthcommand line command line displays the flow data.

switch246:FID128:admin> flow --create myflow_22 -feature monitor -egrport 21 -srcdev 0x010200 -dstdev 0x011500

switch246:FID128:admin> mapsconfig --import myflow_22

switch246:FID128:admin> logicalgroup --show ------------------------------------------------------------------Group Name |Predefined|Type |Member Count|Members------------------------------------------------------------------ALL_PORTS |Yes |Port |8 |3/4,3/6-15NON_E_F_PORTS |Yes |Port |2 |3/4,3/6ALL_E_PORTS |Yes |Port |0 |ALL_F_PORTS |Yes |Port |5 |8/0-1,8/4ALL_OTHER_F_PORTS |Yes |Port |1 |8/0ALL_HOST_PORTS |Yes |Port |1 |8/8ALL_TARGET_PORTS |Yes |Port |0 |ALL_QUARANTINED_PORTS |Yes |Port |2 |8/0,8/4ALL_2K_QSFP |Yes |Sfp |4 |8/28-31ALL_100M_16GSWL_QSFP |Yes |Sfp |0 |myflow_22 |No |Port |3 |4/4,4/10,4/47

switch246:FID128:admin> mapsrule --create myRule_22 -group myflow22 -monitor TX_FCNT -timebase hour -op g -value 22 -action RASLOG -policy myPolicy

switch246:FID128:admin> mapspolicy --enable policy myPolicy22

switch246:FID128:admin> mapsdb --show

1 Dashboard Information:=======================DB start time: Fri Nov 21 11:12:31 2014Active policy: myPolicy22Configured Notifications: SW_CRITICAL,SW_MARGINALFenced Ports: NoneDecommissioned Ports: NoneQuarantined Ports : None

2 Switch Health Report:=======================Current Switch Policy Status: MARGINAL (output truncated)

Flow Vision statistics supported by MAPSMAPS can monitor statistics supported by the Flow Vision Flow Monitor feature.

The following Flow Vision Flow Monitor statistics can be monitored using MAPS. The term in parentheses is the MAPS element.

• Frame statistics:

– Number of frames transmitted from the flow source (TX_FCNT)– Number of frames received by the flow destination (RX_FCNT)– Number of megabytes transmitted per second by the flow source (TX_THPUT)– Number of megabytes received per second by the flow destination (RX_THPUT)

• SCSI statistics:

– Number of SCSI I/O read command frames recorded for the flow (IO_RD)– Number of SCSI I/O write command frames recorded for the flow (IO_WR)– Number of SCSI I/O bytes read as recorded for the flow (IO_RD_BYTES)– Number of SCSI I/O bytes written as recorded for the flow (IO_WR_BYTES)

Viewing Flow Vision Flow Monitor data with MAPS


For more information on Flow Vision, refer to the Flow Vision Administrator's Guide.

Statistics produced by the Flow Vision Flow Monitor feature are displayed in the MAPS dashboard within the Traffic Performancesubsection of the Switch Health Report section. This data is not included in the History Data section of the MAPS dashboard. Refer tothe MAPS dashboard on page 77 chapter for examples and additional information.

Restrictions on Flow Vision flow monitoringA Flow Vision flow can be imported and monitored using MAPS any time after it has been defined in Flow Vision, subject to thefollowing restrictions:

• It must be a flow created using the Flow Monitor feature.

• The flow must be active. In Fabric OS 7.3.0 and later, both static and learned flows (sub-flows created using an asterisk (*)) canbe imported and monitored.

• When importing a flow, the flow name must be specified. Once a flow is imported to MAPS, you can define MAPS rules tomonitor the flow. Each rule has a threshold criterion and alerting mechanism defined. If the threshold criterion is met, then aconfigured alert is generated.

• MAPS monitoring starts after a flow has been both activated in Flow Vision and imported into MAPS. Deactivating a flowcauses monitoring to stop until it is reactivated. When the flow is reactivated, monitoring automatically restarts.

• If you do not want to continue monitoring an imported flow, it can be removed (deimported) from MAPS. Refer to Removingflows from MAPS on page 73 for more information.

Removing flows from MAPSIf you do not want to monitor a flow using MAPS, use the mapsConfig --deimport flow_name -force command to remove the flowfrom MAPS.

You can only remove one flow at a time. Removing a flow only removes it from MAPS, it does not affect the flow definition in FlowVision. If you do not use the -force option, removing a flow will succeed only if you have deleted all the rules associated with that flow.

To remove a flow from MAPS, complete the following steps.

1. Enter logicalGroup --show to see the list of flows imported into MAPS.

2. Identify the flows you want to remove from MAPS.

3. Enter mapsConfig --deimport flow_name -force.

The following example removes the flow named “myflow22” from MAPS.

switch:admin> mapsconfig --deimport myflow22 -force

If a flow is deleted in Flow VisionIf you delete a Flow Vision flow that has not been imported into MAPS, there is no change in MAPS. If you delete a Flow Vision flow thathas been imported into MAPS, the flow is marked as deleted, but the group corresponding to the flow will remain. Groups are onlyremoved if the flow --deimport command is used.

If a flow is deleted in Flow Vision, MAPS will not automatically begin monitoring that flow if it is recreated. If you try to import a flow withthe same name as the deleted flow, the import will fail and a RASLog message is generated. If you are certain that you want to importthat flow and monitor it using the existing rules for that flow, you must use the -force keyword as part of the mapsConfig --importcommand.

Viewing Flow Vision Flow Monitor data with MAPS


The following example demonstrates importing a flow named “myExFlow” using the -force keyword.

switch:admin> mapsconfig --import myExFlow -force

Sub-flow monitoring and MAPSMAPS supports monitoring both static and learned flows (flows created using an asterisk (*)).

For a learning flow (one created using an asterisk (*)), the sub-flow membership may change dynamically; that is, the sub-flows that arepart of the learning flow may get deleted or new sub-flows may become part of the learning flow. One case where this can happen iswhen the portEnable or portDisable command is applied to an ingress or egress port for a sub-flow that is depending on the flowlearning definition for its existence. The thresholds configured for a flow are applied at the sub-flow level.

If the sub-flow membership changes for a learning flow that has been imported, MAPS will automatically start monitoring the addedsub-flows and stop monitoring the deleted sub-flows.

The member count shown in the output of the logicalGroup --show command shows the current number of sub-flows present in theflow. The following example shows that the flow named “thruputflow” had four sub-flows at the time the command was run.

switch0:FID128:admin> logicalgroup --show thruputflow-------------------------------------------------------------------------------------Group Name |Predefined |Type |Member Count|Members-------------------------------------------------------------------------------------thputflow |No |Flow |4 |Monitored Flow

Monitoring traffic performanceThe following examples illustrate how to use MAPS to monitor traffic performance.

Monitoring end-to-end performanceIn the following example, MAPS is configured to monitor the throughput of a flow between two specific devices through port 5. Toachieve this, you define a flow using the -feature monitor for a particular Source ID, Destination ID, and port using the Flow Vision flowcommand. Then, you import the flow into MAPS and create rules to monitor the throughput for the flow.

switch246:admin> flow --create E2E_flow -feature monitor -ingrport 5 -scrdev 0x010200 -dstdev 0x020300

switch246:admin> mapsconfig --import E2E_flow

switch246:admin> mapsrule --create E2E_rule -monitor TX_THPUT -group E2E_flow -timebase min -op g -value 10 -action rasLog -policy flowpolicy

switch246:admin> mapspolicy --enable flowpolicy

NOTEThe group name needs to match the imported flow name. In this case“E2E_flow”.

Monitoring frames for a specified set of criteriaIn the following example, MAPS uses the flow “abtsflow” to watch for frames in a flow going through port 128 that contain SCSI ABORTsequence markers.

switch246:admin> flow --create abtsflow -feature mon -ingrport 128 -frametype abts

switch246:admin> mapsconfig --import abtsflow

Monitoring traffic performance


You can then define rules for this flow (group), and then re-enable the policy so they take effect. THe following example creates only onerule, “abts_rule”.

switch246:admin> mapsrule --create abts_rule -monitor txfcnt -group abtsflow -timebase min -op ge -value 10 -action raslog -policy flowpolicyswitch246:admin> mapspolicy --enable flowpolicy

NOTEAny new rule you create will not take effect until you enable the policy associated withit.

Monitoring learned flowsFlow Vision allows you use a wild character when creating flows, so that you do not have to specify a SID or DID. In such cases, FlowVision “learns” all the flows that match the input criteria, and if Flow Monitor feature is enabled on these flows, metrics are captured foreach of the learned flows. This ability allows you to capture information about multiple flows or gather information when you do not knowa specific flow that is of interest.

If a learned flow is imported into MAPS and rules created for the flow, MAPS will evaluate the configured conditions for each of thelearned flows.

The following examples illustrate some of the ways you might want to monitor learned flows.

Excessive throughput notificationTo be notified of all the Source ID-Destination ID device pairs for which the RX throughput is greater than a threshold, you would import alearning flow with both the Source ID and Destination ID specified as "*" and define a rule to provide the notification, as shown in the

following example.

switch246:FID128:admin> flow --create thruputflow -feature monitor -ingrp 123 -srcdev "*" -dstdev "*"

switch246:FID128:admin> mapsconfig --import thruputflow

switch246:FID128:admin> mapsrule --create thruputflow_thput_10 -group thruputflow -timebase hour -m RX_THRUPUT -op ge -v 10 -a RASLOG,EMAIL

Possible bottleneck notificationTo determine which Source ID-Destination ID device pairs have an “abort frame” count that exceeds a specified limit (and consequentlycause network bottlenecking), you would import a learning flow that monitors the SCSI Abort notifications with both the Source ID andDestination ID specified as “*” and define a rule to provide the notification, as shown in the following example.

switch:admin> flow --create frmcntflow -feature monitor -egrp 234 -srcdev "*" -dstdev "*" -frametype abts

switch:admin> mapsconfig --import frmcntflow

switch:admin> mapsrule --create frmcntflow_framecnt_1000 -group frmcntflow -timebase hour -m TX_FCNT -op ge -v 1000 -a RASLOG,EMAIL

Monitoring learned flows



MAPS dashboard• MAPS dashboard overview...........................................................................................................................................................................77• Viewing the MAPS dashboard.....................................................................................................................................................................80• Clearing MAPS dashboard data..................................................................................................................................................................88

MAPS dashboard overviewThe Monitoring and Alerting Policy Suite (MAPS) dashboard provides a summary view of the switch health status that allows you toeasily determine whether everything is working according to policy or whether you need to investigate further.

MAPS dashboard sectionsThe MAPS dashboard output is divided into the following main sections. A history section is displayed if you enter mapsdb --show all.

Dashboard high-level information sectionThe dashboard high-level information section displays basic dashboard data: the time the dashboard was started, the name of the activepolicy, and any fenced, decommissioned, or quarantined ports.

The following output extract shows that the dashboard was started at 1:02 PM on February 27, 2015, the active policy is“dflt_base_policy”, and that there are no fenced, decommissioned, or quarantined ports.

switch:admin> mapsdb --show all 1 Dashboard Information:=======================DB start time: Fri Feb 27 13:02:19 2015Active policy: dflt_base_policyConfigured Notifications: NoneFenced Ports : NoneDecommissioned Ports : NoneQuarantined Ports : None (output truncated)

Switch Health Report sectionThe Switch Health Report section displays the current switch policy status and lists any factors contributing to that status as defined bythe Switch Health Report rules in the active policy.

The following output extract shows a sample Switch Health Report section; revealing that the switch status is HEALTHY.

2 Switch Health Report:=======================

Current Switch Policy Status: HEALTHY

(output truncated)

Refer to Switch Status Policy on page 34 for more details on switch policies.

Summary Report sectionThe Summary Report section has two subsections, the Category report and the Rules Affecting Health report. The Category reportsubsection collects and summarizes the various switch statistics monitored by MAPS into multiple categories, and displays the current


status of each category since midnight, and the status of each category for the past seven days. If a rule violation has caused a change inthe status of a category, rule-related information is displayed in the Rules Affecting Health subsection, broken out by category.

The following categories are monitored by MAPS:

• Port Health on page 28

• FRU Health on page 29

• Security Violations on page 29

• Fabric State Changes on page 30

• Switch Resources on page 31

• Traffic Performance on page 31

• FCIP Health on page 32

• Fabric Performance Impact on page 33

The following output extract shows a sample Summary Report section.

3.1 Summary Report:===================

Category |Today |Last 7 days |-------------------------------------------------------------------------- Port Health |Out of operating range |No Errors |Fru Health |Out of operating range |In operating range |Security Violations |No Errors |No Errors |Fabric State Changes |No Errors |No Errors |Switch Resource |In operating range |In operating range |Traffic Performance |In operating range |In operating range |FCIP Health |Out of operating range |In operating range |Fabric Performance Impact|Out of operating range |In operating range |

(output truncated)

When a category contains an “out-of-range” error, the dashboard displays a table showing the rules triggered in that category since theprevious midnight. This allows you to see more precisely where the problem is occurring. Each category in the table contains thefollowing information:

• The number of times rules were triggered in each category

• The rules that were triggered

• The time when the rule was triggered

• The entities (ports, circuits, and others) that triggered the rule

• The values of these entities when the rule was triggered

For each category, the dashboard stores the following information for each hour since midnight:

• The five most recent distinct rule violations that occurred.

• For each rule, the five most recent entities on which the rules were triggered.

• Although a rule might be triggered multiple times within a given hour, only the timestamp of the latest violation is stored.

• However, each violation of a rule individually is reflected in the rule count for that category and the repeat count for that rule.

For example, if the same rule was triggered 12 times in one hour, the repeat count value (shown as RptCnt in the following example) for

that rule will be 12, but only the timestamp for the last occurrence is displayed. In addition, the last five distinct entities on which this rulewas triggered are stored (and these could be stored from different instances of the rule’s violation). Alternatively, if a rule was triggered 12times since midnight, but each violation happened in a different hour, then each violation is logged separately in the dashboard.

MAPS dashboard overview


The following output extract shows a sample Rules Affecting Health section, showing that there are six errors affecting four rules. Thecolumn headings in the example have been edited slightly so as to allow the example to display clearly.

3.2 Rules Affecting Health:===========================

Category(Rule Cnt)|RptCnt|Rule Name |Execution Time |Object |Triggered Value(Units)|-------------------------------------------------------------------------------------------------------Port Health(2) |1 |defALL_OTHER_F_PORTSCRC_40|07/09/13 17:18:18|Port 1 |876 CRCs | |1 |defALL_OTHER_F_PORTSCRC_21|07/09/13 17:18:18|Port 1 |876 CRCs |Fru Health(2) |2 |defALL_FANFAN_STATE_FAULTY|07/09/13 19:15:17|Fan 2 |FAULTY | | | | |Fan 1 |FAULTY |FCIP Health(2) |1 |low_tunnel_mon |11/20/13 06:19:6 |Tunnel |25 |

(output truncated)

History Data section (optional)When displayed, the History Data section provides information on how the switch has been behaving regardless of whether rules weretriggered. It contains only port-related statistics, and is the raw counter information recorded since the previous midnight.

The historical data log stores the last seven days on which errors were recorded (not the last seven calendar days, but the last seven days,irrespective of any interval between these days). If a day has no errors, that day is not included in the count or the results. Using thisinformation, you can get an idea of the errors seen on the switch even though none of the rules might have been violated. If you seepotential issues, you can reconfigure the appropriate rule thresholds to specifically fit the switch based on the actual behavior of traffic onthe switch. For more information on historical data, refer to Viewing historical data on page 85.

The following output extract shows a sample History Data section.

(output truncated) 4.1 Front end port History Data:=================================Stats(Units) Current 07/21/14 07/14/14 --/--/-- --/--/-- --/--/-- --/--/-- Port(val) Port(val) Port(val)----------------------------------------------------------------------------------------------CRC(CRCs) 1/13(20) - - - - - -ITW(ITWs) - 1/13(612) - - - - -LOSS_SYNC(SyncLoss) - - - - - - -LF - - - - - - -LOSS_SIGNAL(LOS) - - - - - - -PE(Errors) - - - - - - -STATE_CHG - - - - - - -C3TXTO(Timeouts) - - - - - - -RX(%) - - - - - - -TX(%) - - - - - - -UTIL(%) - - - - - - -BN_SECS(Seconds) - - - - - - -

4.2 Backend port History Data:=================================Stats(Units) Current 07/21/14 07/14/14 --/--/-- --/--/-- --/--/-- --/--/-- Port(val) Port(val) Port(val)---------------------------------------------------------------------------------------------CRC(CRCs) 6/8(50) - - - - - -

Notes on dashboard dataThe following information should be kept in mind when examining dashboard data.

• The following dashboard state conditions can be displayed:

– No Errors: Displayed if there are no errors for the switch ports, security, fabric, or FCIP health; for example, if no port hashad an error since midnight.

– In operating range: Displayed if there are no errors, or if there were errors but no rule was triggered.

MAPS dashboard overview


– Out of operating range: Displayed if at least one error triggered a rule belonging to the category in which this state messageappears.

• RX, TX, UTIL errors are not displayed in the History Data section unless port errors are recorded for that day.

• The “Rule Count” value is the absolute number of different violations in that category since the previous midnight. The “RepeatCount” is the number of times a rule has been violated in the hour, for example, between 10:00:00 and 10:59:59.

• By default, only the last five violations are displayed for each category. However, entering mapsdb --show all causes thedashboard to display all the rule violations currently stored along with additional historical data.

MAPS dashboard display optionsThe mapsdb command allows you to the MAPS dashboard for a specific period of time. You can use various options of the mapsdbcommand to display data gathered since midnight, for any one-hour period since midnight, or for the last seven days on which errorswere recorded.

Refer to the Fabric OS Command Reference for detailed instructions on using the mapsdb command options to configure thedashboard.

NOTEIf the Fabric Vision license is not active, then only the results for unlicensed features will be displayed in the MAPS dashboard.Refer to MAPS commands that do not need a licence for a list of these features.

Viewing the MAPS dashboardThe MAPS dashboard allows you to monitor the switch status. There are three primary views: a summary view, a detailed view (whichincludes historical data), and a history-only view.

To view the status of the switch as seen by MAPS, complete the following steps.


2. Enter mapsDb --show followed by the scope parameter: all, history, or details. Entering details allows you to specify either aspecific day or a specific hour of the current day.

Viewing the MAPS dashboard


The following example shows a typical result of entering mapsDb --show all.

switch:admin> mapsdb --show all1 Dashboard Information:=======================DB start time: Sun Mar 30 20:46:59 2014Active policy: dflt_moderate_policyConfigured Notifications: SW_CRITICAL,SW_MARGINALFenced Ports : NoneDecommissioned Ports : None

2 Switch Health Report:=======================Current Switch Policy Status: HEALTHY

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 |No Errors |No Errors |Switch Resource |In operating range |Out of operating range |Traffic Performance |In operating range |In operating range |FCIP Health |Not applicable |Not applicable |Fabric Performance Impact|Out of operating range |In operating range |

3.2 Rules Affecting Health:===========================Category(Rule Count)|RepeatCount|Rule Name |Execution Time |Object |Triggered Value(Units)|---------------------------------------------------------------------------------------------------Switch Resource (1) |1 |defCHASSISCPU_80|03/30/14 20:50:00|Chassis|99.00 % |

4 History Data: ===============Stats(Units) Current --/--/-- --/--/-- --/--/-- --/--/-- --/--/-- --/--/-- Port(val) ---------------------------------------------------------------------------------------------CRC(CRCs) 0(>9999) - - - - - - 1(876) - - - - - - ITW(ITWs) - - - - - - -LOSS_SYNC(SyncLoss) - - - - - - -LF - - - - - - -LOSS_SIGNAL(LOS) - - - - - - -PE(Errors) - - - - - - -STATE_CHG - - - - - - -LR - - - - - - -C3TXTO(Timeouts) - - - - - - -RX(%) - - - - - - -TX(%) - - - - - - -UTIL(%) - - - - - - -BN_SECS(Seconds) - - - - - - -

Refer to MAPS monitoring categories on page 27 for explanations of the categories listed in the dashboard output.

Viewing a summary switch status reportA summary view provides health status at a high level and includes enough information for you to investigate further if necessary.

To view a summary switch status report, complete the following steps.


2. Enter mapsdb --show with no other parameters to display the summary status.



The following example displays the general status of the switch (MARGINAL) and lists the overall status of the monitoring categories forthe current day (measured since midnight) and for the last seven days. If any of the categories are shown as being “Out of range”, the lastfive rules that caused this status are listed. If a monitoring rule is triggered, the corresponding RASLog message appears under RulesAffecting Health of the dashboard. Be aware that the example column headings have been edited slightly so as to allow it to displayclearly.

switch:admin> mapsdb --show

1 Dashboard Information:=======================DB start time: Tue Mar 3 22:27:52 2015Active policy: dflt_aggressive_policyConfigured Notifications: RASLOGFenced Ports : NoneDecommissioned Ports : NoneQuarantined Ports : None

2 Switch Health Report:=======================Current Switch Policy Status: MARGINALContributing Factors:---------------------*BAD_PWR (MARGINAL).*BAD_FAN (MARGINAL).

3.1 Summary Report:===================Category |Today |Last 7 days |--------------------------------------------------------------------------------Port Health |No Errors |No Errors |BE Port Health |No Errors |No Errors |Fru Health |Out of operating range |In operating range |Security Violations |No Errors |No Errors |Fabric State Changes |No Errors |No Errors |Switch Resource |In operating range |In operating range |Traffic Performance |In operating range |In operating range |FCIP Health |Not applicable |Not applicable |Fabric Performance Impact|In operating range |In operating range |

3.2 Rules Affecting Health:===========================Category(Rule Count)|RptCnt|Rule Name |Execution Time |Object |Triggered Value| (Units) |-------------------------------------------------------------------------------------------------------Fru Health(1) |1 |defALL_PSPS_STATE_FAULTY|03/04/15 00:03:09|Power Supply 2 |FAULTY |



Sub-flow rule violation summariesIn the MAPS dashboard you can view a summary of all sub-flows that have rule violations.

When a rule is triggered, the corresponding RASLog rule trigger appears in the “Rules Affecting Health” sub-section of the dashboard aspart of the Traffic Performance category. In this category, the five flows or sub-flows with the highest number of violations since theprevious midnight are listed.

The naming convention for “Object” in sub-flows has the format: Flow (flow_name:sub-flow parameters), where flow_name is

the name of the imported flow.

The following extract provides an illustration of violations of the “thruputflow_thput_10” rule. The output has been split at \ to allow theexample to display clearly.

switch:admin> mapsdb --show ...3.2. Rules Affecting Health:=================================Category(Rule Count) |Repeat Count|Rule Name |Execution Time| \Traffic Performance(10) |5 | thruputflow_thput_10|2/21/13 1:30:6| \ 2/21/13 1:30:6| \ 2/21/13 1:28:6| \ 2/21/13 1:26:6| \ 2/21/13 1:24:6| \

\|Object |Trigger Value(Units) \|Flow (thruputflow:SID=011000,DID=011200,Tx=10)| 860 MBps \|Flow (thruputflow:SID=012000,DID=011200,Tx=10)| 707 MBps \|Flow (thruputflow:SID=012100,DID=011200,Tx=10)| 812 MBps \|Flow (thruputflow:SID=012200,DID=011200,Tx=10)| 753 MBps \|Flow (thruputflow:SID=012300,DID=011200,Tx=10)| 736 MBps (output truncated)

• For learning flows, in addition to the name of the flow being monitored by the rule, the source and destination values for eachindividual sub-flow that violated the threshold are included in the RASLog entry. These values replace the learning parametersspecified in the flow definition. The specific type of values (such as SID, DID, SFID, DFID, Rx, Tx and so on) are derived from theflow definition. In the following example, “(SID=039c00,DID=040700,Rx=10)” is the flow identifier for the learned flow“flows_to_did” (which was defined using "*" for the source and destination devices).

2014/04/07-07:20:01, [MAPS-1003], 11131, SLOT 4 | FID 128, WARNING, SWAT_TUHIN_PLUTO, Flow (flows_to_did:SID=039c00,DID=040700,Rx=10), Condition= flows_to_did (TX_FCNT/hour>=10), Current Value:[TX_FCNT,698366979], RuleName=flow2, Dashboard Category=Traffic Performance.

• For static flows, the name of the flow is provided as part of the RASLog. In the following example, “max_thruput_flow” is thename of the problematic flow.

2013/12/21-11:50:00, [MAPS-1003], 1225, FID 128, WARNING, sw0, Flow (max_thruput_flow), Condition=max_thruput_flow(TX_FCNT/min>=10), Current Value:[TX_FCNT,42654538], RuleName=thruputflow_thput_10, Dashboard Category=Traffic Performance.

Viewing a detailed switch status reportThe detailed switch status displays historical data for port performance errors in addition to the summary view.

To view a detailed switch status report, complete the following steps.




2. Enter mapsdb --show all to display the detailed status.

The following example shows the detailed switch status. The status includes the summary switch status, plus port performancedata for the current day (measured since midnight). If a monitoring rule is triggered, the corresponding RASLog messageappears under the summary section of the dashboard. The column headings in the example have been edited slightly so as toallow the example to display clearly.

switch:admin> mapsdb --show all 1 Dashboard Information:=======================DB start time: Wed May 14 23:40:58 2014Active policy: dflt_aggressive_policyConfigured Notifications: SW_CRITICAL,SW_MARGINALFenced Ports : NoneDecommissioned Ports : NoneQuarantined Ports : None

2 Switch Health Report:=======================Current Switch Policy Status: CRITICALContributing Factors:---------------------*BAD_PWR (MARGINAL).*BAD_FAN (CRITICAL).

3.1 Summary Report:===================Category |Today |Last 7 days |--------------------------------------------------------------------------Port Health |Out of operating range |No Errors |BE Port Health |No Errors |No Errors |Fru Health |Out of operating range |In operating range |Security Violations |No Errors |No Errors |Fabric State Changes |No Errors |No Errors |Switch Resource |In operating range |In operating range |Traffic Performance |In operating range |In operating range |FCIP Health |Out of operating range |In operating range |Fabric Performance Impact|Out of operating range |In operating range |


Category(Rule Cnt)|RptCnt|Rule Name |Execution Time |Object |Triggered Value(Units)|-------------------------------------------------------------------------------------------------------Port Health(2) |1 |defALL_OTHER_F_PORTSCRC_40|07/09/13 17:18:18|Port 1 |876 CRCs | |1 |defALL_OTHER_F_PORTSCRC_21|07/09/13 17:18:18|Port 1 |876 CRCs |Fru Health(2) |2 |defALL_FANFAN_STATE_FAULTY|07/09/13 19:15:17|Fan 2 |FAULTY | | | | |Fan 1 |FAULTY |FCIP Health(2) |1 |low_tunnel_mon |11/20/13 06:19:6 |Tunnel |25 |

4.1 Front-end port History Data:=================================Stats(Units) Current 07/21/13 07/14/13 --/--/-- --/--/-- --/--/-- --/--/-- Port(val) Port(val) Port(val)---------------------------------------------------------------------------------------------CRC(CRCs) 13(20) - - - - - -ITW(ITWs) - 13(612) - - - - -LOSS_SYNC(SyncLoss) - - - - - - -LF - - - - - - -LOSS_SIGNAL(LOS) 12(4) 12(4) 13(5) - - - - - 13(4) 12(4) - - - - - 14(4) 14(4) - - - -PE(Errors) - - - - - - -STATE_CHG 12(5) 12(5) 12(9) - - - - - 13(5) 13(9) - - - - - 14(5) 14(9) - - - -LR - 13(6) 12(10) - - - - - 12(4) 13(10) - - - - - 14(4) 14(10) - - - -



C3TXTO(Timeouts) - - - - - - -RX(%) - - - - - - -TX(%) - - - - - - -UTIL(%) - - - - - - -BN_SECS(Seconds) - - - - - - - 4.2 Back-end port History Data:=================================Stats(Units) Current 07/21/13 07/14/13 --/--/-- --/--/-- --/--/-- --/--/-- Port(val) Port(val) Port(val)---------------------------------------------------------------------------------------------CRC(CRCs) 2/1/0(15) - - - - - -LOSS_SYNC(SyncLoss) 2/1/0(1) 3/3/1(2) 3/3/1(2) - - - -

Viewing historical dataTo view what has happened on a switch since the previous midnight, enter mapsdb --show history to view a summarized status historyof the switch for this period, including both front-end ports and back-end ports (if present). History data for back-end ports is collectedfor a period of seven days and it is displayed in the "Backend port History Data" section.

NOTEThe output of the mapsdb --show history command differs depending on the platform on which you run it. On fixed-portswitches, ports are shown in port index format; on chassis-based platforms, ports are shown in slot/port format.

To view a summarized history of the switch status, complete the following steps.


2. Enter mapsdb --show history.



The following example displays all stored historical port performance data.

switch:admin> mapsdb --show history

Front-end port History Data:=================================Stats(Units) Current 07/21/13 07/14/13 --/--/-- --/--/-- --/--/-- --/--/-- Port(val) Port(val) Port(val)---------------------------------------------------------------------------------------------CRC(CRCs) 13(20) - - - - - -ITW(ITWs) - 13(612) - - - - -LOSS_SYNC(SyncLoss) - - - - - - -LF - - - - - - -LOSS_SIGNAL(LOS) 12(4) 12(4) 13(5) - - - - - 13(4) 12(4) - - - - - 14(4) 14(4) - - - -PE(Errors) - - - - - - -STATE_CHG 12(5) 12(5) 12(9) - - - - - 13(5) 13(9) - - - - - 14(5) 14(9) - - - -LR - 13(6) 12(10) - - - - - 12(4) 13(10) - - - - - 14(4) 14(10) - - - -C3TXTO(Timeouts) - - - - - - -RX(%) - - - - - - -TX(%) - - - - - - -UTIL(%) - - - - - - -BN_SECS(Seconds) - - - - - - - Back-end port History Data:=================================

Stats(Units) Current 07/21/13 07/14/13 --/--/-- --/--/-- --/--/-- --/--/-- Port(val) Port(val) Port(val)---------------------------------------------------------------------------------------------CRC(CRCs) 2/1/0(15) - - - - - -LOSS_SYNC(SyncLoss) 2/1/0(1) 3/3/1(2) 3/3/1(2) - - - -

Viewing data for a specific time windowDetailed historical data provides the status of the switch for a specific time window. This is useful if, for example, users are reportingproblems on a specific day or time. The same port-display patterns apply to viewing detailed historical data as for ordinary historical data.

To view detailed historical data about a switch, complete the following steps.


2. Specify either the day or the hour of the current day you want to view:

• To specify the day, enter mapsDb --show details -day mm/dd/yyyy.

• To specify the hour, enter mapsDb --show details -hour hh.



The following example displays historical port performance data for May 19, 2014 for a chassis-based platform. Because the healthstatus of the current switch policy is CRITICAL, the sections “Contributing Factors” and “Rules Affecting Health” are displayed. If thecurrent switch policy status was HEALTHY, neither of these sections would be displayed. The column headings in the example have beenedited slightly so as to allow the example to display clearly.

switch:admin> mapsdb --show details -day 04/19/2014

1 Dashboard Information:=======================

DB start time: Mon May 19 23:40:58 2014Active policy: dflt_aggressive_policyConfigured Notifications: SW_CRITICAL,SW_MARGINALFenced Ports : NoneDecommissioned Ports : None

2 Switch Health Report: =======================

Current Switch Policy Status: CRITICALContributing Factors:---------------------*BAD_PWR (MARGINAL).*BAD_FAN (CRITICAL).

3.1 Summary Report: ===================

Category |Today |Last 7 days |--------------------------------------------------------------------------------Port Health |Out of operating range |No Errors |Fru Health |Out of operating range |In operating range |Security Violations |No Errors |No Errors |Fabric State Changes |No Errors |No Errors |Switch Resource |In operating range |In operating range |Traffic Performance |In operating range |In operating range |FCIP Health |Out of operating range |In operating range |Fabric Performance Impact|Out of operating range |In operating range |


Category(Rule Cnt)|RptCnt|Rule Name |Execution Time |Object |Triggered Value(Units)|-------------------------------------------------------------------------------------------------------Port Health(2) |1 |defALL_OTHER_F_PORTSCRC_40|04/19/14 17:18:18|Port 1 |876 CRCs | |1 |defALL_OTHER_F_PORTSCRC_21|04/19/14 17:18:18|Port 1 |876 CRCs |Fru Health(2) |2 |defALL_FANFAN_STATE_FAULTY|04/19/14 19:15:17|Fan 2 |FAULTY | | | | |Fan 1 |FAULTY |FCIP Health(2) |1 |low_tunnel_mon |04/18/14 06:19:6 |VEPort 2|25 |

4 History Data: ===============

Stats(Units) Current 04/19/14 --/--/-- --/--/-- --/--/-- --/--/-- --/--/-- Port(val) ---------------------------------------------------------------------------------------------CRC(CRCs) 0(>9999) 0(>9999) - - - - - 1(876) 1(876) - - - - - ITW(ITWs) - - - - - - -LOSS_SYNC(SyncLoss) - - - - - - -LF - - - - - - -LOSS_SIGNAL(LOS) - - - - - - -PE(Errors) - - - - - - -STATE_CHG - - - - - - -LR - - - - - - -C3TXTO(Timeouts) - - - - - - -RX(%) - - - - - - -TX(%) - - - - - - -UTIL(%) - - - - - - -BN_SECS(Seconds) - - - - - - -



Clearing MAPS dashboard dataTo delete the stored data from the MAPS dashboard, enter mapsdb --clear. This command is useful if you want to see only the data thathas been logged after you have made a change to a switch (or a rule). The dashboard is also cleared if either a reboot or an HA failoverhappens.

To clear the stored dashboard data from a switch, complete the following steps.


2. Enter mapsdb --clear and specify the level of data (all, history, or summary) you want to remove from the display.

When the dashboard is cleared, a RASLog message is generated. For more details on RASLog messages in MAPS, refer to theFabric OS Message Reference.

NOTEThe mapsdb --clear command does not clear the current day's history data (that is, the first column of the historydata). To clear the first column, enter slotstatsclear.

The following example clears only the dashboard summary data.

switch:admin> mapsdb --clear -summary

Clearing MAPS dashboard data


Other MAPS monitoring capabilities• Fabric performance impact monitoring using MAPS.........................................................................................................................89• Scalability limit monitoring.............................................................................................................................................................................91• MAPS Service Availability Module............................................................................................................................................................. 95• MAPS monitoring for Extension platforms.............................................................................................................................................97

Fabric performance impact monitoring using MAPSMAPS allows you to monitor your fabrics for performance impacts, including timeouts, latency, and throughput.

There are many distinct elements and layers in a fabric (applications, servers, switches, targets, LUNs, and other elements) andconsequently multiple places that could possibly be the cause of fabric performance impacts (bottlenecks). Because each application’sbehavior is unique, the impact of a bottleneck on one individual application might be different from its impact on another application.Each MAPS event needs to be viewed in conjunction with other server or application events to determine the actual root cause of theproblem.

The Brocade blades, chassis, and fixed-port switches are also continuously monitored for thermal safety. For more information, refer to“System temperature monitoring” in Fabric OS Administrator's Guide.

Enabling MAPS Fabric Performance Impact monitoringMAPS Fabric Performance Impact (FPI) is automatically enabled for new Brocade switches already running Fabric OS 7.3.x, or if thelegacy bottleneck monitoring feature was not enabled before the switch firmware was upgraded to Fabric OS 7.3.x.

NOTEIf you want to use FPI monitoring, the legacy bottleneck monitoring feature cannot be enabled.

If FPI has been disabled for some reason, complete the following steps to re-enable it.


2. Enter mapsconfig --enableFPImon. This will return one of two messages:

• If the legacy bottleneck monitoring feature is not enabled, you will see the following message:

Error: MAPS Fabric Performance Impact monitoring is enabled

• If the legacy bottleneck monitoring feature is enabled, you will see the following message:

Operation failed. Bottleneck monitoring is enabled. Please disable bottleneck monitoring and retry.

Enter bottleneckmon --disable to disable the legacy bottleneck monitoring feature, and then enter mapsconfig --enableFPImon again to enable MAPS Fabric Performance Impact monitoring.

For more information on the relationship of MAPS FPI monitoring and the legacy bottleneck monitoring feature, refer to MAPS FabricPerformance Impact monitoring and legacy bottleneck monitoring on page 91.


Bottleneck detection with the MAPS dashboardBottleneck monitoring based on the Fabric OS bottleneck daemon is integrated with the MAPS dashboard, enabling you to easily seewhich ports are impacted by either persistent or transient bottlenecks.

The MAPS dashboard displays the following latency events:

• Latency bottlenecks on any port

• Timeouts occurring on any 16 Gbps-capable Fibre Channel platform port

• A stuck Virtual Channel on any port

• Congestion bottleneck events (backpressure) on individual F_Ports (but not F_Port trunks)

The MAPS dashboard identifies the ports on which bottlenecks are seen and sorts them based on the number of seconds that theyexceeded the bottleneck threshold. This identifies the most strongly affected ports, no matter what the cause.

The bottleneck information appears in the “Rules Affecting Health” section as part of the Port Health category, and includes bottleneckevents detected by the bottleneck daemon. However, even if the bottleneck daemon does not log a bottleneck event (due to lack ofpersistence), the data shown in the “History Data” section displays entries both for those ports that have bottlenecks detected by thedaemon and for those ports that have cred_zero counters that are not zero. If the cred_zero counter increases for a port but nobottleneck time is recorded, this indicates a potential transient bottleneck on the port.

In the following example, the last three lines list bottlenecks, with the final bottleneck caused by a timeout rather than a numeric value. Beaware that the column headings in the example have been edited slightly so as to allow the example to display clearly.

3. Rules Affecting Health:===========================Category(RuleCnt)|RptCnt|Rule Name |Execution Time |Object |Triggered Value (Units) |-------------------------------------------------------------------------------------------------------Port Health(12) |1 |defALL_OTHER_F_PORTSLR_10 |08/21/02 0:30:06|D_Port 23|11 | 1 |defALL_OTHER_F_PORTSLR_5 |08/21/02 0:29:54|D_Port 23|7 | 1 |defALL_OTHER_F_PORTSC3TXTO_3 |08/21/02 0:29:36|D_Port 23|57 | 1 |defALL_OTHER_F_PORTSC3TXTO_10|08/21/02 0:29:36|D_Port 23|57 | 6 |Bottleneck_stuckvc |08/21/02 0:30:24|D_Port 23|STUCKVC | 1 |Bottleneck_latency |08/21/02 0:30:20|D_Port 23|60 | 1 |Bottleneck_timeout |08/21/02 0:30:27|D_Port 23|TIMEOUT | (output truncated)

When a latency rule is triggered, the instance is listed as part of the Traffic Performance category. In the both the “Front-end port HistoryData” section and the “Back-end port History Data” sections, the five ports with the longest total backpressure times since the previousmidnight are shown, as shown in the following example. Be aware that the headings in the example have been edited slightly so as toallow the example to display clearly.

3. Rules Affecting Health:=================================Category(RuleCnt) |RptCnt|Rule Name |Execution Time |Object |Trig Val(Units)|Fabric Perf Impact(5)|2 |defALL_PORTS_IO_PERF_IMPACT |08/21/02 0:30:6 |F_Port 13|IO_PERF_IMPACT 08/21/02 10:30:6|F_Port 22|IO_PERF_IMPACT 3 |defALL_PORTS_IO_FRAME_LOSS |08/21/02 0:30:6 |F_Port 3 |IO_FRAME_LOSS 08/21/02 10:30:6|F_Port 2 |IO_FRAME_LOSS 08/21/02 10:30:6|F_Port 4 |IO_FRAME_LOSS4.1 Front-end port History Data:=================================Stats(Units) Current 07/21/13 07/14/13 --/--/-- --/--/-- --/--/-- --/--/-- Port(val) Port(val) Port(val)---------------------------------------------------------------------------------------------CRC(CRCs) 13(20) - - - - - -ITW(ITWs) - 13(612) - - - - -LOSS_SYNC(SyncLoss) - - - - - - -LF - - - - - - -LOSS_SIGNAL(LOS) 12(4) 12(4) 13(5) - - - - - 13(4) 12(4) - - - - - 14(4) 14(4) - - - -

Fabric performance impact monitoring using MAPS


PE(Errors) - - - - - - -STATE_CHG 12(5) 12(5) 12(9) - - - - - 13(5) 13(9) - - - - - 14(5) 14(9) - - - -LR - 13(6) 12(10) - - - - - 12(4) 13(10) - - - - - 14(4) 14(10) - - - -C3TXTO(Timeouts) - - - - - - -RX(%) - - - - - - -TX(%) - - - - - - -UTIL(%) - - - - - - -BN_SECS(Seconds) - - - - - - - 4.2 Back-end port History Data:=================================Stats(Units) Current 07/21/13 07/14/13 --/--/-- --/--/-- --/--/-- --/--/-- Port(val) Port(val) Port(val)---------------------------------------------------------------------------------------------CRC(CRCs) 2/1/0(15) - - - - - -LOSS_SYNC(SyncLoss) 2/1/0(1) 3/3/1(2) 3/3/1(2) - - - -

NOTEThe MAPS dashboard will continue to log events whether RASLogs are set to on or off in the bottleneckconfiguration.

MAPS Fabric Performance Impact monitoring and legacy bottleneck monitoringThe 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 monitoringfeature is not enabled on a switch, MAPS will automatically start monitoring for impacts on fabric performance when the switchis restarted after upgrading to Fabric OS 7.3.0. However, if the legacy bottleneck monitoring feature was enabled before theupgrade, MAPS will not monitor for impacts on fabric performance. To use MAPS FPI monitoring, you will need to bothexplicitly 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 isenabled, 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 netmonapplication using the mapsconfig command.

• Disabling legacy bottleneck monitoring only disables the latency and congestion features, it does not disable stuck VCmonitoring. This means that a RASLog message stating “Severe latency detected” is still posted if that condition occurs.

Scalability limit monitoringMAPS monitors changes of fabric-level monitoring systems. These systems all have scalability limits which MAPS can monitor and sendalerts using RASLog entries, SNMP messages, or e-mail. The monitoring results are captured in the MAPS dashboard under the “FabricState Changes” category. Although there are default rules that monitor these values, MAPS allows you to define new rules with differentthresholds and actions.

MAPS can monitor the following scalability limits:

• The number of logged-in device connections in a pure Layer 2 fabric.

• The size of the zone configuration resource that is used.

• The number of Fiber Channel Router configurations.

Scalability limit monitoring


• The number of Logical SAN (LSAN) device connections (this includes both edge fabric and Backbone fabric deviceconnections).

NOTEMAPS monitors the device count per FCR switch.

When a rule is triggered, the corresponding RASLogs appear in the summary section of the dashboard. The following example showstwo rules (LSAN_DEVCNT_PER and L2_DEVCNT_PER) have been triggered. The column headings in the example have been editedslightly to allow the example to display clearly.

3.1 Summary Report:===================Category |Today |Last 7 days |--------------------------------------------------------------------------------Port Health |No Errors |No Errors |BE Port Health |No Errors |No Errors |Fru Health |In operating range |In operating range |Security Violations |No Errors |No Errors |Fabric State Changes |No Errors |No Errors |Switch Resource |In operating range |In operating range |Traffic Performance |In operating range |In operating range |FCIP Health |Not applicable |Not applicable |Fabric Performance Impact|In operating range |In operating range |

3.2 Rules Affecting Health:===========================Category(Rule Count) |RptCnt|Rule Name |Execution Time |Object |Triggered Value (Units)|-------------------------------------------------------------------------------------------------Fabric State Changes(2)|1 |LSAN_DEVCNT_PER|03/21/16 00:30:6|D_Port 23|12 % | |1 |L2_DEVCNT_PER |03/21/15 01:04:6|D_Port 23|12 % |

For more detailed information on scalability limits, refer to Brocade SAN Scalability Guidelines: Brocade Fabric OS v7.X.

Layer 2 fabric device connection monitoringA pure Layer 2 fabric is a collection of Fibre Channel switches and devices and switches that doesn’t participate in a metaSAN. In such afabric, rules for device counts are calculated as a percentage of the total number of devices. For example, a Layer 2 fabric with 5500devices logged in is using 92 percent of the maximum limit of 6000 devices for a Layer 2 fabric. So if user have configured a rule totrigger an alert at 90 percent or greater, then MAPS triggers the action configured for that rule and sends the data to the dashboard.

LSAN device connection monitoring in a metaSANThe collection of all devices, switches, edge and Backbone fabrics, LSANs, and routers that make up a physically connected but logicallypartitioned storage network is called a metaSAN. Using MAPS, the total number of LSAN device connections (including the total numberof devices from all edge fabrics) in a metaSAN can be monitored for a scalability limit.

NOTEMAPS rules for monitoring imported LSAN device connections in a metaSAN can be configured only on switches that are apart of the Backbone fabric.

Device counts in this framework are calculated as a percentage of the total number of LSAN devices in a metaSAN (including importeddevices from all edge fabric). For example: if a fabric has four switches in the Backbone fabric and four switches each in four edgefabrics, the total number of LSAN devices in this metaSAN (including imported devices from all edge fabrics) is 1200. Given amaximum of 10000 devices, this is 12 percent. If you have configured a rule to trigger at 10 percent or greater, then MAPS triggers theaction configured for the rule, but only on those switches that are part of the Backbone fabric, and caches the data in the dashboard.



Backbone fabric Fibre Channel router count monitoringIn a Backbone fabric, there can be maximum number of 12 Fibre Channel routers (FCRs). MAPS rules can be configured to monitor thenumber of Fibre Channel routers in the Backbone fabric as an absolute value. If the number of Fibre Channel routers reaches theconfigured threshold, MAPS triggers the action configured for the rule and caches the data in the dashboard. Refer to Default rules forscalability limit monitoring on page 94 for these values.

The following example shows a typical RASLog entry for exceeding the threshold for the number of Fibre Channel routers in theBackbone 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 theBackbone fabric. Be aware that the column headings in section 3.2 of the example have been edited slightly so as to allow the exampleto display clearly.

3.1 Summary Report:===================Category |Today |Last 7 days |--------------------------------------------------------------------------Port Health |No Errors |No Errors |BE 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 monitoringIn Fabric OS 7.3.0 and later, MAPS can monitor zone configuration size. Based on the platform, a switch supports either a maximumzone configuration size of 1 MB or 2 MB. The monitoring value is calculated as a percentage of the zone configuration space used. If theconfiguration size reaches the configured threshold limit, MAPS triggers the action configured for the rule and caches the data in thedashboard. Refer to Default rules for scalability limit monitoring on page 94 for these limit values.

NOTEMAPS 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 dependenciesThe 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 limitmetrics.

• The number of device connections in an edge fabric or Backbone fabric also have scalability limits themselves, and thesecannot be monitored using MAPS.



• Scalability limit monitoring (using L2_DEVCNT_PER) occurs only at midnight. Therefor, if a switch is moved from being a partof the Layer 2 fabric to being a part of the edge fabric, the device count metrics (how many devices in the fabric) will not changeuntil the next midnight.

• The “LSAN-imported device” metric is only monitored in switches that are a part of a Backbone fabric.

• Scalability limits that are determined internally by a device cannot be monitored by MAPS.

Default rules for scalability limit monitoringThe following table lists the scalability monitoring default rules in each of the default policies, and shows the actions and condition foreach rule.

TABLE 22 Scalability monitoring default rules

Policy name Rule name Rule condition Rule action

dflt_conservative_policy defSWITCHL2_DEVCNT_PER_90

defSWITCHLSAN_DEVCNT_PER_90

defSWITCHZONE_CFGSZ_PER_90

defSWITCHBB_FCR_CNT_12

L2_DEVCNT_PER greater than 90

LSAN_DEVCNT_PER greater than 90

ZONE_CFGSZ_PER greater than 90

BB_FCR_CNT greater than 12

RASLOG, SNMP, EMAIL

dflt_moderate_policy defSWITCHL2_DEVCNT_PER_75








RASLOG, SNMP, EMAIL

dflt_aggressive_policy defSWITCHL2_DEVCNT_PER_60








RASLOG, SNMP, EMAIL

Examples of scalability limit rulesThe following examples show the patterns for creating device counts, Fibre Channel router counts, and zone configuration usage rules forMAPS.

Rule for device counts in a Layer 2 fabricIn the following example, when the total device count in all switches that are part of the Layer 2 fabric rises above 90 percent of the totalpermissible count in the fabric, MAPS reports the threshold violation using a RASLog message.

switch123:FID128:admin> mapsrule --create L2_Dev_Count -group SWITCH -monitor L2_DEVCNT_PER -timebase none -op ge -value 90 -action RASLOG -policy scalability_policy

Rule for LSAN device countsIn the following example, when the total device count in all switches that are part of the metaSAN (edge plus Backbone) fabric rises above90 percent of the total permissible count in the fabric, MAPS reports the threshold violation using a RASLog message on that platform.

switch123:FID128:admin> mapsrule --create LSan_Dev_Count -group SWITCH -monitor LSAN_DEVCNT_PER -timebase none -op ge -value 90 -action RASLOG -policy scalability_policy



Rule for Fibre Channel router count in Backbone fabricIn the following example, when the maximum limit of 12 Fibre Channel routers in the Backbone fabric is reached, MAPS reports thethreshold violation using a RASLog message.

switch123:admin> mapsrule --create FCRCount -group SWITCH -monitor BB_FCR_CNT -timebase none -op ge -value 12 -action RASLOG -policy scalability_policy

Rule for zone configuration sizeIn the following example, when the zone configuration size limit reaches 90 percent of the total size, MAPS reports the threshold violationusing a RASLog message.

switch123:admin> mapsrule --create ZoneConfigSize -group SWITCH -monitor ZONE_CFGSZ_PER -timebase none -op ge -value 90 -action RASLOG -policy scalability_policy

For ZONE_CFGSZ_PER policy, the default time base is "none" and the system performs a daily check. The policy does not supportother time base.

MAPS Service Availability ModuleThe MAPS Service Availability Module (MAPSSAM) reports display CPU, RAM, and flash memory usage and the port status for everyphysical and virtual Fibre Channel port on the switch.

There are three options for the mapsSam command:

• --show: Displays the MAPSSAM report. Additional option parameters are shown in the table below.

• --clear: Clears the SAM report.

• --help: Displays how to use the command.Only mapsSam --show has additional option parameters. These parameters are listed in the following table and illustrated in thefollowing examples.

TABLE 23 MAPSSAM --show command option parameters

Option Details

--show

(default option)

For each physical and virtual Fibre Channel port on a switch, this displays the total up, down, and offline time (aspercentages), and the number of times the port has been down. This enables you to see if a particular port is failing moreoften than the others.

NOTEThe report does not distinguish why a port is recorded as down, it only reports how long the port has been down.

--show cpu Displays the CPU usage as a percentage.

--show memory Displays the general RAM memory usage as a percentage, along with total, used, and free memory values.

--show flash Displays the flash memory usage as a percentage.

The following examples demonstrate using the various mapsSam --show option parameters.

MAPS Service Availability Module


Using only “--show”When you enter simply mapsSam --show, the report lists the following information for each port:

• Port Number

• Port type

– AE (AE_Port)– DIS (disabled port)– DIA (D_Port)– DP (persistently disabled port)– E (E_Port)– F (F_Port)– G (G_Port)– N (N_Port)– T (Trunk port)– TF (F_Port trunk)– U (U_Port)

NOTEThe MAPSSAM report does not include the health status of gigabyte Ethernet (GbE) ports.

• Total up time — Percentage of time the port was up.

• Total down time — Percentage of time the port was faulty.

• Down occurrence — Number of times the port was faulty.

• Total Offline time — Percentage of time the port was offline.

• Number of ports

All percentages are based on the total time the switch was up or down since the switch was rebooted, MAPS was activated, or themapsSam --clear command was last run.

The following example shows typical output for mapsSam --show.

switch:admin> mapssam --show Total Total Down TotalPort Type Up Time Down Time Occurrence Offline Time (Percent) (Percent) (Times) (Percent)======================================================================0 F 100.00 0.00 0 0.001 F 100.00 0.00 0 0.002 U 0.00 0.00 0 100.003 F 100.00 0.00 0 0.004 DIS 0.00 0.00 0 100.005 DIS 0.00 0.00 0 100.006 DIS 0.00 0.00 0 100.007 DIS 0.00 0.00 0 100.00Number of ports: 8

Using “--show cpu”The following example shows the output for mapsSam --show cpu.

switch:admin> mapssam --show cpu memoryShowing Cpu Usage: CPU Usage : 3.0%

MAPS Service Availability Module


Using “--show memory”The following example shows the output for mapsSam --show memory.

switch:admin> mapssam --show memoryShowing Memory Usage: Memory Usage : 22.0% Used Memory : 225301k Free Memory : 798795k Total Memory : 1024096k

Using “--show flash”The following example shows the output for mapsSam --show flash.

switch:admin> mapssam --show flashShowing Flash Usage: Flash Usage : 59%

MAPS monitoring for Extension platformsFCIP Quality of Service (QoS) monitoring uses policies based on a combination of data characteristics and delivery requirements toappropriately prioritize data traffic. For example, while ordinary data traffic is tolerant of delays and dropped packets, real-time voice andvideo data are not. MAPS QoS policies provide a framework for accommodating these differences in traffic packets as they pass througha network, and can help you investigate issues such as packet loss, excessive bandwidth utilization, and similar issues.

MAPS can monitor the following on all FCIP-supported platforms:

• Tunnel

• Tunnel QoS

• Circuit

• Circuit QoS

QoS monitoring using MAPS uses the predefined QoS priorities of High, Medium, Low, and F-class. You can configure the values usedby these priorities at both the FCIP tunnel and circuit level. The attributes monitored by MAPS for QoS at circuit level are throughput andpacket loss. Throughput is the percentage of QoS circuit or tunnel utilization in a configured time period (hour, minute, or day); packetloss is the percentage of the total number of packets that have had to be retransmitted. MAPS monitors the state changes andthroughput of each individual tunnel using these QoS priorities. QoS monitoring is not High Availability (HA)-capable.

For tunnel-level monitoring, MAPS can monitor the predefined groups ALL_TUNNELS, ALL_TUNNEL_HIGH_QOS,ALL_TUNNEL_MED_QOS, ALL_TUNNEL_LOW_QOS, and ALL_TUNNEL_F_QOS. These groups correspond to the FCIP tunnels.

For circuit-level monitoring, MAPS can monitor the predefined groups ALL_CIRCUIT_HIGH_QOS, ALL_CIRCUIT_MED_QOS,ALL_CIRCUIT_LOW_QOS, ALL_CIRCUIT_F_QOS, as well as the ALL_CIRCUITS group for round-trip time (RTT) and connectionvariance (Jitter) in addition to the CIR_STATE, CIR_UTIL, and CIR_PKTLOSS parameters. Monitoring the RTT and Jitter values helps toalert you to possible network disruptions and congestion in the network.

Brocade FCIP monitoring parameters and groupsThe available statistics are broken out in the following table, and rules corresponding to these statistics are in the default policies.

TABLE 24 Use of Brocade FCIP monitoring groups as metrics

Parameter Groups where the parameter is used as a metric

State change (STATE_CHG) ALL_TUNNELS

MAPS monitoring for Extension platforms


TABLE 24 Use of Brocade FCIP monitoring groups as metrics (continued)

Parameter Groups where the parameter is used as a metric

Percent utilization (UTIL) ALL_CIRCUIT_HIGH_QOS, ALL_CIRCUIT_MED_QOS, ALL_CIRCUIT_LOW_QOS,ALL_CIRCUIT_F_QOS, ALL_TUNNELS, ALL_TUNNEL_HIGH_QOS, ALL_TUNNEL_MED_QOS,ALL_TUNNEL_LOW_QOS, and ALL_TUNNEL_F_QOS

Percentage of packets lost intransmission (PKTLOSS)

ALL_CIRCUIT_HIGH_QOS, ALL_CIRCUIT_MED_QOS, ALL_CIRCUIT_LOW_QOS,ALL_CIRCUIT_F_QOS, ALL_TUNNEL_HIGH_QOS, ALL_TUNNEL_MED_QOS,ALL_TUNNEL_LOW_QOS , ALL_TUNNEL_F_QOS

Round-trip time in milliseconds (RTT) ALL_CIRCUITS

Variance in RTT in milliseconds (Jitter) ALL_CIRCUITS

CIR_STATE, CIR_UTIL, andCIR_PKTLOSS

Refer to FCIP Health on page 32 for descriptions of these parameters.

TABLE 25 FCIP monitoring parameters

Platform Supported parameters

All FCIP platforms: • CIR_UTIL

• CIR_STATE

• CIR_PKTLOSS

• RTT

• JITTER

• PKTLOSS (Circuit QoS, Tunnel QoS)

• UTIL (Tunnel, Circuit QoS, Tunnel QoS)

• STATE_CHG (Tunnel)

MAPS monitoring for Extension platforms


Updating monitoring policy for 4 PSUdevicesWhen you increase the number of Power Supply Units (PSUs) in a chassis that supports more than two power supplies, you mustchange the active MAPS power supply switchstatus policy settings in order to enable the “call home” feature to be activated for all fourPSUs.

NOTEThis procedure applies only to the following platforms:

• Brocade DCX

• Brocade DCX 8510-8

To change the settings, complete the following steps.

1. Display the MAPS policy rules using one of the following commands.

• Enter mapspolicy --show -all.

• Enter mapsrule --show fw_CHASSISBAD_PWRCrit_3.The following examples show the results of each of these commands when the policy is set for two PSUs.

switch:admin> mapspolicy --show -allfw_CHASSISBAD_PWRCrit_3 SW_CRITICALCHASSIS(BAD_PWR/none>=3)...Active Policy is 'fw_active_policy'.

switch:admin> mapsrule --show fw_CHASSISBAD_PWRCrit_3Rule Data: ----------RuleName: fw_CHASSISBAD_PWRCrit_3Condition: CHASSIS(BAD_PWR/none>=3) Actions: SW_CRITICALAssociated Policies: fw_active_policy

2. Verify that the fw_CHASSISBAD_PWRCrit_3 setting is set to CHASSIS(BAD_PWR/none>=3).

3. Record the Active Policy name. This name is required to complete the following step.

4. Enter the command mapsrule --config fw_CHASSISBAD_PWRCrit_3 -policy policy_name from Step 3 -monitor BAD_PWR-group CHASSIS -timebase none -op ge -value new_value -action SW_CRITICAL to change the CHASSIS(BAD_PWR/none>=3) setting to CHASSIS(BAD_PWR/none>=1) . When you change a policy, you must enter all the values for the policy,even if you are changing only one value.In this example, the -policy value is fw_active_policy that you noted earlier and -value 1 changes the CHASSIS(BAD_PWR/none) value from 3 to 1.

switch:admin> mapsrule --config fw_CHASSISBAD_PWRCrit_3 -policy fw_active_policy -monitor BAD_PWR -group CHASSIS -timebase none -op ge -value 1 -action SW_CRITICALAssociated Policies: fw_active_policy


5. Enter mapsrule --show fw_CHASSISBAD_PWRCrit_3 to verify the value is set to 1.

switch:admin> mapsrule --show fw_CHASSISBAD_PWRCrit_3Rule Data: ----------RuleName: fw_CHASSISBAD_PWRCrit_3Condition: CHASSIS(BAD_PWR/none>=1) <- Note the changed value.Actions: SW_CRITICALAssociated Policies: fw_active_policy


MAPS Threshold Values• Viewing monitoring thresholds................................................................................................................................................................. 101• Fabric state change monitoring thresholds..........................................................................................................................................102• Extension monitoring thresholds............................................................................................................................................................. 102• FRU state monitoring thresholds.............................................................................................................................................................103• Port Health monitoring thresholds.......................................................................................................................................................... 103• Resource monitoring thresholds.............................................................................................................................................................. 107• Security monitoring thresholds.................................................................................................................................................................107• SFP monitoring thresholds........................................................................................................................................................................ 107• Fabric Performance Impact thresholds................................................................................................................................................. 108• Switch status policy monitoring thresholds......................................................................................................................................... 109• Traffic Performance thresholds.................................................................................................................................................................113

Viewing monitoring thresholdsYou can use the CLI to view the thresholds for a policy, or for a group within a policy.

To view monitoring thresholds, complete the following steps.


2. Enter mapspolicy --show policy_name. To see only the thresholds for a specific group in a policy, use --show policy_name |grep group_name.

The following example shows all the thresholds for the ALL_D_PORTS group in the policy named “dflt_conservative_policy”.

switch:admin> mapspolicy --show dflt_conservative_policy | grep ALL_D_PORTSdefALL_D_PORTSCRC_3 RASLOG,SNMP,EMAIL ALL_D_PORTS(CRC/MIN>3)defALL_D_PORTSPE_3 RASLOG,SNMP,EMAIL ALL_D_PORTS(PE/MIN>3)defALL_D_PORTSITW_3 RASLOG,SNMP,EMAIL ALL_D_PORTS(ITW/MIN>3)defALL_D_PORTSLF_3 RASLOG,SNMP,EMAIL ALL_D_PORTS(LF/MIN>3)defALL_D_PORTSLOSS_SYNC_3 RASLOG,SNMP,EMAIL ALL_D_PORTS(LOSS_SYNC/MIN>3)defALL_D_PORTSCRC_H90 RASLOG,SNMP,EMAIL ALL_D_PORTS(CRC/HOUR>90)defALL_D_PORTSPE_H90 RASLOG,SNMP,EMAIL ALL_D_PORTS(PE/HOUR>90)defALL_D_PORTSITW_H90 RASLOG,SNMP,EMAIL ALL_D_PORTS(ITW/HOUR>90)defALL_D_PORTSLF_H90 RASLOG,SNMP,EMAIL ALL_D_PORTS(LF/HOUR>90)defALL_D_PORTSLOSS_SYNC_H90 RASLOG,SNMP,EMAIL ALL_D_PORTS(LOSS_SYNC/HOUR>90)defALL_D_PORTSCRC_D1500 RASLOG,SNMP,EMAIL ALL_D_PORTS(CRC/DAY>1500)defALL_D_PORTSPE_D1500 RASLOG,SNMP,EMAIL ALL_D_PORTS(PE/DAY>1500)defALL_D_PORTSITW_D1500 RASLOG,SNMP,EMAIL ALL_D_PORTS(ITW/DAY>1500)defALL_D_PORTSLF_D1500 RASLOG,SNMP,EMAIL ALL_D_PORTS(LF/DAY>1500)defALL_D_PORTSLOSS_SYNC_D1500 RASLOG,SNMP,EMAIL ALL_D_PORTS(LOSS_SYNC/DAY>1500)

The first column is the name of the statistic being monitored. The second is the actions for that statistic that will be triggered ifthe threshold is passed. The third column lists the group being monitored, followed by the metric, followed by the threshold.This means that “defALL_D_PORTSCRC_3 RASLOG,SNMP,EMAIL ALL_D_PORTS(CRC/MIN>3)” :

• Is named “defALL_D_PORTSCRC_3”

• Has the actions RASLog, SNMP, and e-mail

• Applies to all D_Ports

• Measures CRC errors per minute. The threshold to trigger the listed actions is “more than three errors in a minute”.


Fabric state change monitoring thresholdsAll the fabric state change monitors support the Minute, Hour, and Day timebases. They do not support the “None” timebase.

The following table lists the default monitoring thresholds for fabric state change criteria used by MAPS. All thresholds are measured perminute and actions are triggered when the reported value is greater than the threshold value.

TABLE 26 Default fabric state change monitoring thresholds and actions

Monitoring statistic

Fabric state change monitoring threshold values by policy

ActionsAggressive Moderate Conservative

Domain ID change 1 1 1 RASLOG, SNMP, EMAIL

Fabric logins 4 6 8 RASLOG, SNMP, EMAIL

Fabric reconfigurations 1 2 4 RASLOG, SNMP, EMAIL

E_Ports down 1 2 4 RASLOG, SNMP, EMAIL

Segmentation changes 1 2 4 RASLOG, SNMP, EMAIL

Zone changes 2 5 10 RASLOG, SNMP, EMAIL

L2 Device Count 60 75 90 RASLOG, SNMP, EMAIL

LSAN Device Count 60 75 90 RASLOG, SNMP, EMAIL

Zone Configuration size 70 80 90 RASLOG, SNMP, EMAIL

FCR Count 12 12 12 RASLOG, SNMP, EMAIL

Extension monitoring thresholdsThese FCIP monitors support Minute, Hour, Day, and Week timebases: Tunnel state change, Tunnel throughput, Tunnel QoS throughput,Tunnel QoS Packet loss, FCIP Circuit State Changes, FCIP Circuit Utilization, FCIP Packet loss, FCIP Circuit Round Trip Time, and FCIPconnection variance.

The following tables list the default monitoring thresholds for Fiber Channel over IP (FCIP) criteria used by MAPS. All actions aretriggered when the reported value is greater than the threshold value.

TABLE 27 Default FCIP monitoring thresholds and actions

Monitoring statistic Units

FCIP monitoring threshold values by policy


Circuit state change(CIR_STATE)

Changes per minute 0 3 5 RASLOG, SNMP, EMAIL,FENCE

Circuit utilization percentage(CIR_UTIL)

Percentage per hour 50 75 90 RASLOG, SNMP, EMAIL

Circuit packet loss percentage(CIR_PKTLOSS)

Percentage per minute 0.01 0.05 0.1 RASLOG, SNMP, EMAIL

Circuit round-trip times (RTT) Total delay in milliseconds 250 250 250 RASLOG, SNMP, EMAIL

Circuit jitter (JITTER) Percentage of delay, calculatedfrom the difference of twosuccessive minutes. The totaldelay in milliseconds is averagedper minute for each minute.Values less than 5 ms in theconverted percentage areignored.

5 15 20 RASLOG, SNMP, EMAIL

Tunnel (STATE_CHG) Changes per minute 0 1 3 RASLOG, SNMP, EMAIL

Tunnel or circuit QoS (UTIL) Percentage per hour 60 75 90 RASLOG, SNMP, EMAIL

Fabric state change monitoring thresholds


TABLE 27 Default FCIP monitoring thresholds and actions (continued)

Monitoring statistic Units

FCIP monitoring threshold values by policy


QoS Packet loss percentage(PKTLOSS)

Percentage per minute 0.01 0.05 0.1 RASLOG, SNMP, EMAIL

FRU state monitoring thresholdsFor all FRU monitoring statistics, the default MAPS thresholds are part of blade and WWN rules for Brocade DCX and Brocade DCX+systems. All threshold conditions are absolute, and actions are triggered when the statistic value either does or does not match the value(depending on how the rule is written). FRU monitoring statistics do not use any timebases.

TABLE 28 FRU monitoring statistics, states, and actions

Monitored Statistic Supported States Actions

Power Supply (PS_STATE) ON, OUT, FAULTY RASLOG, SNMP, EMAIL

Fan (FAN_STATE) ON, OUT, FAULTY RASLOG, SNMP, EMAIL

Slot (BLADE_STATE) ON, OFF, OUT, FAULTY RASLOG, SNMP, EMAIL

SFP (SFP_STATE) IN, OUT, FAULTY RASLOG, SNMP, EMAIL

WWN (WWN) ON, OUT, FAULTY RASLOG, SNMP, EMAIL

Port Health monitoring thresholdsAll Port Health monitoring thresholds used by MAPS are triggered when they exceed the listed value. For thresholds that have both anupper value and a lower value, the threshold is triggered when it exceeds the upper value or drops below the lower value. All thresholdsother than RXP, TXP, and Utilization percentage are measured per minute. The RXP, TXP, and Utilization percentage thresholds aremeasured per hour.

The following Port Health monitors support Minute, Hour, and Day timebases: CRC Errors, Invalid Transmit Words, Loss of sync, LinkFailure, Loss of Signal, Protocol Errors, Link Reset, C3 Time outs, and State change. The SFP Current, SFP Receive Power, SFPTransmit Power, SFP Voltage, SFP Temperature, and SFP Power On Hours monitors support only the “None” timebase.

D_Port default Port Health monitoring thresholdsThe following tables list the default D_Port Port Health monitoring threshold values and actions, broken out by policy.

TABLE 29 Aggressive policy default D_Port Port Health monitoring threshold values and actions

Monitoring statistic Unit Threshold Actions

CRC Errors (defALL_D_PORTSCRC_1) Min 1 EMAIL, SNMP, RASLOG

Invalid Transmit Words (defALL_D_PORTSITW_1) Min 1 EMAIL, SNMP, RASLOG

Link Failure (defALL_D_PORTSLF_1) Min 1 EMAIL, SNMP, RASLOG

Sync Loss (defALL_D_PORTSLOSS_SYNC_1) Min 1 EMAIL, SNMP, RASLOG

CRC Errors (defALL_D_PORTSCRC_H30) Hour 30 EMAIL, SNMP, RASLOG

Invalid Transmit Words (defALL_D_PORTSITW_H30) Hour 30 EMAIL, SNMP, RASLOG

Link Failure (defALL_D_PORTSLF_H30) Hour 30 EMAIL, SNMP, RASLOG

Sync Loss (defALL_D_PORTSLOSS_SYNC_H30) Hour 30 EMAIL, SNMP, RASLOG

CRC Errors (defALL_D_PORTSCRC_D500) Day 500 EMAIL, SNMP, RASLOG

Port Health monitoring thresholds


TABLE 29 Aggressive policy default D_Port Port Health monitoring threshold values and actions (continued)


Invalid Transmit Words (defALL_D_PORTSITW_D500) Day 500 EMAIL, SNMP, RASLOG

Link Failure (defALL_D_PORTSLF_D500) Day 500 EMAIL, SNMP, RASLOG

Sync Loss (defALL_D_PORTSLOSS_SYNC_D500) Day 500 EMAIL, SNMP, RASLOG

TABLE 30 Moderate policy default D_Port Port Health monitoring threshold values and actions














TABLE 31 Conservative policy default D_Port Port Health monitoring threshold values and actions














E_Port default Port Health monitoring thresholdsThe following table lists the default E_Port Port Health monitoring threshold values and actions.

TABLE 32 Default E_Port Port Health monitoring threshold values and actions


E_Port monitoring threshold values by policy


C3 Time out (C3TX_TO) 5 10 20 EMAIL, SNMP, RASLOG



TABLE 32 Default E_Port Port Health monitoring threshold values and actions (continued)


E_Port monitoring threshold values by policy


CRC Errors (CRC) Low: 0

High: 2

Low: 10

High: 20

Low: 21

High: 40

Low: EMAIL, SNMP, RASLOG

High: EMAIL, SNMP, FENCE, DECOM

Invalid Transmit Words(ITW)

Low: 15

High: 20

Low: 21

High: 40

Low: 41

High: 80



Link Reset (LR) Low: 2

High: 4

Low: 5

High: 10

Low: 11

High: 20



State Change(STATE_CHG)

Low: 2

High: 4

Low: 5

High: 10

Low: 11

High: 20



Loss of signal(LOSS_SIGNAL)

0 3 5 EMAIL, SNMP, RASLOG

Link Failure (LF) 0 3 5 EMAIL, SNMP, RASLOG

Sync Loss (LOSS_SYNC) 0 3 5 EMAIL, SNMP, RASLOG

F_Port default Port Health monitoring thresholdsThe following table lists the default Host F_Port Port Health monitoring threshold values and actions.

TABLE 33 Default Host F_Port Port Health monitoring threshold values and actions

Monitoring statistic Host F_Port monitoring threshold values by policy Actions

Aggressive Moderate Conservative

C3 Time out (C3TX_TO) Low: 2

High: 4

Low: 3

High: 10

Low: 11

High: 20

Low: EMAIL, SNMP, RASLOG, FMS

High: EMAIL, SNMP, FENCE, DECOM, FMS


High: 2

Low: 10

High: 20

Low: 21

High: 40




Low: 15

High: 20

Low: 21

High: 40

Low: 41

High: 80




High: 4

Low: 5

High: 10

Low: 11

High: 20




Low: 2

High: 4

Low: 5

High: 10

Low: 11

High: 20







The following table lists the default Target F_Port Port Health monitoring threshold values and actions.

TABLE 34 Default Target F_Port Port Health monitoring threshold values and actions


Target F_Port monitoring threshold values by policy


C3 Time out (C3TX_TO) Low: 0 Low: 3 Low: 6 Low: EMAIL, SNMP, RASLOG, FMS



TABLE 34 Default Target F_Port Port Health monitoring threshold values and actions (continued)


Target F_Port monitoring threshold values by policy


High: 2 High: 5 High: 10 High: EMAIL, SNMP, FENCE, DECOM, FMS


High: 2

Low: 5

High: 10

Low: 11

High: 20




Low: 5

High: 10

Low: 11

High: 20

Low: 21

High: 40




High: 2

Low: 3

High: 5

Low: 6

High: 10




Low: 0

High: 2

Low: 3

High: 7

Low: 8

High: 15







NOTEIf an F_Port cannot be identified as either a host or a target, the thresholds for it are the same as those for HostF_Ports.

Non-F_Port default Port Health monitoring thresholdsThe following table lists the default non-F_Port Port Health monitoring threshold values and actions.

TABLE 35 Default non-F_Port Port Health monitoring threshold values and actions


Non-F_Port monitoring threshold values by policy


C3 Time out (C3TX_TO) N/A N/A N/A N/A


High: 2

Low: 10

High: 20

Low: 21

High: 40



Invalid Transmit Words (ITW) Low: 15

High: 20

Low: 21

High: 40

Low: 41

High: 80




High: 4

Low: 5

High: 10

Low: 11

High: 20



State Change (STATE_CHG) Low: 2

High: 4

Low: 5

High: 10

Low: 11

High: 20









Resource monitoring thresholdsThe only timebase the Resource monitors support is “None”.

The following table lists the default monitoring threshold values and associated actions for the switch resource criteria monitored byMAPS. All thresholds are measured per minute and are triggered when they are greater than the shown value.

TABLE 36 Default resource monitoring thresholds and actions


Resource monitoring threshold values by policy


Flash memory percentage used(FLASH_USAGE)


CPU percentage used (CPU) 80 80 80 RASLOG, SNMP, EMAIL

Memory percentage used(MEMORY_USAGE)


Ethernet management port state(ETH_MGMT_PORT_STATE)

Up/Down Up/Down Up/Down RASLOG, SNMP, EMAIL

Temperature Sensor (TEMP) OUT_OF_RANGE OUT_OF_RANGE OUT_OF_RANGE RASLOG, SNMP, EMAIL

Security monitoring thresholdsAll the Security Health monitors support the Minute, Hour, and Day timebases. They do not support the “None” timebase.

The following table lists the default monitoring thresholds for security criteria used by MAPS. Unless noted otherwise, all thresholds aremeasured per minute and actions are triggered when the reported value is greater than the threshold value.

TABLE 37 Default security monitoring thresholds and actions


Security monitoring threshold values by policy


DCC violations 0 2 4 RASLOG, SNMP, EMAIL

HTTP violation 0 2 4 RASLOG, SNMP, EMAIL

Illegal command 0 2 4 RASLOG, SNMP, EMAIL

Incompatible security DB 0 2 4 RASLOG, SNMP, EMAIL

Login violations 0 2 4 RASLOG, SNMP, EMAIL

Invalid certifications 0 2 4 RASLOG, SNMP, EMAIL

No-FCS 0 2 4 RASLOG, SNMP, EMAIL

SCC violations 0 2 4 RASLOG, SNMP, EMAIL

SLAP failures 0 2 4 RASLOG, SNMP, EMAIL

Telnet violations 0 2 4 RASLOG, SNMP, EMAIL

TS out of sync 1 per hour

2 per day

2 per hour

4 per day

4 per hour

10 per day

RASLOG, SNMP, EMAIL

SFP monitoring thresholdsSFP monitoring statistics do not use any timebases.

SFP monitoring thresholds


All SFP monitoring thresholds used by MAPS are triggered when the reported value exceeds the threshold value. For thresholds withboth an upper value and a lower value, actions are triggered when the reported value exceeds the upper threshold value or drops belowthe lower threshold value.

10 Gbps and 16 Gbps SFP monitoring threshold defaultsThe following table lists the default thresholds for 10 Gbps and 16 Gbps SFPs.

TABLE 38 Default SFP monitoring thresholds and actions for 10 Gbps and 16 Gbps SFPs


10 Gbps and 16 Gbps SFP monitoring thresholds for all policies

Actions10 Gbps SWL 10 Gbps LWL 16 Gbps SWL 16 Gbps LWL

Current (CURRENT) (mA) 10 95 12 70 SFP_MARGINAL, RASLOG,SNMP, EMAIL

Receive Power (RXP) (μW) 1999 2230 1259 1995 SFP_MARGINAL, RASLOG,SNMP, EMAIL

Transmit Power (TXP) (μW) 1999 2230 1259 1995 SFP_MARGINAL, RASLOG,SNMP, EMAIL

Voltage (VOLTAGE) (mV) 3000 to 3600 2970 to 3600 3000 to 3600 3000 to 3600 SFP_MARGINAL, RASLOG,SNMP, EMAIL

Temperature (TEMP) (°C) -5 to 90 -5 to 90 -5 to 85 -5 to 90 SFP_MARGINAL, RASLOG,SNMP, EMAIL

Quad SFPs and all other SFP monitoring threshold defaultsThe following table lists the default threshold and actions for Quad SFPs and all other SFPs that are neither 10 Gbps nor 16 Gbps.

TABLE 39 Default SFP monitoring thresholds and actions for QSFPs and all other SFPs


QSFP and other SFP monitoring thresholds for all policies

ActionsAll QSFPs All Other SFPs

Current (CURRENT) (mA) 10 50 RASLOG, SNMP, EMAIL

Receive Power (RXP) (μW) 2180 5000 RASLOG, SNMP, EMAIL

Transmit Power (TXP) (μW) - 5000 RASLOG, SNMP, EMAIL

Voltage (VOLTAGE) (mV) 2940 to 3600 2960 to 3630 RASLOG, SNMP, EMAIL

Temperature (TEMP) (°C) -5 to 85 -13 to 85 RASLOG, SNMP, EMAIL

Fabric Performance Impact thresholdsThe following FPI monitors support the Minute, Hour, and Day timebases: Receive Bandwidth usage percentage, Transmit Bandwidthusage percentage, and Trunk Utilization percentage. The Fabric Performance Impact monitor (DEV_LATENCY_IMPACT) supports onlythe “None” timebase.

The following table lists the default latency threshold values for FPI monitoring. They are binary, in that the threshold value is eitherpresent or it is not. When the latency returns within the threshold values, another message is issued, IO_LATENCY_CLEAR. .

NOTEWhenever IO_PERF_IMPACT is used, IO_LATENCY_CLEAR must also be included in the active policy to clear the latencyrecord.

Fabric Performance Impact thresholds


TABLE 40 Default Fabric Performance Impact latency monitoring threshold values and actions

Monitoring statistic Value (Y/N) for all policies Actions

Fabric Performance Impact(DEV_LATENCY_IMPACT)

IO_FRAME_LOSS

IO_PERF_IMPACT

IO_LATENCY_CLEAR

RASLOG, SNMP, EMAIL, TOGGLE

RASLOG, SNMP, EMAIL, TOGGLE

RASLOG, SNMP, EMAIL

The following table lists the default Receive Bandwidth usage percentage, Transmit Bandwidth usage percentage, and Trunk Utilizationpercentage value monitoring thresholds for E_Ports, Host F_Ports, Target F_Ports, and non-F_Ports.

TABLE 41 Default Fabric Performance Impact RX, TX, and UTIL monitoring threshold values and actions


FPI monitoring threshold values by policy


Receive Bandwidth usage percentage (RX) 60 75 90 EMAIL, SNMP, RASLOG

Transmit Bandwidth usage percentage (TX) 60 75 90 EMAIL, SNMP, RASLOG

Trunk Utilization percentage (UTIL) 60 75 90 EMAIL, SNMP, RASLOG

Switch status policy monitoring thresholdsThe following tables list the default switch status policy monitoring thresholds used by MAPS. All threshold conditions are absolute andactions are triggered when the reported value is greater than or equal to the threshold value. The only timebase the Switch statusmonitors support is the “None” timebase.

The switch status policy sends alerts every minute. Therefore, if a monitoring statistic is faulty for less than a minute, the alert for thatstatistic is not sent. For thresholds with both an upper value and a lower value, an action is triggered when the reported value exceeds theupper threshold value or drops below the lower threshold value. The following tables list the default Switch Status monitoring thresholdvalues and actions for each policy.

Aggressive policy default Switch Status monitoring thresholds and actionsThe following table lists the default Switch Status monitoring thresholds and actions for the default aggressive policy.

Monitoring statistic Description Switch status threshold values Actions

Devices Marginalthreshold

Criticalthreshold

BAD_FAN Number of fans that areabsent or faulty

Brocade 6505 n/a n/a Critical: SW_CRITICAL, SNMP, EMAIL

All other platforms n/a 1

BAD_PWR Power supply is absentor faulty

Brocade DCX, BrocadeDCX-4S, Brocade DCX8510-4, and Brocade DCX8510-8

n/a 3 Marginal: SW_MARGINAL, SNMP,EMAIL

Critical: SW_CRITICAL, SNMP, EMAIL

Brocade 7800 n/a 2

Brocade 6505 n/a n/a


BAD_TEMP Sensors indicatetemperature is outsideof range

All supported platforms 1 2 Marginal: SW_MARGINAL, SNMP,EMAIL


Switch status policy monitoring thresholds




Criticalthreshold

DOWN_CORE Number of core bladesthat are not functioning

Only chassis are supported 1 2 Marginal: SW_MARGINAL, SNMP,EMAIL


ERR_PORTS Percentage of portswith errors

All supported platforms n/a n/a Critical: SW_CRITICAL, SNMP, EMAIL

FAN_AIRFLOW_MISMATCH

Air flows of fans aremismatched

Brocade 6505, Brocade6510, Brocade 6520, andBrocade 7840

TRUE n/a Marginal: SW_MARGINAL, SNMP,EMAIL

FAULTY_BLADE Percentage of faultyblades

Only chassis are supported 1 n/a Marginal: SW_MARGINAL, SNMP,EMAIL

FAULTY_PORTS Percentage of portsthat are faulty

All supported platforms n/a 5 Critical: SW_CRITICAL, SNMP, EMAIL

FLASH_USAGE Percentage of storagespace being used

All supported platforms 90 n/a RASLOG, SNMP, EMAIL

HA_SYNC High Availability is notsynchronized

Only chassis are supported sync=0 n/a SW_MARGINAL, SNMP, EMAIL

MARG_PORTS Percentage of marginalports

All supported platforms n/a 5 Critical: SW_CRITICAL, SNMP, EMAIL

MISSING_SFP Percentage of SFPsthat are missing

All supported platforms n/a n/a n/a

WWN_DOWN Number of faulty WWNsystems

Only chassis are supported n/a 1 Critical: SW_CRITICAL, SNMP, EMAIL

Moderate policy default Switch Status monitoring thresholds and actionsThe following table lists the default Switch Status monitoring thresholds and actions for the default moderate policy.



Criticalthreshold








Brocade 7800 n/a 2













Criticalthreshold


All supported platforms n/a n/a Marginal: SW_MARGINAL, SNMP,EMAIL






















Conservative policy default Switch Status monitoring thresholds and actionsThe following table lists the default Switch Status monitoring thresholds and actions for the default conservative policy.



Criticalthreshold








Brocade 7800 n/a 2













Criticalthreshold


All supported platforms n/a n/a Marginal: SW_MARGINAL, SNMP,EMAIL






















Base policy default Switch Status monitoring thresholds and actionsThe following table lists the default Switch Status monitoring thresholds and actions for the default base policy.



Criticalthreshold

BAD_FAN Number of fansthat are absent orfaulty



BAD_PWR Power supply isabsent or faulty

Brocade DCX 8510-4 andBrocade DCX 8510-8


Critical: SW_CRITICAL, SNMP, EMAILBrocade 7800 n/a 2



BAD_TEMP Sensors indicatetemperature isoutside of range



DOWN_CORE Number of coreblades that are notfunctioning







Criticalthreshold


Air flows of fansare mismatched



FAULTY_BLADE The number ofblades with a faultystatus


FLASH_USAGE Percentage ofstorage spacebeing used


HA_SYNC High Availability isnot synchronized


MARG_PORTS Percentage ofmarginal ports



MISSING_SFP Percentage ofSFPs that aremissing


WWN_DOWN Number of faultyWWN systems


Traffic Performance thresholdsTraffic Performance monitors are used to monitor imported Flow Vision flows. The default policies do not include pre-set thresholds.

Monitor Description Grouptype

Supported timebases Actions

Minute Hour Day None

RX_THPUT Receive throughput FC Port RASLOG, SNMP, EMAIL

TX_FCNT Transmit frame count FC Port Yes Yes Yes Yes RASLOG, SNMP, EMAIL

RX_FCNT Receive frame count FC Port RASLOG, SNMP, EMAIL

TX_THPUT Transmit throughput Flow Yes Yes Yes Yes RASLOG, SNMP, EMAIL

IO_RD I/O read command count Flow Yes Yes Yes Yes RASLOG, SNMP, EMAIL

IO_WR I/O write command count Flow Yes Yes Yes Yes RASLOG, SNMP, EMAIL

IO_RD_BYTES I/O read data Flow Yes Yes Yes Yes RASLOG, SNMP, EMAIL

IO_WR_BYTES I/O write data Flow Yes Yes Yes Yes RASLOG, SNMP, EMAIL

All monitors for latency monitoringfeature

Flow Yes Yes Yes Yes RASLOG, SNMP, EMAIL

Traffic Performance thresholds


Documents

Brocade Monitoring and Alerting Policy Suite ... · Supporting Fabric OS 7.3.0, Fabric OS 7.3.1, and Fabric OS 7.3.2 ADMINISTRATION GUIDE Brocade Monitoring and Alerting Policy Suite