Ken Innes, Chris Palmer and Ryan Sackenheim

Architect: Ken Innes
Tool-Smith: Ryan Sackenheim
Scribe: Chris Palmer

1. Map and document Earlham's network. This should include all the college owned servers, routers, hubs and other active components.
2. Create or find a tool to monitor and measure the network traffic on campus. This should include everything we mapped plus the three external links (T1 to IHETS, frame relay to Infocom and fiber to RP&L). Traffic should be shown by protocol, with capacity and response time being shown for major links.
3. Engineer proposals for possible off-campus future expansion of the network. Locations should include Brick City, all college houses, the observatory, the stables and Norwich lodge. The addition of video and voice capacities should also be considered.
4. Write up a report on where Earlham's network can or should be improved due to security and traffic in the present and near future. The current subnet layout is one issue that has already been raised and will be examined.

We plan to try and implement a single solution to the first two goals. This will probably be a program (we are currently looking at TKINED) which uses SNMP to not only discover existing hardware, but also monitor current conditions. We would like this to have a web viewable component, although this may only be a less detailed and non-interactive report of current traffic conditions. Hopefully the use of this tool (or set of tools) will show the flaws in the current network, and so lead us towards our fourth goal. TCPDUMP or some other sniffing tool may be used in addition. We plan on interviewing some Earlham Computing Services staff to find out about the existing network, as well as their ideas for future expansion plans.