Issue with SolarWinds connector changing CI class of a Windows 2016 server to Network Gear

[PiotrAG]

Hi all,

We have been testing ServiceNow Discovery in Dev alongside the SolarWinds connector to populate our CMDB. We have started of with a specific IP range.

ServiceNow Discovery works well. It discovers 3 servers as expected. Two 2012 windows servers and one 2016 windows server. The 2016 is a HPE server with ILO. This server in SolarWinds is correctly classified as a server.

When running SolarWinds discovery without any reconciliation rules, that server name will change to the ILO name and become network gear in the CI Classification. It clearly sees the ILO and thinks it needs to update that server CI. At this point we're not interested in the ILO in our CMDB and frustratingly it is taking precedence over the server when SolarWinds reports the information. 

I've been playing with reconciliation rules and the best I've managed to get is to set ServiceNow Discovery to have priority over SolarWinds on the Hardware class which also produces are interesting result. 

This will not change the name now which is good but it will classify it as network gear, before 30 seconds later reclassifying it as a computer. Now this is some progress however it is still clearly wrong. It should be set as Windows Server CI Classification. And everytime they both run they will just overwrite eachother. I've tried difference reconciliation rules on different hierarchies of CI's. 

Does anyone know what might be causing this and how I can fix this?

I've looked at previous forum posts and had people recommend using ETL to change the CI classification however to me that's just patching over the issue. I need it to keep the record as a server rather then network gear due to the ILO.

Our discovery set up is very much out of the box following the wizard so nothing custom going on. We are currently on Vancouver version. I am new to CMDB and Discovery in general.

Thanks,
Piotr

[PiotrAG]

From further investigation, I'm assuming its how ServiceNow is dealing with the information. We have the ILO which is set to network or other as device type and then we have the server which is set to server. I'm assuming the connector is bringing these both back, but for whatever reason the ILO is getting the precedence and overwriting the CI when they could be two separate records or at least the Server has precedence.