download link for project report in word format.doc.doc

BSc Computer Studies & Information Systems Stage 3 Assignment 1

NDM Module Midshires University LAN Design

Introduction to the Group Assignment

The Group

Our group consists of Mike Bailey, BSc Information Systems Year 4, and Paul

Smith and Dave Portass, both BSc Computer Studies Year 4, University of

Derby.

At our first meeting we allocated responsibilities for this assignment, following

the suggestion in the assignment spec:

All: Detailed network design (11.7).

Dave Portass: Detailed costings for all elements of the design including

options (11.13).

Paul Smith: Statement of Mandatory, Desirable and Question

requirements (11.4; 11.5; 11.6).

Mike Bailey: Management Summary, organisation, strategy, project

plan, implementation, reference sites, and standards

(11.1-11.3; 11.8-11.12).

Each of the main numbered sections of the Operation Requirements

Response has a sub-heading attributing the author of that section. Mike also

had the responsibility for bringing all the parts together as one document, and

printing the final assignment.

Our Progress

We met together on a regular basis to discuss the network design, and

compared ideas as we went along. On Feb 24th 2003 we presented our initial

design to the tutorial group and received a favourable response. A number of

minor changes have been made since then.

Dave Portass, Paul Smith, Mike Bailey May 2003



All the individual sections were completed independently by each of us, and

brought together at the end. Some comparing of information and sharing of

ideas took place during this stage.

The Assignment

The bulk of this assignment represents an OR Response to Midshires

University by our fictional company: International Network Solutions.

This Introduction, an assignment Title Page, and a Bibliography have been

added to complete the assignment for academic purposes. They are not

strictly part of the Response.




International Network

Solutions

Specialist provider of medium and large

scale network design and installation

across Europe

Operational Requirements

Response

for:

Midshires University, UK

FAO. Mr K. Smith

SEIS Project Manager

Midshires University

Centrester

CE11 1AA

Tel: 0999 111222

International Network Solutions




A University Degree Project by Mike Bailey, Paul Smith, & Dave Portass

University of Derby




Table of Contents

Introduction to the Group Assignment.........................................................1

Operational Requirements Response...........................................................3

Table of Contents...........................................................................................4

Table of Figures..............................................................................................7

1 Management Summary...........................................................................8

1.1 Summary of Proposal.........................................................................8

1.2 Summary of Approach to LAN Provision............................................9

1.3 Summary of Proposal Cost................................................................9

2 Supplier Organisation...........................................................................10

3 LAN Strategy..........................................................................................11

3.1 Reliability..........................................................................................11

3.2 Expandability....................................................................................11

3.3 Upgradeability..................................................................................12

3.4 Security............................................................................................12

4 Statement on Mandatory Requirements..............................................13

4.1 Access to Mainframe Systems.........................................................13

4.2 Building 7’s Unix System..................................................................14

4.3 The Network Availability...................................................................15

4.4 Media Trunking................................................................................17

4.5 Media European Standards..............................................................17

4.6 Environmental Precautions..............................................................19

4.7 ‘E’ End Points Protocol Access........................................................21

4.8 Compatibility with Windows-NT and Novell Protocols......................23

4.9 ‘V’ and SNA Connections.................................................................24

4.10 ‘E’ and ‘V’ Outlet Conversion............................................................24

4.11 Outlet Indication...............................................................................25

4.12 Infrastructure Expandability..............................................................26

4.13 Call-out Service................................................................................27

4.14 Fault Escalation Procedure..............................................................28

4.15 End-to-end Testing...........................................................................28




5 Statement on Desirable Requirements................................................30

5.1 Communications Equipment Standards...........................................30

5.2 Twisted Pair Cabling should be at least Cat 5..................................31

5.3 Outlets should be RJ45 for Unshielded Twisted Pair Cable.............32

5.4 List the Protocols used on the Network............................................33

5.5 ‘V’ Outlets and Concurrency.............................................................33

5.6 Additional ‘V’ or ‘E’ Sockets..............................................................34

5.7 Serviceability Between ‘E’ Outlets....................................................34

5.8 Serviceability Between ‘V’ and ‘E’ Outlets........................................35

6 Further Information Required From Suppliers...................................37

6.1 Standards Used...............................................................................37

6.2 Customer References......................................................................38

6.3 Network Security..............................................................................39

6.4 Internet Functionality........................................................................40

6.5 Network Backbone...........................................................................41

6.6 Warranty...........................................................................................42

6.7 Maintenance.....................................................................................43

6.8 Testing Scope..................................................................................44

7 Description of System Proposal..........................................................45

7.1 System Overview.............................................................................45

7.2 Logical Connections.........................................................................47

7.3 Physical Connections for each Building...........................................48

7.4 Communications Protocols...............................................................55

7.5 Network Management......................................................................56

7.6 Main Components Used in the Network...........................................58

7.7 Additional Equipment Required........................................................58

7.8 Additional Items Required from MU.................................................59

8 The Project Plan....................................................................................60

8.1 Phase 1 – Planning and Site Audit...................................................62

8.2 Phase 2 – Cabling, Equipment, and Software..................................62

8.3 Phase 3 – Testing............................................................................66

8.4 Phase 4 – Training, Documentation, and Handover.........................66

8.5 Phase 5 – Service and Support........................................................68

8.6 Phase 6 – Future Maintenance and Upgrades.................................68

9 Implementation......................................................................................69




10 Level of Serviceability...........................................................................70

10.1 Availability........................................................................................70

10.2 Reliability..........................................................................................71

10.3 Fault Handling..................................................................................71

11 Reference Sites.....................................................................................72

12 Standards...............................................................................................73

12.1 Standards Bodies.............................................................................73

12.2 Quality Standards.............................................................................73

13 Total Costs.............................................................................................74

13.1 Capital Costs....................................................................................74

13.2 Other Non Recurring Costs..............................................................76

13.3 Recurring Annual Costs...................................................................79

13.4 Conclusions......................................................................................79

13.5 Suppliers..........................................................................................80

Bibliography..................................................................................................81

Appendix 1 Network Management..............................................................84

Appendix 2 Network Components Itemised per Floor..............................86

Appendix 3 Literature Describing Main Network Components................93




Table of Figures

Figure 4.1 IBM Token Ring Network (IBM, 1997)........................................13

Figure 4.2 The OSI Reference Model (Tanenbaum, 1996)..........................22

Figure 7.1 Network Backbone......................................................................46

Figure 7.2 Logical Connections....................................................................47

Figure 7.3 Building 1 Physical Connections.................................................48

Figure 7.4 Building 2 Physical Connections (1)............................................49

Figure 7.5 Building 2 Physical Connections (2)............................................50





Figure 7.10 Building 7 Physical Connections...............................................55

Figure 8.1 Project Plan..................................................................................61

Figure 8.2 Project Plan Phase 1...................................................................63

Figure 8.3 Project Plan Phase 2...................................................................64

Figure 8.4 Project Plan Phases 3 & 4...........................................................67




1 Management Summary

By Mike Bailey

1.1 Summary of Proposal

We are pleased to present this proposal for a network design in response to

the Operational Requirements from Midshires University. We have met all of

the requirements laid down in the OR, and can deliver the network on time

and within budget.

Our team has put together a design which will meet the current needs of MU,

with the following features:

1. As required we have provided connectivity to the IBM mainframe system in Building 1, with provision for its replacement.

2. A secure connection is created with the Unix system in Building 7, limiting the confidential data, while allowing access to the rest of the network.

3. All the existing file servers are included.

4. The design creates the required user groups within Building 2.

5. Cross-connection of switches, to ensure that some workstations will still operate in each area in the event of switch failure.

6. Reliable Internet connection with a dedicated security firewall.

7. A network Management System which will monitor the entire network, warn of likely faults, alert emergencies, and aid in fault diagnosis.

8. The design accommodates future expansion and upgrades.

At the core of this network is a reliable, high speed, fibre optic backbone. This

is connected entirely with a Cisco router in each building, in a partial mesh

topology, providing resilience against failure, and ample bandwidth for the

needs of the users.

Within each building the network is brought from the router to a central

distribution point on each floor, which supplies every workstation via banks of




Cisco switches. The cabling used here is also capable of carrying a higher

data rate than is currently required.

Full details and diagrams of our design can be found in Section 7. Information

about how this response meets all of the requirements of the OR can be

found in Sections 4, 5, and 6. Our Project Plan for this response can be found

in Section 8.

1.2 Summary of Approach to LAN Provision

Ethernet LAN is now the most popular current network structure. It is flexible,

expandable, and uses the same basic protocols as the Internet. However,

without careful design and implementation there can be problems with

reliability and security. We endeavour to resolve these issues through our top

quality service, and our dedication to ensuring reliability, expandability,

upgradeability, and security. Please see Section 3 for further details.

1.3 Summary of Proposal Cost

This network proposal is of the highest quality, meeting all of the requirements

of MU, and can be supplied within the timescale. It is also well within the

budget of £2,000,000. In the following summary table the costs are split into

initial capital costs, other non-recurring costs (such as training installation and

project management), and recurring annual costs to cover ongoing support

and maintenance.

Item Cost Qty Total

Capital Costs 884921.66 1 884921.66

Other Non Recurring Costs 324000 1 324000

Recurring Annual Costs 690000 1 690000

Total 1898921.66

Please see Section 13 for detailed costings.




2 Supplier Organisation

By Mike Bailey

International Network Solutions (formerly Network Solutions, UK), operates

across the UK and Europe to provide the highest quality design and

implementation of Local Area Networks. We now focus on medium and large

networks for companies and institutions, but can still accommodate smaller

systems if required. Although we design and build complete systems, we

specialise in extending and upgrading existing and legacy systems. We are

currently in negotiation regarding growth into integration of our networks into

Metropolitan Area Networks in certain UK cities.

We started as a small group of graduates in 1995, and went public three

years later. Our share price remains reasonably stable, in the context of the

current economic climate. We aim to provide 2-3 large scale networks each

year, as well as a number of smaller projects. Our annual turnover is now

approaching £10 M.

We have a core team of enthusiastic and highly qualified staff, and employ

expert consultants, and specialist subcontract cabling teams as required. For

this project at MU the key members of our team are as follows:

Project Manager Mike Bailey, BSc

Chief Designer & on-site Team Manager Dave Portass, BSc

Head Requirements Analyst Paul Smith, BSc

We are all graduates of the University of Derby, a widely respected centre of

excellence in this field. Mike Bailey graduated in Information Systems, while

Dave Portass and Paul Smith graduated in Computer Studies. Each of us are

members of the British Computer Society, and Dave Portass is a Microsoft

Certified Engineer.




