Nav-dev September 2008

nav-dev@lister.sikt.no

4 participants
6 discussions

Suggested text for the new netmap
by Vidar Faltinsen 26 Sep '08

26 Sep '08

Netmap Netmap is a network weather map that displays the layer 3 and layer 2 topology of your network. Current traffic conditions are shown using colored links. - Vidar

2 1

Removing HP SwitchStack support from NAV
by Morten Brekkevold 17 Sep '08

17 Sep '08

Hi everyone, for quite some time we've been aware of many fundamental problems with the way support for HP SwitchStacks has been implemented in NAV. HP SwitchStack support was implemented in NAV 3.0 at NTNU, whose HP equipment consisted solely of HP SwitchStacks at that time. The result is code which is heavily biased towards SwitchStacks, to the point that NAV thinks HP devices are always SwitchStacks, no matter what. While we have been pondering alternative ways to model HP SwitchStacks (and consequently, Cisco switch clusters, which are basically the same thing), NTNU has entirely stopped using SwitchStacks. Today, they're experiencing bad side effects of the existing HP-related code in NAV. They're using some HP devices for routing, which NAV cannot handle at all (because of said "HP=SwitchStack only" view). No router ports are collected for these routers. Also, they seem to have many errors in topology information when HP devices are involved. Realizing that NTNU have stopped using SwitchStacks, we also do not know of anyone else who does, so now we are considering dropping support for SwitchStacks entirely from NAV. This way, the existing NAV code can treat HP devices like everything else. Preliminary tests of these changes at NTNU show promising results. So my question to the users of NAV is: Does anyone actually use virtually stacked HP switches? Will anyone miss support for this if removed from NAV? If there is no feedback on this issue, we will likely remove this support starting from NAV 3.5. -- mvh Morten Brekkevold UNINETT

2 3

Regarding IP info center and 3.5
by Vidar Faltinsen 12 Sep '08

12 Sep '08

Stein Magnus, As I understand it IP Device Info will be feature complete for 3.5 and will be included as a new tool, now also seen from the toolbox. Will you use the RJ45 jack as icon (the one from IP Info center)? Perhaps better with an icon of a switch or something? How about "stealing" the Device Management icon? And then for the new Device History use a faded router icon, perhaps surrounded with a graph or cornered with a clock indicating history? Suggestion for the text in toolbox: "IP Device Info displays all recorded information about a given IP address. If the device is a NAV registered switch or router a port view with details on status and activity is also shown" Even if you are not reimplementing IP Info Center, is it possible to remove this as a tool from the toolbox and instead invoke the tool from the query page of ipdevinfo, in the case the given ip is not a NAV registered box? I think leaving the two tools in the toolbox will confuse users (as indeed is the reason for merging the tools in the end). I further suggest IP Device Info is listed in the toolbox after report. BTW - Morten; The first box in the report links today to "IP Device Center" and leads to /browse Change to "IP Device Info" and go to /ipdevinfo It seems this change has to be done all over the place in report; swap links for /browse with /ipdevinfo Morten; I guess we should work through more of the text from the toolbar. Also the text for the verktøykasse nfsen, here I suggest: "NFSen integrates with NAV to analyze and display your netflow traffic data" - Vidar

3 7

Neat
by Vidar Faltinsen 09 Sep '08

09 Sep '08

https://launchpad.net/nav/+milestone/v3.5.0 ey, ey, ey very neat. I like. I am missing a couple of blueprints: * improvements in netmap o the best list is from the minutes of the July 1 meeting * remove vlanplot and tomcat (is this a blueprint?) - Morten: o we should remove the traffic map portion of seed db as well then? might complicate the possibility of running vlanplot as a contrib? o there are also some (3) vlanplot specific tables: http://metanav.uninett.no/devel:database#traffic_map - Vidar

2 2

Status on certain tasks
by Vidar Faltinsen 09 Sep '08

09 Sep '08

Dear summer developers, Could you please enlighten me, Kristian, * Is all of this done; http://metanav.uninett.no/devel:tasklist I will test, but your word is of value :) your blueprint status is "good progress"... * For the network map * Are we sure the rrd values you get are correct? On nav.uninett.no trd-osl has no load... there should be heaps of traffic here... * The absolute view... how is that coming a long? * Layer two cricket stats - can you display that? i.e. between two swithes Magnus/Thomas * For alert profile/user admin is the following solved; with reference to http://metanav.uninett.no/devel:tasklist - MB7: Admin can change his/her effective user ID - MB8: Support delayed SMSes Magnus; * When deleting a profile subscription you get an extra confirm page for the delete. The info presented there is not what one expect, it reflects the profile time period, not the actual subscription I was to delete... * Have you had a complete walk thru/demo of alert profiles with Morten? If not we should do this and look for potential bugs/missing stuff Thomas; * The new user admin panel returns an error message on navdev. Hard to test :) Are all the subtasks 1-5 of TA3 solved? - Vidar

5 9

Edit DB renamed to Seed DB, needs test and merge
by Stein Magnus Jodal 04 Sep '08

04 Sep '08

Hi, I've just spent an hour on renaming editdb to seeddb, as described in the https://blueprints.launchpad.net/nav/+spec/rename-editdb blueprint. The code is now running at navdev and is available at navdev:~jodal/nav/jodal/rename-editdb. 1) Morten and Vidar: could you please poke around at navdev a bit to test that everything seems okay? 2) Morten: could you please merge the branch or give me a green signal for merging before other branches diverges too much? I've changed code in large parts of NAV (including the infamous nav.django.urls) to accomplish the renaming, and would very much like to win the merge war by merging first ;-) Upgrade instructions are included at the blueprint status whiteboard. -- Stein Magnus Jodal UNINETT

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Nav-dev September 2008