<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<HEAD>
<TITLE>NMIS Documentation</TITLE>
<META HTTP-EQUIV="Content-Language" CONTENT="en-us">
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1252">
<STYLE TYPE="text/css">
TD {
border-width : 1px;
border-style : solid;
border-color : #aaaaaa;
font-family : Arial;
}
TABLE {
color : Black;
background : White;
border-width : 1px;
border-style : solid;
border-color : #aaaaaa;
width : 100%;
font-family : Arial;
}
P {
font-family : Arial;
}
BODY {
font-style : normal;
font-variant : normal;
font-size : small;
color : white;
background-color : #190032;
text-decoration : none;
font-family : Arial;
}
A:active {
color : red;
background-color : White;
text-decoration : none
}
A:link {
color : blue;
background-color : White;
text-decoration : underline
}
A:visited {
color : blue;
background-color : White;
text-decoration : underline
}
A:hover {
color : red;
background-color : White;
text-decoration : underline
}
.heading {
font-style : normal;
font-weight : bold;
font-size : x-large;
font-family : "Arial Rounded MT Bold";
background-color : #190032;
color : White;
}
#rrdtool {
position : absolute;
left : 200px;
top : 150px;
}
</STYLE>
</HEAD>
<BODY>
<div class="heading">NMIS To Do</div>
<table>
<tr>
<td width="33%">Last updated 21 June 2001</td>
<td width="33%">
<p align="center"><a href="http://www.sins.com.au/nmis/nmis-todo.html">Online
Version</a></p>
</td>
<td width="33%">
<p align="center"><a href="http://www.sins.com.au/nmis/">NMIS Home Page</a></p>
</td>
</tr>
<tr>
<td width="100%" colspan="3"><b><a name="To Do"><font size="2">To Do</font></a></b><ul>
<li><font size="2">Write an installation script.</font></li>
<li><font size="2">Make polling engine multi-threaded.</font></li>
<li><font size="2">Enhance documentation.</font></li>
<li><font size="2">Use NET-SNMP as the SNMP Package</font></li>
</ul>
</td>
</tr>
<tr>
<td width="100%" colspan="3">
<b><font size="2">Health</font></b>
<p><font size="2">Make health include metrics for interface utilisation, could be done by
doing utilisation summarystats for each interface where each interface
utilisation was weighted out of 100 where 50 utilised would equal 50, etc,
which then contributed to a total number divided by the number of interfaces
and then weighted into the total health metric.</font>
</td>
</tr>
<tr>
<td width="100%" colspan="3">
<font SIZE="2"><b>summarystats </b></font>
<p><font SIZE="2">I would actually like to rewrite the summary stats routine to
return a "summarystats hash".</font></p>
</td>
</tr>
<tr>
<td width="100%" colspan="3">
<font size="2"><b>Interface Stats</b></font>
<p><font size="2">For each interface which supports it collect in/out
frames, broadcast, unicast. This would allow determination of average
packet size on link and on network. It would also allow thresholds to
be set for percentage of broadcast traffic on network.</font>
<p><font size="2">More Notes:</font>
<p><font size="2">An excellent idea, this would be very good information, this is already <br>
on the todo list but there are few "dependancies":<br>
<br>
1. The poller should be enhanced first to be multi-threaded which will <br>
enable improved performance for SNMP and increase the number of mibs <br>
polled per second per node. I think this is the next major improvement <br>
required. That along with making NMIS a daemon which go hand in hand.<br>
<br>
2. I would also like to support packet stats, ie pkt in and out, as well <br>
as unicast and non unicast. There are different error stats per <br>
interface type.<br>
<br>
3. Not all interfaces support full if-mib stats, ie frame relay <br>
subinterfaces on Cisco devices only support ifInOctets and ifOutOctets, <br>
all other stats are in the Frame Relay mibs. This is also true for <br>
other interface types like ATM. So the solution is to keep the extended <br>
stats in a different RRD for each interface, I would envisage that there <br>
would be the current interface, extra bit (pkts, errors, etc), specific <br>
(frame-relay, ATM, etherlike, etc), so one interface may have 1 <br>
interface RRD while another my have 3. This could be implemented in <br>
phases too I suppose.<br>
<br>
4. Yes putting error rates in the node health metric would be excellent.<br>
<br>
5. Other metrics could be calculated for nodes and the network:<br>
* like per interface/link average packet size;<br>
* entire network average packet size;<br>
* error rates per interface/network (this equates to the much heard <br>
never seen "accuracy" metric);<br>
* lots of others that we might think of later.<br>
<br>
6. Thresholding on errors should be done (easy).<br>
</font>
</td>
</tr>
<tr>
<td width="100%" colspan="3">
<font size="2"><b>Create RRD</b></font>
<p> <font size="2"> I had been thinking about making this config options and putting the formulas in the code.</font>
</td>
</tr>
<tr>
<td width="100%" colspan="3">
<b><font size="2">NMIS Command Line</font></b>
<p><font size="2">simple script to provide status of nodes and basic info
like summary.pl
but commandline oriented.</font>
</td>
</tr>
<tr>
<td width="100%" colspan="3">
<b>
<font size="2">
Thresholds</font></b>
<p><font size="2">Put the threshold code seperate for just using in nmis.pl</font>
</td>
</tr>
<tr>
<td width="100%" colspan="3">
<b>
<font size="2">
SENDMAIL</font></b>
<p><font size="2">Perl based sendmail for better mail control.</font>
</td>
</tr>
</table>
</BODY>
</HTML>
distrib
>
Mandriva
>
2010.0
>
i586
>
media
>
contrib-release
>
by-pkgid
>
14e7762649c6c85d29d87b731da4bd26
>
files
>
44
