ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

The default alarm policy was not created after MCS profile was created

book

Article ID: 240013

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

The default alarm policy was not created after MCS profile was created.

Environment

Release : 20.4

Component : UIM OPERATOR CONSOLE - ALARM POLICY

Resolution

 The policy_management.log in the OC robot shows the below errors:

2021-12-10 14:34:22,073 DEBUG com.ca.uim.policy.management.events.service.HeartBeatService:registerThisNode:243 [Timer-1]   - Registering the policy node to [email protected]://<Primary hub IP address>/adminconsoleapp
2021-12-10 14:34:22,073 ERROR com.ca.uim.policy.management.events.service.HeartBeatService:registerThisNode:307 [Timer-1]   - Registration of this policy node to master failed, java.net.ConnectException: connect: Address is invalid 

or you can see the error below when the adminconsole page won't load:

2021-12-10 14:34:22,073 ERROR com.ca.uim.policy.management.events.service.HeartBeatService:registerThisNode:307 [Timer-1]   - Registration of this policy node to master failed, java.lang.RuntimeException: Failed : HTTP error code : 404


Please verify the below:

- The adminconsole is up and running, if it is not, please deploy the latest adminconsole package to the Primary hub.

- The wasp probe on the primary hub (adminconsole) has the "http_port" key.