UCT Campus Network Upgrade

University of Cape TownsupaTsela PIC

14 July 2005

Network Blueprint

- 2 -PIC 2005-07-14

Current network: risks and deficiencies

• Outdated and hard to update

– Uneven mix of technologies including legacy connectivity

– Cannot deploy new services required by UCT quickly enough

• Difficult and costly to manage

– Does not conform to a standards-based model

– Staff time is spent reactively on support and maintenance

• Cannot be properly secured

– Security incidents cause significant downtime

– Lack of structured security policies to govern network access

– Unmanaged switches and hubs cannot be properly secured

• Not sufficiently reliable

– Lack of fault tolerance - no redundancy on the backbone

- 3 -PIC 2005-07-14

Network design methodology

• As-is network documentation: extensive information gathered on access ports, cabling, services, environmental conditions

• Network traffic analysis: traffic flows and volumes baselined

• Business requirements: discussions held with major UCT business units; information gathered via a questionnaire

• “To-be” network design

• Phased migration plan: the future network will be built alongside the existing network with a gradual conversion of users

As-is Traffic Analysis

Business workshops

Network design

Migration plan

- 4 -PIC 2005-07-14

To-be design: layered network model

• Three main building blocks: core, distribution and access layers

• User workstations connect to access layer switches

• Access switches in turn connect to distribution layer switches which act as aggregation points

• The core layer provides for connectivity between the data centres

To be design:

core

- 6 -PIC 2005-07-14

To-be design: four building models

Type Size Users Remarks Number

A Large > 400 • provides alternate network routes in the event of a data centre failure

• mini server farms connected at 1Gbps to provide for distributed services.

5

B Large 200 – 350 • small number of servers connected via 1Gbps Ethernet.

26

C Medium 100 – 200 • few or no servers 19

D Small 1 - 100 • cost effective model

• provides for network access speeds of 100Mbps to the desktop

58

- 7 -PIC 2005-07-14

To-be design: wireless

• Provision made for about 30 secure wireless hotspots on all campuses.

• Locations determined based on

– questionnaires returned

– information from P&S about open access areas

- 8 -PIC 2005-07-14

Future proofing

• The new design has the capacity to incorporate new technologies in the future and at additional cost

• The most likely future technologies for possible implementation at UCT were analysed:

– IP Telephony

– Voice over IP (VOIP)

– IPV6

– Content Networking

– IPTV

- 9 -PIC 2005-07-14

As-is

• Outdated

• Hard to update

• Difficult and costly to manage

• Cannot be properly secured

• Not sufficiently reliable

To-be

• Fully switched network infrastructure with enhanced performance and throughput

• Capacity for future growth and technologies

• Pro-active central management to resolve problems and reduce costly downtime

• Managed switches from a single vendor that have enhanced security features

• Enhanced availability through managed network components and redundancy.

As-is and to-be compared

The new design supports consistent service-level improvements in networking services across campus.

- 10 -PIC 2005-07-14

Blueprint scope exclusions

• Internet bandwidth

• 1Gbps connectivity to the desktop

– The design model allows for this

– It has not been included in the budget

– The additional costs of such connectivity will be for the account of the user

• Issues addressed by the NIR workstream, but not part of the blueprint:

– WAN (Wide Area Networking) links

– Cabling within and between buildings

– Residences

- 11 -PIC 2005-07-14

Recommendations:

• That PIC approve implementation of the UCT Campus Network Renewal and Upgrade as per the recommendations contained in the Network Blueprint document and associated documents.

• That PIC note and approve the revised budget in respect of the Network Upgrade in Academic and Administrative Buildings.

UCT Campus Network Upgrade

University of Cape TownsupaTsela PIC

14 July 2005

Proposal to contract with T-Systems as the Implementation

Partner

- 13 -PIC 2005-07-14

T-Systems as a partner in Phase 1 of the Network Implementation

• T-Systems overall performance was satisfactory

• Their technical competence and performance was good

• We have established a good working relationship with the T-Systems team

To switch to another partner for Phase 2 (implementation) of the Network Renewal would result in significant delays, could be more expensive, and does not appear justified in view of the comments above.

- 14 -PIC 2005-07-14

Proposed scope of work for T-Systems (in conjunction with UCT)

• Implementation of Network Management Systems (CiscoWorks and HP OpenView Network Node Manager)

• Implementation of Cisco Access Control System

• Implementation and testing of a pilot network which will include the full core layer and the distribution and access layers for a Model-A Building (Commerce) and a Model-B building (Menzies) as a B-model and the HSF Lab in Anatomy as an A-model at Medical School

• Development of the Migration templates

• Full Rollout of the Core Layer and all the Distribution Layer in Model-A Buildings together with the first two Model-B Buildings

• A quality assurance role throughout the network rollout

- 15 -PIC 2005-07-14

Recommendations:

• That T-Systems be awarded a contract to provide services as per the scope definition in the previous slide.

• That the supaTsela Project Team be authorised to negotiate the cost of this contract up to a maximum value of R 750,000 + VAT (current indications are that it will be substantially less than this).

UCT Campus Network Upgrade

University of Cape TownsupaTsela PIC

14 July 2005

Proposal to contract withT-Systems for the Maintenance of

the Network Core Switches

- 17 -PIC 2005-07-14

Cisco Shared Support Program (CSSP)

• CSSP is an offering through which Cisco and channel partners provide technical support to customers

• CSSP must be purchased on all products at time of order

• CSSP can selectively be renewed in the second year and onwards

- 18 -PIC 2005-07-14

Benefits of Cisco Shared Support Program

• Online access to Cisco technical support

• Access to software upgrades and bug fixes

• Best effort warranty replacement through partner

- 19 -PIC 2005-07-14

T-Systems’ Maintenance Proposal

• ObjectiveProvide UCT with a hardware maintenance contract for mission critical hardware components.

• Benefits- Minimum client network downtime- Fixed cost budgeting in an unpredictable environment- Spares holding facility

• Service OverviewA Platinum Service Level Agreement with a Guaranteed Mean Time To Restore (GMTTR) of 4 hours

- 20 -PIC 2005-07-14

Recommendations:

• That UCT should contract with T-Systems for the maintenance of the Core layer equipment.

• That the supaTsela Project Team be authorised to negotiate the cost of this contract up to a maximum value of R 600,000. This is based on 15 months of a monthly paid three year contract at $1=R7.5.

• That UCT should hold stock of the Access and Distribution layer equipment to provide for rapid replacement of any defective equipment.

- 21 -PIC 2005-07-14

x

x x

x