OK, I've been searching the last year's worth of forum topics for help on setting up HQ to intercept SNMP traps and haven't gotten it right yet.
I have a piece of software that produces SNMP traps and can forward them to a IP/port that I'm able to configure. The application uses OUTBOUND only SNMP and cannot be queried.
Currently, I have HQ server installed on one desktop and the SNMP enabled application on another. Using wireshark, I can see the traps making it to my server (if that's the destination ip/port I've configured), but I'm unable to capture the traps with HQ.
Here are some of the combinations I've tried with the results:
HQ agent installed on application client with traps sent to it's own IP (not 127.0.0.0) using various ports (162, 2144, 7080). I don't see any network activity making it to my HQ Server.
HQ agent installed on the server with traps sent to its IP and ports (162, 2144, 7080). Using ports 2144 and 7080 I get error messages in wireshark that the 'destination unreachable (port unreachable)'. However, using port 162, I can see the SNMP traps arriving on my server- just not displayed in HQ.
I've tried setting up the Network Device as instructed. It appears to work, but no metrics are displayed (and no traps). Looking further on the Monitor tab, it gives the error error message 'Unable to connect to SNMP Agent (snmp:null null,null)'. When I go to the Configuration Properties, it defaults the snmpIp to the client application IP, the snmpPort to 161, and the transport, version, and community. The transport and version are defaulted correctly, for the community, we use a string other than public. No matter what combination of IPs and ports I put in, I get the error message 'Unable to connect to [ip:port]: Connection refused: connect'
I've tried using the version 1 option as I've seen that it helps others, but it doesn't resolve anything.
I'm hoping someone can figure out what the heck I've done wrong.
Thanks in advance!
Kev
I've tried installing the agent on the server as well as the app. client and forwarding the traps to each using the default 2144 and 7080 ports but I get
I have a piece of software that produces SNMP traps and can forward them to a IP/port that I'm able to configure. The application uses OUTBOUND only SNMP and cannot be queried.
Currently, I have HQ server installed on one desktop and the SNMP enabled application on another. Using wireshark, I can see the traps making it to my server (if that's the destination ip/port I've configured), but I'm unable to capture the traps with HQ.
Here are some of the combinations I've tried with the results:
HQ agent installed on application client with traps sent to it's own IP (not 127.0.0.0) using various ports (162, 2144, 7080). I don't see any network activity making it to my HQ Server.
HQ agent installed on the server with traps sent to its IP and ports (162, 2144, 7080). Using ports 2144 and 7080 I get error messages in wireshark that the 'destination unreachable (port unreachable)'. However, using port 162, I can see the SNMP traps arriving on my server- just not displayed in HQ.
I've tried setting up the Network Device as instructed. It appears to work, but no metrics are displayed (and no traps). Looking further on the Monitor tab, it gives the error error message 'Unable to connect to SNMP Agent (snmp:null null,null)'. When I go to the Configuration Properties, it defaults the snmpIp to the client application IP, the snmpPort to 161, and the transport, version, and community. The transport and version are defaulted correctly, for the community, we use a string other than public. No matter what combination of IPs and ports I put in, I get the error message 'Unable to connect to [ip:port]: Connection refused: connect'
I've tried using the version 1 option as I've seen that it helps others, but it doesn't resolve anything.
I'm hoping someone can figure out what the heck I've done wrong.
Thanks in advance!
Kev
I've tried installing the agent on the server as well as the app. client and forwarding the traps to each using the default 2144 and 7080 ports but I get