This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
So what we see is that a device upon initial discovery will inherit certain object types/indicators with its working SNMP OIDs. We reimport devices because of physical hardware changes and the historical data no longer matches what the current operating system or model is of the new hardware.
We reimport devices to fix baselines of snmp objects that picked up again, gather new objects, clear all previous alerts, and update reports.
Its also to mention that this does happen frequently due to planned system upgrade timelines in the environment and there is a need to reimport when device hardware is being changed due to data integrity.
Outside cluster settings clearing the objects per automation, nothing will fix historical data of generic objects are captured for the same ifMIBs, it will just continue on the same object once picked up again.
Hey Jacob, also please tell us more about the business use case driving the need for this and how often does it occur?
I could guess that you want to "reset" the device by deleting all the historical data, alerts, group memberships, etc., and start over with a new device but using the some of its previous base configuration, but not others?
Hi Jacob,
Thanks for the suggestion, I just want to make sure I completely understand. Have you tried editing the existing device and changing the Name, Description and IP Address? Discovery will add new objects that didn't exist before the hardware change and the orphaned objects will be automatically cleaned up as per your cluster settings (30 days by default).
Otherwise, are the only fields you'd like to change the ones you mentioned? All other settings should be preserved?