Robot Trapper can monitor for traps sent from your UNIX and Linux servers. UNIX and Linux use SNMP daemons to process SNMP requests and send traps. Each daemon has a configuration file denoted by a suffix of .conf. The file contains the trap destination information. To get your UNIX or LINUX servers to send traps to Robot Trapper, you must find and end the SNMP daemon, then find the SNMP configuration file. Then, you must configure and restart the SNMP daemon.
You may have the master SNMP Daemon ps - ef | grep snmp running on your UNIX or Linux system. If this daemon running, you will see the PID of the daemon.
If your server has a script to start or stop the daemon, use the stop script to stop the daemon. If not, use the following command to end the SNMP daemon, where is the ID discovered when you enter the PS command.
Verify that the SNMP Daemon is down.
The information contained in and required by the configuration file for each of your UNIX and Linux servers may be different. For this reason, we suggest that you find the configuration file. Some common names for the configuration file are SNMPD.CONF and SNMPDM.CONF. You can search your system for a configuration file using the find command:
find / -file name "snmp*" -print
If you find the configuration file, write down its full path and file name.
If you do not find a configuration file, search your installation disk for the SNMP related objects, or use the keyword SNMPD in an Internet search engine to find a site that has an SNMP daemon that will run with your release of UNIX or Linux.
To determine the keywords your daemon requires for configuration, use the man command, where is the name of the configuration file. Keywords will vary from daemon to daemon.
Make a copy of the configuration file.
Use an editor to edit the configuration file; add the keywords required by your daemon to the bottom of the file.
Note: The keywords may have been overwritten or appear as blank spaces.
Ensure that the community name is public.
Change the host name to the IP address of the IBM i running Robot Trapper.
Change the port, if required, to 162. Typically, the default is162.
If the daemon allows you to choose if authenticationError will be sent, choose whether or not it will be sent. The default usually is Off.
Save your changes.
If your server has a script to start or stop the daemon, use the start script to start the daemon. If not, start the daemon by entering the name of the daemon with the full qualified name, or change the directory to match the library where the daemon is located and type the name of the daemon. For example:
Your agent may send a coldStart trap to inform the IBM i that the daemon is running.
Still have questions? We can help. Submit a case to Technical Support.