3 LAN Strategy

By Mike Bailey

Ethernet LAN is by far the most popular network type as it can utilise all

current standard cabling, and it uses the same protocols as the Internet. A

fully switched network would be standard now for a smaller system, but when

using a fibre backbone in a larger network we regard routers as standard, as

these will automatically cater for multi-path topologies (essential for backbone

resilience), and direct data along the most appropriate route at that time.

We at International Network Solutions work on a number of principals to

inform our strategy for design and installation of Ethernet LAN networks:

Reliability

Expandability

Upgradeability

Security

3.1 Reliability

Network failure is one of the most disruptive problems facing network

managers. Our customers require networks that are highly reliable and free

from failure. Acknowledging that failures will, and do, occur, we also ensure

that faults can be quickly and easily diagnosed and repaired. This is down to

good design, superior installation, and quality components.

Please see Section 10 for further details on network reliability in this proposal.

3.2 Expandability

We recognise that companies and institutions are not static. They change,

move on, and grow. Therefore we expect our networks to be capable of

modification and growth also. The overall technology of Ethernet LAN allows

additions and changes to be made to a network, and we ensure that our




designs make full use of this capability. It is an integral part of our design

process that we investigate the likely and possible future growth in size and

requirements of our customers.

Please see Section 4.12 for further details on expandability in this proposal.

3.3 Upgradeability

The days of co-axial cable networks have passed, as have the days of hub-

based networks. Advances in the quality of twisted pair cable have meant

that this is now a minimum spec for Ethernet LAN cabling, and the cost of

devices has reduced sufficiently to make fully switched networks a realistic

option. However not only are there advances in technology, but the demands

of network users increase. Networks need to cater for thousands, not

hundreds of users, demand for corporate access to the Internet continues to

rise, and graphics and streaming multimedia demand ever higher bandwidth.

We expect not only to keep up with the technology, but to be at the forefront

of new developments. Where 10/100 Mbps Cat 5 UTP cable was standard

last year, we are now using Cat 5e shielded cable, and Cat 6 100 Mbps cable

as standard. For backbone cables in larger networks we always recommend

1 Gbps fibre as a minimum. 10-100 Gbps LAN technology is on its way.

Please see Section 4.12 for further details on upgradeability in this proposal.

3.4 Security

Too often security is not seen as a priority. Threats come in a number of

guises; from theft or loss of data to physical protection of valuable equipment

from theft or fire; from external hackers and viruses to internal infiltration or

misuse. We always recommend high, but appropriate, levels of security in our

network designs.

Please see Section 6.3 for further details on network security in this proposal.




4 Statement on Mandatory Requirements

By Paul Smith

4.1 Access to Mainframe Systems

The existing mainframe in building 1 is connected to the network using IBM’s

token ring technology on IBM’s SNA. We will be keeping this token ring

network and connecting it to the rest of the network. To do this we are using a

specialist router in this building that can handle both token ring protocol and

the Ethernet outside. This is essential to making the information on the token

ring accessible to the rest of the network. As such the router used in this room

will probably be more expensive than the rest used throughout the site.

Figure 4.1 IBM Token Ring Network (IBM, 1997)




IBM’s token ring has a data rate of just over 4mbps and works in the following

way, it is almost identical to other token rings except it specifies that it should

be set up using a star topology. Each end station is then connected to a unit

called a Multi Station Access Unit (MSAU) it is then this device that is

connected to the rest of the network. If as with the MU site it needs to change

protocol then an intermediary device is needed.

4.2 Building 7’s Unix System

Building seven holds staff that will be using information that needs to be very

secure such as the payroll and personnel information. Because of this we

have taken special care to segment this part of the network in such a way that

nobody outside can get access into this building unless specifically set up to

and the staff within can still get access outside to use features such as the

Internet and files servers across campus.

This has been achieved by implementing two features in this building. Firstly

we have included a bridge behind the router for this building to help

segmentation of the traffic that this building creates which we expect to be

heavily internal using the Unix host to process records. The segmentation in

this way creates a Virtual Private LAN for the building as Norton (2001) points

out VLAN’s cannot communicate directly with other parts of the network

outside of it. Obviously this creates a problem for staff when they want to

access the email or web servers in other buildings. To combat this the

inclusion of a level 3 devices is needed, the bridge or switch used to segment

the network is a level 2 devices and is a good solution to take bandwidth off

the main backbone of the network as well as segmenting it. A level 3 devices

is then needed to make it possible to communicate between the VLAN and

the rest of the network. The level 3 devices we have used are routers that are

used on the main backbone of the network.

Because it is now possible to access the VLAN we need to include some

measures to stop unauthorised access and to monitor what comes in and out

of this section. To do this we have also included a Hardware / Software




firewall between the router and bridge for this building to stop unwanted traffic

from gaining access to the sensitive information. As well as this feature our

network management system will work in conjunction with the firewall and

record data inbound and outbound and helping to give early warnings or

preventing any breach from occurring.

4.3 The Network Availability

The availability of a network is a measurement of the total time in which the

network is in productive use. There are two measurements for acknowledging

this time period; these are as follows:

Mean Time Before Failure (MTBF)

Mean Time to Repair (MTTR)

These figures are then used to create the availability of the network with the

following equation:

‘Availability = MTBF / (MTBF + MTTF)’

So to increase the availability of your network you should do one of two

things, firstly lengthen the time before a failure. Secondly you can shorten the

time it takes to repair those failures once the happen.

ZNYX Networks (2000) specify nine reasons for networks to have downtime.

These are as follows:

Hardware Faults,

Network Faults,

Operating system Faults,

Application Failures,

Human error,

Environmental Conditions,

System Overload,




Security Breaches,

Terrorism.

The document also suggests five ways in which you can combat these

problems. Firstly improving the detection of them, Secondly Diagnosing what

the problems are fast, Thirdly being able to isolate the problem easily,

Fourthly your network being able to recovery from one of these problems with

minimum interference and Lastly improving the speed at which you can repair

the problem.

To create the 98% availability that the MU are looking for we have tried to

address these problems raise by the ZNYX’s document. Firstly to combat the

problems with Hardware faults we have provided backup equipment for the

most important areas in the network, this includes the Routers on the

backbone, switches for each building and specialist equipment such as

hardware firewalls used in building seven.

To improve the recovery from faults in the network we have provided a

backup system for the main backbone that can be connected up if the

backbone suffers any errors. Also to improve the time to a failure in the

backbone we have used a partial mesh topology so that any one building can

still access the network if they lose a connection on the backbone.

To help with the detection of faults on the network we have implemented

Cisco’s network management system CISCOWORKS which has several

features as described in the appendix for recording of network statistics,

monitoring traffic to find potential faults and to log information about all

equipment used on the network to make it easier to maintain the network or

fix errors.




4.4 Media Trunking

REQUIREMENT – M6. 2.1 ALL SURFACE MOUNTED MEDIA MUST BE HOUSED IN SUITABLE

TRUNKING.

All the trunking we use on room floors in our design is PVC and manufacture

to the BS4678 standards all the trunking will be housed using manufacturers

recommendations for installation and every effort will be made to conceal exit

points for cabling by housing this at the back of the PVC trays. The cables

shall also be secured to the PVC trunk in accordance to the manufacturers

recommendations for how this should be done and the distance between such

securing.

Also as well as this trunking we will be covering any cables that are passed

through walls that have been drilled to prevent damage to them.

Cabling between floors and in the cavity space in the ceiling however is

housed in a metal conduit. This is to adhere to European fire regulations that

state that if cables will produce a noxious or hazardous gas then this mustn’t

be transported around the building using the airspace between floors.

4.5 Media European Standards

REQUIREMENT – M6. 2.2 SUPPLIERS MUST GIVE ASSURANCES THAT THE MEDIA THEY INTENT TO

USE WILL MEET, WHEN INSTALLED AND CONNECTED TO WORKING EQUIPMENT, THE CURRENT AND

ANTICIPATED NATIONAL AND EUROPEAN STANDARDS FOR SAFETY, FIRE RESISTANCE AND ELECTRO-

MAGNETIC INTERFERENCE.

European standards have been produced on top of the existing ISO standards

to cover cabling methods and the fire and safety aspects of these. To govern

these standards most European countries have there own standards body

such as the UK’s standards body however more general standards which are

covered in the cabling area have been covered by a European wide standards

body called CENELEC. CENELEC is based in Belgium and the standards for

cabling is equivalent to ISO’s IS11801 standard but with additions for

European communities.




4.5.1 Fire Standards

Unfortunately there have been no minimum requirements for cabling set by

the manufacturers of the product. Cable makers offer products at various

degrees of fireproofing and with various degrees of protection again toxic

fumes and fire spreading. For the best protection again fire it is recommended

that you use special Low Smoke Zero Halogen (LSZH) cables but again some

manufacturers make these cables with only partial covering with fire

retardants such as only the inner core. Whilst this would protect the cables it

doesn’t stop fire spreading and production of toxic gases.

The European standard CENELEC HD405 has two minimum requirements for

fire safety that our company will meet when choosing cabling trunking and the

installation methods these are as follows.

Firstly if flame spread and fire retardant properties only are required for the

cables in an installation, IEC332 Part 3 (which is a fire testing standard)

should be specified.

Secondly if an installation requires full LSZH properties then IEC332 Part 3 for

flame spread and fire retardant (fire testing standards) should be used and as

well as this tests for toxicity should be used via the IEC754 Part 2 for acidic

gas emissions and IEC1034 for smoke emission.

4.5.2 Electromagnetic Radiation

There are several standards for cable manufacturers to make there cabling

limit the Electromagnetic interference as well as this there are also standards

for the producers of electronic equipment to adhere to. These are covered in

the CISPR-22 specification that uses the following CENELEC standards.

EN 50081

EN 50081 is split into two parts; firstly part one covers the emissions

standards required for domestic or commercial and light industrial electronic

equipment. Secondly part two is currently in draft form for industrial

equipment.Dave Portass, Paul Smith, Mike Bailey May 2003



EN 50082

EN 50082 again is split into two parts, this standard is the opposite of

EN50081 in that it covers how much tolerance to EMR that equipment should

have. Part one again specifies the tolerance for domestic or commercial and

light industrial equipment and secondly the part two is in draft form for the

Industrial environment.

EN 55022

EN 55022 is a specification of the limits and the methods of transition of EMR

in information technology equipment this is especially useful for the Midshires

environment to adhere to.

EN 55024

This is a draft standard which is similar to EN50082 in that it covers the

tolerance of electronic equipment however EN55024 is specifically concerned

with the field of Information Technology Equipment. This standard covers the

