View previous topic :: View next topic |
Author |
Message |
RRing
Joined: 16 Aug 2006 Posts: 39
|
Posted: Thu Sep 11, 2014 2:40 pm Post subject: SNMP Trap Does Not Display |
|
|
I have currently setup HostMonitor to receive traps via the Miscellaneous Tab-SNMP Trap Test- Receive traps on UDP port 161. I then added a SNMP trap test method that accepts traps from ANY-ANY-ANY-ANY on the trap filter and then display OID. after this, I am not able to see any items in the reply field of the test. all that is displayed is OK for the test status.
To verify the test is being received, I setup IPTools trap receiver which receives and shows and properly displays the Traps being sent to the Hostmonitor Server so not sure what is wrong in the Hostmonitor Configuration. Any Idea's what I am missing here? I have reviewed the manual and the forum with no luck |
|
Back to top |
|
|
KS-Soft Europe
Joined: 16 May 2006 Posts: 2832
|
Posted: Thu Sep 11, 2014 2:59 pm Post subject: |
|
|
Only one SNMP Trap receiver can be started at the same time on same system. Please close all SNMP Trap receivers (Windows SNMP Trap service should be stopped as well), then start HostMonitor. |
|
Back to top |
|
|
RRing
Joined: 16 Aug 2006 Posts: 39
|
Posted: Thu Sep 11, 2014 3:12 pm Post subject: SNMP Trap Receiver Verification |
|
|
I verified the Windows Trap Receiver service was off and set to manual startup, Made sure IP-Tools Trap receiver was not running, then restarted HostMonitor. I am still unable to view any reply in the Trap Receiver test. I do not get any socket bind errors on hostmonitor startup, so still not sure why I do not see a displayed value when the trap is received?
Thanks |
|
Back to top |
|
|
KS-Soft Europe
Joined: 16 May 2006 Posts: 2832
|
Posted: Thu Sep 11, 2014 3:16 pm Post subject: |
|
|
Please check what application is using UDP port 162.
You may use the following command:
netstat -anb -p UDP |
|
Back to top |
|
|
RRing
Joined: 16 Aug 2006 Posts: 39
|
Posted: Thu Sep 11, 2014 3:48 pm Post subject: SNMP Display Solved |
|
|
We figured out there error after multiple test. The Trap filter good status was set to low, so it was immediatly setting the test to good after the trap was received. |
|
Back to top |
|
|
|