<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Bericht</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1597" name=GENERATOR></HEAD>
<BODY text=#000099 bgColor=#ffffff>
<DIV><SPAN class=595464707-03092007><FONT color=#0000ff size=2>Nothing to be
amazed of:</FONT></SPAN></DIV>
<DIV><SPAN class=595464707-03092007><FONT color=#0000ff size=2>According to the
SNMP definitions (RFC 1155) the instances have to be unique and must be
accompanied by a description. </FONT></SPAN></DIV>
<DIV><SPAN class=595464707-03092007><FONT color=#0000ff size=2>They also have to
be flexible to appear and disapear (like the statistics for a specific
user in a OS, the definition of a new sub-interface or the statistics for a
specific vpn tunnel etc.) </FONT></SPAN></DIV>
<DIV><SPAN class=595464707-03092007><FONT color=#0000ff size=2>
<DIV><SPAN class=595464707-03092007><FONT color=#0000ff size=2>Nothing is said
about the index number staying the same all the time. </FONT></SPAN></DIV>
<DIV><SPAN class=595464707-03092007></SPAN></FONT></SPAN><SPAN
class=595464707-03092007><FONT color=#0000ff size=2>Several vendors (Cisco,
Microsoft) rebuild their indexes when starting the SNMP process. So the
indexnumber can change after a reboot, especially after a some reconfiguration
after the previous boot.</FONT></SPAN></DIV>
<DIV><SPAN class=595464707-03092007><FONT color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=595464707-03092007><FONT color=#0000ff size=2>To avoid problems
with broken graphs MRTG offers some methods to identify the right oid. See <A
href="http://oss.oetiker.ch/mrtg/doc/mrtg-reference.en.html#IInterface_by_IP">http://oss.oetiker.ch/mrtg/doc/mrtg-reference.en.html#IInterface_by_IP</A> for
details.</FONT></SPAN></DIV>
<DIV><SPAN class=595464707-03092007><FONT color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=595464707-03092007><FONT color=#0000ff
size=2>HTH,</FONT></SPAN></DIV>
<DIV><SPAN class=595464707-03092007><FONT color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=595464707-03092007><FONT color=#0000ff
size=2>Jan.</FONT></SPAN></DIV></DIV>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=nl dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B>
mrtg-bounces@lists.oetiker.ch [mailto:mrtg-bounces@lists.oetiker.ch] <B>On
Behalf Of </B>gaurav<BR><B>Sent:</B> Friday, August 31, 2007 9:11
PM<BR><B>To:</B> mrtg@lists.oetiker.ch<BR><B>Subject:</B> [mrtg] OIDs
changing.<BR><BR></FONT></DIV><FONT size=-1><FONT face=Verdana>Dear
all,<BR><BR>Recently I was amazed to see few things in the devices I was using
MRTG for.<BR><BR>First, I have two cisco uBR 7200 with same IOS version and
same model but the OIDs in them for same datas to are to be retrieved are
different in the leaf OIDs whereas the branch OID is the same.<BR><BR>i mean
if 1.3.2.1.2.1.2.3.1.2.1.2 was for one than </FONT></FONT><FONT size=-1><FONT
face=Verdana>1.3.2.1.2.1.2.3.1.2.1.9 was for the other..<BR><BR>Second thing
is one of the device got automatically rebooted because of some power failure
lately, and i was unable to see MRTG graphs for few of the datas polled. Upon
further diagnose i found that the leaf OIDs have increased with two <BR><BR>i
mean if </FONT></FONT><FONT size=-1><FONT face=Verdana>1.3.2.1.2.1.2.3.1.2.1.2
was the OID that was polled than after the reboot it wasnt existing and
</FONT></FONT><FONT size=-1><FONT face=Verdana>1.3.2.1.2.1.2.3.1.2.1.4 was the
one that was providing the necessary values.<BR><BR>Has any one came across
this type of situations before...please do share..<BR><BR>Does the OIDs get
changed so abnormally or is it because of some faults in the
device.<BR><BR>TIA,<BR><BR>Gaurav<BR></BLOCKQUOTE></FONT></FONT></BODY></HTML>
<table><tr><td bgcolor=#ffffff><font color=#000000>_________________________________________________________<br>
<br>
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten.<br>
_________________________________________________________<br>
<br>
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The state accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.<br>
_________________________________________________________<br>
</font></td></tr></table>