The policy_management queue on the primary hub is yellow / not connected
Article ID: 264650
Updated On:
Products
Issue/Introduction
The policy_management queue on the primary hub is not connecting and it has some queued messages. How can we fix this?
Environment
Release : UIM 20.4.x
Cause
The policy_management queue is needed solely for Default Alarm Policy creation after an Enhanced MCS Profile is deployed. More information here: MCS Alarm Policies management and policy_management queue (Broadcom)
In some cases, it is observed that the queue does not connect properly and it stays in a yellow state in the primary hub. The cause could be that the policy management module inside the OC Wasp has not properly started.
Although the queue is only needed for registering the new Default Policies created, the fact that the queue is not connecting might be a symptom of a nonfunctioning policy management module inside the wasp given by a "bad wasp restart".
This faulty state of the policy management module in the wasp could affect the correct functioning of Alarm Policies updates and modifications.
Resolution
To fix this issue:
1. redeploy the policy_management_ws package from the archive (the latest version available in the archive) to the OC Wasp
2. The wasp will restart. When the wasp is up and running, verify in the primary hub if the queue has reconnected.
3. If needed (policy_management queue is still not connected), force a hub restart too, and check if the queue is connected.
Additional Information
Feedback
