[603] in resnet
Re: Network Management Platform
daemon@ATHENA.MIT.EDU (John Kristoff)
Wed Dec 19 15:32:20 2001
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <3C20F841.DF55F385@depaul.edu>
Date: Wed, 19 Dec 2001 14:27:45 -0600
Reply-To: jtk@aharp.is-net.depaul.edu
From: John Kristoff <jtk@DEPAUL.EDU>
To: RESNET-L@listserv.nd.edu
"King, Michael" wrote:
> We're looking into replacing the Network Management software that we use to
[...]
> What would other people recommend looking at?
Depending on your level of sophistication this may not fly, but I always
steer clear of the all-in-one, big-honking, commercial, $$$ NMS stuff.
In my experience, you often end up spending more time managing your
network management system than the actual network. You mentioned
maintaining historical info as being a major goal. Syslog may be a
good, free alternative. Essentially you set all your internetwork
equipment to log to a centrally secure syslog server. From that central
server you can keep archives and run reports using your own scripts. In
fact, I have some rudimentary ones that should appear on the Sourceforge
COSI project page shortly:
http://cosi-nms.sourceforge.net
There are also good free tools to do trending on SNMP statistics (e.g.
MRTG) and availability (Netsaint). If you're looking for pretty GUIs of
equipment and remote management via SNMP to control particular devices,
a commercial NMS may be what you want, but I've found many networks
don't really need them and in some cases, those that have them, rarely
use them.
> Our Cisco rep has suggested that we look at CiscoWorks2000.
Hehe, of course.
John
___________________________________________________
You are subscribed to the ResNet-L mailing list.
To subscribe, unsubscribe or search the archives,
go to http://LISTSERV.ND.EDU/archives/resnet-l.html
___________________________________________________