following areas; Electro Static Discharge, Radiated Fields, Electrical Fast

Transient/Burst, Surges and Conducted Radio Frequency Disturbances.

4.6 Environmental Precautions

REQUIREMENT – M6. 2.3 MEDIA AND OTHER HARDWARE INSTALLATION MUST ALSO MAKE PROPER

ALLOWANCE FOR THE ENVIRONMENT IN WHICH IT IS INSTALLED, PARTICULARLY AS REGARDS,

TEMPERATURE, HUMIDITY, RECEIVED LEVELS OF ELECTRO-MAGNETIC RADIATION AND POSSIBLE

VARIATIONS IN ELECTRICAL EARTH POTENTIAL AT DIFFERENT POINTS AROUND THE SITE.

4.6.1 Temperature Precautions

Temperature can adversely affect the amount of time a cable can hold data

when you install the cables. The hotter the cabling is when installed the less

the distance that can be used between repeaters. For example Category 6

cables laid at 90°C will have a reduced maximum length of 96 meters rather

than 100 meters when set at optimal temperature. This is especially important

when laying cables in airspaces between rooms and trunking up buildings.




This is because these areas are often a lot hotter than rooms inhabited by

people and so this becomes more of a problem.

4.6.2 Humidity Precaution

The humidity of a building can effect the build-up of static this means that a

building with high humidity produces a lot more static charge than one with

low humidity, this of course can effect cables just as the temperature can and

cause noise to be created on the cable and maybe corruption of data.

4.6.3 Electromagnetic Interference

Electro magnetic interference can be created both naturally and be man

made. Electro magnetic interference can interfere with some types of cabling

and so precautions have to be taken in areas known to have this interference

present. This sort of interference can be created in any environment where a

lot of electrical equipment is in use. This has been noted to be the case within

building four at the Midshires University. To combat this problem there has

been developments in cabling to help shield the signals within. So instead of

using the Unshielded Twisted Pair (UTP) cables within these environments

you can use Shielded Twisted Pair (STP) cables that are Category Six.

4.6.4 Electro-earth Interference

Another source of unexpected electrical energy can come from grounding

systems. Electrical systems may be grounded for a number of reasons, most

notably to stop electrocution. However if cabling is present near to a

grounding point then this can obviously cause the same problems as are

present in environments with lots of electrical equipment. As before shielded

cables should be used if they must travel near to such interference, however it

is strongly recommended that you find alternative routes for cables near to

such a force.

Our team will check for these entire element upon the viewing of the

Midshires University Site and take appropriate actions with regards to cabling

lengths and types according to results of such.Dave Portass, Paul Smith, Mike Bailey May 2003



4.7 ‘E’ End Points Protocol Access

REQUIREMENT – M7. 1.1 THOSE ENDPOINTS DESIGNATED ‘E’ MUST SUPPORT DIRECT ACCESS TO

THE ISO 8802/3 PROTOCOL AS DEFINED IN GOSIP V3.1 LAN LAYERS 1 AND 2, FOR SUPPORT OF

100BASET SYSTEMS.

The ISO 8802/3 or IEEE 8802.3 is the specification of the Ethernet protocol

used today on thousands of networks as the means of communication. ISO

8802/3 is a level 2 protocol meaning it works on the Data Link level of the ISO

Protocol Diagram as shown below;

Fast Ethernet is an improvement upon standard Ethernet in that it can support

speeds of 100BaseT. The Ethernet specification is split into the two levels of

Data Link and Physical. Running on the Data link level there is a Media

Access Control (MAC) that is responsible for formatting the information for

travel and the way in which it will be sent. The lower level physical layer is

then concerned with getting the data onto and off the designated medium

used for the network.

GOSIP Version 2.0 specifies the use of ISO 8802/2 or Logical Link Control

(LLC 1) as the highest-level part of the Ethernet protocol on the Data Link

layer as a means for controlling the rest of the Data link layer and physical

layer chosen below.

GOSIP also states that X.25 is the most common protocol used for the

physical layer in conjunction with the above.




Figure 4.2 The OSI Reference Model (Tanenbaum, 1996)

4.8 Compatibility with Windows-NT and Novell Protocols

REQUIREMENT – M7. 1.2 THE LAN INFRASTRUCTURE INSTALLED MUST BE COMPATIBLE WITH

BOTH MICROSOFT WINDOWS NT AND NOVELL NETWARE PROTOCOLS.




Windows NT uses the NetBEUI protocol to access the network with and any

lower protocol in use, such as Ethernet in the Midshires case. However IBM

use a different service called NetBios to achieve this and Novell use yet

another protocol using their software NetWare

Windows NT can get direct access to IBM systems using an inbuilt driver

called the Data Link Control (DLC). The DLC also provides the ability to

connect to IBM Mainframes directly. However the DLC is not recommended

as the primary protocol of use for communication over the network and should

only be used for the cross over to either IBM or accessing independent

devices on the network.

The NetWare Software uses the IPX/SPX protocol to in its software as a point

to start communication with the Ethernet or other lower protocol used on the

network. Parts of this software such as NWLink set up a link directly to the

protocol(s) used on the system except if it is a specialist type such as the IBM

token ring. If it NetWare isn’t installed on all clients on the network it is

possible to provide a gateway instead for these clients to use to access the

protocol.

Other problems of communicating between these types of servers comes

from the fact that each different service offers different interpretations on

hardware and how they run, this obviously causes an extra problem when

trying to send data from one service to another. These problems of cross,

communicating cease to exist though however when information is sent

through the OSI model which Ethernet ISO 8802.3 is part of. The ISO model

works by breaking down messages into manageable components that can be

understood universally by all the top-level vendors. They are then rebuilt once

sent and will be able to be read by all.

4.9 ‘V’ and SNA Connections

REQUIREMENT – M7. 1.3. THOSE ENDPOINTS DESIGNATED ‘V’ MUST SUPPORT SNA-

CONNECTIONS TO ONE OR MORE OF THE OTHER ‘V’ OUTLETS.




IBM developed system Network Architecture (SNA) in the early 1970’s as a

response to the fact that large companies were often unwilling to put

automated processes through networks that they saw as unreliable. IBM’s

solution to this SNA took the approach of setting up a network so that it could

handle almost all errors that occurred automatically. This worked quite well

when the network is heavily planned and set up correctly however it doesn’t

work quite so well on a network being grown over time.

In SNA networks computers don’t just share information, they first have to

create a session. This is usually done through an intermediate such as a

mainframe computer. We will set up the Midshires mainframe computer as

such an intermediate if it isn’t already so. So that SNA connections can be

created between any V connections on the network once a session is created

over the network.

SNA networks have literally the opposite values of that using TCP/IP in that

whilst the SNA connections are very robust and if set up correctly run very

well however they are very complex to set up and run and so TCP/IP systems

which are easily set up have become more popular. TCP/IP systems however

will often generate lots off errors that aren’t even recognised when they would

be on SNA and dealt with automatically.

4.10‘E’ and ‘V’ Outlet Conversion

REQUIREMENT – M7. 2.1. IT MUST BE POSSIBLE TO MAKE CERTAIN ‘E’ DESIGNATED END POINTS

INTO ‘V’ DESIGNATED ENDPOINTS AND VICE-VERSA, WITH MINIMUM OF EFFORT. DESCRIBE THE

EFFORT INVOLVED IN PERFORMING THESE CONVERSIONS.

The conversion of an end point from either E to V or visa versa will require the

following. Since we are using Cisco Routers we can use a Cisco tool called

Enterprise Extender (EE) to provide a conversion of end points to work as if

they are IP networked with minimum of ease. This is a less costly alternative

to rerunning either swapping the cabling to an end point or using spare end

points provided for this service. The EE provides a direct link to the IP network

through the router set up on the backbone and by passes the regular SNA




networking method of creating sessions using the IBM host. The EE however

makes this end point slower than if it was running on genuine IP but the cost

benefit and time to install make it a valid alternative.

4.11Outlet Indication

REQUIREMENT - M7. 2.3. THERE MUST BE A SIMPLE INDICATION OF WHETHER A PARTICULAR END

POINT IS ‘V’ CONNECTED OR ‘E’ CONNECTED. THIS MUST BE UPDATED AS PART OF THE

CONVERSION DESCRIBED IN M7. 2.1. SUPPLIERS ARE ASKED TO DESCRIBE THE SYSTEM OF

INDICATION PROPOSED, AND THE MEANS OF MODIFYING IT WHEN CHANGING FROM V CONNECTIONS

TO E CONNECTIONS AND VICE-VERSA.

We will be using two methods to help the distinction between end point types.

Firstly the use of different colour cable ties for the cables in the end points.

Also we will provide a simple notification via a label method attached to each

end point frontage. The all V, E and N end points will be recognisable by both

colour and by code.

We will use the existing codes provided by the Midshires University to

implement this system so they will appear as follows:

Ethernet Connections - E / End Point Number / Patch Panel

Token Ring Connections - V / End Point Number / Patch Panel

Un-Connected - N / /

The modification of these end points will just be a case of recording the

changes and updating the frontage stickers as the cabling should all be tied

appropriately anyway.

4.12Infrastructure Expandability

REQUIREMENT – M7. 3.1. THE LAN INFRASTRUCTURE MUST BE CAPABLE OF EXPANSION TO MEET

POTENTIAL FUTURE TRAFFIC GROWTH AS WELL AS GROWTH IN GEOGRAPHICAL COVERAGE AND AN

INCREASE IN END SYSTEM CONNECTIONS AND / OR USER POPULATION.




There are several measures that we have taken with regard to the expansion

of the network at the Midshires University. Firstly to keep the traffic off the

backbone as much as possible we have segmented each building into what is

essentially a VLAN as we have provided a bridge in most rooms such as

building seven to segment the traffic, however the bridge isn’t placed onto the

actual backbone and is then connected to a router which is. This enables the

backbone controllers to be free for longer and ensures that all local traffic is in

fact only affecting the local part of the network.

The backbone that we will install is using a Fibre mesh topology this ensures

that the cable will be able to handle more traffic over time, as fibre cables

don’t run at full capacity at the present time. However if this becomes an issue

in the future then we suggest the following steps be taken before undertaking

this exercise. Firstly when migrating the backbone you should still think about

running the old network in parallel as this may take time to achieve. Secondly

the swap over to the new backbone could be taken in one of two approached

firstly connecting the new network backbone to the network and phasing out

the old once the new is running or secondly doing a straight swap over. The

two method both have plusses and minuses for instance although running two

backbones concurrently provides the robustness when converting it will also

probably be expensive to program your routers to perform this for such a short

time if different protocols are used. However a straight switch over is highly

