Network Alert Procedures

1. Justin will contact Brenda when there are problems by using x2888.  This
   number must be used for network problem alerts ONLY.


Key Customers to notify in the event of network problems:
   * Admissions
   * Payroll/Human Resources
   * Teacher Education Department (Ann Thomas) - classes use network
   * SUNYNet Operations
   * Libraries - access to card catalog


Services which are mission critical to the college:

   * Telephone service should be operational 24hrs/day, 7 days/week, 
     365 days/year.  If there is a problem, we need to respond ASAP.
     Brenda would be the team member to contact.

Services which are essential to the mission of the college:

   * Television service problems should be responded to as quickly as 
     possible when problems are encountered during 8am - 10pm (Sun. - Fri.)
     and 10am - 10pm (Saturday).

   * Internet access (campus-related) problems should be responded to as
     quickly as possible when problems are encountered during 6am - 10pm
     (Sun. - Fri.)  .....discussion on this to be continued.

Disaster Revorery planning:

1. identify critical subnetworks - support critical applications to the 
   College; mission critical operations.  Consider RTO (Recovery Time 
   Objective) for each area as some will require more attention to *avoidance* 
   than recovery.
2. identify *single* points of failure (e.g., Wellfleet) because if the RTO 
   must be low, you must eliminate these points of failure
3. UPS's! and other environmental/building concerns (security)
4. individuals! - need cross-training and having access to up-to-date 
   documentation
5. Establish a recovery strategy - develop failure scenarios and the strategy 
   for recovery

  ** consider the Master Plan and the moves that will take place and the 
     services that will be required in the building to be moved to **

6. Network Exposure Analysis
   a. Review Network Configuration
      Confirm Cricitical Functions
      Understand Physical Topology
      Confirm Recovery Time Objective (RTO)

   b. Identify Single Pints of Failure
      Define Risk Avoidance Options
      Establish Recovery Strategy

   c. Estimate Implementation Costs
      Develop Action Plans

   d.  Present Findings

References:
Rappaport, David M., "Toward a Robust Network Environment": Disaster Recovery, Business Communications Review, September, 1993 (9/93) pg. 78-86.