Alarm Policies not loading on secondary UMP server configured with Loadbalancer

book

Article ID: 186138

calendar_today

Updated On:

Products

NIMSOFT PROBES DX Infrastructure Management

Issue/Introduction

When multiple UMP servers are configured behind a loadbalancer the alarm policies are not loading on secondary UMPs

Cause

Alarm Policies cannot be worked on. The moment we click Setup Wizard -> Alarm Policies in Operator Console, all we get is the spinning loading icon forever. We are running two UMP servers behind a load balancer.
When we use the Chrome developer tools, we can see that the browser is trying to reach the policy_management_ws and getting a 404 http return code.

Environment

Release : 9.2.0

Component : UIM - ALARM POLICY

Resolution

for multiple UMP behind a loadbalancer you have to deploy the following fixes:

please download 
extract mon_config_service-9.2.0-HF2.zip, and extracted folder 
first apply the mon_config_service-9.2.0-HF2.zip to primary hub where monconfig service is running.
then apply mon_config_service_usm_patch-9.2.0-HF2.zip  to all the UMP servers.
then download policy-management-ws-0.2.2-HF3.zip and apply to all the UMP servers.
Choose any one of the wasp server. then add
 one config parameter policy_processing as true.

You can download the fixes from here 

https://techdocs.broadcom.com/us/product-content/recommended-reading/technical-document-index/ca-unified-infrastructure-management-hotfix-index.html?r=2

Here the instructions from the policy-managment-ws-.2.2-hf3.txt

For Multi UMP environment, this flag needs to be enabled only on a single UMP node. For other UMP nodes, this should be set to false. 
 
Sample configuration is as follows:
   
   <policy_management_ws>
        reloadable = true
        cross_context = true
        load_on_startup = true
        unpack_war = true
        <custom>
            <uncrypted>
                thread_count = 5
                max_retries = 3
                polling_interval = 5
                policy_processing = true
            </uncrypted>
        </custom>
        path = /policy_management_ws
    </policy_management_ws>
 
 
Dependencies/Prerequisites:
None

Steps to apply the patch:
1. Drag the policy_management_ws-0.2.2-HF3.zip from your local drive to the Archive folder in IM.
2. Stop the wasp using IM.
3. Edit wasp.cfg to set the flag "policy_processing" appropriately (refer notes above for DE436327).
4. Drag the policy_management_ws installation package (version 0.2.2-HF3) from the Archive folder in IM to the UMP robot.
5. Start the wasp probe using IM.

Related patches:
The following hotfixes are related and need to be applied. Refer to the respective release notes.
1. mon_config_service-9.2.0-HF2 
2. ump_usm-9.2.0-HF2


Limitation:
The alarm policy name as such still contains the group name of its creation time and not the renamed group name.