problematic especially if the network needs to be running straight away.

There are two options for the swap over of parts of the network to quicker

protocols or topologies these are as follows:

Start-at-one-end migration

Leveraged segment migration

Both these options use a method of taking a small section of the network and

updating it accordingly then moving onto the next. The option of start-at-one

end migration is based on geography of the network and performing changes

as you go across the network whilst Leveraged segment migration is based

on converting the important areas first followed by the less important ones.




Any increases in Internet have been factored into the design of the Midshires

site in that we have put a direct link onto the backbone of the site using gigabit

Ethernet. This ensures that any increases of bandwidth that are provided over

time should be manageable over the network. To increase the security there

are several things which could be done, firstly our network managements

system provides excellent monitoring for networks firewalls and so if extra

area of the network become security specific then new licences for this

software can be purchase and used to monitor then as VLAN’s.

4.13Call-out Service

REQUIREMENT – M8. 2.2 A CALLOUT SERVICE APPROPRIATE TO THE SERVICEABILITY

REQUIREMENTS OF SECTION *.1, MUST BE PROVIDED FOR THE REMEDY OF SOFTWARE AND

HARDWARE FAULTS, EITHER BY REPAIR OR REPLACEMENT.

Any Hardware of Software faults either due to faulty equipment or failures on

the network the first option should always be to consult the list of spares that

were provided with the installation of the network. If this solves the problem

then make sure to follow the guidelines for replacement of spares.

The next option should be to call our company help phone line, which can

handle all customer enquiries and provide basic support for technical

assistance with fault finding and fixing of faults.

Once faults have been found then a team of engineers can be sent upon

request to replace and install any faulty equipment if under guarantee.

Alternatively the equipment can be sent out for your technician staff to install.

4.14Fault Escalation Procedure

REQUIREMENT – M8. 2.3. A FAULT ESCALATION PROCEDURE INVOLVING SENIOR MANAGEMENT AND

SENIOR TECHNICAL STAFF MUST BE AVAILABLE IF FAULTS ARE NOT RECTIFIED WITHIN AGREED

TIMESCALES.

Level One Fault (Localised faults)




Any localised faults that do not affect the backbone of the university site or the

vital part of the sites running can be handled by our first level response of a

customer support phone line. The phone line is manned from 8:00-22:00

weekdays and can provide technical feedback on installation of spares to the

tracking down of error within the network (our phone number – +44 (12345)-

678901)

Level Two Fault (Important Areas of Network)

If the problem cannot be solved by phone support of the problem is effecting

the running of your company we provide a call out service for our engineering

staff to fix the problem with your network.

Level Three Fault (Backbone Failure or Level Two Fault after 12 hours)

If there has been a total loss of the network or a level two fault isn’t corrected

in a 12-hour limit from the time of the fault then a company executive will be

sent with a company team to fix the problem.

4.15End-to-end Testing

REQUIREMENT – M9. 4.1. END TO END TESTING OF THE NETWORK MUST BE PROVIDED, INCLUDING

OVER THE LONGEST END-TO-END ROUTE IDENTIFIABLE.

End to end testing of the network is an important consideration when creating

your networks. Our installation team will provide end to end testing to the

following specification. Firstly we will test the sending of information through

all types of equipment to find any problem areas. We will also provide several

tests of cross protocol connections to make sure all conversion processes are

working correctly.

Lastly to provide we will use echoplexing to find the longest and shortest

routes through the network.




5 Statement on Desirable Requirements

By Paul Smith

5.1 Communications Equipment Standards

DESIRABLE – D6. 1.1 EACH PRODUCT USING COMMUNICATIONS PROTOCOLS SHOULD HAVE BEEN

INDEPENDENTLY TESTED AND BEEN FOUND TO CONFORM TO THE APPROPRIATE GOSIP, OSI OR DE

FACTO STANDARD(S) AS APPROPRIATE.

Our installation shall follow relevant local and international standards in

ensuring that all equipment media and installation processes are adhered to

below are a list of the standards we will make sure are used and that all

equipment that we purchase and install uses in it manufacturing process.

5.1.1 General Cabling Standards

Our standards are all specification made by the major international

organisations such as the ISO or relevant local organisations such as

CENELEC who make all relevant European standards in Belgium and any

localised standards to the UK.

5.1.2 Fire and Safety Cabling Standards

British Standards

NES 713 (Toxicity test),

European Standards

EN 50173,

EN 50167,

EN 50168,

EN 50169,

prEN 50174

International StandardsDave Portass, Paul Smith, Mike Bailey May 2003



The International Standards Organisation (ISO),

International Electrochemical Committee (IEC).

IEC 61935,

ISO/IEC 14763 (Implementation and Operation of CPC),

IEC 332 (Flammability and fire retardance),

IEC 754 (Corrosivity and aciditivity),

IEC 1034 (Smoke Emissions)

5.1.3 Electromagnetic Radiation

European Standards

EN 50081 (emissions of radiation)

EN 50082 (tolerance to radiation)

EN 55022 (emissions of information technology equipment)

prEN 55024 (tolerance of information technology equipment)

5.1.4 Other Standards

British Standards

BS4678 (Cable Trunking)

European Standards

EN 50173 (Generic cabling systems)

5.2 Twisted Pair Cabling should be at least Cat 5.

We will use a selection of the following cable in the design of the Midshires

network.

Category 5e

Category 6




Fibre Pair

The main backbone for the network will be all installed as fibre pairs; this is to

ensure the upgradeability of the network in the future as well as the fast

running of the backbone in the present environment.

Category 6 cable will be used in most buildings for trunking up the buildings

and in the plenum space on floor roofing space. This is to ensure that the

cable in this area that could come into contact with EMR and must follow local

guidelines on fire and safety will be followed. Cat 6 will also be used in

building 4 on the main building floors usage this is because of the buildings

purpose of teaching using electronic equipment. With this sort of environment

the use of Cat 6 is preferred to alleviate noise as discussed in the mandatory

section of this report.

All other areas of the building use Cat 5e cabling, as on the initial survey there

have been no other sources of electromagnetic radiation or static found.

However when the company do our comprehensive review of the area we will

modify this plan if extra sources of radiation are found. This will be reflected

on the overall price plan.

5.3 Outlets should be RJ45 for Unshielded Twisted Pair

Cable.

DESIRABLE – D.7. 1.5. OUTLETS SHOULD BE RJ45 FOR UNSHIELDED TWISTED PAIR CABLE.

All cabling used within the buildings uses category 5e and 6 cabling this

ensures that all end points will support a RJ45 connection to the network.

RJ45 is the standard connection type for Ethernet cable connections and is

essentially similar to a phone line connector except its connection is several

times larger.

5.4 List the Protocols used on the Network

DESIRABLE – D7. 1.7 SUPPLIERS ARE ASKED TO GIVE DETAILS OF PROTOCOLS THAT ARE

SUPPORTED AND HOST SYSTEMS TO WHICH THEY ARE CONNECTED.




Our implementation of the network will use the following protocols to provide

coverage to all systems in the Midshires University. Firstly the physical layer

protocol used will be standard X.25 protocol. X.25 is has been recommended

by the International Consultative Committee for Telegraphy and Telephony

(CCITT) as the protocol of choice for physical level communication. X.25 is a

packet switched data network protocol that is connection orientated and

defines the recommendation for the exchange of the data across the network.

The Level two Protocol used will be Ethernets standard ISO 8802/3 or IEEE

8802.3 Ethernet uses a MAC layer to help format the information which is to

travel the network. I also use this MAC address that is unique to address the

target PC.

Other protocols used on the network include Novell’s NetWare software which

uses the IPX/XSP protocol, NT’s servers use the NetBios system which can

use any of the NetBEUI, NetWare IPX/SPX transport, TCP/IP protocols and

IBM which uses the SNA protocol.

5.5 ‘V’ Outlets and Concurrency

DESIRABLE – D7. 1.7. ‘V’ OUTLETS SHOULD SUPPORT A CAPABILITY TO ESTABLISH MORE THAN

ONE CONCURRENT CONNECTION FROM A TERMINAL TO OTHER HOST SYSTEMS RESPECTIVELY.

To provide more than one concurrent session on the IBM token ring system

we will use the Advanced Peer-to-Peer Networking (APPN) system to create

multiple connections to the host. The APPN system uses a process or

Dependant Logical Unit Receivers / Servers (DLUR/DLUS) these are used by

either the receiver or server to create a session between the two parties. This

method can then be used to create extra concurrent connections between the

host system and others.

This service also provides an automatic network shutdown service (ANS)

which shuts down the dependant terminal when left unused, this service also

record what state the session was in when the session is terminated so that it

can be re-established from that point if needed.




The APPN also provides ways to swap on end terminals session to another

for reasons such as power outages.

5.6 Additional ‘V’ or ‘E’ Sockets

DESIRABLE – D7. 2.2 WHERE NECESSARY IT SHOULD BE POSSIBLE TO PROVIDE EXTRA ‘V’ OR ‘E’

SOCKETS ADJACENT TO EXISTING ‘V’ OR ‘E’ SOCKETS RESPECTIVELY.

The design we have provided can use extra V or E connections at end point

depending on when Midshires would like to implement these. This will not cost

the Midshires at all as the network has been designed to provide extra points

in end floor switches and spares for the connection of these switches to patch

and end points.

However extra trunking may be needed as well as end point facings however

the cost for these items should be minimal and perfectly within the budget

suggested.

5.7 Serviceability Between ‘E’ Outlets

DESIRABLE – D8. 1.1. THE REQUIRED NETWORK SERVICEABILITY FOR AN ‘E’ CONNECTED END

SYSTEM TO ANY OTHER ‘E’ CONNECTED END SYSTEM SHOULD BE GREATER OR EQUAL TO 99.95%

WITH A MTBF OF 8000 HOURS.

We provide high serviceability of all E end points by many methods, these

methods all draw on making the network more robust and less redundancy to

the end user. Firstly the backbone has a backup fibre pair so that any

downtime for this is minimal. Secondly the installation team shall provide

spares for all parts of the network that are vulnerable to faults. This includes

the following equipment:

Routers

Switches

UPS

Cat 6 Cable




Cat 5e Cable

Patch Panels

Patch Cables

This means that any equipment on the network that goes wrong can be

installed and put to use without the need to call for support from our team.

Also any software faults causing problems with network management can be

supported as we provide backup servers that can take over monitoring the

network if first systems go down.

Lastly we will provide second to none technical support via our help line which

can deal with requests about equipment installation, information about

ordering of spares and the installation and use of software installed by the

installation team.

5.8 Serviceability Between ‘V’ and ‘E’ Outlets

