UIM 20.4 CU5 Nas and alarm_enrichment probes fail to start.
Article ID: 262505
Updated On:
Products
Issue/Introduction
UIM 20.4 CU5
alarm_enrichment probe does not startup with error message
Feb 27 07:42:01:543 [main, alarm_enrichment] ****************[ Starting ]****************
Feb 27 07:42:01:544 [main, alarm_enrichment] 9.36
Feb 27 07:42:01:612 [main, alarm_enrichment] Nas: Starting: Alarm Enrichment Process
Feb 27 07:42:01:743 [main, alarm_enrichment] CmdbCacheEnrichmentSource: Loading CMDB Interfaces
Feb 27 07:42:01:743 [main, alarm_enrichment] CmdbCacheEnrichmentSource: Loading CMDB Interface origin_by_ip(com.nimsoft.probe.service.enrichment.cmdb.CmdbCacheEnrichmentSource)
Feb 27 07:42:01:744 [main, alarm_enrichment] CmdbCacheEnrichmentSource: Loading Datasource com.nimsoft.probe.service.enrichment.cmdb.CmdbJdbcDataSource for cache origin_by_ip
Feb 27 07:42:01:745 [main, alarm_enrichment] CmdbJdbcDataSource: GenericCmdbJdbcDataSource intializing with config path enrichment-source/cmdbs/origin_by_ip
Feb 27 07:42:01:747 [main, alarm_enrichment] CmdbJdbcDataSource: connecting to database
Feb 27 07:42:02:230 [main, alarm_enrichment] CmdbCacheEnrichmentSource: finished initializing origin_by_ip
Feb 27 07:42:02:231 [main, alarm_enrichment] CmdbCacheEnrichmentSource: Loading CMDB Interface blka_cmdb(com.nimsoft.probe.service.enrichment.cmdb.CmdbCacheEnrichmentSource)
Feb 27 07:42:02:231 [main, alarm_enrichment] CmdbCacheEnrichmentSource: Loading Datasource com.nimsoft.probe.service.enrichment.cmdb.CmdbJdbcDataSource for cache blka_cmdb
Feb 27 07:42:02:231 [main, alarm_enrichment] CmdbJdbcDataSource: GenericCmdbJdbcDataSource intializing with config path enrichment-source/cmdbs/blka_cmdb
Feb 27 07:42:02:231 [main, alarm_enrichment] CmdbJdbcDataSource: connecting to database
Feb 27 07:42:03:315 [main, alarm_enrichment] CmdbJdbcDataSource: I/O-Fehler: The Network Adapter could not establish the connection
Feb 27 07:42:03:315 [main, alarm_enrichment] (1) error, Failed to connect to database: I/O-Fehler: The Network Adapter could not establish the connection
Feb 27 07:42:03:318 [main, alarm_enrichment] (1) error, Failed to connect to database: I/O-Fehler: The Network Adapter could not establish the connection
at com.nimsoft.probe.service.enrichment.cmdb.CmdbJdbcDataSource.connectToDatabase(CmdbJdbcDataSource.java:113)
at com.nimsoft.probe.service.enrichment.cmdb.CmdbJdbcDataSource.initialize(CmdbJdbcDataSource.java:57)
This exception causes that nas probe does not startup anymore. We found that the cmdb database has been moved to another server internally and disabled the respective connection profile in the alarm_enrichment probe.
After this both, alarm_enrichment and nas started successfully. Our question is how can a connection failure on one of the connection profiles in the alarm_enrichment probe lead to a total down condition for nas ?
How can it happen that the alarm_enrichment probe simply doesn´t startup when one of it´s connection profiles fails to establish the database connection and impacts the whole UIM monitoring. From our understanding this is a bug. The product should have a better error handling here.
Environment
Release : 20.4 CU5
Cause
NAS has a dependency on the alarm_enrichment probe so if alarm_enrichment is not working, this will have an impact on Nas.
Resolution
NAS has a dependency on the alarm_enrichment probe so if alarm_enrichment is not working, this will have an impact on Nas.
This information can be verified here: [https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/monitoring/infrastructure-core-components/nas-alarm-server.html]
The probe is working as per the design. As the connection configuration is one-time activity, once it is successful this issue will not occur.
Additional Information
But still, this can be taken up as an enhancement How to raise an enhancement request for UIM for better exception handling.
Feedback
