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

Node not reporting down, interface says unknown

Python

For some reason NPM is no longer reporting nodes as going down/offline.

When i disconnect a device from the network the node has the green dot with a blinking grey dot, and it says :

Node is Up
One or more Interfaces are in an Unknown state.

How do i fix this so it reports the node as down.

Find more posts tagged with

Accepted answers

Python

I found my problem.

The event viewer logs were displaying:

The SolarWinds Collector Polling Controller service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

I came across this thread:

Which fixed my issue.

All comments

mcbridea

A node going down is not immediately detected. The node will go into a warning state on the next poll and then show down once the warning period has expired and the device cannot be reached. During the warning period Orion fast polls the device to determine if it is truely down.

patriot

Andy, is it true that a node can be showing "up" or "warning" while interfaces are showing "unknown" due to the separate and probably overlapping polling schedules that NPM uses to poll for Node status and Interface status?

In other words, if NPM polls for Interface status soon after the node is disconnected, NPM will not be able to obtain any interface data and the interfaces on the node will be "unknown, even while the node itself is still in fast polling mode and is not yet fully down?

Is that correct?

mcbridea

Yes - that is true

Python

I found my problem.

The event viewer logs were displaying:

The SolarWinds Collector Polling Controller service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

I came across this thread:

Which fixed my issue.