Here is a much better set of scripts and templates for collecting Cisco interface errors via a Perl Net::Telnet script.
This script was written because after going around and around with the Cisco TAC, I arrived at the conclusion that I could not get all the (exact) information found on the command line (when you do a show interface) in the MIBs. I asked Cisco and they confirmed this.
My manager wanted to be alerted every time a 'frame circuit' took errors (we have like 80+ remote sites on frame) - So, I wrote this script to collect the data, and created a 'thold' template to alert me via email. It seems to be working fine so far.
It should work on most cisco IOS based gear. It basically telnets to the device, does a show interface {interface} and parses the output for the 5 things I am collecting: input_errors; crc_errors; frame_errors; overrun_errors; ignored_errors.
This is a script query, which is nice because it uses cacti's cool templating system.
The first version I put up would only handle one interface per device, but this one will handle many. I also corrected a lot of bugs that increased performance and should have eliminated the errors in the cacti error log. I also removed the need for all the Perl modules, besides one: Net::Telnet. I took much of the online help out, but if you run the script with no options from the command line, you will get usage directions.
To install:
1.) Make sure you have Perl and the Net::Telnet module.
2.) Put the script in your <path to cacti>/scripts directory and edit the $path_to_cacti variable to be where your cacti install lives.
3.) Put the cisco_IntErr.xml file in your <path to cacti>/resources/script_queries directory and edit your telnet user name and password. Also change the path to Perl to be where you Perl lives. Sorry, but still no tables in cacti for user names and passwords for Telnet. Therefor you will have to have a unified user and pass for all the devices you want to colllect statistics on. Also, if you have a different prompt (other than what is expected '#') change it in the Open_Telnet subroutine in the script - or change it on your device to be '#'.
4.) Make sure both above files are read/executable by the user whom would be running them (cactiuser/www/etc..).
5.) Import the templates that are included (if they don't work, sorry, I tried).
6.) create directory called script_logs, that is read/write/executable to the user running the scripts, in the <path to cacti>/scripts directory. This is for all the filles that will be created in order for the script to get the 'delta' values for each error it collects on.
7.) Go create graphs!
Hope this works out for someone else. If nothing else, it was a good practice in creating script queries in cacti!
This script was written and tested in UNIX, so if it works in Windows, great! If not, then I don't know what to tell you - I have no Windows box to try it on.
If you have trouble feel free to post back and I will try to help, but no guaranties.. Also, feel free to take the code and do whatever you want with it, just don't blame me for breaking stuff
. Have fun.
