Simple setup of snmptd probe

Products

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

Issue/Introduction

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

Environment

Release: Any
Component: snmptd probe

Cause

Guidance

Resolution

1. Check if the snmptd 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.

2. Add your community string, or SNMPv3 user and password 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 provide information on how to get the engine ID.

3. Load the MIB(s) and any dependent MIBs from the IMPORTS section of the Main MIBs via MIB Setup Wizard (if needed).

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

4. Create a profile via the MIB Trap Browser

- select the MIB

- highlight all traps

- right click select create profile

- close

5. Use the SNMP Trap Monitor. Click the Play button and then send a test trap from the network device to the robot IP where the snmptd probe is deployed.

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

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

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

Additional Information

Sending and receiving traps

When you have already taken the proper steps to send traps from the network device to the server/IP running the snmptd probe and you want to check for the traps using the snmptd Trap Monitor, use the Infrastructure Manager (IM) on/from the same server where snmptd is installed and check the snmptd logs at loglevel 5 to confirm that the traps are being received. Use a logsize of 30000.

Check Trap Destination: Ensure the trap destination IP address in the device's SNMP configuration is correct and points to the robot IP where snmptd probe is deployed.
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
Verify SNMP Settings: Confirm that SNMP is enabled and configured correctly on the device.
Check Community String: Ensure the community string used by the device matches the one configured in the snmptd probe.
Network Routing Issues: Verify that network routing allows the trap to successfully reach the snmptd probe.
Firewall: Check for firewalls that might be blocking trap traffic. [Standard trap port is 162 (UDP)]

You may have to work with your network team and use Wireshark if the test trap doesn't seem to be able to make it to the server/IP where snmptd is installed.