Wiring Project Team

Meeting 4/9/96 - Electronics

Wiring project page

Attending:  Garnet Barrigar, Dave Brouwer, Carmen Casolara, Bob Jewett, Justin 
            Sipher, Bill Todd (DEC)


Last meeting:  4/5/96     Next meeting (update):  5/15/96


Agenda: Specifications for electronics (active components) design

   1. Backbone technology
   2. Service/Maintenance
   3. Network Management
   4. Limit on nodes per collision domain
   5. Router
   6. Fiber usage
   7. Scaling our equipment to meet demand


----------------------------------------------------------
Specifications for electronics (active components) design:
----------------------------------------------------------

1. Prefer ATM as the "backbone" technology for our campus network (existing LAN
   and the proposed residential LAN).  The determination will be based upon
   cost and manageability.  We prefer that the management of our network *not*  
   require Unix skills.  We just do not have the depth of people/skills on our
   campus.

   NOTE: ATM is scalable; that is, it can grow in capacity as our needs for 
         performance grow.  FDDI and FastEthernet both are limited to 100Mbs.  
         However, ATM is still an emerging standard and therefore may involve
         more "risk" than FDDI and FastEthernet.


2. Service/Maintenance:  We want to adopt a "critical" spares method for repairs
   and maintenance of our system rather than pay for on-site service.  The
   critical spares method will require us to purchase the necessary spare parts
   that are needed to keep our LAN operational should a critical component fail.
   If the spare is on warranty, it would be replaced free of charge.

   This method will give us the best service for the cost.  We can replace
   something much more quickly than a service provider could when you consider
   their travel time.    

   We also want phone support included in the cost of any service contract.


3. Network Management:  We want training included in any proposal for network 
   management.  (see #1 above about Unix).  


4. We want to limit the number of nodes (computers, printers, etc) on any 
   network collision domain to 32 or less.  This limit should allow us to
   take advantage of lower-cost network hubs while maintaining reasonable levels
   of performance.


5. We will need a router that will connect the existing campus LAN to the
   proposed residential LAN, and will connect the residential LAN to the 
   Internet.  We may also need a connection for Potsdam Central Schools if we 
   are able to partner with them for Internet access.  Therefore, the router
   must be capable of supporting a minimum of two (2) LANs and a serial port; if
   the partnership with PCS works out, we will need a minimum of three (3) LANs
   and a serial port.


6. Fiber usage:  Vendors may consider the use of 12 strands of fiber between
   Stowell Hall and any of the 5 residential buildings in their electronics
   design.  By setting the limit to 12 strands, the campus will have 2 strands
   available as spares and 2 strands for possible use in a proposed fire-
   alarm network (Physical Plant is working on this).


7. Any proposal for equipment must be scalable.  That is, we must know how we
   can "grow" our residential network to meet the needs that students may
   place on it.  We also want to be able to move equipment around and 
   consolidate it as needed to meet demands.



REFERENCES:

Project cabling RFP-type specifications
Summer housing schedule prepared by John Horan.
SUNY Potsdam's response to Cabletron questions
Gartner Group conference call