Hi Dan,
To track down the southbound synchronization you'll have to set the catalyst debug on the SOI manager and UCF debug on the UIM connector machine:
- Edit CA\SOI\tomcat\lib\log4j.xml
Go to the line
<logger name="com.ca.ssa.sor" additivity="false">
<level value="INFO" />
<appender-ref ref="CAT" />
</logger>
and set the level value to DEBUG from INFO
save the file. You'll have to recycle the CA SOI Application server service for this take affect. This is SOI manager service so you'll have to setup a downtime for this. The catalyst.log are in CA\SOI\tomcat\logs folder
- On the UIM connector machine edit CA\Catalyst\CatalystConnector\container\etc\log4j-ucf.propeties, go to the line
log4j.logger.com.ca.ucf=INFO, LOGFILE
and set the INFO to DEBUG
save the file and recycle CA Catalyst Container service. The ucf logs are in CA\Catalyst\CatalystConnector\container\data\log
- Note down one nimid (source Alert ID on SOI console) for one UIM alert and clear it from SOI console.
- Open catalyst.log and search for the "source Alert ID" you just cleared and you should see details of the alert properties and values including "<usm-core:IsCleared>true</usm-core:IsCleared>".
- Same "source Alert ID" should show up in the ucf.log on the UIM connector machine if the notification makes it through from SOI manager to the connector. from ucf.log the alert clear notification also should show up in the UIM connector log.
Thanks
Shaheen
Original Message:
Sent: 03-09-2020 11:01 AM
From: Daniel Blanco
Subject: What logs check why UIM not closing when closed in SOI?
SOI v4.2 with SO07439
UIM 9.20 Robot Version 9.20HF9
Recently I noticed that when alerts cleared in SOI they are not clearing the respective alert in UIM. I'm running the Global Delivery UIM Connector and wondering what files do i have to enable debug on and how to check why alerts are not getting cleared on the UIM side?
I see these entries in the Nimsoft_connector.log file but it doesn't help:
[2020-03-09 09:15:23] [Thread-70222] WARN [com.ca.usm.ucf.nimsoft.controller.AlarmSubscriber] - alarm_close received for unknown alarm VN90115072-52048
[2020-03-09 09:15:23] [Thread-70222] DEBUG [com.ca.usm.ucf.nimsoft.controller.AlarmSubscriber] - chgMgr is not null and about to close alarm VN90115072-46576
------------------------------
Daniel Blanco
Enterprise Tools Team Architect
DBlanco@alphaserveit.com
------------------------------