Client is seeing alarms in SOI using the SOI connector where the Content Add-ins link does not display for properly in PPM.
This is causing a problem with alarm correlation between UIM and SOI.
The SOI connector uses the following SQL queries to return the cm_computer_system table information for an alarm in UIM:
1) Select * from nas_alarms where nimid=? (copy the source alert id value for the alert in question to query this)
2) Collect dev_id and hostname from the result
3) Select * from cm_device where dev_id=?
4) Collect cs_id from the result
5) Select * from cm_computer_system where cs_id=?
6) Match the dns_name of computersystem with hostname of alert.
In this case it was found that hostname field in the nas_alarms table did not match up to the dns_name in the cm_computer_system
The root cause of this issue is the CDM probe can monitor remote device drives. By default the CDM probe will create a new dev_id and not use the local system dev_id.
NOTE: From the CDM documentation:
A key has been introduced in probe’s raw-configuration section named as ‘allow_remote_disk_info’ which is set as ‘yes’ by default.
Which means no change in probe behavior will be observed on probe upgrade.
To disable this feature, user has to set 'allow_remote_disk_info’ as ‘no’ so as to make the dev_id of shared drive and local drive identical.
To correct this problem the following steps will need to be followed:
1) User raw config to set the allow_remote_disk_info = no in the CDM probe(s).
2) Clear current alarms.
3) run the PU command to clear he nisache for the system and restart or delete the contents of the nimsoft\niscache folder and then restart the robot
4) do a discovery reset for the affected systems
This should allow for new dev_id to be creed for the cdm probe that will match the local system and allow for proper integration to SOI.