[mrtg] Re: Cisco interface numbers

Keith E Johnson kj at sunclipse.com
Wed Jan 16 18:07:02 MET 2002


I'm running ifindex persist on a couple of my host routers, it works pretty
good, it just tacks new interfaces to the end.

-----Original Message-----
From: Paul C. Williamson [mailto:pwilliamson at mandtbank.com]
Sent: Wednesday, January 16, 2002 6:29 AM
To: mrtg at list.ee.ethz.ch; HDeschenes at oakley.com
Subject: [mrtg] Re: Cisco interface numbers



Heath,

I don't about how good ifindex persist is.  We only use it on a few routers
that change often.  For everything else, I just use the regular interface.
You could try one of the other ones...

--ifref=nr        interface references by Interface Number (default)
 --ifref=ip                         ... by Ip Address
 --ifref=eth                        ... by Ethernet Number
 --ifref=descr                      ... by Interface Description
 --ifref=name                       ... by Interface Name
 --ifref=type                       ... by Interface Type

As for the second item...

It is very easy to move old data to new configs - if you move the .log or
.rrd 
file before you have new data.  Just rename it to what the new Target will
be called.  If I notice a problem, I usually generate a new config, compare
it 
to the existing one, adjust the data files accordingly, then replace the 
existing config with the new config.  The whole operation takes about 2
minutes. 
But, putting on my sysadmin hat, I should probably take the time to write a
script to do all that for me automatically!

Paul

>>> Heath Deschenes <HDeschenes at oakley.com> 01/15/02 11:41AM >>>
Is this (ifindex persist) the best method of keeping the interfaces from
rearranging when a new card is added/removed and the router is rebooted? and
does it use much resources? I tried using the options listed and I keep
getting errors stating that --iref=name (also tried by type, IP, and eth) is
not unique for this interface.

Also, is there a way to save data from an old config to apply it to a newly
created config after the interfaces have changed for the purpose of keeping
history information?

Thank you,
Heath

-----Original Message-----
From: Paul C. Williamson [mailto:pwilliamson at mandtbank.com] 
Sent: Tuesday, January 15, 2002 6:36 AM
To: kth at hp.is; mrtg at list.ee.ethz.ch 
Subject: [mrtg] Re: Cisco interface numbers



The command we use (on IOS 12.1(5)T), is 

ifindex persist

Here's more info:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121

t/121t5/dt5ifidx.htm

Other than that, you can reference the interfaces by something else, like
description, ip, or one of the other options in cfgmaker.

Paul
>>> "Kristjan Thordarson" <kth at hp.is> 01/15/02 09:19AM >>>
Anyone know of a way to work around the way Cisco IOS routers re-arrages
it's interface numbers when it's reloaded?
 
Regards,
Kristjan
 

--
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 


--
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




--
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