nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Problems adding a node

jlstewart

Any ideas as to why I can't add a single node in node management? I'm getting test failed when I try to validate the polling via the IP address. This is a new switch that we just put on the network and I need to add it to SolarWinds for monitoring.

SW adding a node 12_10_18.PNG

Find more posts tagged with

Accepted answers

jlstewart

Update on this issue. Network team had to add my SolarWinds server to the ACL on the new switch.

All comments

mesverrum

Presumably because there is something preventing you from reaching the switch with SNMP. Can you putty from the orion server to that switch's IP? Can you telnet from the orion server to the switch on port 161?

jlstewart

I think you're right. I need to get with my network team to see what's going on. Thanks for your response.

rschroeder

There are a few possible reasons why adding your node to NPM via snmp is failing. The easy and obvious ones are:

Typos in either the NPM community string or the snmp string on the node. Verify them on both sides.
Access Control List rule(s) in the node that define which snmp pollers are allowed to talk to the node with specified community strings.
Firewall rules that allow or prohibit access from a poller to a node.
Routing that allows or prohibits traffic from the poller to the node.

For best security and easiest AAA:

- Never use a default community string like "public"
- Don't give snmp read-write power on any of our equipment. This makes AAA and TACACS and logging of events much easier to troubleshoot when someone actually has to SSH into a switch or router or firewall and manually make a change that's tied to their user name, instead of letting someone use a network management tool like NPM make changes on their behalf via snmp.
- Use snmp-v3 if you have data that should remain encrypted, private from sniffing. Remember that snmp-v3 is not compatible with User Device Tracker.

jlstewart

Update on this issue. Network team had to add my SolarWinds server to the ACL on the new switch.

Quick Links

All Categories
Recent Posts
Activity
Unanswered
Groups
Help
Best Of