This is because the 7606 answers with 'integers' to 1.3.6.1.4.1.9.3.6.11.1.4.
With this change to initBox.py I could add this device:
162c162
< except UnicodeDecodeError, e:
except AttributeError or UnicodeDecodeError, e:
--
mvh
Morten Brekkevold
UNINETT
>From martin.roll at elementum.info Wed Nov 22 19:01:21 2006
From: martin.roll at elementum.info (Martin Roll)
Date: Wed Nov 22 19:01:30 2006
Subject: [Nav-users] Installing NAV on SLES9
In-Reply-To:
4558FA04.4010102@elementum.info
References:
4554962A.6060104@elementum.info 45583974.8060805@uninett.no
4558FA04.4010102@elementum.info
Message-ID:
45649071.6080403@elementum.info
Hello again!
I have discovered another Problem with my Installation and I hope you
can help me with it as well.
When I log in using the NAV Webinterface, everything seems fine at first.
But when I click on Toolbox --> Network Explorer I get this notice:
Error, could not connect to database!
I have no idea what the reason for that message could be as I followed
exactly the description located at
http://metanav.ntnu.no/moin.cgi/InstallingOnSLES.
When I click on Toolbox --> Edit database I get this weird stuff:
Mod_python error: "PythonHandler editdb"
Traceback (most recent call last):
File "/usr/lib/python2.3/site-packages/mod_python/apache.py", line 287, in HandlerDispatch
log=debug)
File "/usr/lib/python2.3/site-packages/mod_python/apache.py", line 457, in import_module
module = imp.load_module(mname, f, p, d)
File "/usr/local/nav/apache/webroot/editdb/editdb.py", line 29, in ?
import editTables,nav.Snmp,sys,re,copy,initBox,forgetSQL,nav.web
File "/usr/local/nav/apache/webroot/editdb/initBox.py", line 29, in ?
from nav.Snmp import Snmp,NameResolverException,TimeOutException
ImportError: cannot import name Snmp
or that:
Mod_python error: "PythonHandler editdb"
Traceback (most recent call last):
File "/usr/lib/python2.3/site-packages/mod_python/apache.py", line 287, in HandlerDispatch
log=debug)
File "/usr/lib/python2.3/site-packages/mod_python/apache.py", line 457, in import_module
module = imp.load_module(mname, f, p, d)
File "/usr/local/nav/apache/webroot/editdb/editdb.py", line 29, in ?
import editTables,nav.Snmp,sys,re,copy,initBox,forgetSQL,nav.web
File "/usr/local/nav/lib/python/nav/Snmp.py", line 24, in ?
from pysnmp.proto import v1, v2c
ImportError: No module named proto
Do you have any idea what I could have done wrong?
Thanks for helping!
Martin
>From JanEgil.Artun at sauda.kommune.no Wed Nov 22 20:39:43 2006
From: JanEgil.Artun at sauda.kommune.no (=?iso-8859-1?Q?Jan_Egil_=C5rtun?=)
Date: Wed Nov 22 20:39:49 2006
Subject: [Nav-users] NAV 3.1.1 and cricket problem
Message-ID:
6D2D4563A4B76A4EB43F7E71B511D6DB43941C@HOLMAKNUTEN.ryfylke.local
Hello
Ive installed NAV 3.1.1 on CentOS4.4 using the RHEL4 guide and it seems to work pretty good, except for a few problems. I added a few switches and a server as a test to see how things worked. Everything worked good until i added the server. When I added the server navcron started a process called Java, and this process took more and more memory until the computer running nav crashed. I removed the ip device from the database but then cricked displayed this error at the bottom of the cricket webpage:
Config tree needs to be recompiled: Referenced file /usr/local/nav/cricket/cricket-config/servers/"IPofServer"/"IPofServer"
The two questions I got then is: what is that java prosess that started the trouble and how can I prevent it from happening the next time I added a server? How do I get that Cricket error fixed?
I feel more comfortable in a windows enviroment but NAV offer some good functionality that I think could be useful in our network, so I would really like to get this working.
----
mvh
Jan Egil ?rtun
Sauda Kommune
>From roger.aas at hsh.no Thu Nov 23 11:17:31 2006
From: roger.aas at hsh.no (Roger Aas)
Date: Thu Nov 23 11:17:57 2006
Subject: [Nav-users] Updated InstallingOnRHEL4 to cover NAV 3.1.1
Message-ID:
4565753B.1080102@hsh.no
I have the last days done some much needed editing of my installation
description of NAV on CentOS and RHEL.
The highlights:
- Updated for NAV 3.1.1
- Tested on RHEL4 Update 4 and CentOS 4.4
- Added possibility for receiving syslog messages from equipment
- Added sample firewall setup
- No more vi edits, all done by cat and sed
- Made clearer what site specific information needs to be entered and where
Same link as before:
http://metanav.ntnu.no/moin.cgi/InstallingOnRHEL4
Always nice with feedback on this document, especially if you find some errors.
Best regards,
- Roger
--
Roger Aas
Stord/Haugesund University College