DESIRABLE – D8. 1.2. THE REQUIRED NETWORK SERVICEABILITY FOR A ‘V’ CONNECTED END

SYSTEM TO AND OTHER ‘V’ OR ‘E’ CONNECTED END SYSTEM SHOULD BE GREATER OR EQUAL TO

99.9% WITH A MTBF OF GREATER THAN 8000 HOURS.

Serviceability between V and E end points is similar to between Ethernet only

but with a few extra considerations taken places. Below is a list of other

hardware that is provided by the installations team as spares at the time of

installation to make the network more robust.

Specialist Router Backup (Has conversion capabilities)

IBM Token Ring cable

Spare parts for IBM mainframe that need to be active to achieve

sessions

As well as this the network needs to provide robustness for specialist software

that is used for either connecting to NT or Novell servers or to connect via

SNA to the IP network.




Again much like the serviceability between Ethernet only connections we can

provide technical support for any software problems relating to the

communication between the IBM and IP networks and we will give advice and

solutions to installation and set up of specialist hardware.




6 Further Information Required From Suppliers

By Paul Smith

6.1 Standards Used

QUESTION – Q6. 2.4. THE SUPPLIER IS REQUIRED TO STATE WHAT INSTALLATION STANDARDS OR

CODE OF PRACTICE(S) WILL BE ADOPTED.

The installation team will use the following standards in choosing products to

installation to safety on site. The mains standards bodies that have been used

for information are as follows;

International Organization for Standardization (ISO)

International Electrotechnical Committee (IEC).

CENELEC

IEEE

The following lists of standards have been taken into consideration in the

development of this plan and will be used to implement our design if

successful.

British Standards

NES 713 (Toxicity test),

BS4678 (Cable Trunking)

European Standards

EN 50173,

EN 50167,

EN 50168,

EN 50169,

prEN 50174

EN 50081 (emissions of radiation)




EN 50082 (tolerance to radiation)

EN 55022 (emissions of information technology equipment)

prEN 55024 (tolerance of information technology equipment)

EN 50173 (Generic cabling systems)

International Standards

IEC 61935,

ISO/IEC 14763 (Implementation and Operation of CPC),

IEC 332 (Flammability and fire retardance),

IEC 754 (Corrosivity and aciditivity),

IEC 1034 (Smoke Emissions)

ISO17799 (Security Management)

6.2 Customer References

QUESTION – Q7. 1.4. A LIST OF SUITABLE CUSTOMER REFERENCE SITES IS REQUIRED WITH

SITES INDICATING WHERE A VISIT MAY BE MADE BY MU IF REQUIRED.

Our company has been running for many years and has installed networks of

a comparable size to the Midshires University all over Europe. Below is a list

of three such companies that have agreed to accept visits from potential

customers.

Frankfurt University – This system uses the same topology as suggested in

this plan of a partial mesh. However extra consideration had to be taken with

this design as the university houses a chemicals research plant.

Nottingham City Hospital – The recent redevelopment of the City’s hospital

created the need for changing and updating the hospitals current network to

encompass new buildings and to redesign older areas of the network that

were considered outdated.




Toyota Manufacturing Plant – This project was different as it provided the

environment where not many systems were needed but what was to be

installed had to be suitably robust to handle a electrically noisy and

unpredictable environment.

6.3 Network Security

QUESTION – Q7. 4.2. SUPPLIERS ARE REQUIRED TO DESCRIBE IN DETAIL HOW THEY INTEND TO

ENSURE THE SECURITY AND INTEGRITY OF MU END SYSTEMS ONCE CONNECTED TO THE INTERNET.

The security of the network has been looked at in the design for this system.

Areas of interest occur on both the insider looking through the network and

the outsider looking into the network from elsewhere (the internet).

To protect the system from hackers we have installed a hardware and

software firewall between the university and the Internet connection. As well

as this we have provided a bridge behind the firewall for easy isolation of the

Internet connection if there is a break in security. Also on top of this we will

install Cisco’s network management solution for security that has advanced

features for both monitoring of network usage but also blocking and reporting

breaches.

To protect the system internally we have provided many different methods,

firstly to secure the systems in building seven from the rest of the university

we have installed a second firewall and management system in this building

so that no unauthorised access to data in this restricted are can take place

unless strictly prohibited.

Also internal to the network we suggest the setting up of several systems as

referenced from ISO17799 which states that you should create a security

policy for the university which gives details about who can access which

information on the network, how this should be segmented and what should

happen if a security breach occurs.

The second thing to note is the running of the security operation at the

university this should be clearly specified with roles of senior staff decided on




and what there duties are with regards to the security of data over the

network.

Then to access the system there should be appropriate security controls on

access for example passwords and authentication for staff and students alike

so that monitoring of user activity can be set up correctly via the network

management system we shall provide.

6.4 Internet Functionality

QUESTION – Q7. 4.2. SUPPLIERS ARE REQUIRED TO ADD FURTHER INFORMATION ON PROVIDING

ENHANCED INTERNET FUNCTIONALITY SUCH AS REMOTE ACCESS, DISTANCE LEARNING AND

CONFERENCING SOLUTIONS.

6.4.1 Remote Access

Flexibility is the most important aspect of any remote access network. Remote

networks need to be able to integrate quickly with emerging technologies as

new sites are added to the system.

This adaptability is required because of the resources needed by the end host

can change over time either growing or shrinking. Through our research we

have found that the best approach to any remote site is to start small

successful system are ones that start small and grow to meet the demand set

by employees. The setting up of a core group is important to get a perspective

on the potential problems that could be encounter as the remote access

grows. This could be because of different lines of connection or equipment at

the host site.

6.4.2 Video Conferencing

To create a video conferencing system certain extra equipment must be set

up by the MU at both the sender and receiver of video feeds. This equipment

includes cameras, microphones and speakers. The quality of the video feed

produced is dependant then upon the amount of bandwidth that can be used

for the service. Obviously if this was an internal operation then this would be




cheap however if you plan to use the internet to transmit the images then the

better the quality of image the longer and more expensive it will be to send

and maintain.

From our companies research we have found that to achieve a smooth video

feed with both audio and video at 15-30 frames a second the bandwidth

needed would be around the 384 Kbps. This is of course maintainable on the

MU’s current system however on a 1 Megabit connection it is using just under

half the bandwidth so it may effect other operation in the university, and the

MU should note that all Internet activity will compete with each other and so

this may produce jerky or broken pictures in the video feeds.

6.4.3 Distance Learning

Distance learning can be developed by in house or by contractors. Essentially

however it is basically an extension of the company’s intranet over the

Internet. To make this secure it is best to house this sort of system outside

any firewall protection. Then any documents that are to be shared in this

system can be stored here and shared by use of a web distribution service

without giving the outside world access to the network within.

6.5 Network Backbone

QUESTION – Q8. 1.3. SUPPLIERS ARE REQUIRED TO DESCRIBE IN DETAIL HOW THEY INTEND TO

ACHIEVE THIS LEVEL OF SERVICEABILITY AND ARE REQUIRED TO PROVIDE QUANTITATIVE

JUSTIFICATION FOR THERE CLAIMS.

The backbone topology that we will use in the design of the system is using a

partial mesh topology. This enables a lot more robustness in the design, as

there is more than one route into and out of each building, in fact in some of

the buildings that will use the highest bandwidth there are more than 2

connections. Building two for instance has four pairs of fibre as its backbone

connection.

This provides adequate robustness to the design but to allow for high

serviceability we have also included a set of spare fibres allowing each route.




This will allow for speedy change over if a fault does occur in any of the

segments. This is also without the network being affected as the robustness in

the design means the routers can find alternate routes thought the system.

At the same time we have also allowed for keeping the routers on the network

as free as possible through the segmentation of each building. This has been

achieved by adding a switch or bridge behind the routers in each building

essentially making sure that any traffic generated in the buildings LAN only

traffic which is meant for outside that building will actually access the

backbone or ever the router which is on it. This frees the backbone up for

transporting traffic solely for file servers and Internet traffic.

6.6 Warranty

QUESTION - Q8. 2.1. SUPPLIERS ARE REQUIRED TO STATE WHAT LEVELS OF WARRANTY IS

INCLUDED IN THE PRICE OF EQUIPMENT. PLEASE SPECIFY THE LENGTH OF WARRANTY, THE TERMS

OR WARRANTY AND ANY ADDITIONAL COSTS.

All hardware incorporated into the design of the Midshires campus is included

in a limited warranty. This warranty enables the University to obtain new

equipment for free however delivery charges will be in effect. The warranty of

all equipment supplied will be set according to manufacturers guidelines about

average lifeline of equipment and cost of repair of equipment.

Thus Routers connected to the main backbone will have a warranty of 5

years. Switches and bridges on the network will have a warranty of 3 years

and other hardware connected to the network including files servers and

firewalls will have a warranty of 4 years.

The warrant of these items will be invalidated if unqualified staff have tried to

fix the items in question or if the fault was not made during normal running of

the network. Improper use of the said product will result in the warranty being

invalid also.

Software disc failures can be replaced via postal services free of charge.




6.7 Maintenance

QUESTION – Q8. 2.4. SUPPLIERS ARE REQUIRED TO SUGGEST A RANGE OF MAINTENANCE

OPTIONS AND TO DESCRIBE THE CORRESPONDING DEMANDS ON MU PERSONNEL. PLEASE STATE

LEVEL OF EXPERTISE NEEDED, SPARES NEEDED AND WHAT WILL BE PROVIDED.

6.7.1 Technical Expertise of Technician staff

The staff hired by the Midshires will be offered the chance to attend a detailed

training of all duties that they will be responsible for one the network. These

duties include the following;

Monitoring of network using the network management system provided. This

task although it may take some time to train staff to use the required software

one they are familiar with it Cisco have made the product easy to use and so

the level of expertise should be fairly low for this practice.

Faultfinding. However the finding of faults isn’t always as simple as the

monitoring software telling them where faults have occurred. The service will

give hints but the staff should have enough expertise to be able to use

equipment to find cable usage, finding bottlenecks broken links or cable

working below par. Again equipment has been provided in the design plan for

this facility and training will take place on how to use this.

Repairing. Technician staff will also be expected to have reasonable skills in

repairing problems with PC’s connected to the network and with simple repair

to the other hardware elements on the network.

Installation. Lastly the technician staff will be expected to be able to install and

configure any of the devices supplied in the design. This includes

programming of routers that requires more technical knowledge.

Spares Supply. In the design plan for the MU we have provided spares for all

major items within the network. It is recommended that you update this

stockpile whenever an item is used to makes sure that the network

experiences as little down time as possible.




6.8 Testing Scope

