We have setup the snmptd probe to include Vbrick switch related traps. Vbrick support has tried sending numerous times and we haven't seen anything on the Nimsoft side. Would like to meet with someone with knowledge of the snmptd probe if possible to see if anything is missing with our snmptd probe setup.
Via raw configure for the snmptd probe set loglevel to 5, logsize to 100000.
Ensure that the relevant TRAP or SYSTEM MIBs as well as any dependent MIBs listed under the IMPORTS section of the MIBs have been imported-loaded into snmptd.
Deactivate-Activate snmptd.
As per netstat command output results, is the port open and LISTENING on the robot where snmptd is deployed?
netstat -ano -p udp
netstat should show snmptd.exe process LISTENING on port 162. To validate this run:
netstat -aB >> file1
Open file1
look for:
UDP 0.0.0.0:162 *:*
[snmptd.exe]
Send a few test traps
In Windows Services, select and configure the SNMP Service agent and traps with community string and destination (IP of robot where snmptd is deployed),
on a Windows server to send some basic traps as a test.
How to send an SNMP trap from a Windows Server to test trap send/reception?
or...
Download and use an snmptrap utility to send a few traps, such as:
https://ezfive.com/snmpsoft-tools/snmp-trap-gen/
Here is an example SnmpTrapGen command to generate and send traps from a Windows server:
SnmpTrapGen.exe -r:10.48.xxx.xx -t:20 -c:"n3tcool" -to:.1.3.6.1.4.1.4289.3.3.1.2
-r: = device ip address
-t: = timeout
-c: = community name
-to: = OID
Example of command output:
Traps were then successfully received by the snmptd probe as per the results in the snmptd Trap Monitor window in less than a minute.
Therefore this proves that the snmptd probe side is setup properly and communication and trap reception is verified.
The customer must recheck with his network team regarding the device setup and traps since they are simply not reaching the robot where snmptd is deployed.
Potential causes of interference may include:
Troubleshooting (debug) tips:
If the traps were not received by the snmptd probe during the test, a Wireshark trace can be performed on the robot where snmptd is deployed.
Other causes of no traps in the trap monitor could be due to:
If you still see no traps in the SNMP Trap Monitor:
Check the snmptd.log for this error: snmptd: Rejected! Community not in list
In snmptd probe GUI config under Security-> Properties
1. Confirm if the community string related to this device is present or not.
If present, double-check the correct community string spelling.
This is in the probe settings under Security Manager -> Community tab. Please note that this is CASE-sensitive as well.
2. Alternatively, you can add a "*" in the community string for testing
To convert SNMP Trap alarms to Nimsoft alarms: