Why servers are being changed to "Out-of-band device" class?

[Miguel Lara]

Hello everyone,

We recently noticed that some servers (specially some Windows and Linux) have been reclassified by Discovery as "Out-of-band devices". How does ServiceNow decides whether a CI should be moved across classes like this? In some cases I have also noticed that the CI goes into the Windows class one week, and the next Discovery gets it back to out-of-band and so on; it keeps flapping between these 2 classes.

Any hint to start troubleshooting will be appreciated.

Thanks in advance!

Miguel.

[doug_schulze]

My best bet is that the device is failing on its class identification then being caught with SNMP which is moving it over to the Out of Band class.

This process is controlled by these properties.

Id start by checking these things..

1. Are you consistently able to discover the devices with the expected credential (WMI/SSH).

2. Are you discovering these IPs consistently in the same schedule, meaning do you have one schedule with these IPs with all available protocols and correct credentials? Do you have a specific schedule with these IPs that are using a protocol selected discovery (Behaviors), perhaps SNMP only?

[Community Alums]

Hi Lara, 

To assess further i would recommend you to disable whatever you do not need in ( Discovery definition > Configuration console ) run discovery and check the Discovery logs

The second option is to re-scan the range with behaviors https://docs.servicenow.com/bundle/newyork-it-operations-management/page/product/discovery/reference... ( either WMI for windows or SSH for linux ) and check the logs.

[Sudharsanan Rav]

Hi Miguel,

This is a bit tricky, I suspect these Out of Band devices is capable of responding for both SNMP and SSH requests.

You can double-check the logs for the same to confirm. If yes, I would recommend using IP Service Affinities or Update Discovery behaviors.

Best,
Sudharsanan Ravichandran