SNMPTT GUI
A web based database driven SNMP trap monitor for SNMPTT
and Net-SNMP
Screenshots
Current status
The software works well on Windows and should possibly run on Linux as well even if this
has not yet been tested.
History
Version |
Date |
Description |
0.2 |
031205 |
Added support for colored warninglevels and a few bug-fixes |
0.2beta |
030528 |
Bug fix to solve problem with hardcoded severity levels. Added support
for snmptt 0.8 trapoid field |
0.1 |
030409 |
Initial release |
System requirements
- Net-SNMP snmptrapd (version as defined by snmptt) preferably 5.0.8 with
patches 722075 and 715603 added or 5.0.9++
- SNMPTT v0.4+, preferably 0.8 in log to database mode
- Perl v5.6.1 or 5.8.0
- Perl modules:
Download
The latest version can be downloaded from sourceforge
Upgrading
0.1 to 0.2
- Create a new text field called trapoid in the snmptt table
- Delete all scripts and replace them with new versions from the scripts directory
Installation
- Unpack the files to a directory of your choice
- Add a virtual directory on your web server pointing to the directory of
your files
- Make sure read and scripting access is allowed
- Make sure that perl is associated with the .plx extention (this is done
by the Activestate installation program on Windows)
Configuration
- Create the database or use the provided sample Microsoft Access database
- If you are using RMON you might consider to edit the provided sample rmonMap.txt
and put it in the same directory as the scripts. This way you will get nicer
looking event messages. It replaces the OID of the RMON check with a text
string. With snmptt 0.8++ this can also preferably be done using the REGEX
trapd.conf parameter
- If you want to change colors or fonts please edit the provided .css stylesheets
- Change behaviour of the application using alarms.ini
- Datasource name
- Automatically submit changes to filters or not
- Default number of rows per page
- Delete or archive records
- Show LOGONLY records or not
- Show archived records or not
- Log changes made to records or not
Database setup
A sample Microsoft Access database is provided which includes all necessary
fields. To use it please create a ODBC datasource pointing to it and edit the
alarms.ini file to reflect the ODBC datasource name.
If you prefer another database manager you can create a database according
to the snmptt instructions. In addition to this you should create a table called
log with the following script:
USE snmptt;
DROP TABLE log;;
CREATE TABLE log (
id MEDIUMINT NOT NULL AUTO_INCREMENT,
logtime VARCHAR(50),
username VARCHAR(50),
severity_old VARCHAR(50),
severity_new VARCHAR(50),
category_old VARCHAR(50),
category_new VARCHAR(50),
comment_old VARCHAR(50),
comment_new VARCHAR(50),
description_old VARCHAR(50),
description_new VARCHAR(50),
acknowledge_old VARCHAR(50),
acknowledge_new VARCHAR(50),
PRIMARY KEY(id));
You also need to create a auto-incrementing id field in the snmptt table, using
a script similar to this:
USE snmptt;
ALTER TABLE snmptt
ADD COLUMN id MEDIUMINT NOT NULL AUTO_INCREMENT,
ADD INDEX (id),
ADD PRIMARY KEY (id) FIRST;
Usage
Connect a browser to the webservers virtual directory and most functions should
be pretty self explainatory. A few features worth mentioning is:
- You can invert a filter by clicking on the columns heading text (description)
- You can click on an alarm to see its details and change some of its properties,
here is also where you delete or archive a single alarm
- In the alarm list the information icon to the right turns green when a description
has been entered, if you rest the mouse cursor over the symbol you will see
the description
- Freetext search searches the severity, category, time and source in addition
to the message text itself
- If you select filtering on severity all alarms in that severity class and
more critical are shown if standard severities are used, i.e Normal, Warning,
Minor, Major, Critical. Other "home-made" severities can be used
but filtering on them will only show chosen severity, not more critical.
- When changing between delete and archive in the alarms.ini file the buttons
in the GUI changes accordingly
Future
- Provide support for editing and viewing trapd.conf and ini files used by
snmptt and snmptt-gui
- Possibility to suppress repetitive alarms and up/down flaps, i.e. simple
event correlation
- Possibility to show a events description as defined in the trapd.conf SDESC/EDESC
field on the details view for an alarm
- Test and make it run on Linux
- Set username field to some value when changes are made and logging is enabled
Feedback
Please send feedback to roger.lindholm@modul1.se or even better use sourceforge.