What about doing two or more of the following(they are all related anyway):
- Enable all your linux boxes with SNMP (for remote monitoring) - Setup one box to be your SNMP trap server(monitor server) - Write your own (maybe in perl/tcl/tk) trap log viewer to be run on the server - Write your own snmp MIB browser (php, perl/tcl/tk, etc) - Find out all the information you can obtain remotely via the SNMP protocol and, - extend the MIB tree for linux(or some vendor) to incorporate more information (i.e. raid status, process accounting, some other hardware/application status, etc.) - Compare the differences of snmp v2 and v3 and make your own recommendation on why one should be prefered over the other one; mention issues, incompatibilities, security, etc) - Since snmp is mostly supported on most server OSs, throw in a windows server to be monitored as well and seen how much system info you can get. - On your monitor server, write an application that stores data collected via snmp (like the "system contact" info) to a database to be used in case a system goes down. - Write your notification system based on the above: If a system goes down, page/email the admin of that box by querying the database on the monitoring server. - As an extra bonus, create a map application that shows a gui status of your network (i.e. a red server icon means a system/service object is down, etc) Let me know if you need more ideas, I have plenty by the way :) -mtm ----- Original Message ----- From: "Tony Vance" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, October 22, 2003 2:53 PM Subject: [uug] Suggestions for a Linux networking project? Hey everyone, I'm taking a networking class and I need to come up with an idea for a networking project. I have a small lab of computers availible to me on which I can install Linux or Windows Server 2003, or whatever. I'd like to do something fun with Linux and learn something useful. do you have any suggestions for a networking project that's not too hard (I've heard setting up a Kerberos server is difficult to do). Some ideas I've had so far: * configure several workstations to communicate using a VPN * configure Linux and Windows workstations to communicate together using Samba Any other ideas? Thanks! --Tony ____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list ____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
