We answer the most common questions about Trap Console here:
Are there any built-in accounts in Trap Console ?
Trap Console comes pre-configured with two accounts:
NOTES:
How can I change my password ?
Trap Console displays the result of the operation, with the possible error message, or "OK" if the password has been changed.
Can I start Trap Console on a port, other than the default 6610 ?
Yes! Trap Console's Web server listens on the TCP port 6610 by default. It is possible to start Trap Console on other port. Modify the command line arguments and add the parameter "-p <port number>":
java -cp tc.jar Main -p 80
The command line above will start Trap Console and let it listen on the default HTTP port 80.
Note: You must restart Trap Console for this change to take effect.
Can I start Trap Console to listen on a port, other than the default 162 ?
Yes! Trap Console listens for SNMP traps on the default UDP/TCP trap port 162. It is possible to let Trap Console listen for SNMP traps on another port.
From the main menu, select Runtime and choose the tab for the appropriate trap receiver. Enter new port number in the Receiver Port edit line and click Set. Receiver will restart if already running. No application restart is needed.
How can Trap Console cooperate with a syslog daemon?
Trap Console action "Send syslog message" allows to forward selected trap information to a remote syslog server. Define outgoing syslog message parameters, specify remote syslog server and add the action to an existing or new trap rule.
Trap Console itself can act like a syslog server. Syslog message reception is initially disabled. Go to the Runtime/Syslog UDP(TCP) Receiver page, select the port number to bind, click Set and Start Receiver. Trap Console will start converting received syslog messages into traps, processing them the same way as regular SNMP originated traps. Trap Console syslog converter uses included MIB (CSCARE-SYSLOG-MIB) to build trap PDU containing variables with syslog message attributes as their values.
To receive any syslog message, setup forwarding at your syslog daemon or any other source of syslog messages to a remote syslog server. In this case specify Trap Console host and syslog receiver port as the destination. Trap Console supports BSD syslog protocol (RFC 3164). Include csSyslogTrap in a rule to match received syslog messages (converted into traps). It is defined in CSCARE-SYSLOG-MIB under csSyslogEnterprise.
Linux stock syslog daemon syslogd has the facility to receive messages from the network, using an internet domain socket. Usually it is disabled initially, enable it using "-r" command line option. Inspect syslogd service script for a method how to specify additional options (in /etc/init.d/syslog). For example, RedHat linux script reads /etc/sysconfig/syslog and uses SYSLOGD_OPTIONS variable as the syslogd command line.
Syslogd can forward received messages to a remote server, including Trap Console with syslog reception activated. Edit its configuration file /etc/syslog.conf and add an entry with an action part containing a host name prepended with a "@"
#forward ALL messages to a remote host *.* @hostnameor more specifically
#forward all kernel messages to a remote host kern.* @hostname
Syslog-ng is a common replacement for syslogd. Remote syslog reception is active by default. Configuration file /etc/syslog-ng.conf contains source definition
source net { udp (); tcp (); };
Forwarding to a remote host is enabled by destination definition:
destination trapconsole_udp { udp("tchost" port(1514)); };
destination trapconsole_tcp { tcp("tchost" port(514)); };
#forward local user messages to trap console host
log { source(sys); filter(f_user); destination(trapconsole_udp); };
How is Trap Console licensed ?
The primary task of Trap Console is to receive SNMP traps being sent to Trap Console from some SNMP agents residing in your network. Thus, Trap Console is licensed according to the maximum count of different SNMP agents it can receive traps from.
For example: If you want to handle SNMP traps from 10 different devices in your network (for instance 3 servers, 5 switching hubs and 2 print servers), you need 10 Trap Console licenses.
Trap Console logs dynamically the first 10 different IP addresses. All traps received from different IP addresses subsequently are indicated as License Overflow.
What is the Trap Console license key?
Trap Console licenses are being distributed in the form of license keys. License key is a string holding encoded serial number and a specific number of Trap Console licenses. You can combine more license keys in Trap Console. It is also perfectly possible to add new license keys at any time there is a need to extend capabilities of Trap Console without stopping Trap Console operations.
You can enter license keys into Trap Console after logging in with your Web browser, see the next paragraph.
How can I add a new license key to Trap Console ?
The Trap Console license key can be entered in the Web browser as follows:
The new license key is added to the Registered Serial Keys list. There you can find serial number keys and the number of licenses of each entered license key. In addition, you can also see the total number of your Trap Console licenses.
Note: The above described license key manager is available only in the commercial version of Trap Console.
How are traps over the license handled ?
Traps over the license were just logged into the application log file and discarded in Trap Console version less than 1.3. This caused problems when a new SNMP agent started to send traps to Trap Console. Its traps were discarded unless you have added new licenses. In such case you could not control this SNMP agent by means of Trap Console.
Starting from the version 1.3 such traps are handled as the others under the license. In addition, Trap Console executes several notification procedures to warn the administrator that the license is exceeded.
Trap Console provides following notification procedures:
Trap Console can be stopped as follows: