<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1264" name=GENERATOR></HEAD>
<BODY style="MARGIN-TOP: 2px; FONT: 10pt Arial; MARGIN-LEFT: 2px">
<DIV>Thanks to Thornton Prime for insights into SNMP security and reindexing
issues. One further clarification about reindexing though if you don't
mind.</DIV>
<DIV> </DIV>
<DIV>It seems that you do agree that the SNMP table for a device can reindex
with a reboot or change to certain system configuration (hard drives etc).
This would force me to reconfigure the Services.cfg file of Nagios to conform to
that right? This seems like a big task for a changing environment with
lots of servers (400+) like mine. My real question is wouldn't most of
this be avoided if I use the Nagios agents such as Nsclient, MRTGEXT.NLM and
those for UNIX which use logical names for these same system objects (disks,
RAM, CPU)?</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>> My original quesion about SNMP tables reindexing ></DIV>
<DIV><BR>> 2) Object IDs can reindex when a server reboots, resulting in
having to <BR>> reconfigure Nagios (which also happens when new devices are
added)<BR></DIV>
<DIV>> Thornton's answer below ></DIV>
<DIV><BR>>This will normally only happen within the context of a SNMP table,
and <BR>>the tables are designed to make it easy to find a piece of
information <BR>>even when a row has been added, removed or re-ordered
because the system <BR>>has been reconfigured. For example, hrStorageTable is
no harder or <BR>>easier to parse than the output of "df", and you run the
same level of <BR>>risk from re-ordering if you added or removed volumes, or
changed your <BR>>mount order. ifTable is much easier to parse than the
output of ifconfig.<BR><BR>Thanks again!</DIV>
<DIV> </DIV>
<DIV>Larry C<BR><BR><BR></DIV></BODY></HTML>
<P>------------------------------------------------------------------------------<br>
This message may contain confidential information, and is intended only for the use of the individual(s) to whom it is addressed.<br>
<br>
<br>
==============================================================================<br>
</P>