Brocade Fibre Channel Networking Community

Expand all | Collapse all

Too many alerts from MAPS

  • 1.  Too many alerts from MAPS

    Posted 07-19-2018 11:30 AM

    We have Brocade DCX series as well as 5100/65XX switches in our environment  having  FOS   v7.4.1b with MAPS enabled for monitoring.  We receive 100's of alerts everyday. I would like to stop messages which are not critical. Your help is highly appreciated.


    Affected Entity:   E-Port 1/5

    Rule Name:                        defALL_PORTS_IO_PERF_IMPACT

    Condition:                          ALL_PORTS(DEV_LATENCY_IMPACT==IO_PERF_IMPACT)

    Current Value:                  [DEV_LATENCY_IMPACT,IO_PERF_IMPACT, 12 ms Frame Delay]

    Dashboard Category:      Fabric Performance Impact

    Switch Name:                   SWXXXX

    Switch WWN:                   10:00:00:27:f6:5a:8f:34

    Switch IP:                 

    Fabric Name:                     uninitialized

    VFID:                                   126



  • 2.  Re: Too many alerts from MAPS

    Posted 07-19-2018 11:31 AM
      |   view attached

    Attaching File of Switch configs. 



    mapsconfig.docx   12K 1 version

  • 3.  Re: Too many alerts from MAPS

    Posted 07-31-2018 12:50 AM



    the message you are refering to is a FPI message. FPI thresholds can not be changed. Try to investigate why this port is introducing latency as a next step.




  • 4.  Re: Too many alerts from MAPS

    Posted 08-01-2018 12:30 AM

    Hi again,


    another option if you just want to suppress the messages you could youse the quiet time for messages.





    1. The clone the defALL_PORTS_IO_PERF_IMPACT to custom rule cust_ALL_PORTS_IO_PERF_IMPACT.

    mapsrule --clone defALL_PORTS_IO_PERF_IMPACT -rule cust_ALL_PORTS_IO_PERF_IMPACT


    1. Congiure the custom rule with quiet time. Quiet time can be like 5 mins or 30 mins or 1 hour based on your requirement. Below example to configure quiet time of 5 mins (in seconds)

    mapsrule --config cust_ALL_PORTS_IO_PERF_IMPACT -qt 300


    1. Add the new custom rule to custom policy. If the active policy is a default policy, then needs to clone the respective policy too, then delete the default rule and add the new qt rule.
    2. Finally enable the policy.