DX Unified Infrastructure Management

 View Only
  • 1.  Alarm policy kills MCS cdm QoS

    Posted Sep 15, 2020 11:08 AM
    HI all

    in 9.20
    Has anyone found that when enabling an Alarm Policy in Operator Console, monitoring an MCS profile, it stops the QoS from spooling, for the specific MCS profile ?

    Example:
    Create MCS profile for <robot>, to monitor Default Disk via USM. QoS is collected and working fine.
    Create Operator Console Alarm Policy - Settings-> Alarm Policies -> Add -> Add Condition -> Group -> Select Group -> Select Metric (Default Disk) -> Save. Qos stops collecting.

    Plugin_version 7.9.5

    When running PU (metric_plugin_info) on robot spooler qos_msgs_filtered increases. When OC alarm policy is disabled, this count stops.

    Is this a fault or design ?


    Thanks


  • 2.  RE: Alarm policy kills MCS cdm QoS

    Posted Sep 15, 2020 11:20 AM
    There have been some updates relating to these type of problems. 
    Check out mon_config_service_9.20_HF5_bundle.zip and it's readme lists the other packages that need to be deployed along with it. 
    https://support.broadcom.com/external/content/release-announcements/CA-Unified-Infrastructure-Management-Hotfix-Index/7233

    ------------------------------
    Support Engineer
    Broadcom
    ------------------------------



  • 3.  RE: Alarm policy kills MCS cdm QoS

    Posted Sep 15, 2020 12:01 PM
    Thanks for the response.
    I have applied this hotfix, as well as the hotfixes around it and also experience the same issue. This issue is also experienced on a 20.1 system.


  • 4.  RE: Alarm policy kills MCS cdm QoS

    Posted Sep 15, 2020 12:41 PM
    A support case very well may be needed for this. 
    One thing comes to mind is to setup a new robot with the HF version and see if it has the problem, or do a clean reinstall at an existing robot. 

    One item not so obvious is when using mcs only mcs is used to administer the probe and neither IM or AC is used for that instance of the probe.

    ------------------------------
    Support Engineer
    Broadcom
    ------------------------------



  • 5.  RE: Alarm policy kills MCS cdm QoS

    Broadcom Employee
    Posted Sep 15, 2020 03:23 PM
    HI Nick,

    Had something similar. Does Dr Nimbus show QOS subjects coming from the probe? If so check d_engine log and maybe do a hard restart of DE...this fixed a similar issue I had. DE got confused

    If no QoS in Dr. Nimbus then more likely need an issue.

    Also Alarm Policy is only supported ,(I believe),when you use Enhanced profiles So double check you are using Enhanced Setup CDM and Default Disk. Dont see a reference above.