Start a Conversation

Unsolved

This post is more than 5 years old

2255

May 27th, 2016 09:00

Exclude workstations and other devices?

We are trying to use OME to manage only Servers running OMSA, iDRACs and ESXi hosts. In the discovery I did not check "Windows server without OMSA", nor did I check "windows desktop/laptop", nor "Other device".

However it STILL pulled in all of my printers, workstations, etc. 

How can we purge all of those devices from the inventory, and how do I keep it from detecting them again? (I'm not against deleting the database and starting over as we arent that deep into the project) 


Having things like printers and workstations just clutters up the system and causes bogus alerts when users restart or shut down their systems. 

8 Posts

May 27th, 2016 10:00

I dont see a way to change the protocol once a range is created and I try to edit it.  It looks like I'm going to have to shake the etch a sketch and start from scratch. I can see that ability if I create a new range using the standard and not the guided wizard. But under guided you have no choice in protocol. (at least not after the fact) 

And is there  a quick way to eliminate the entire database and start from scratch? It looks like I'll need to remove all discovered devices, as well as create an entirely new set of discovery ranges. 


3 Apprentice

 • 

2.8K Posts

May 27th, 2016 10:00

Hi Roy and thanks for the post.

So if for the iDRAC and ESXi we are making the connections via WSMan, so that's likely not the issue.

For discovering OMSA boxes, we can connect via WMI or SNMP depending on how you fill out the discovery wizard (there is a classic wizard and a guided wizard).

If you pick the WMI protocol and uncheck the SNMP protocol, then you probably won't see printers or SNMP devices any more.

For the workstations, it kind of depends how they are set up.  If you were *trying* to discover Dell Precision Workstations, I'd suggest you use WMI plus the Dell Client Command agent.  It used to be called OMCI.  If your workstations are being picked up, they might be getting discovered via SNMP or WMI depending how you set it up.

If there are only a few of these bothersome devices, you can right click on the device and click Exclude.  It will create an exclude range so it won't be picked up in subsequent discovery runs.  Thus, the other solution is to handle this problem with Exclude ranges.

Hope this helps,

Rob

3 Apprentice

 • 

2.8K Posts

May 27th, 2016 13:00

I don't think there is a re-set db.

But if you just delete the discovery ranges, it ought to delete the corresponding devices.  Then you can create a new range.  There is a settings/preference that let's you change from guided to classic wizard if that suits your needs more.

Thanks!

Rob

8 Posts

June 6th, 2016 10:00

After shaking the etch a sketch to the point of even uninstalling and reinstalling OME, I still cant get it to work as expected. 

To prevent unwanted devices I set it to only scan the IP addresses of my servers and DRACs. 

When it scans it detects them all, but...

  • it will not categorize the servers at all.
  • Only about 60% of the DRACs are tagged properly with several listed as OEM devices and the rest as unknown. 

My Solarwinds ORION management software has no trouble categorizing any of the devices and reading them using the same SNMP strings. 

3 Apprentice

 • 

2.8K Posts

June 6th, 2016 11:00

Hi Roy,

Can you confirm that you are using the WSMan protocol for discovering your iDRACs?

You won't need the SNMP protocol when discovering your iDRACs, so you can uncheck SNMP if you like.

Thanks,

Rob

8 Posts

June 6th, 2016 13:00

Yes, WSMAN is used for the dracs, and it works for most of them. (they all use the same credentials)

But it wants to use SNMP to manage the servers per the documentation. 



No Events found!

Top