Operator Console - Monitoring Config console cannot be opened

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Client cannot open Monitoring Config Console in Operation Console.

It looks like the page is loading but without results.

 

Environment

Release : 20.4

Component : UIM OPERATOR CONSOLE - MCS UI

Resolution

When opening Monitoring Configuration Service in the operator console, it just does not open (the loading icon is visible)

initial debugging has revealed the following HTTP 500 internal server message:

"status":500,"message":"Insufficient permission for operation - one of the following permissions are required: SELFSERVICE_MONITORING,SELFSERVICE_READONLY"

 

the WASP probe seems to be reporting to the primary HUB: 

<ump_common>
   maintenance_mode = /CAUIM_domain/UIMPrimHUB/UIMServer/maintenance_mode
   ems = /CAUIM_domain/UIMPrimHUB/UIMServer/ems
   nas = /CAUIM_domain/UIMPrimHUB/UIMServer/nas
   mcs_ui_app_url = /mcs-ui-app/
   ace = ace
   automated_deployment_engine = /CAUIM_domain/UIMPrimHUB/UIMServer/automated_deployment_engine
   discovery_server = /CAUIM_domain/UIMPrimHUB/UIMServer/discovery_server
   mpse = /CAUIM_domain/UIMPrimHUB/UIMServer/mpse
   lists_use_java_cache = false
   sla_engine = /CAUIM_domain/UIMPrimHUB/UIMServer/sla_engine
   udm_manager = /CAUIM_domain/UIMPrimHUB/UIMServer/udm_manager
</ump_common>

 

The OC robot is under secondary HUB (as noticed earlier) - this is wrong, and such a config is not supported. Before applying the CU2 update, please perform the following PoA:

 

1. Move the OC robot to Primary HUB:
 - in IM right click on the robot name, select move
 - find the primary HUB and select it
 - Click OK 
 - Refresh IM

2. Then the robot should be under primary HUB.

3. Once the robot is under primary, please right click on this and click "restart"