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
Store

possible yet to ignore interface up/down status?

I've seen many posts regarding this topic, but they were rather old, and was wondering if this feature has become available yet. We're an academic environment, and we have numerous laptop carts with mobile WiFi access points on them. Becuase of their transient nature, they are not always online, but I would still like to gather interface stats. I don't want to see if they are up or down. My staff like to see all green lights. Has this become a feature yet or does anyone know how to do this?

thanks!

Find more posts tagged with

Accepted answers

All comments

njoylif

if you are talking port level, edit the interface(s) and select the option to mark as unplugged when down.

wickedtiinker

Got me in the right direction, thanks. I did enable that on my interfaces. They are now ticked for "unpluggable", but the status still shows unreachable, and hence the node shows down. I am on NPM 10.1.3, is it perhaps a bug?

njoylif

didn't realize they were unreachable; could be many reasons for unreachable...are these interfaces off a node or is it a "node" or device?

check poller load off the admin page, check "list resources" to ensure no issues there, etc..

Goliath

Ah, I think the unpluggable option is best used for interfaces rather than nodes themselves (i.e. for switch interfaces that support end users so you don't get a "down" alert when they turn their PC off etc). The status of the WiFi point itself will show as unreachable when it's not online simply because it's considered a node and NPM can't contact it. The only way around this is to use something like the unmanage scheduler utility to stop NPM from trying to poll it when it's not in use, this does depend on you having a schedule though (how good are your timetables )

Regards,

John

wickedtiinker

These are indeed interfaces off of a node in question. . The node (and its three interfaces) are currently unreachable as they are off for the Summer, so the reason for that is known. That is the problem, as I don't want to show a site with down equipment because their mobile AP is stored away in a closet. They are Cisco AP's, and have two radio interfaces and one Ethernet interface thatwe're monitoring. All three were set as "pluggable". I even checked my test subject from SQL, and that field is set to 1, but the web interface shows the interfaces as unreachable, which leads me to believe it is a bug in this version. Does it perhaps need to be online at least once after the tick is set?