Kristian Eide wrote:
I've just looked at the code, and what should happen is that if you are logged in as a valid NAV user the buttons should appear. We have occasionally had some problems with this, however, which could be due to the version of Apache/Tomcat in use as well as the Java VM. I see that you are using Linux; have you tried this on Windows?
I'll try on other systems as soon as I get access again.
In the mean time you could connect to the navprofiles database and try something like this:
UPDATE account SET password='md5'||md5('password') WHERE login='login'
Also, please CC the nav-users list when you reply (unless you are including sensitive info you don't want archived).
UPDATE account SET password='md5'||md5('XXX') WHERE login='admin' The above command did not work. I entered it into navprofiles database as user postgres, it did not give any errors but I still can't login. (Perhaps you could reproduce the bug by creating a new admin account and trying.)
From kreide at gmail.com Fri Aug 19 19:09:43 2005
From: kreide at gmail.com (Kristian Eide) Date: Fri Aug 19 18:09:53 2005 Subject: [Nav-users] In-Reply-To: 4306009f.6176d3e4.2ca6.ffffb7d3SMTPIN_ADDED@mx.gmail.com References: b4c110fd050818161414e965df@mail.gmail.com 4306009f.6176d3e4.2ca6.ffffb7d3SMTPIN_ADDED@mx.gmail.com Message-ID: b4c110fd05081909095e0d6c61@mail.gmail.com
Kristian, thank you for your prompt responses and help. Should I be copying the list on this, or just wait until there is a possible solution? Here is the output of the OID that you asked for:
It seems my suspicion is correct:
.1.3.6.1.2.1.2.2.1.10.3 = Counter32: 0 .1.3.6.1.2.1.2.2.1.10.20 = Counter32: 0
.1.3.6.1.2.1.2.2.1.5.3 = Gauge32: 4294967295 .1.3.6.1.2.1.2.2.1.5.4 = Gauge32: 1544000 .1.3.6.1.2.1.2.2.1.5.5 = Gauge32: 1544000 [...] .1.3.6.1.2.1.2.2.1.5.19 = Gauge32: 1544000 .1.3.6.1.2.1.2.2.1.5.20 = Gauge32: 1536000
The ifSpeed OID lists all ifIndices, however, it seems the ifInOctet OID is not complete. I'm not sure why this happens; the device in question is a Cisco 7204VXR and while we do not have this exact type I do not believe we have observed this with other Cisco equipment.
The first missing port, with ifindex 4, do you know if it is in a disabled state which might prevent it from being reported? You might also try to upgrade to a newer firmware version as I think this should be considered a bug (0 values should be reported instead of the OID being invalid). When John Magne comes back from vacation he might implement a more graceful degradation where Cricket will simply ignore the invalid OIDs.
Also, I prefer to always CC the list (unless some sensitive info has to be included) since this makes the discussion searchable later and thus adds to the NAV knowledge base.