Re: VS: Radius service monitor
Istvan Bernath <ibe@...
2009-10-15 11:06:20 GMT
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!