Devices display multiple origins in the OC Inventory view
search cancel

Devices display multiple origins in the OC Inventory view

book

Article ID: 442559

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

We are currently using CU6 in our dev environment and we have encountered an issue regarding device origins.

All devices in the inventory are appearing with multiple origins.

Environment

  • DX UIM 23.4 CU6

Cause

  • customer states there are too many origins listed for the same device

Resolution

Seeing multiple origins for all or most devices in your inventory typically occurs because a device is either:
 
- monitored by different hubs
- targeted by multi-tenant/remote probes
- has historical origin data cached in the database
 
Depending on whether you want to completely merge these into a single origin for correlation or just clean up the display, follow the solutions below:
 
1. Differentiate "Origin" vs. "Latest Origin"
If you recently upgraded or reorganized your Hub structure, the Operator Console (OC) default Origin column displays a cumulative list of all historical origins that the robot or device has ever reported under.
  • Workaround: Add the Latest Origin column to your Inventory view. This column was introduced to show only the current, active Hub origin from the database (cm_computer_system), effectively filtering out the historical multi-origin noise.

As of 23.4 CU5 or higher, 

  • The Origin column contains all of the different origins to which the robot was associated

  • The Latest Origin shows the current Origin HUB

  •  The Latest Origin was an enhancement added to display only the latest origin from the cm_computer_system table in the Inventory and Device Details pages. 

2. Adjust Device Correlation Rules
By default, the discovery_server matches and groups devices based on specific attributes, and Origin is often one of them. If two entries for the same device have different origins, UIM treats them as distinct or gives them multiple origins.

To configure UIM to ignore or merge these origins, you can update the correlation configuration:
  1. Open the Admin Console or Infrastructure Manager.
  2. Go to the discovery_server probe and open Raw Configure.
  3. Navigate to <device> -> <correlation>.
  4. Locate or create the <treat_as_equal_values> section. Here, you can group different origin names together so UIM treats them as equal for correlation purposes.
  5. Alternatively, for simple network probes (like net_connect), ensure you define profiles with both Hostname and IP address instead of just an IP address. This allows name-based correlation to bypass origin mismatches.
  6. Save and restart the discovery_server probe.
3. Override Origins at the Robot/Hub Level
If the multi-origins are coming from probes reporting data from multiple distinct paths (e.g., a local robot monitoring a device, but an ICMP/net_connect probe on a remote hub also polling it), you can explicitly override the origin so everything aligns.
  • At the Hub level: Open the Hub configuration and explicitly set the Origin field to match your primary naming standard rather than defaulting to the hub name.
     
  • At the Robot level: If a single hub handles multiple environments, you can override the origin inside the robot.cfg (or via controller probe configuration) to force a matching origin name across all components on that machine.
4. Clear the niscache (If duplicates persist)
If devices are deeply cached with old origin data, you may need to force a reset of the local robot and discovery cache:
  1. Delete the duplicate/affected device entries from the OC Inventory page (do not select deep clean or delete metrics unless you want to wipe history).
  2. On the robot(s) pushing the multiple origins, stop the Nimsoft Robot Service.
  3. Delete the contents of the ($NIMSOFT_HOME)/niscache/ folder.
  4. Restart the Nimsoft Robot Service to force it to re-register clean discovery data with a single, active origin.
You can delete niscache in bulk for all robots or a list of robots by following this article.
Powered by Wolken Software