Simple setup of snmptd probe
search cancel

Simple setup of snmptd probe


Article ID: 242196


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)


Looking for a simple process for configuration and testing of snmptd. What is a basic configuration?


Release : Any
Component : snmptd probe


- Check if the probe package version exists in the local Archive. If the probe package file is missing, the IM will pop-up the Raw Configure window instead of the probe GUI.

- Add your community string, or SNMPv3 user as needed.

When you send a trap from the device, you can get the engine ID from a pcap of a trap sent by the device to the snmptd probe. Also the vendor should be able to give you information on this.

- Load the MIB(s) via MIB Setup Wizard (if needed)

You will need to add any supporting mibs as well. In other words if the trap related mib is has imports (other mib requirements) those need to be added to snmptd.

- Create profile via MIB Trap Browser 

- select the MIB
- highlight all traps 
- right click select create profile 
- close

Use the SNMP Trap Monitor. Click the play button and then send a test trap from the device to the IP of the snmptd probe.

Once the trap is listed in the trap monitor you can right click and select to create a profile for it.

Once you have created the profile you will want to bounce back to the configuration screen and select to Apply so the configuration is saved in the probe.

You can then send the trap once again and it should now show in IM or Operator Console.

Additional Information

If it appears that you are not getting alarms in the console, than there a few things that you will likely want to look into:

-validate that snmptd.exe on the probe machine is listening on port 162, and that no other application is. (this may require that you move the probe to another robot)
-validate your device is sending to port 162
-validate that the trap is making it to the probe machine (wireshark can be used to determine this, if not it is likely a firewall, or blocking issue)