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 resources not staying checked off

I have a Cisco 2921K9 that is being polled via snmp, when listing resources I can clearly see the selection box for CPU and Memory. I check it off, save but when I go back to look at it the box is unchecked. I find this annoying. Any ideas or solutions would be welcome, Thanks.

Find more posts tagged with

Accepted answers

stuartd

For us, when this happens it means SolarWinds hasn't natively recognised the device. As a consequence it doesn't know how to do the hardware health side of it.

You may need to update your version of SolarWinds -- or your MIB file -- or create UnDPs to specifically monitor this device. We don't have any 2921 K9's so can't advise what we see. We do have 2901's and 2951's that work.

Might be worth raising a ticket with support.

All comments

marlief22

Hi there,

Do you have any network discovery jobs that are scheduled to run regularly? These would automatically add back poller that have been removed previously.

If that isn't the case, it could be that there is some issue with the way that the request is being sent to the database, I would check to see if the database table is ACTUALLY being changed by doing the following query on the DB:

SELECT * FROM [dbo].[Pollers]
where (PollerType like 'N.CPU%' or PollerType like 'N.Memory%')
and NetObjectID = '3' --Change this value for your node

You can get the node ID by going to the node details page and looking at the URL bar:

Check the 'Enabled' Column to see if it's been unticked once you press submit.

You would have to submit a ticket in that case, as there's likely something not communicating correctly on the platform.

Kind regards,

Marlie Fancourt | SolarWinds Pre-Sales Manager

Prosperon Networks | SolarWinds Partner since 2006

If this helps answer your question please mark my answer as confirmed to help other users, thank you!

superfly

You could try deleting and re-adding in the the node.

stuartd

ecklerwr1

I wonder if it's possible it's not recognized because it was End of LIfe February 4, 2014? Regardless you could do a UnDP for it like like @stuartd said.

Bill

cwjohnson3rd

That is the one question I have not asked yet. I have had this issue before with devices that are at or past the EOL, but I ran SMNP walk and I might have to try to build a poller for it. But my out will be to tell them that their device is too old.