How to delete robots in UIM when a VM with a robot has been powered off/decommissioned
search cancel

How to delete robots in UIM when a VM with a robot has been powered off/decommissioned

book

Article ID: 117796

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM) Unified Infrastructure Management for Mainframe

Issue/Introduction

Customers may decommission VMs that contain UIM robots running on them. Therefore, they want to permanently remove the robots from IM/USM.

The order in which the steps are followed is important.

The Help doc on 'How to Delete Devices in USM' focuses on discovered devices and does not discuss the complete process for permanently deleting robots.


https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/20-4/installing/discover-systems-to-monitor/advanced-configuration/remove-devices-in-usm.html



Customers may follow the Help documentation on 'How to Delete Devices from inventory' assuming that it also includes robots.

Environment

Release: ANY UIM version

Component: Any robot version

Resolution

How to delete robots in UIM when a VM with a robot has been powered off/decommissioned:

  1. When a VM that is running a robot on a Guest OS has been powered off, there is of course no need to stop the UIM (Nimsoft) Robot watcher service and/or uninstall the robot.

  2. In the Infrastructure Manager (IM), navigate to the hub where the decommissioned robots were connected/previously running.

  3. Then open that same hub probe GUI go to the Robots tab, select the robot and chose Rt-click delete to delete the robot(s).

  4. Login to OC and select the Inventory icon/node.

  5. Use the Quick filter and search for the robots/hostnames.

  6. Select the Actions dropdown and delete and then chose the desired options, e.g., delete alarms and measurements, but do not choose prevent rediscovery unless it makes sense for your purposes. Delete measurements prevents further QOS from being generated. The raw QOS data associated with probes that were running on the given robots will age out according to the data_engine raw data retention settings, e.g., 35 days.

  7. After ~30 seconds or less the robot hostnames should disappear from the view.

Additional Information

If the hub/robot reappears within a few minutes or so, you can also try deleting the niscache again, e.g., on the Primary Hub using the niscache clean probe utility callback.

If the hub or robot persists (comes back into the IM window), check for the following as well:

1. hub Name services (not just the Primary)

2. Any leftover queues that involve that hub

3. If the hubs.sds file is caching the old data


If a hub keeps reappearing in the Infrastructure Manager (IM):

  1. Shutdown the 'reappearing' hub-robot service, for example, if for some reason a hub was installed twice on differet drives, and may have a leftover entry in the hubs.sds cache.

  2. Delete the hubs.sds file from each and every every hub and restart them.

  3. Then go into other hub GUIs and select the Hubs tab, and find the hub, then Rt-click and Remove it

  4. Then make sure any Name Services entries for that hub are removed.

  5. Leave the hub-robot service shutdown for at least 10 minutes. This should allow the other hubs / hub 'lists' to repropagate. 

  6. Finally, if after 15 minutes the hub remains gone and does ot reappear, then start the correct hub-robot service up again.

Powered by Wolken Software