Right now the deletion of device from the UMP and IM of Nimsoft is a hectic process. Can you make it a simple one
MichaelHarris is that situation what you can do then if you know for sure that the robots that are removed are gone for good and accounted for, you could stop the Nimsoft Robot Services on those robots hub box, delete the robots.sds file in the \nimsoft\hub folder and then start back up. The hubs robot list will be empty and all robots then will re-register them selves and you'll have a only valid and running robots checking into the hub at that moment.
I wish the removal of a device (in USM) were capable of doing it.
Unfortunately, we need you to spend little extra scripting time.
We have HUB callback "removerobot" which allows you to detach robot from hub.
robot unregister from hub time out
I'm well aware of that feature and have been using it since released. That still however doesn't resolve the original issue of deleting it also from the hub inventory even if the robot has stopped reporting. I still have to go to each affected hub and remove the robot from its inventory. While as long as it is only a couple of systems that's not that bad there have been times I've had to remove hundreds. Death by a thousand clicks.
This is how I interpreted the original idea. Make it to where we only have to delete once.
Delete Devices in USM - CA Unified Infrastructure Management - 8.5.1 - CA Technologies Documentation
In UIM 8.51 in USM you can go down into the inventory section and find a robot or device you want to delete.
put a check mark next to it and go to actions and choose delete selected.
you will be presented with a dialogue with 3 options.
You can choose as you see fit.
The one thing this does not do is if the robot or device is still reporting into IM then it will still be displayed there.
The above process can not deactivate or uninstall a robot.
Hope this helps clarify.
If you are having a problem with this I would suggest opening a support case.
This is labeled as "Delivered". I'd like to know in what version. I'm running 8.51 with the latest service packs and hot fixes. Still not there. Don't claim it's "delivered" but only in a version prior to GA.
I'm throwing the BS flag here.
This command line solution that might be usefull for automation (tested on 8.31):
./bin/pu -u *** -p 'yyy' /domain/hub/robot/discovery_server remove_master_devices_by_cskeys 570c9f0f-91cc-41cb-a7a4-d69accc72853
I am new to CA UIM and will be happy to hear if there is an equally simple way to get the cs_key.
A "select * from cm_computer_system" is not always practical.
when is this going to be implemented? I do not see any timelines and it is also something that we would like to have as well.
I have also just upgraded to UIM/UMP 8.40 and couldn't see this either...
cooja09 wrote: "With our next release you be able to perform the deletes from within the USM GUI."
That's a good start. We just upgraded to 8.4, so I am trying to find the new functionality. I clicked a server I wanted to delete and checked the Actions menu, but there was no "Delete" option. Where is the new option? Thanks!
Thanks to those who have contacted me with interest in participating in this discussion. I have sent an email and a Webex invite out to all of you. I look forward to conversing with each of you and better understanding your needs and critical use cases of UIM. If you have contacted me, but have not recieved an email, please reach out to me again.
I am planning on a Webex meeting to discuss this at 10:00 AM Mountain time on Wednesday October 28th. If you have not contacted me and would like to join us, please send me an email at email@example.com. I will be sure to forward the invite.
Add me to
Count me in.
OneNeck® IT Solutions, a TDS® Company
Count me also in
Count me in... Sent email...
I am a Product Owner for UIM. I am seeking the input of customers to help provide their thoughts as we improve the UIM solution to better handle the delete use cases that exist in the product. If you are interested in working via a private group that has a focus on this idea, I am asking that you send me an email. Once I receive an email from you, I will send you correspondence on our next steps forward.
I just learned about this yesterday so sharing on this post since its directly related. This new probe utility option in the discovery_server probe only removes the instance of the target robot in all associated tables but does not remove the QoS data associated with the robot being deleted.
That’s a great news Jim. Any idea which release will have this feature published in full fledge…. Right now it’s a pain to delete these unwanted QOS and node details of the same
Associate Infrastructure Specialist
<callto:tel:3822236> <sip:firstname.lastname@example.org> <callto:mob:+919995269269>
I'm Jim Cooke, the Product Manager for the UIM Server Core Service team. As noted above we actually already accepted these requests into our backlog. So I have set the status of this request accordingly. One other note however, with respect to the SQL procedures for deleting data from the NIS tables... As of UIM Server 8.1, inventory data is going to both the NIS tables and to our new UDM (Unified Data Management) data store. To facilitate keeping both data stores in sync, we provided Discovery Server callbacks to delete CS_IDs. With our next release you be able to perform the deletes from within the USM GUI. We are also working on providing a means to designate that the deleted inventory items should not come back into the inventory via any of the discovery avenues. All the other ideas, for decommissioning both inventory and monitoring and having the option to also deal with the associated QoS, are also in the backlog for subsequent releases.
Jim Cooke, Product Manager, UIM Core Services
Yes this would be great. I have written a python script to delete from all the discovery and device tables as well as the qos but still would be great to have it built in the product. Only thing that is hard to script is the niscache stuff would be nice if deleting a device would delete it from the nis cache as well.