Alarms being created for undefined policy
search cancel

Alarms being created for undefined policy


Article ID: 269748


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)


We have observed the issue repeatedly with alarms being triggered for undefined policy.


  • Release: 20.4 CU6


We found 2 policy_management webapps were trying to process the alarms, so we were suspecting this was the main root cause for corruption of the xml in the ssrv2policyprofileblob database table.

1. Therefore, as a first step, we added policy_processing = false in one of the policy_management instances and everything started working as expected.

   a. policy_processing flag is set in the wasp.cfg
   >>>webapps/policy_management_ws/custom/uncrypted/policy_processing to true, policy processing will happen, if set to false, processing will not happen. This is the manual means of configuration.

   b. In a load-balanced environment with multiple policy_management_ws nodes,  policy_processing should happen in an HA mode.

For that to occur, webapps/adminconsoleapp/custom/uncrypted/ha_mode should be set to true and all the policy_management_ws nodes should not have a 'policy_processing' flag set.

Then, the nodes will be selected dynamically and work in HA mode.