On Fri, 02 Oct 2009 12:12:41 +0200 "Istvan Bernath" ibe@life.ku.dk wrote:

Sorry about the inconvenience!

I've been on the sidelines in the past 3 years, receiving all messages from the nav-users list and running a maintained and updated test installation all that time.

To my pleasure this time it will be official, and the Faculty of Life Sciences, Copenhagen University gives NAV a chance as the global monitoring tool of all the new HP 2510 switches our net is now upgraded to.

Music to my ears. Although I'm curious as to how NAV will perform on an all HP network. We've had some problems with HP in the past. Not all of them are completely behind us, but they hopefully will be in NAV 3.6.

Monitoring of several services will also be crucial.

NAV's service monitoring capabilities have been somewhat downplayed by UNINETT, due to lack of resources. We've left maintenance of those systems in the capable hands of the University of Tromsø. Hopefully, their developers can answer your questions, as I don't know radius or the service monitor all that well. I've prodded one of their guys to look at your servicemon question.

I have though problems with monitoring the Radius service, and booth topology and MAC behind a port do not work with the new HP ProCurve switches.

Your topology problems are intriguing. Are you experiencing a total lack of topology information, or just plain wrong topology? I've had reports of the latter from other HP-heavy installations.

Are you able to search any MAC data for any of your switches?

I hope somebody can help me rectifying the last problems.

It might take some Q&A, but hopefully we can be of assistance :)