Hi Craig, thanks for the question.

We really don't have a way to distinguish active vs retired.  

If you delete the device (right click delete) from the device tree, it will come back at the next discovery.

You can also remove the IP from the discovery range if you don't want it to come back, or add an exclude range for that IP.

Hope that helps,

Rob

Well in OME a system is either monitored or not depending on if it is in the discovery range you create.  If you delete the device and the ip from the discovery range, it just removes it from the Device table in the SQL database (pretty sure).

Thx

Rob

Hmmm, if you right-click delete it from the device tree and re-run discovery after adding it to the exclude range, I would have expected it to be removed from the Device tree.  Can you confirm you did both of these things?

Thx!

Rob

I do see the system(s) added to the exclusion range for discovery however they still exist in the dbo.devices table. By chance, are you able to test/replicate this behavior on OME 1.3?

Thanks, Rob- are you able to determine how the web-based admin console is able to filter these "retired" systems out? 

Thanks, Rob. The system hasn't been in the device tree but I do see it listed as a separate item in the exclude range for discovery. I went ahead and removed one of these 5 systems in question from the exclude range and then re-ran discovery across the board. Unfortunately, I still see the systems in questions listed in the 'devices' table in the database.

My intention is to run my own query's for a separate project - so I would like to (hopefully) get accurate data.

Hi Craig,

Sorry, I think I'm a bit muddy on the exact order of events...Is it like this:

1. Add 10.1.1.1-255 as a disc range

2. Device 10.1.1.5 shows up in the tree

3. you want .5 to go away

4. Add 10.1.1.5 exclude range

5. Delete .5 from the tree

6. Re-run discovery

7. Does .5 go back in the tree _and_ the Device table at this point?

Thanks,

rob