Thanks for the kind reply!
Right now all our active switches are registered in NAV. There are about
130 pcs. 2510-48 and a couple of 2600-8, 2610, 2626, 2650, 2810 and 2824.
The core switches are two 5406 and a single 5412.
Traffic data is collected from the switches correctly. Statistics are presented
fine via Cricket.
Alerts, like firmware upgrade and cold start, are all noticed via Alert Manager
as it should.
Topology right now is totally missing, but luckily I've cached a hint of topology
with a single 2824 in the middle and one 2626 one 2650 and a 2510 as the
neighbors before my colleague, sorry to say, have updated to the latest firmware.
The magic surely was, that the 2824 had a complete CDP and LLDP implementation
in the old firmware, while all the new HP firmware has only a crippled Receive Only
The missing topology is rather crucial since we can be flooded by SMS and mails
in case a box at the top fails.
MAC information is collected, so it is possible to find a MAC number belonging to an
IP number, but the MAC is not associated to any switch port, so we can not trace
MAC, and use Arnold.
Service monitoring is rather important for us, since our server people do need
a better identification of a functioning server than a simple ping. Needless to say
that a process can fail while the server still is pingable.
Right now we are monitoring DNS, HTTP, IMAP, SMB, SMTP with success.
The only service we are missing, for the time beeing, is the RADIUS.
If I can help the developers with any tests, I would be more than happy to do it!
>>> Morten Brekkevold <morten.brekkevold(a)uninett.no> 10/15/09 11:14 AM >>>
On Fri, 02 Oct 2009 12:12:41 +0200 "Istvan Bernath" <ibe(a)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
> 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
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 :)