[mrtg] Re: mrtg newbie question
Hunt, Chris
cjhunt at lehman.COM
Fri Dec 7 10:09:32 MET 2001
Marc,
Might I suggest that you post the FULL config to the list after of course,
you have disguised any sensitive information?
Please can you post the results of cfgmaker before and after the problem
occurs (a working cfg file and a "broken" one). That way we can see better
what is happening.
Regards,
Chris
-----Original Message-----
From: Quibell, Marc [mailto:mquibell at icn.state.ia.us]
Sent: 06 December 2001 17:59
To: 'Hunt, Chris'; 'mrtg at list.ee.ethz.ch'
Subject: RE: [mrtg] mrtg newbie question
T ran cfgmaker, and before today as well, to compare the results. The lines
cfgmaker comes up with are commented out and follows with the following
message:
"The following interface is commented out because: * has a speed of 0 which
makes no sense"
The real question is how these all of a sudden quit working and what I can
do to restore it? Thanks!
Marc
-----Original Message-----
From: Hunt, Chris [mailto:cjhunt at lehman.COM]
Sent: Thursday, December 06, 2001 10:11 AM
To: 'Quibell, Marc'; Hunt, Chris; 'mrtg at list.ee.ethz.ch'
Subject: RE: [mrtg] mrtg newbie question
Marc,
What happens if you run cfgmaker against the device before and after a
change and compare the results of the file it generates - therein may lie
the answer. This might illustrate a different IF Index for the interface and
would explain your problem.
What I'm saying is that I've never had any issues with using the default IF
index means of tracking an interface, but that I know it can change. I have
never had any trouble tracking by IP address and don't expect to either.
Instead of
Target[a.b.c.d_3]: 3:public at a.b.c.d:
I am using something more like
Target[easyname]: /w.x.y.z:public at a.b.c.d: //w.x.y.z is the IP address of
the specific interface whose current IF index is 3.
It's OK if your interface does have an IP address of course - if not then
this won't apply.
This is because the index 3 is possibly going to change on a system under
certain conditions.
Regards,
Chris
-----Original Message-----
From: Quibell, Marc [mailto:mquibell at icn.state.ia.us]
Sent: 06 December 2001 15:23
To: 'Hunt, Chris'; 'mrtg at list.ee.ethz.ch'
Subject: RE: [mrtg] mrtg newbie question
We track this particular interface by the following syntax:
Target[205.222.43.16_1]: \Physical\ port\:\ so.5.1\
Sprint-376493:community at 172.30.1.2:::::2
The error I get is:
WARNING: Could not match host:'community at 172.30.1.2:::::2' ref:'Descr'
key:'Physical port: so.5.1 Sprint-376493'
Are you saying this is not ideal? I believe we've also had problems using
the IP address. But what happened is that once we make a change to the
interface, like turning on Scrambling or something minor, there seems to be
a file pointing to the old (OID?) values and it breaks while still trying to
connect to the old values. So, is there a file or something I need to be
changing or deleting as well? What if I delete the entire interface
directory?
This description we use above for the interface has not changed, neither has
the IP address or the community. Somewhere deep in the code there are values
that are not being updated or viewed.
Thanks for your help!
Marc
-----Original Message-----
From: Hunt, Chris [mailto:cjhunt at lehman.COM]
Sent: Thursday, December 06, 2001 8:58 AM
To: 'Quibell, Marc'; 'mrtg at list.ee.ethz.ch'
Subject: RE: [mrtg] mrtg newbie question
Hi,
>From what I understand, it is possible for the interface index reference to
change when a router is changed (reloaded or whatever, cards / modules
re-inserted etc.). So tracking the unit by interface index (default
behaviour) is not a 100% reliable way to track the traffic. Although I have
not yet been bitten by this, I decided that this could be nasty and have
begun tracking interfaces by IP address. This is detailed in the MRTG
reference guide.
Regards,
Chris
-----Original Message-----
From: Quibell, Marc [mailto:mquibell at icn.state.ia.us]
Sent: 06 December 2001 14:46
To: 'mrtg at list.ee.ethz.ch'
Subject: [mrtg] mrtg newbie question
Whenever we make changes to a router interface, the graph for that interface
breaks and can no longer snmp probe the interface ("Could not match host"
error). Even if we just make unrelated changes to the interface, such as
turning off cell scrambling. A collegue here suggests that it is the changed
Identifier in what used to be a .ok file. None of the attributes for the
interface has changed: IP address, description...etc are the same. I cannot
find any OK file. PLease tell me what has happened. Thanks.
Marc
--
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
----------------------------------------------------------------------------
--
This message is intended only for the personal and confidential use of the
designated recipient(s) named above. If you are not the intended recipient
of this message you are hereby notified that any review, dissemination,
distribution or copying of this message is strictly prohibited. This
communication is for information purposes only and should not be regarded as
an offer to sell or as a solicitation of an offer to buy any financial
product, an official confirmation of any transaction, or as an official
statement of Lehman Brothers. Email transmission cannot be guaranteed to be
secure or error-free. Therefore, we do not represent that this information
is complete or accurate and it should not be relied upon as such. All
information is subject to change without notice.
----------------------------------------------------------------------------
--
This message is intended only for the personal and confidential use of the
designated recipient(s) named above. If you are not the intended recipient
of this message you are hereby notified that any review, dissemination,
distribution or copying of this message is strictly prohibited. This
communication is for information purposes only and should not be regarded as
an offer to sell or as a solicitation of an offer to buy any financial
product, an official confirmation of any transaction, or as an official
statement of Lehman Brothers. Email transmission cannot be guaranteed to be
secure or error-free. Therefore, we do not represent that this information
is complete or accurate and it should not be relied upon as such. All
information is subject to change without notice.
------------------------------------------------------------------------------
This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.
--
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
--
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