QUESTION – Q9. 4.2. THE SUPPLIER IS REQUIRED TO RECOMMEND THE SCOPE FOR END-TO-END

TESTING SPECIFIED IN THE MANDATORY REQUIREMENTS SECTION.

The scope of the end-to-end testing that is described in the mandatory

requirements section is to provide tests for all equipment using a route

through all types of equipment on the network. This will ensure that the

equipment installed can access any other piece of equipment on the network

if it is allowed. Also we will test all interactions between different protocols on

the network to ensure that conversions are happening in the correct manner

with no errors occurring because of this.

Lastly we will provide end-to-end testing for finding the longest route in the

network and to provide the shortest route.




7 Description of System Proposal

By Dave Portass, Paul Smith, Mike Bailey

7.1 System Overview

The proposed network is an Ethernet Local Area Network (LAN), with specific

connections to the existing legacy IBM mainframe, and the various Novell, NT

and Unix servers (see Sections 4.8 & 4.2). At the core of the network is a

high speed (1Gbps) fibre-optic backbone (see Figure 7.3). This is connected

in each building by a series of routers. Resilience is built in by having multiple

connections to each building and, therefore, multiple routes between them

(see Section 6.9). Spare fibre cables will be laid alongside so that they can

be connected immediately if an existing cable fails, to minimise the downtime.

Within each building Cat 6 Ethernet cable is used to link the backbone to

distribution switches on each floor. From these Cat 5e cable is used to

connect the network to individual outlets in all buildings except Building 4.

Because of the electrical machinery in that building Cat 6 cable is used

throughout to protect from interference.

Building 1 has the addition of a bridge after the router connection in order to

segment the mainframe traffic within that building (see Section 4.1). Building

7 has the addition of a hardware firewall after the router to isolate traffic in that

building for security (see Section 4.2).

Building 2 is somewhat more complicated. To cater for the Geography group

on Level 1 a bridge has been inserted to segment that area. Levels 2 and 3

have the standard switch configuration. For the Computing group on Levels

4-7 an additional router has been inserted to segment that area. This will be

located on Level 4. The Internet connection has been routed through a

hardware firewall to the web server. This then has a direct connection to the

backbone router with Cat 6 cable. See Figure 7.4 for an illustration of these

details.




Figure 7.3 Network Backbone




7.2 Logical Connections

Figure 7.4 Logical Connections




7.3 Physical Connections for each Building

At every distribution point, each patch panel has inputs from more than one

switch to maintain a level of operation in the event of switch failure.

Figure 7.5 Building 1 Physical Connections




Figure 7.6 Building 2 Physical Connections (1)




Figure 7.7 Building 2 Physical Connections (2)





7.4 Communications Protocols

Our implementation of the network will use the following protocols to provide

coverage to all systems in the Midshires University:

Level one Protocol – X.25

Level Two Protocol – Ethernet (ISO 8802/3)

Novell Protocol – IPX/XSP

NT Protocol – TCP/IP, IPX/XSP or NetBEUI

IBM Token Ring Protocol – SNA

For further details see Section 5.4.




7.5 Network Management

We will include two sets of software for the management of the university

campus, Firstly we will provide a system for the general management of the

system and secondly the security of various areas within the university.

7.5.1 General Management

1 x CiscoWorks LAN Management Solution – (ver. 2.1).

Complete package – 1 server.

Provides Performance Management, Configuration Management, Accounting

Management and Fault (Event) Management. See Appendix 1 for further

details.

This Includes:

Cisco nGenius Real Time Monitor - The nGenius Real-Time Monitor is software for the monitoring, troubleshooting and maintenance of traffic over your LAN. IT is web enabled and so can be used remotely. It includes applications for Packet analysis and traffic monitoring.

CiscoWorks Device Fault Manager - This piece of software provides various tools for data collection and analysis techniques. It also has features to find faults and alert the network administrator, via email or onscreen display.

CiscoWorks Campus Manager - Campus Manager provides powerful Layer 2 tools for configuring, managing, and understanding complex physical and logical infrastructures.

CiscoWorks Resource Manager Essentials - This part of the software package is to manage the inventory, configuration, and software updates in Cisco routers and switches.

CiscoWorks CiscoView - Is a device manager that provides dynamic status, monitoring and configuration information.

CiscoWorks CD One - This is the part of the software that integrates

everything together.

Cost for 1 license: £13464.99 (15821.36 inc VAT).




7.5.2 Security Management

2 x CiscoWorks VPN/Security Management Solution – (ver. 2.1).

License only – 1 server, unlimited devices.

Provides Security Management, including Firewall and Router Monitoring.

See Appendix 1 for further details.

This includes:

CiscoWorks VPN Monitor - Allows network administrators to collect, store and view information on VPN connections.

CiscoWorks Resource Manager Essentials - A set of tools for switches, routers and access servers that make administering the network easier to manage.

CiscoWorks CiscoView - Also provided in Cisco’s LAN Management Solution

CiscoWorks CD One - Also provided in Cisco’s LAN Management Solution

CiscoWorks Common Services Software - A set of tools that help with the management of the security on your LAN network, via the creation of User roles and access privileges.

Cisco IDS Host Sensor - Cisco IDS Host Sensor and Console can identify an attack and prevent access to critical server resources before any unauthorized transactions occur.

CiscoWorks Auto Update Server Software - Supports a pull model of configuration that can be used for the initial configuration, configuration updates, operating system updates and periodic configuration verification.

CiscoWorks Management Centre for IDS Sensors - Management software for the configuration of Network IDS and Switch IDS sensors.

CiscoWorks Management Centre for PIX Firewalls - Provides coverage and management for up to 1’000 Cisco firewalls.

CiscoWorks Management Centre for VPN Routers - Provides scalable security management for the configuration and deployment of VPN connections.




CiscoWorks Monitoring Centre for Security - Provides a unified server

to capture, view, correlate and report on events from Network IDS,

Switch IDS, Host IDS, PIX and IOS devices.

Cost for 1 license: £10628.99 (£12489.06 inc VAT).

7.6 Main Components Used in the Network

Cisco 7507 Router

Cisco Catalyst 3550-48 Port Switch

Cisco Systems Expansion module – Gigabit EN – fibre optic, 1000Base-SX – 1000 Mbps – 2 port(s)

Cisco Systems Expansion module – 16 port(s) – 1000Base-T – 1000 Mbps – Gigabit EN

Cisco 585 LRE Bridge

Cisco Catalyst 6503 Firewall Security System

Further details of each of these can be found in Appendix 3.

7.7 Additional Equipment Required

7.7.1 Equipment Required to Install the Network

No-Nik Fibre Strippers 3 Piece Kit

Professional RJ Crimping Tool with Ratchet

LSA contact / Krone Tool

Belkin Tool Kit

Pan-Quik Hand-Held Printer

Universal Labels

7.7.2 Equipment Required to Support the Network

Simplifiber – SC connectors Fibre Tester




Omniscanner 2 – Handheld Cat5e & Cat6 Tester

Rechargeable Nicam Battery for Omniscanner 2

Cat 5e and Cat6 Channel Adapter for Omniscanner 2

32Mb memory card for Omniscanner 2

7.8 Additional Items Required from MU

Provide any specialist equipment for access in particular areas – ladders etc

Protection information relating to lab environments – dangerous chemicals etc

Provide Instructions regarding your emergency fire and safety procedures for any staff working on site.

Provide the office space & support for use by installation team

A list of the current software that is being use to help in the upgrading of the network.

Provide a scheduled time for training of technician staff for new

procedures and maintenance techniques.




8 The Project Plan

By Mike Bailey

The following section provides an overview of our Project Plan, with particular

reference to the plan for installation. The plan is subject to agreement at

initial planning meetings with MU should we be awarded the contract.

The plan is divided into six phases. These describe different areas of the

work rather than being chronological stages. Therefore there will be some

overlap in when these phases take place. The six phases are as follows:

1. Initial planning meetings and environmental study.

2. Installation of cabling, equipment, and software.

3. System testing.

4. Training of technical staff, documentation, and handover to MU.

5. Service and support of the network – to be agreed.

6. Future maintenance and upgrades – to be agreed.

This plan deals primarily with the first four phases. Please see Figure 8.13 for

a Gantt chart showing this period. The tasks are colour codes as follows:

Blue General meetings, Training, etc

Green Cabling

Purple Equipment and Software Installation

Red Testing

The green arrows show the deadline dates for tasks as detailed in the OR.

Some dates have been adjusted to take them from a weekend into the

nearest week day.

On the following pages are further charts showing the individual phases in

more detail.




Figure 8.13 Project Plan




8.1 Phase 1 – Planning and Site Audit

See Figure 8.14.

After the award of contract on July 17 we would propose to hold final planning

meetings with MU during the following week, so that we can agree on

commitments and project milestones by the deadline of July 28.

We would immediately conduct our Site Audit, or Environmental Study, from

July 28, to be completed by August 1. It is from the start of this week that we

would request the use of office space for our team on site. This team will be

headed by Dave Portass.

We have allocated the following week to enable us to finalise the designs

following the site audit. Any significant changes will be discussed with MU.

During these three weeks we will also be finalising our own arrangements for

the installation, including sub-contractors and ordering of equipment and

software. This is in preparation for the start of cabling on August 11.

8.2 Phase 2 – Cabling, Equipment, and Software

See Figure 8.15.

We anticipate that cabling will commence on August 11. There will be four

separate installation teams working on site. Because of the timescale we will

require two teams working simultaneously in the buildings throughout this

period. These will be sub-contracted cabling specialists. Also starting on

August 11, our own specialist team will lay the fibre backbone between the

buildings. Finally our own team of installers will follow the cabling teams and

fit the various devices and equipment in each building in turn. They will also

install the software and configure the equipment.

A complex plan has been devised to ensure the minimum overall time for

installation, while reducing the slack time between tasks for the equipment

team, and minimising any delay between cabling and equipment installation.




Figure 8.14 Project Plan Phase 1




Figure 8.15 Project Plan Phase 2




The timescales for cabling each building have been calculated according to

the number of floors, the number of devices, and the complexity in that

building. The timescales for installation of equipment and software in each

building have been calculated based on the number and type of devices to be

installed.

Priority has been given to installing the backbone, and to the largest and most

complex building – Building 2 – which serves as the centre point of the

network. However we anticipate that cabling Building 2 will take six weeks,

and installation a further two weeks.

We have also met all the constraints in the OR. Full cabling and installation of

Building 4 will be completed by September 10, prior to the deadline of

September 16. In addition to this, equipment will be on site for Buildings 7

and 6, and for the backbone, well before the deadline of September 16.

Consequently equipment will be installed and commissioned in Buildings 7, 4,

and 6, and the backbone, by the required date of September 30. We

anticipate that full installation of the site will be completed by October 28, prior

to the deadline of October 31.

This plan is subject to final agreement with MU, as well as any changes

deemed necessary after the site audit. However a certain amount of slack

has already been built in, in case of over-run. The allocated timescales for

cabling are generous, but further cabling technicians can be brought in if

necessary. For the equipment installation team a number of slack days are

available in the first half of this phase, and it is likely that they can commence

installation of a building before the cabling is complete. However if there is an

over-run towards the end, then we anticipate that final installation can be

permitted to run on onto the first week of testing without interference.

Subject to agreement with MU we would anticipate holding progress meetings

on a weekly basis throughout the installation period. Any deviation from the

agreed network design will be subject to change control procedures agreed

prior to implementation.




8.3 Phase 3 – Testing

See Figure 8.16.

In this Project Plan we have allocated three full weeks for testing of the

installation. The final week will incorporate MU Acceptance Testing,

culminating in user acceptance in the week commencing November 17.

Please see Section 4.15 for further details of our testing procedure.

8.4 Phase 4 – Training, Documentation, and Handover

See Figure 8.16.

8.4.1 Training

We plan to meet with MU during the week commencing October 13 to agree

the training plan. Subject to agreement with MU we anticipate providing three

training sessions for MU technical staff, of three days each. This will then be

completed by the deadline date of November 7.

8.4.2 Documentation

We anticipate holding meetings during the week commencing November 10 to

facilitate the handover of full documentation of the system infrastructure and

implementation. This will then be completed by the deadline of November 14.

8.4.3 Handover to MU

Subject to the satisfactory completion of system testing we anticipate holding

meetings during the week commencing November 17 to agree on acceptance

of the system by MU. This will then be completed by the deadline of

November 21.

Subject to that we would complete full implementation and handover of the

system to MU during the following week. This will then be completed by the

deadline of November 28.




Figure 8.16 Project Plan Phases 3 & 4




8.5 Phase 5 – Service and Support

During the week commencing December 1 we plan to hold meetings with MU

to agree responsibilities for service and support of the system. Out of this we

will produce a Service Level Agreement. This will then be completed by the

deadline of December 5.

Please see Sections 4.13, 4.14, and 6.7 for further details of our service and

support provision.

8.6 Phase 6 – Future Maintenance and Upgrades

Subject to further discussion we provide the option of continued maintenance

of the system, as well as provision of upgrades to equipment and software in

the future.




9 Implementation

By Mike Bailey

Our company is acutely aware of issues affecting success and failure of

projects, having followed the findings of the Standish Group in their Chaos

Report 1994 (Standish, 1994). We believe that good project planning and

management are key to this.

We are therefore very careful in our planning and implementation of network

installations, to ensure that:

1. Planned timescales are realistic.

2. Slack time is included in the plan.

3. Plans are carefully adhered to.

4. Any slippage or over-run is detected early.

5. Opportunities to make up time or increase staffing are utilised.

We believe that the customer would rather pay a realistic price for a project

delivered on time and within budget, rather than risk delays or shortcuts to

make up lost time.

Details of how this policy will be implemented for this project can be found in

Section 8.2.




10 Level of Serviceability

By Mike Bailey

We are confident that we can meet the stringent requirements for availability

of the network detailed in the OR Section 3.2, and the requirements for

reliability detailed in the OR Section 8.1.

Not only do we use the latest high quality devices and cables, but we employ

highly qualified staff for the design and implementation of our network

systems. This results in systems with high availability and reliability.

10.1Availability

High availability of the network is achieved by increasing the Mean Time

Between Failures (MTBF), and reducing the Mean Time To Repair (MTTR).

Availability = MTBF / (MTTR + MTBF)

The MTBF can be increased through a high degree of reliability in the network

(see Section 10.2). The MTTR can be decreased through speed of diagnosis

and repair (see Section 10.3).

The network management software we will install will constantly monitor the

network, and provide both an early indication of likely faults, and analysis

tools to aid in diagnosing faults.

The primary devices in this network design, routers and switches, use the

Simple Network Management Protocol (SNMP) for communication with the

network management software. In addition, the switches are compatible with

Remote Monitoring (RMON). Although RMON may not be necessary for the

Ethernet LAN in this proposal, it would be a valuable tool for monitoring the

IBM token ring network connected to the Ethernet LAN.

Section 4.3 in this document provides further details of network availability in

this project.




10.2Reliability

In this system an increase in the MTBF is achieved by:

High quality equipment and cables

Thorough system testing

Use of UPS

Resilience in the backbone topology through redundant links

Network management software with fault detection

Sections 5.7, 5.8, and 6.5 in this document provide further details of network

reliability (serviceability) in this project.

10.3Fault Handling

In this system a reduction in the MTTR is achieved by:

Supply of essential spares

Spare backbone cables pre-laid alongside those in use

Training of MU technical staff

Network management software with fault analysis

Technical support provided by this company

Sections 4.13, 4.14, 6.7.1, and 7.5.1 in this document provide further details

of fault handling in this project.




11 Reference Sites

By Mike Bailey

International Network Solutions has provided medium and large scale

network infrastructure design and implementation in the UK, and across

Europe, for a number of years. We are pleased to supply a list of customers

who have agreed to act as reference sites on our behalf:

Frankfurt University, Germany

Similar to the MU proposal.

Nottingham City Hospital, UK

This required extensive upgrading of the current legacy system, combined

with enlarging the system into new buildings.

Toyota Manufacturing Plant, UK

A medium sized system, with particular problems relating to the high levels of

interference generated by the manufacturing environment.

Further information and contact details will be provided on request.




12 Standards

By Mike Bailey

It is one of the key policies of this company that we adhere closely to the

latest British, European, and International standards. There are a wide range

of standards, and standards bodies, but these are gradually being brought

together under the ISO and IEC.

Many standards relating to products and installation are referred to throughout

this document, see Section 6.1 for a summary of these. These are largely

included in the GOSIP documentation (NIST, 2003).

12.1Standards Bodies

Currently we comply with standards issued by:

British Standards Institute (BSI)

Comite European de Normalisation [Electrotechnical] (CENELEC)

International Organization for Standardization (ISO)

International Electrotechnical Commission (IEC)

Institute of Electrical and Electronic Engineers (IEEE)

Although we are not governed by the American IEEE they are considered a

world authority on standards. Many of their standards are now being adopted

by the ISO and IEC.

12.2Quality Standards

We also comply with the latest standards for our Quality Management

Systems (QMS). Currently these are the ISO 9000 series (formerly EN 2900

series, and BS 5750 series). In particular we comply with ISO 9001, which

deals with the QMS for design, development, production, installation and

service (ISO, 2003).




13 Total Costs

By Dave Portass

The following section will layout the bulk of the costs involved in this project in

a staged way and with use of tables for ease of reading. The full costing of

cabling and hardware and where it is to be set up is included in Appendix 2.

13.1Capital Costs

13.1.1 Data Communications Equipment

Item Cost Qty Total

Cisco 7507 Router 13144.99 9 118304.91

Cisco Catalyst 3550-48 Port Switch 2414.99 73 176294.27

Cisco Systems Expansion module - Gigabit EN - fibre optic, 1000Base-SX - 1000 Mbps - 2 port(s)

2235.99 17 38011.83

Cisco Systems Expansion module - 16 port(s) - 1000Base-T - 1000 Mbps - Gigabit EN

9822.99 10 98229.90

Cisco 585 LRE 125.99 2 251.98

Total 431092.89

13.1.2 Network and Internet Security

Item Cost Qty Total

Cisco Catalyst 6503 Firewall Security System 32456.99 3 97370.97

Total 97370.97




13.1.3 Power Backup

Item Cost Qty Total

Pulsar Extreme C UPS System 526.81 9 4741.29

Total 4741.29

13.1.4 Software

Item Cost Qty Total

CiscoWorks LAN Management Solution ( ver. 2.1 ) 13464.99 1 13464.99

CiscoWorks VPN/Security Management Solution (VMS) 10628.99 2 21257.98

Total 34722.97

13.1.5 Cabling

The Backbone Fibre costs are structured in the table below.

Fibre Cost Qty Total

Building 2 - Building 1 688.80 4 2755.20









Total 19458.60




The table below gives the total cabling costs for the project.

Item Cost Qty Total

Optic Fibre Cabling See Above 19458.60

Cat 6 Cable – 12M Length 2.52 28 70.56



Cat 5e Cable – 70M Length 13.30 2654 35298.20

Cat 5e Cable – 3M Patch 1.79 2654 4750.66

Cat 5e Cable – 0.5M Patch 0.82 2849 2336.18

Cat 5e Cable – 1M Patch 0.82 250 205.00

Total 62414.04

13.1.6 Total Costs

The total cost for the equipment, hardware and software, including spares is

listed as follows.

Item Cost Qty Total

Equipment Costs 884921.66 1 884921.66

Total 884921.66

13.2Other Non Recurring Costs

13.2.1 Phased Installation

Phase 1 – The University will have to be prepared first so that exact plan of

installation can be created and locations of trunking and hardware can be

placed.




Phase 2 – The University will be set up with all of the new cabling, hardware,

and software for management.

Phase 3 – Testing of new system and software before training of University

staff.

Phase 4 – Training of IT staff in use of new network and management

systems and then handover to university

Phase 5 – Continuing onsite and offsite support of university for new network

Phase 6 – Future Maintenance and upgrades (to be negotiated at a later date

if needed).

13.2.2 Installation

The following is the cost for installation of the entire network package and

implementation as described in the 6 phases above. It includes all of our

costs and any cost of contracting out work for items such as cabling to outside

companies.

Item Cost Qty Total

6 Phased Installation of Network 160000 1 160000

Total 160000

13.2.3 Project Management

Item Cost Qty Total

Team to cover 6 phases onsite management 85000 1 85000

Team to review the network, plan for any upgrades/maintenance and provide off site support

25000 1 25000

Total 110000




13.2.4 Documentation

We will provide all of our designs, schematics, costing and any other relevant

information in document form. This will be useful for the university if they

chose to use another company to maintain or upgrade the network after the

period of the contract with us exists.

We will also provide documentation about the operation of the network and all

of the devices on it.

There will also be a troubleshooting guide which will cover most situation

involving situations involving device failure or any other fault known by us.

Item Cost Qty Total

Midshires University Network Design 9000 1 9000

Network Management and Support 10000 1 10000

Network Troubleshooting Guide 10000 1 10000

Future Upgrade Potential for the Network 4000 1 4000

