Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

NextRediscovery date is in the past

Hi!

I'm having a problem regarding the Next Rediscovery date in a lots of nodes... mostly Huawei Switches. The NextRediscovery date keeps stuck in the past whenever we're using the "Default node details poller by Solarwinds". I've noticed that when we set a Custom Node details poller, it updates the field correctly... however, due the amount of devices we have on our network, we have a daily "Network discovery" performed in order to detect new "up" interfaces and add them to the Npm, and everytime the Network Discovery is finished, the Default node details poller is assigned again.

Is there any way to keep my custom poller whenever a Network discovery is performed? Or a way to disable the defaut solarwinds poller? Or to force my poller to be an exact match?or a way to change the poller daily automatically?

Find more posts tagged with

Comments

marcrobinson

In Network Discovery there is an "ignore list" and you can add those Huawei switches to it. Hopefully that gets you past this issue. Having the next rediscovery date stuck is generally not a good sign for polling and system rediscovery (not the network discovery). You may want to dive deeper into that particular issue too.

hsh

The problem is that we have almost 500 Huawei devices and everyday there's a new link, so if I add these devices, I wouldn't have all the new interfaces monitored.

I read in other posts with other people the same issue with certain devices and solving that using a custom Node Details Poller