[mrtg] IfName and MPLS interfaces

McDonald, Dan Dan.McDonald at austinenergy.com
Wed Jun 12 00:13:53 CEST 2013

Ok, so it’s already been fixed upstream....  I’m running 2.16.0, so I’ll see
about testing a newer version and using the —ifref=”name,ip’ syntax.

I believe type 166 are currently ignored as is, so no worries there.  166
counters are only interesting if you are running traffic engineering tunnels
and your device supports type 150 interfaces as well.


On 6/11/13 4:55 PM, "Steve Shipway" <s.shipway at auckland.ac.nz> wrote:

> You could just add --if-filter=’$if_type!=166’ to the cfgmaker command line,
> this will cause cfgmaker to ignore type 166 interfaces (though you’ll need to
> also use --ifref=’name,nr’ to make it fall back to using the interface number
> for the unique identifier since name is not unique).
> The ifref and ifdesc options of cfgmaker (after MRTG 2.16.something) allow
> multiple option to be specified in comma-separated form as alternative options
> if the first one is nonunique (My patch! My patch!)
> Or is the problem that you want one graph from the type 6 and one form the
> type 166?  In this case, you might be able to achieve it with an interface
> template  that tests the iftype and uses the default for type 6 but a
> different setup for the type 166.
> Steve
> Steve Shipway
> ITS Unix Services Design Lead
> University of Auckland, New Zealand
> Floor 1, 58 Symonds Street, Auckland
> Phone: +64 (0)9 3737599 ext 86487
> DDI: +64 (0)9 923 6487
> Mobile: +64 (0)21 753 189
> Email: s.shipway at auckland.ac.nz <mailto:s.shipway at auckland.ac.nz>
> P Please consider the environment before printing this e-mail : 打印本邮件,将减少一棵树存
> 活的机会
> From: mrtg-bounces+s.shipway=auckland.ac.nz at lists.oetiker.ch
> [mailto:mrtg-bounces+s.shipway=auckland.ac.nz at lists.oetiker.ch] On Behalf Of
> Daniel McDonald
> Sent: Wednesday, 12 June 2013 9:42 a.m.
> To: mrtg
> Subject: [mrtg] IfName and MPLS interfaces
> In general, we use ifName to identify interfaces monitored by mrtg.  However,
> on MPLS PE or P routers, there are two instances with the same ifName – one
> with ifType 6 for the physical characteristics, and one with ifType 166 for
> the MPLS counters.  Without a lot of hacking to ignore ifType 166 interfaces,
> I think I’ll need to come up with another way to identify those interfaces.
> Cfgmaker doesn’t appear to have any sort of fallback to change ifref if the
> criteria specified by —ifref is unavailable.  I tried a bunch of ways to work
> around it, but short of creating a new configuration option, it’s pretty
> insistent on not allowing it.
> Would anyone find that a useful option for cfgmaker?  Perhaps a name like
> —ifref2?  I imagine for consistency I would also need --ifdesc2....

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/mrtg/attachments/20130611/e6c2fa72/attachment-0001.htm 

More information about the mrtg mailing list