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

does not respond with the community string

I'm evaluating NPM for a special project and it is not going particularly well. Thus far, every node I have attempted to add has generated an error "The node 'xxx.xxx.xxx.xxx' does not respond with the community string 'xxxxxxxx'"

I am (of course) using community strings that were configured when snmp was built on my servers in prep for this evaluation. None of the prior postings on this forum seem to contain a solution (except the v8.x patch - I'm evaluating v10). The recommendation to install WireShark was not well received by my corporate network folks. Are there any other approaches available?

Find more posts tagged with

Accepted answers

All comments

cdh

Hi Denniss -

When you say the community strings you are using are the ones built on your server, I'm not sure I'm clear on your goal. Are you attempting to discover network devices (routers, switches, etc.) with NPM, or are you actually testing APM and trying to manage servers?

The SNMP string you would use for NPM is the one that's configured on the routers/switches.

morgolis

When you can't get to a machine that has snmp enabled and properly configured using the correct (case sensitive) community string, it's either a routing issue (usually ACL's), a firewall problem in the middle or the firewall is enabled on the monitored server.

Wireshark rocks to see if packets are actually getting to the server.

jtimes

Check the server(s) to ensure that SNMP is allowed to accept packets from either Any Host or specific hosts. To check the server RDP / console into the server with administrative rights, go to Services, then SNMP Service, Right click on the service name then go to Properties. Click on the Security Tab. Depending on your organization's security levels select the appropriate method.

As for the firewalls - That could also be a contributing factor; although Orion can monitor the server it is installed on, and unless your default gateway is a firewall interface, there "shouldn't" be any other reason why you couldn't poll Orion's own server. Well other than not having the correct case sensitive community string in Orion for a particular node...

Hope that helps