Total 33000

13.2.5 Training

The University IT staff will be fully trained in the use of the new Network

equipment and software. With attempting to fully train the key members of

staff it will lead to minimise the cost of our support for problems which could

be sorted onsite with the correct training.

Item Cost Qty Total

Network Management Training 10000 1 10000

Troubleshooting (Detection & Problem Solving) Training 11000 1 11000

Total 21000




13.3Recurring Annual Costs

These are for any future upgrades needed for any new devices which might

be needed for sudden upgrades of a department or building depending on

needs of a department. We have aimed to provide a network which is future

proof for years to come but as many people know the computer industry is

sometimes far from predictable.

Item Cost Qty Total

Annual Maintenance of the Network 90000 6 540000

Annual Review of the Network 25000 6 150000

Total 690000

13.4Conclusions

These are the final costs for all three sections of the costing terms for the

Networking Project.

Item Cost Qty Total

Capital Costs 884921.66 1 884921.66

Other Non Recurring Costs 324000 1 324000

Recurring Annual Costs 690000 1 690000

Total 1898921.66

13.4.1 Payment

The following payments will be made to a specified bank account on a

specified day of each year for the period of seven years as stated in the

agreement.




If a payment is more than a week late then there will be a £50000 per week

fine for non payment.

Year 1 Year 2 Year 3 Year 4 Year 5 Year 6 Year 7 Total

Non-Recurring Costs 1098921.66 1098921.66

Annual Maintenance 85000 90000 90000 90000 90000 90000 90000 625000

Annual Review 25000 25000 25000 25000 25000 25000 25000 175000

Total 1208921.66 115000 115000 115000 115000 115000 115000 1898921.66

13.5Suppliers

Connectis

Rexel Senate Electrical Supplies

Ascott Drive

Derby

Insight UK

http://www.insight.com/uk/

CEF

http://www.cef.co.uk


http://www.cef.co.uk/




Bibliography

Books

Leinwand, A., Conroy, K.F., 1996. Network Management, A Practical

Perspective. Addison Wesley.

Stallings, W., 2000. Data & Computer Communications. Prentice Hall.

Tanenbaum, A.S., 1996. Computer Networks. Prentice Hall.

Websites

Barrett, M., 2001. Cabling Basics. http://www.datacottage.com/nch/basics.htm

Behl, W., 1993. Advanced SNA/IP: A Simple SNA Transport Protocol.

http://www.faqs.org/rfcs/rfc1538.html

BSI, 2003. http://www.bsi-global.com/index.xalter

CableTesting.com, 2003. http://www.cabletesting.com/CableTesting/default.htm

CableTesting.Com, 2003, European Standards.

http://www.cabletesting.com/CableTesting/Standards/European+Standards+Documents.htm

Cisco Systems, 2001. Token Ring/IEEE 802.5.

http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/tokenrng.htm

Cisco Systems, 2002. Extending the Enterprise: SNA Application Transport

over IP. http://www.cisco.com/warp/public/cc/so/neso/ibso/ibm/s390/eesna_wp.htm

Gilbert, H., 1995. Introduction to SNA.

http://www.yale.edu/pclt/COMM/SNA.HTM#contents

IBM, 1997. Token-Ring Migration to Switched LAN.

http://www.networking.ibm.com/trl/trl0c01.html

ISO, 2003. http://www.iso.ch/iso/en/ISOOnline.openerpage

Kakadia, D., 2001. Enterprise Network Design Patterns.

http://www.sun.com/solutions/blueprints/0902/816-7883-10.pdf


http://www.sun.com/solutions/blueprints/0902/816-7883-10.pdf

http://www.iso.ch/iso/en/ISOOnline.openerpage

http://www.networking.ibm.com/trl/trl0c01.html

http://www.yale.edu/pclt/COMM/SNA.HTM#contents

http://www.cisco.com/warp/public/cc/so/neso/ibso/ibm/s390/eesna_wp.htm

http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/tokenrng.htm

http://www.cabletesting.com/CableTesting/Standards/European+Standards+Documents.htm

http://www.cabletesting.com/CableTesting/default.htm

http://www.bsi-global.com/index.xalter

http://www.faqs.org/rfcs/rfc1538.html

http://www.datacottage.com/nch/basics.htm



Khun, M., 2001. - ISO.

http://www.uni-giessen.de/faq/archiv/osi-protocols/msg00000.html

Knowhow Networks, 2000. The History and Organisation of Structured

Cabling Standards. http://www.kwhw.co.uk/structured.htm

Mahoney, D., 2002. Guide to ICT Networks Cable Standards.

http://www.ict.ic.ac.uk/ict/policies/cable_standards.pdf

Maple Systems, 2000. Ground Wiring and Electrical Noise Reduction.

http://www.maple-systems.com/0907/09071027.pdf

Microsoft Corp., 2000. Network Load Balancing Technical Overview.

http://www.microsoft.com/windows2000/techinfo/howitworks/cluster/nlb.asp

Microsoft Corp., 2003. Using DLC with Windows NT.

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winntas/

reskit/net/sur_dlc.asp

Moran, J., 2002. Two Routers are Not Better than One.

http://www.practicallynetworked.com/qa/qa20021202.shtml

NIST, 2003, - GOSIP. http://dns.antd.nist.gov/pub/gosip/

Norton, M.J., 2001. Basics of Network Segmentation: Switching and Bridging.

http://www.oreillynet.com/pub/a/network/2001/03/16/net_2nd_lang.html

Standish, 1994. http://www.standishgroup.com

Primedia, 2003. Remote access networks spread the word.

http://www.americancityandcounty.com/ar/government_remote_access_networks/

ZNYX Networks, 2000. Network Level Resiliency for High Availability (HA)

Ethernet Networks.

http://www.znyx.com/products/software/openarchitect/OAHA/OA_HA_30page_001_web.pdf

Suppliers Websites

CEF, 2003. http://www.cef.co.uk


http://www.cef.co.uk/

http://www.znyx.com/products/software/openarchitect/OAHA/OA_HA_30page_001_web.pdf

http://www.americancityandcounty.com/ar/government_remote_access_networks/

http://www.standishgroup.com/

http://www.oreillynet.com/pub/a/network/2001/03/16/net_2nd_lang.html

http://dns.antd.nist.gov/pub/gosip/

http://www.practicallynetworked.com/qa/qa20021202.shtml

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winntas/reskit/net/sur_dlc.asp

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winntas/reskit/net/sur_dlc.asp

http://www.microsoft.com/windows2000/techinfo/howitworks/cluster/nlb.asp

http://www.maple-systems.com/0907/09071027.pdf

http://www.ict.ic.ac.uk/ict/policies/cable_standards.pdf

http://www.kwhw.co.uk/structured.htm

http://www.uni-giessen.de/faq/archiv/osi-protocols/msg00000.html



Insight UK, 2003. http://www.insight.com/uk/





Appendix 1 Network Management

Performance Management

Make viewable aspects of network that are to do with performance, for

instance, network throughput, user-response times and line utilization.

How this is done:

Gathering of performance data

Analysis of data

Determine a performance threshold for network elements so excessive usage can be found from then on.

What system are we going to use?

CiscoWorks Real Time Monitor

Configuration Management

Monitoring of Network/System Configuration, this is useful so that updates or

bugs in certain devices on the network need to be sorted. With Configuration

management it is instantly viewable where these devices are.


CiscoWorks Cisco View

CiscoWorks Campus Manager

CiscoWorks Resource Manager Essentials

Accounting Management

Measures the usage of different parts of the network; this is useful so that

anything on the network can then be regulated in the correct way minimizing

problems with over usage of certain resources.





CiscoWorks Real Time Monitor

Fault (Event) Management

Fault or event management is the process of detecting logging and fixing or

notifying the user of problems on the network stopping it running effectively.

How this is done:

Determine the symptoms

Isolation of the problem area, device.

Problem is fixed then tested on all-important subnets

Record the problem and solution to help future usage and creating of

Knowledge Based System


CiscoWorks Device Fault Manager

Security Management

Security management is about controlling the access on the different areas

within the network according to the company’s guidelines so that sensitive

information cannot be stolen or sabotaged.

How this is done:

Partition resources on the network into area that are either allowed to all or only allowed to some.

Authentication of users accessing the network.

Log any inappropriate attempts to view secure information.


CiscoWorks VPN/Security Management Solution




Appendix 2 Network Components Itemised per Floor

The following is a printout of an Excel spreadsheet detailing all the network

components, itemised for each floor of each building, with prices.




Appendix 3 Literature Describing Main Network

Components

The following pages are a series of printouts from the Website of the main

supplier www.insight.com.

URLs

Cisco 7507 Router: http://www.insight.com/uk/apps/productpresentation/index.php?product_id=CISNA02244&style=printable

Cisco Catalyst 3550-48 Port Switch: http://www.insight.com/uk/apps/productpresentation/index.php?product_id=CISNA02LV3&style=printable

Cisco Systems Expansion module – Gigabit EN – fibre optic, 1000Base-SX – 1000 Mbps – 2 port(s): http://www.insight.com/uk/apps/productpresentation/index.php?product_id=CISNA02EZD&style=printable

Cisco Systems Expansion module – 16 port(s) – 1000Base-T – 1000 Mbps – Gigabit EN: http://www.insight.com/uk/apps/productpresentation/index.php?product_id=CISNA01MDE&style=printable

Cisco 585 LRE Bridge: http://www.insight.com/uk/apps/productpresentation/index.php?product_id=CISLA03C4H&style=printable

Cisco Catalyst 6503 Firewall Security System: http://www.insight.com/uk/apps/productpresentation/index.php?product_id=CISLA03DIE&style=printable


http://www.insight.com/uk/apps/productpresentation/index.php?product_id=CISLA03DIE&style=printable


http://www.insight.com/uk/apps/productpresentation/index.php?product_id=CISLA03C4H&style=printable

http://www.insight.com/uk/apps/productpresentation/index.php?product_id=CISLA03C4H&style=printable

http://www.insight.com/uk/apps/productpresentation/index.php?product_id=CISNA01MDE&style=printable

http://www.insight.com/uk/apps/productpresentation/index.php?product_id=CISNA01MDE&style=printable



http://www.insight.com/uk/apps/productpresentation/index.php?product_id=CISNA02LV3&style=printable

http://www.insight.com/uk/apps/productpresentation/index.php?product_id=CISNA02LV3&style=printable

http://www.insight.com/uk/apps/productpresentation/index.php?product_id=CISNA02244&style=printable

http://www.insight.com/uk/apps/productpresentation/index.php?product_id=CISNA02244&style=printable

http://www.insight.com/