Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management 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 (

Shape the future of IBM!

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:

Search existing ideas

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 your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Needs more information
Workspace SevOne
Created by Guest
Created on Apr 8, 2024

Device Reimport Options | Managing device upgrades IRT.

Today, when we are doing device management and we identify when device hardware has changed, we must reimport the device into the solution.

That process today requires us to add the device to the deletion queue, wait for deletion, then readd via csv or manual import (there are also API options we are exploring)

A simple idea is that on the device editor page, there is a "Reimport Device" Option. Where all of the same plugin/peer information is kept, but requires manual input for the Name, AltName, Description and IP Address to be added. Device Groups could have an option to "Pin to Groups" if there is no planned change for device reporting procedure or alerting. The device would create a candidate in discovery manager before deletion, deletes the device, and then discovery takes care of the rest.

This solution would help administrators address changes in the network, this could even be an API function that could be automated to perform when a certain criteria is identified. A use-case today is when devices are upgrading to new hardware, we can have a process where ServiceNow Change Records create a subtask of SevOne to reimport automatically after a hardware change. Automation of this, allows our team to focus on new devices, and working towards more automated features of the tool.

Idea priority Low
  • Admin
    Ryan Wilson
    Apr 9, 2024

    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?

  • Admin
    Matt Sweet
    Apr 8, 2024

    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?