-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all, I'm looking for a network management software. And as the network grows it clearly becomes that manual notes is getting too tedious. Also an integrated troube ticketing systemm would be great. Any reference is really appreciated. Thanks. - -- Fajar Priyanto | Reg'd Linux User #327841 | Linux tutorial http://linux2.arinet.org 13:10:54 up 5:02, 2.6.24-18-generic GNU/Linux Let's use OpenOffice. http://www.openoffice.org The real challenge of teaching is getting your students motivated to learn.
Fajar Priyanto wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all, I'm looking for a network management software. And as the network grows it clearly becomes that manual notes is getting too tedious. Also an integrated troube ticketing systemm would be great. Any reference is really appreciated.
For managing my "network" of servers(assuming what you mean since your posting to a CentOS list and not a network equipment list), I use CFengine to manage them(www.cfengine.org). Puppet(t?) is also increasing in popularity as well(don't know the web site and doing a google search didn't come up with anything obvious).
For a ticketing system I suggest Request Tracker(RT) (http://www.bestpractical.com/rt).
For monitoring I use a combination of an extremely customized cacti[collects 10+ million points a day](www.cacti.net) and Nagios(www.nagios.org).
For documentation I highly recommend confluence (http://www.atlassian.com/software/confluence/).
nate
On Mon, 11 Aug 2008, nate wrote:
I'm looking for a network management software. And as the network grows it clearly becomes that manual notes is getting too tedious. Also an integrated troube ticketing systemm would be great. Any reference is really appreciated.
For managing my "network" of servers(assuming what you mean since your posting to a CentOS list and not a network equipment list), I use CFengine to manage them(www.cfengine.org). Puppet(t?) is also increasing in popularity as well(don't know the web site and doing a google search didn't come up with anything obvious).
I'll second cfengine (available via rpmforge). It takes a while to set up, but it's a pretty sane way to manage configurations.
For a ticketing system I suggest Request Tracker(RT) (http://www.bestpractical.com/rt).
For documentation I highly recommend confluence (http://www.atlassian.com/software/confluence/).
RT is good; I've used it at previous jobs. Be prepared to install a lot of Perl modules. :-)
In my current small-ish setting, I use Trac for tickets and documentation. I keep most configuration files in a Subversion repository (an export of which serves as the depot for cfengine) -- and Trac makes it easy to link between wiki pages, tickets, and repository revisions.
I don't think this setup would scale to a large organization, but it works just fine in smaller environments.
For monitoring I use a combination of an extremely customized cacti[collects 10+ million points a day](www.cacti.net) and Nagios(www.nagios.org).
Nagios, like cfengine, takes a while to get started, but does the job once it's up and running. Wolfgang Barth's book from No Starch Press can be handy to have around if you want an accessible introduction and reference.
In my current small-ish setting, I use Trac for tickets and documentation. I keep most configuration files in a Subversion repository (an export of which serves as the depot for cfengine) -- and Trac makes it easy to link between wiki pages, tickets, and repository revisions.
I second the recommendation for Trac + Subversion for ticketing, documentation, + revision history.
I don't think this setup would scale to a large organization, but it works just fine in smaller environments.
For a large organization that needs a full-blown ticketing system, RT is applicable, but it's really cumbersome to set up if you just need a fairly small system.
Nagios, like cfengine, takes a while to get started, but does the job once it's up and running. Wolfgang Barth's book from No Starch Press can be handy to have around if you want an accessible introduction and reference.
And, for monitoring, I second the vote for Nagios -- very customizable.
M
Fajar Priyanto wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all, I'm looking for a network management software. And as the network grows it clearly becomes that manual notes is getting too tedious. Also an integrated troube ticketing systemm would be great. Any reference is really appreciated.
OpenNMS is pretty good for network monitoring (http://www.opennms.org). It isn't tightly integrated with a trouble ticket system but some work has been mentioned on the mail list about tying it to RT.
On Tue, Aug 12, 2008 at 07:52:45AM +0700, Fajar Priyanto wrote:
Subject: [CentOS] Suggestion on Network Management software with -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all, I'm looking for a network management software. And as the network grows it clearly becomes that manual notes is getting too tedious. Also an integrated troube ticketing systemm would be great. Any reference is really appreciated.
Network management is an area worth some thought.
For tracking events to closure... Look at Bugzilla, Eventium and the other suggestions posted....
I suspect you need tracking, ownership, states (new, assigned, working, OMGH, fixed), attached documents, the ability to generate reports and also solve the do you remember games when systems are down (documentation).....
Network management is interesting.... If there is a problem with the network, bug systems and other "tools" may also be off line. The classic way to monitor a network is to live on it and have a phone, Rolodex and pager handy to contact the other end of the wire.
Nifty Cluster Mitch wrote:
On Tue, Aug 12, 2008 at 07:52:45AM +0700, Fajar Priyanto wrote:
Subject: [CentOS] Suggestion on Network Management software with -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all, I'm looking for a network management software. And as the network grows it clearly becomes that manual notes is getting too tedious. Also an integrated troube ticketing systemm would be great. Any reference is really appreciated.
Kayako system is what you need...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Nifty Cluster Mitch wrote:
I suspect you need tracking, ownership, states (new, assigned, working, OMGH, fixed), attached documents, the ability to generate reports and also solve the do you remember games when systems are down (documentation).....
Network management is interesting.... If there is a problem with the network, bug systems and other "tools" may also be off line. The classic way to monitor a network is to live on it and have a phone, Rolodex and pager handy to contact the other end of the wire.
Hello guys, Thank you so much for the suggestions. All looks interesting and I've downloaded them. It will be an exciting try-out.
After some thoughts, I hope I might be able to find one which answers these: 1. The status of servers (traffic, services, availability) 2. Network inventory (ip, users, host, host's specs) 3. Support ticket (connected to host and user) with history view, so we can see the trend. 4. Knowledge base / documentation management
- -- Fajar Priyanto | Reg'd Linux User #327841 | Linux tutorial http://linux2.arinet.org 13:10:54 up 5:02, 2.6.24-18-generic GNU/Linux Let's use OpenOffice. http://www.openoffice.org The real challenge of teaching is getting your students motivated to learn.
-
Fajar Priyanto -
Les Mikesell -
Lodewijk christoffel -
Meenoo Shivdasani -
nate -
Nifty Cluster Mitch -
Paul Heinlein