[mrtg] Handling device configuration changes/MRTG

Tendolkar Mohit Mohit.Tendolkar at thomson.net
Fri Dec 31 20:37:49 MET 2004


Typically folks setup MRTG to monitor network interfaces and let the
scripts chug for a long time. 

However, occasionally facility configuration changes do occur. Some such
examples are:
A) taking a device offline for servicing
B) adding/removing modules (hot-swap)
C) re-connecting a network cable

How do you guys typically handle such cases wrt MRTG? Of course, I know
the easiest way is to simply re-create the CONFIGs and re-start MRTG,
but there must be some other elegant way to do this without having to
disturb the current monitoring setup, so I thought I'd ask you guys.

Typically on a configuration change like a device restart, or
adding/removing modules, I observe that the SNMP agent has a tendency to
change its table indices (that means physical port A that was last
polled as port.1 may now appear as port.10, or something else other than
port.1). With such changes, either the monitoring starts giving
noSuchName SNMP errors (since the polled SNMP object instance does not
exist anymore), or shows incorrect information for a totally different
port (which is difficult to track!).

Do let me know...

Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive     http://www.ee.ethz.ch/~slist/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi

More information about the mrtg mailing list