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

Temperature Sensor Monitor

I'm trying to add our temperature sensor Temperature@lert Wifi Edition Version 6.24 as a node (entity) but not having much luck. It will not pass the test or allow me to click next and gives me the error message Node does not respond with the supplied read/write community string

I'm going to manage node

Add Node

Enter the IP of the temperature node

Selecting Most Devices

Match the SNMP version, SNMP port and community string from the temperature monitor.
There is no read/write community string on the temperature monitor

I've tried this article Node does not respond with the supplied read/write community string
I have tested adding a different device without issue.

I can ping the temperature monitor from the solarwinds server.

Any help would be greatly appreciated.

Find more posts tagged with

add node

room temperature

Accepted answers

All comments

mesverrum

Does your temperature sensor have a section where it restricts the hosts that it will answer SNMP requests from? Most of the environmental monitors I've used in the past have something along the lines of an Allowed Hosts list where you would need to add in the IP's of all your Solarwinds polling engines.

waldorfji

I didn't see any but will keep looking. Thanks for the reply.

d09h

Try snmpwalk.exe in your Orion installation folder. If it works there, that's what matters most. Some devices I have monitored would consistently fail to respond in an add node/ edit node context but work fine in every other aspect.

Obviously it's possible there are actual issues, but validating with snmpwalk.exe is pretty helpful.

waldorfji

0 OID’s timed out

dodo123

looking at the instructions http://www.tempalert.com/docs/default-source/TM-WIFI220-Documentation/WiFi_Edition_TM-WIFI220_User_Guide.pdf page 27.

(the unit does not respond to SNMP Get requests at this time)

so looks like you can send traps from it to solarwinds. But then depends what it sends as to whether there is something useful to alert.

waldorfji

Good catch I was looking at the 350 but we actually have the 220.

If I can send traps why would the test be failing just to add the mode (entity)?

dodo123

Thats the difference between snmp get and trap.

Solarwinds use snmp get to access the device and uses the mib to gather information.

SNMP Trap is when a device sends out alerts like a ups going onto battery, or a tempture device getting to hot so sends an alert.

The problem is its very basic, you would just have to add the device to solarwinds as an ICMP which will just ping it. Then set the device to send traps to the solarwinds box, from there you can do certain things based on the traps it sends out.

The supplier should have that information so you can get the trap viewer to alert on those messages but again this is very basic and lot more work on your part.

waldorfji

Thanks so much for your help.