Interfaces going unknown after an OS Migration or patching

Hello,

After some patching activities and most OS Migrations we have to re-discover the network interface on our nodes. I believe the reason for this is due to the Windows OS re-indexing the interface causing SolarWinds to be unable to poll the "old" interface even though it is technically the same even though the OS thinks its different. I was wondering if anyone else has encountered this issue and if there is anything that can be done to re-discover these interfaces without manual intervention?

Find more posts tagged with

unknown

interface

Accepted answers

All comments

chad.every

How are you polling those Windows Servers? SNMP? WMI? Agent?

Seashore

Hi @JustinD

Yes, same thing can happen with volumes.

Either you create a scheduled report that tells you what devices needs attention. Or, you set up discovery jobs that finds any new interfaces or volumes you have. Then, in settings, you can choose to automatically remove stale interfaces and volumes after a certain time (7days by default)

JustinD

We are polling these devices with WMI.

JustinD

So I guess the solution here for my end would to create a custom script to kick off a network discovery for that node at the time of triggering the alert to execute the scan to remove and rediscover the interface?