Richard A Steenbergen writes:
> Any software which relies on static ifIndex mappings between polling
> cycles is fundamentally flawed, period, end of discussion. There is
> absolutely no excuse for this, it is beyond trivial to map data by
> ifDescr, and the SNMP spec even tells you that ifIndex is
I'm late jumping into this conversation, but are you using
virtual-chassis by chance?
Did the order of the individual units change when you upgraded?
Chris Adams wrote:
> Once upon a time, Tore Anderson said:
>
>> * Chris Adams
>>
>>> Never used Cisco I guess?
>>>
>> I have. As
Once upon a time, Tore Anderson said:
> * Chris Adams
> > Never used Cisco I guess?
>
> I have. As Steinar haug has already pointed out, IOS supports keeping
> ifIndexes static. Fortunately someone had the good sense to enable that
> feature, so they've never caused me any problems.
I guess I
* Chris Adams
> Never used Cisco I guess?
I have. As Steinar haug has already pointed out, IOS supports keeping
ifIndexes static. Fortunately someone had the good sense to enable that
feature, so they've never caused me any problems.
--
Tore Anderson
Redpill Linpro AS - http://www.redpill-lin
Once upon a time, Tore Anderson said:
> Speaking of Extreme, by the way... Juniper is the first vendor whose
> gear has changed ifIndexes on me, ever.
Never used Cisco I guess?
--
Chris Adams
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - th
> Even though current JUNOS behaviour can be considered spec-compliant I
> would still like to see the ifIndexes being kept static - it would be a
> great feature enhanchement for those of us that (unwittingly) chose SNMP
> software that doesn't handle ifIndexes changing. As I pointed out in my
>
* Richard A Steenbergen
> Normally I'm the one yelling at Juniper when they do something stupid
> and break things for no reason, but honestly...
I admit that the tone in my first e-mail to this thread was over the
line, and for that I do apologise. I hope nobody got offended.
It was extremely
On Fri, Feb 13, 2009 at 08:51:23AM +0100, Tore Anderson wrote:
> * Malte von dem Hagen
>
> > we filed that as a PR for the EX-Series we updated from 9.1 to 9.2 a
> > while ago, and got the response from JTAC that this is expected behaviour.
>
> Unbelievable. This provokes me! I really hope that
Regards,
Masood
-Original Message-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Patrik Olsson
Sent: Friday, February 13, 2009 5:19 PM
To: Chris Adams; juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] SNMP interface index change afte
Dear all,
I do have the same problem. I am using M320, M120.
I upgrade from 9.1R2.10 to 9.3R1.7, and my flow analysis can't get the
right result because one of my analysis depends on the interface snmp
index.
Hope Juniper guy can response and get it fixed.
cheers,
Ethern
On Fri, Feb 13, 2009 at
Once upon a time, Tore Anderson said:
> It has been pointed out that not even MRTG, which I assume is the most
> used traffic graphing suite, handles ifIndex changing (by default).
> Keying off something else, like ifName, adds unnecessary overhead on the
> polling station.
I switched from MRTG t
Once upon a time, Malte von dem Hagen said:
> Am 13.02.2009 13:15 Uhr, Chris Adams schrieb:
> > Um, how about using modern software that doesn't assume static
> > interface
> > IDs? Interface IDs are never guaranteed to be static, so proper
> > SNMP
> > software should handle them changing.
>
> w
Hej,
Am 13.02.2009 13:15 Uhr, Chris Adams schrieb:
> Um, how about using modern software that doesn't assume static interface
> IDs? Interface IDs are never guaranteed to be static, so proper SNMP
> software should handle them changing.
what, if not ifIndex, should be a reasonable index for Inte
I use Cacti (it is free), have not seen this issue (yet). I think I will
poke around in it a bit, but I am with Chris and Tom in the spirit.
Cheers
Patrik
BEGIN:VCARD
VERSION:2.1
N:Olsson;Patrik
FN:Patrik Olsson
ORG:;EMEA Tech Dev
TEL;WORK;VOICE:+46-733927834
TEL;CELL;VOICE:+46-733927834
ADR;WORK
Once upon a time, Tore Anderson said:
> Hey, Juniper, if you're reading this: Do you think that I ENJOY wasting
> hours of my to clear up the mess this «feature» has caused, you're sadly
> mistaken! Not only is it fscking annoying - I use the data in my graphs
> for accounting too (and I think t
Hi Tom,
* Tom Storey
> If using MRTG, and particularly if you use cfgmaker, you could always
> specify the "-ifref=descr" option.
I'm using Munin (http://munin.sf.net/). Unfortunately, its SNMP
collectors relies on the ifIndex to remain constant, so I am out of luck.
I appreciate you taking th
On 13/02/2009, at 6:21 PM, Tore Anderson wrote:
Hey, Juniper, if you're reading this: Do you think that I ENJOY
wasting
hours of my to clear up the mess this «feature» has caused,
If using MRTG, and particularly if you use cfgmaker, you could always
specify the "-ifref=descr" option.
* Patrik Olsson
> Did you see this in your MX240s aswell?
Yes. I'll repeat myself:
> An upgrade of two of my MX 240ies today, going from 9.3R1.7 to
> 9.4R1.8, resulted in all of my graphs becoming hosed.
Regards,
--
Tore Anderson
Redpill Linpro AS - http://www.redpill-linpro.com/
Tore,
Did you see this in your MX240s aswell?
Patrik
Sean Clarke> I believe this to be fixed in 9.4R1 , it's PR 408714,
although the release notes don't mention it - perhaps it was a
"confidential" PR hence not Sean Clarke> published in the release notes
of 9.4
Sean Clarke> It was only
Hej,
Tore Anderson wrote:
It doesn't happen due to reboots, but due to JUNOS upgrades. Like I
wrote in my original e-mail, after upgrading from 9.3R1.7 to 9.4R1.8 all
of my graphs stopped working.
(The original poster reported it happened going from 9.1R1.8 to 9.2R2.15.)
The «you'll just have
Hi Patrik,
* Patrik Olsson
> I wont speak for EX, since I am not sure. But for M/MX/T/TX the SNMP
> index for interfaces (used for graphing for instance) should not change
> due to reboot. I have not seen that in my small lab at least.
>
> What JUNOS version do you see this in?
It doesn't happ
: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Tore Anderson
Sent: den 13 februari 2009 08:51
To: Malte von dem Hagen
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] SNMP interface index change after upgrade to 9.2
* Malte von dem Hagen
> we fi
* Malte von dem Hagen
> we filed that as a PR for the EX-Series we updated from 9.1 to 9.2 a
> while ago, and got the response from JTAC that this is expected behaviour.
Unbelievable. This provokes me! I really hope that the idiot(s) that
made this design desicion are no longer working at Junip
* David Ball
> Anyone else notice this? Am I incorrect in my previous assumption
> that Juniper had solved this issue of SNMP index changes across
> reboots?
They still haven't, unfortunately. An upgrade of two of my MX 240ies
today, going from 9.3R1.7 to 9.4R1.8, resulted in all of my graphs
On Monday 27 October 2008, David Ball wrote:
> I thought Juniper had sorted out their interface SNMP index
> numbering such that they would remain the same, even following a
> reboot? I've been running a simple MRTG instance to monitor some
> 10Gig core links since 8.4 with no problems.
Are you
thanks, Hangu. Unfortunately it appears as though the contents of
this file (must) have changed between 9.1R1.8 and 9.2R2.15.
Unfortuately, I'm not sure I can confirm that, as I have no more
T-640s running 9.1. I have an MX running 9.1, but its file will
certainly differ, as there are completel
David,
On Sun, 26 Oct 2008, David Ball wrote:
I thought Juniper had sorted out their interface SNMP index
numbering such that they would remain the same, even following a
reboot? I've been running a simple MRTG instance to monitor some
10Gig core links since 8.4 with no problems. I recently
Your assumption is correct, actually router maintain snmp index as below
file,
So there is no snmp index changes across reboots.
router# file show /var/db/dcd.snmp_ix
/* file-format-version: 1 */
/*
* mib2d-generated /var/db/dcd.snmp_ix
* Version: MIB2D release 9.2R1.10 built by builder on 200
I thought Juniper had sorted out their interface SNMP index
numbering such that they would remain the same, even following a
reboot? I've been running a simple MRTG instance to monitor some
10Gig core links since 8.4 with no problems. I recently upgraded from
9.1R1.8 to 9.2R2.15 on my T-Series
29 matches
Mail list logo