Network Services Team

Meeting Minutes 4/12/95

Present:  Garnet Barrigar, Brenda Bennett, David Brouwer, Carmen Casolara, 
           Bob Jewett, Justin Sipher



1. Old Business:

   - Shiva LANRover problems/update.  On the basis of tests we've performed,
     and the fact that the LanRovers are bridged off from the rest of the 
     network, the phantom zones may be emmanating from other sources.  Bob
     has called and emailed Eric Wilson at Shiva for new updates to their
     LanRover software.  No response yet.

   - Library CD-ROM server.  No news.  Dave will be meeting with Keith and
     will ask him at that time about the status of the memory upgrade for
     their CD-ROM server.

   - TCP/IP Optimization.  Dave will search the NetNews logfile and 
     send the results to the team before our next meeting.

   - Student access to Unix server room (next to Garnet's office).  Carm 
     checked Erik's keys and will tell him to turn in his #108 key.
 
   - Network Services WWW page. Discussed items to put published on our WWW 
     host.  Bob indicated that all minutes will be published on our WWW first,
     then he will email team members with the URL to get to them.

   - Monitoring # of calls to our modem pool.  Brenda will prepare a weekly 
     report on the peak # of calls to the modem pool.

   - Dave has assumed Joan's Postmaster responsibilities effective immediately.

   - We reviewed the list of summer projects that the team would like to
     accomplish over the summer:

 Phones checked to ensure that they are in working order for students
 returning in the fall. (Brenda, Carm)
 Brenda's student phone service setup for the fall. (Brenda)
 Unix host problems/setup.  Bob suggested that we clean up our usercodes
 as well.  (Dave)
 WWW development and data communication updates on personal computers
 throughout the campus. (Justin)
 Establishing a more streamlined SLIP/PPP install process (Dave, Justin)
 Wiring the "dorms" (Team)

     From this discussion, a number of issues/concerns were raised about 
    the possibility of providing a telephone for every "pillow" as well as
    data.  If we were to provide this level of telephone service, we would 
    have to:
 install at least 100 analog cards in the switch (approx. $50,000)
 acquire more DID trunks
 renegotiate our contract with ACUS
 purchase 1200 more phones
 establish more CPU/storage for additional voice-mailboxes
 determine how to handle the additional administrative load.



2. New Business:

   - no new business raised in this meeting.



3. What's Important to accomplish by next week?

   - LanRover/AppleTalk zone problems.  (Team)

   - continue publishing HTML-based documentation; that is, Asante termination,
     modem numbers; how to program our HOTLINE information, etc.  (Team)

   - modem pool report (Brenda)

   - Library CD-ROM server update (Dave)

   - report on "filtered" NetNews groups (Dave)



4. Continuation of discussion on our roles for network problems and how/when to 
   alert campus of problems with network services:
 
   First, we attempted to identify the hours of service during which we would
   respond to problems for Internet access:

     Mon -> Fri:   6am - 10pm (16hrs/day)

        Sat/Sun:  10am - 10pm (12hrs/day)

   As we began to discuss how we would be informed of problems and who would
   be available to respond to the problem(s), especially evening and weekends,
   we began to address concerns over the level of service the campus expects
   from our team.  Bob agreed to talk to Peter Brouwer about the expectations
   the campus may have about our service and report to the team about that 
   at the next meeting (4/19)


5. Next meeting Weds, 4/19 @ 8:00am
 
   AGENDA items (see calendar for latest revisions):
     Continue discussion on and document (same as 4/12):
     - reports (Bob, Brenda, Dave)
     - when an after-hours alert requires our attention
     - backup role for Justin's role as coordinator for network service problems
     - Brenda's role as information clearinghouse and her backup.
     - how to program (record messages) for the HOTLINE (x2884)