kjartan.malde(a)uis.no wrote:
> The powersupply on my Nav died, and since I got it back up I get these
> messeges every minute. Hope anyone can help me. The messages are coming
> from a one of the cards on a Cat6509. I running Nav 3.0 on CentOS.
>
It seems like the configuration is wrong. Cricket is trying to query an
OID that does not exist, in this case the ifInErrors-counter on the
various ifindexes seen in the mail.
>
> Error and the lines leading up to it:
> [28-Dec-2005 09:12:07 ] Retrieved data for 9_15 (225):
> 166758758,116225181,0,0,1572947,1109513
> [28-Dec-2005 09:12:07 ] Retrieved data for 9_16 (226):
> 10068,558308,0,0,16,8370
> [28-Dec-2005 09:12:07 ] Retrieved data for 9_17 (227):
> 571765657,1224452921,0,0,3818864,4488386
> [28-Dec-2005 09:12:07 ] Retrieved data for 9_18 (228):
> 101553,744762,0,0,589,6513
> [28-Dec-2005 09:12:07*] Received SNMP response with error code noSuchName.
> OID: 1.3.6.1.2.1.2.2.1.14.229
>
<snip>
My guess is that the information in the database was not correct during
the last creation of the config (there is one every night), and it
should disappear as soon as the database comes up to date. Is the
problem still there?
--
John Magne Bredal
NTNU, ITEA - Nettgruppa
"Just because you're paranoid, don't mean they're not after you."
>From john.m.bredal at ntnu.no Tue Jan 3 10:24:05 2006
From: john.m.bredal at ntnu.no (John Magne Bredal)
Date: Tue Jan 3 10:23:14 2006
Subject: [Nav-users] weird problem
In-Reply-To: <200512271957.25492.woj(a)tstd.pl>
References: <200512271921.22867.woj(a)tstd.pl> <200512271949.35618.woj(a)tstd.pl>
<200512271957.25492.woj(a)tstd.pl>
Message-ID: <43BA42B5.6040707(a)ntnu.no>
Wojciech Kozicki wrote:
<snip>
> btw. What should I do with something like this (Nav keeps sending it to my by
> email):
>
> [27-Dec-2005 18:40:03 ] Retrieved data for x.x.1.12 ():
> 18,17,19552316,185184868,904658749,19,29
> [27-Dec-2005 18:40:03*] Cannot
> update /usr/local/nav/cricket/cricket-config/../cricket-data//routers/x.x.1.12.rrd:
> expected 4 data source readings (got 7) from
> N:18:17:19552316:185184868:904658749:19:29:...
>
> x.x.1.12 is 7513 cisco router.
>
Quoting one of my earlier mails on this list:
"
Borge Brunes wrote:
> Folks,
>
> I did an upgrade from svn 3290 to 3318, and now these messages
> are popping in:
> [08-Aug-2005 21:30:34*] Cannot update
/usr/local/nav/cricket/cricket-config/../cricket-data//switches/tf4292-sw.infra.uit.no.rrd:
expected 5 data source readings (got 4) from N:0:1:40827872:56543441:...
>
This problem is very common. RRDTool, which Cricket uses to store data,
uses rrd-files to store data. These files, once created, does only
accept a certain number of data-sets. If you try to insert more or less
datasets than it can handle this error will occur.
The reason for this is that NAV has detected that tf4292-sw.infra.uit.no
can respond to 4 snmp values when it previously responded to 5. When it
tries to store only 4 this error occurs.
There is no easy/good fix to this. One solution is to delete the
rrd-file so that Cricket makes a new one with 4 data-sets. This is the
easiest one but will of course delete all historical data. Another
solution is to dump all old data, create the new file with 4 sets and
insert old data to the new file. This is more complicated though. My
dream is to automate this process, but at the moment there is no time.
"
--
John Magne Bredal
NTNU, ITEA - Nettgruppa
"Just because you're paranoid, don't mean they're not after you."
>From Vidar.Faltinsen at uninett.no Tue Jan 3 10:25:39 2006
From: Vidar.Faltinsen at uninett.no (Vidar Faltinsen)
Date: Tue Jan 3 10:25:45 2006
Subject: [Nav-users] NAV 3.0.0 in Debian?
In-Reply-To: <200512271252.39624.woj(a)tstd.pl>
References: <200512271252.39624.woj(a)tstd.pl>
Message-ID: <Pine.LNX.4.64.0601031016190.12104(a)tyholt-ng.uninett.no>
On Tue, 27 Dec 2005, Wojciech Kozicki wrote:
> 1. Will be NAV ported to Debian?
Our ambition is definitely to maintain an updated NAV debian package.
UNINETT and NTNU are currently planning our 2006 joint activity. There
will be a remarkably increase in activity compared to the relatively
slow 2005.
The primary OS for UNINETT is debian (our so-called samson3 platform).
We will make sure the dedian package is maintained and up to date.
The current status is that a 3.0 package is in the making, final
testing needs to be done. I cannot commit a date for this, as of now,
but we are definitely addressing this and other pressing NAV issues.
Hang in there.
- Vidar
>From woj at tstd.pl Tue Jan 3 10:26:54 2006
From: woj at tstd.pl (Wojciech Kozicki)
Date: Tue Jan 3 10:27:09 2006
Subject: [Nav-users] Cricket error
In-Reply-To: <43BA40F0.1010406(a)ntnu.no>
References: <OF63248337.796A72F9-ONC12570E5.003234BD-C12570E5.003740CC(a)uis.no>
<43BA40F0.1010406(a)ntnu.no>
Message-ID: <200601031026.55728.woj(a)tstd.pl>
On Tuesday 03 January 2006 10:16, John Magne Bredal wrote:
> kjartan.malde(a)uis.no wrote:
> > The powersupply on my Nav died, and since I got it back up I get these
> > messeges every minute. Hope anyone can help me. The messages are coming
> > from a one of the cards on a Cat6509. I running Nav 3.0 on CentOS.
>
> It seems like the configuration is wrong. Cricket is trying to query an
> OID that does not exist, in this case the ifInErrors-counter on the
> various ifindexes seen in the mail.
>
[...]
I have some additional question, is there way to put some user-specific OIDs
to NAV-Cricket?
For example - I have cisco catalyst 2900 + ATM module, NAV is not recognizing
it correctly, can I put somewhere OIDs to have statistics generated?
regards
--
Woj
>From woj at tstd.pl Tue Jan 3 10:33:55 2006
From: woj at tstd.pl (Wojciech Kozicki)
Date: Tue Jan 3 10:34:09 2006
Subject: [Nav-users] NAV 3.0.0 in Debian?
In-Reply-To: <Pine.LNX.4.64.0601031016190.12104(a)tyholt-ng.uninett.no>
References: <200512271252.39624.woj(a)tstd.pl>
<Pine.LNX.4.64.0601031016190.12104(a)tyholt-ng.uninett.no>
Message-ID: <200601031033.55815.woj(a)tstd.pl>
On Tuesday 03 January 2006 10:25, Vidar Faltinsen wrote:
> On Tue, 27 Dec 2005, Wojciech Kozicki wrote:
> > 1. Will be NAV ported to Debian?
>
> Our ambition is definitely to maintain an updated NAV debian package.
> UNINETT and NTNU are currently planning our 2006 joint activity. There
> will be a remarkably increase in activity compared to the relatively
> slow 2005.
It is really great to hear it! Nav is really good piece of software, but its
evolution is quite slow.
> The primary OS for UNINETT is debian (our so-called samson3 platform).
> We will make sure the dedian package is maintained and up to date.
> The current status is that a 3.0 package is in the making, final
> testing needs to be done. I cannot commit a date for this, as of now,
> but we are definitely addressing this and other pressing NAV issues.
>
nice...
best regards
--
Woj