MIDDLESEX UNIVERSITY (MAURITIUS BRANCH CAMPUS) …...middlesex university muritius campus 2013/2014...

Ogirinye Mcjerry M00424931 CCM4310 0

OGIRINYE MCJERRY MIDDLESEX UNIVERSITY

MURITIUS CAMPUS

2013/2014

MIDDLESEX UNIVERSITY (MAURITIUS BRANCH CAMPUS)

SCHOOL OF ENGINEERING AND INFORMATION SCIENCES

NETWORK MODELING AND SIMULATION (CCM 4310)

COURSEWORK THREE

TITLE: A NETWORK DESIGN FOR THE DEPARTMENT OF COMPUTER

AND COMMUNICATIONS ENGINEERING

STUDENT NAME: Ogirinye Mcjerry

STUDENT ID NO: M00424931

COURSE: MSc Computer Networks

LECTURER NAME: DR. Visham Ramsurun


TABLE OF CONTENT

INTRODUCTION ...................................................................................................................................... 2

REQUIREMENT ANALYSIS PROCEDURE .......................................................................................... 4

REQUIREMENTS ANALYSIS:............................................................................................................. 4

USER REQUIREMENTS: ...................................................................................................................... 4

APPLICATION REQUIREMENTS: ..................................................................................................... 6

DEVICE REQUIREMENTS (HOST) ANALYSIS ............................................................................... 8

NETWORK REQUIREMENTS ANALYSIS ........................................................................................ 8

FLOW ANALYSIS PROCESS ............................................................................................................. 10

NETWORK DESIGN AND CONFIGURATION PROCESS .............................................................. 11

NETWORK LOCATION MAP ........................................................................................................... 11

HIERARCHICAL CLIENT – SERVER MODEL .............................................................................. 12

LOGICAL DESIGN .............................................................................................................................. 13

NETWORK COMPONENTS .............................................................................................................. 14

INTERNET PROTOCOL (IP) ADDRESSING AND ALLOCATION SCHEME .......................... 16

NETWORK CONFIGURATION ........................................................................................................ 17

Configuration File Router RA Internal ......................................................................................... 18

Configuration File Router RB Internal .......................................................................................... 18

Configuration File Router RC Internal…………………………………………………………..19

Configuration File Router RD Internal ......................................................................................... 19

NETWORK SIMULATION ON PACKET TRACER AND RESULTS .............................................. 20

USING THE TRACEROOT COMMAND FOR TRACING ROOTS ................................................. 30

DISCUSSION ............................................................................................................................................ 31

CONCLUSION………………………………………………………………………………………….31

References ................................................................................................................................................. 32


TABLE OF FIGURES

FIGURE 1: Requirement Gathering Requirement Model…………………………………………………3

FIGUR 2: The Procedure for Categorizing and Developing Flows...............................................................9

FIGURE 3: Network Devices Location Map Flows.............................................................................11

FIGURE 4: Server – Client Flow Analysis Hierarchical Model......................................................................12

FIGURE 5: Server – Client Flow Analysis Hierarchical Model......................................................................13

FIGURE OF TABLES TABLE 1: User requirements analysis......................................................................................................5

TABLE 2: application service requirements.............................................................................................6

TABLE 3: Application performance.......................................................................................................7

TABLE 4: Application requirements analysis.........................................................................................7

TABLE 5: Host Requirements analysis...................................................................................................8

TABLE 6: Functional requirements analysis..........................................................................................9

TABLE 7: Flows specifications............................................................................................................11

TABLE 8: Hardware and Software Price. …………………………………………………….………..16

TABLE 9: Addressing and Allocation......................................................................................................17


INTRODUCTION

Customarily, network architecture and design could be seen as the skill of putting together some

rules and regulations in order to carefully select network technologies and know how to joint

these technologies, protocols and services into network analysis, architectures and design. As it

was with other professions which the success solely depend on the person doing the work that

hardly reproduce, but this might be so in time past when networking was of routine than

generating income and a crucial resources (McCabe, 2007). However, networking can be seen as

a ubiquitous technology, mission-critical for an organization that might give real time

information access across the globe. The network should be reproducible, defensible and logical

with modification of rule 80/20 so as to cope with the demand for robust network design that can

offer users variety of services, through different techniques and distinct combination of network

technologies (McCabe, 2007).

Further, according to (McCabe, 2007) reviewed, in the past analysis, architecture and design were

more of capacity planning in order to provide a certain amount of bandwidth that can carry

network for short periods. And eventually result in long term fluctuations of traffic. However,

this kind of design will lead to user having problem of network congestion due to reduction in

bandwidth. Considerably, bandwidth is one element of network resources that required attention

while designs, network, as well as network delay. Importantly, network reliability,

maintainability and availability should be augmented during network architecture and design (

Kenneth S. et al, 2008).

However, the problem we are asked to address in this paper is to design a network for the

department of computer and communication engineering, which isolated from the main

university campus, and it will have a link to the corporate campus as well as internet. The

network should have from a minimum of six specialists to eight specialist maximum, with each

terminal having twenty users. Furthermore, in order to successfully solve this problem and

achieved the desire it imperative we adopted the methodological approach. Therefore, in this

work we will start with the discussion of network analysis, architecture and design, how these

will be put together in achieving the proposed network design. Approachable, we will look at

various aspects how the system can provide a classical services to the network users, by going

into network analysis in order to know the requirements, from user, applications and device

(host) perspective. Though, the process needs time and effort, however, the return on investment

is unquantifiable. In this paper, we started discussing from methodological approach to network

design, ranging from requirement analysis leading to user, network, application, and functional

requirements. Through these one should be able to decide the technology and topology to use in

designing the network, in terms of information location equipment and vendor selections.

Additionally, coupled with flow analysis, logical design and routing, physical design and the

configurations on packet tracer simulator, testing, management and security respectively.


REQUIREMENT ANALYSIS PROCEDURE

REQUIREMENTS ANALYSIS: Are the sets of requirements that gives an explanation of network

functionalities and performances that required for the success of the entire network, and to

support its users, applications and devices ( Anurag K. et al, 2004). There are two main sets of

requirements, these includes core and fundamental, though, there may be numerous network

requirements from a diverse sources that could contribute to the achievability of the system, but

we do not need to consider all the requirements else we will set an expectation that may beyond

our reach. So, we will focus on the core and the fundamental in order to cater for the future, as

part of the requirements analysis to accomplish this work. And we will adopt the current practices

stipulated in the IETF request for comments (RFC2119, 1997), to classify our requirements.

However, in this report, we will begin our requirements analysis from user perspective top –

down approach, all through the network analysis, presenting tabular forms individually and

giving the whole structural analysis of the entire requirements mechanism. However, before we

proceed find below the structural requirements analysis process, this model is the basis for all

gatherings, analyze, and development of the network system.

FIGURE 1: Requirement Gathering Requirement Model

Adopted from (James McCabe)

USER REQUIREMENTS: The word user used in the network to mainly characterize the end users

of the system, sometime, however, can include all the people involved the uses of the system such

as management, network and system administrators. User requirements are sets of aspiration and

needs derives or gathered from user input that will enable them to successfully carry out their

desire tasks. Part of our effort to give quality service to the users below are some requirements

for us to achieve it.


User Service

Requirements

Description

Location(s) & Number(s) of

users, all the users have the

same profile

Lab A First floor with 20users,

Lab B First floor with 20users,

Lab C First floor with 20users,

Lab D First floor with 20users,

Lab E First floor with 20users,

Lab F First floor with 20users,

Lab G First floor with 20users,

Lab H First floor with 20users.

Total number of users = 160

Timeliness end-to-end or round-trip delay in terms of file transfer

Expected Growth (users)

After 1 Year 50% increase

Interactivity The remote control as if they were at the model’s

location from device access perspective e.g. Telnet

Reliability 100% performance for some applications in terms of

RMA

Adaptability The system should be able to adapt to user additions,

deletions, changes (in terms of mobility)

Security The system should assure the user of confidentiality,

integrity, authenticity of the user information as well

access to resources.

Affordability

(Cost/Funding)

The system should not cost for users to implement (Rs

15 million/year)


TABLE 1: User requirements analysis.

APPLICATION REQUIREMENTS: This is the component that interface the user and network

devices which can be determined by the experience, testing and the application information

needed for the effective operation of the system, the application should support user

requirements such as functionality, adaptability, intractability, timeliness, quality, reliability and

security. There are three groups of application, these are application group, application type and

application location, also application can type as mission – critical, rate-critical and the real-time

as well as best-effort (McCabe, 2007). Below is the application requirement table.

Application

s (with the

same

profiles)

Controlled Rate Real-Time Best-Effort Appl.

Locations

Internet

communicat

ion.

Email

Application

service.

File transfer

services.

Database

application.

512 Kb/s Lab A First

Floor

99.2% R, 900 Kb/s,

100 ms D

512 Kb/s Lab B First

Floor

240 Kb/s, 80 ms D 512 Kb/s All the labs

First Floor

99.2% R, 3.2

Mb/s,

45 ms D

512 Kb/s Lab D First

Floor

640 Kb/s, 60 ms

D

512 Kb/s Lab E First

Floor

TABLE 2: application service requirements.

Functionality Application requirements, that is an application that

will help users carry on their daily activities

Supportability The system should be able to keep system performance

update as per designed.

Future plan Designers can plan for the future growth, in case

network scale or adding new applications to the system.


Applications Delay Capacity Reliability

Internet

communication.

Email

Application

service.

File transfer

services.

Database

application.

100 ms 100 Mb/s 99.2%

100 ms 100 Mb/s 99.2%

100 ms 100 Mb/s 99.2%

100 ms 100 Mb/s 99.2%

100 ms 100 Mb/s 99.2%

100 ms 100 Mb/s 99.2%

TABLE 3: Application performance.

Category (similar

profiles for all the

users )

Mission Critical Real-time Best-effort Appl. Locations

Internet

communication.

Email Application

service.

File transfer

services.

Database

application.

N/A N/A The same

profiles

applicable to

entire network

Floor 1

TABLE 4: Application requirements analysis.


DEVICE REQUIREMENTS (HOST) ANALYSIS: This component interface with application and

network requirements, it provides support for all the network requirements and mostly,

characteristics with device performance and their location info, with this we can appropriate our

network host and know the kind of systems we should deploy in our network. Below is the host

requirement table.

Type of Device NIC Type Processors Operating

System (OS)

Email Server, Web

server, Windows

and file server,

Database server,

10 Base

T/100 Base

T Fast

Ethernet

Core i7

Window

2008

Cisco routers 2811

series,

MPC860 Cisco IOS

Cisco switches 3560-

24ps

PC405

multilayers and

2950-24,

RC32300

Client computer 10 Base

T/100 Base

T Fast

Ethernet

Intel (R)

Core i5

Window 7

TABLE 5: Host Requirements analysis.

NETWORK REQUIREMENTS ANALYSIS: In the network requirements, the architecture and the

designer can evaluate the system from a different perspective which may include the following,

Limitations from the existing networks, anticipated scaling of the existing networks,

Interoperability among networks, existing network and the maintenance services, Current

architectural and design guidelines. These analysis will help the designer to determine what to

include in the new network architecture/design and what they should not include, based on the

above requirements analysis. However, in this work we have no existing network to practically

analyzed, but we bear in mind the above criteria in case we opportune to analyze the existing

network, we can use them.


Requirements

Network Management

Requirements

Moving and knowing the accessibility of

information, updating the information

Monitoring Methods Acquiring parameters for source to

destination per link, controlling the

features of network per-element.

Instrumentation Methods Making the choice of implements to be

used in investigating management

information.

Scaling network management

traffic

Defining the amount of network capacity

that needed to be kept for managing the

network

In-Band vs. Out-of Band

Monitoring

The decision if management information

flow should be flow in the same path with

user traffic or in a different medium.

Centralized vs. Distributed

Monitoring

Is the management podium a distributed or

a single hardware mechanism

Performance Characteristics Performance comprises set of techniques

adopted for the configuration, function,

controlling, providing and accountable for

the sharing of network assets to the users,

applications and devices. Which contains

capacity planning, traffic engineering and

different facility mechanisms.

Security Requirements Confidentiality, integrity and

authentication of users’ data will be of

higher priority.

Company- or Organization-

Specified

All organization information is hidden

from external entrée

TABLE 6: Functional requirements analysis.


FLOW ANALYSIS PROCESS

The flow analysis can be derived from the gathering requirements as well as the requirements,

we developed ranging from the user requirements, application, and device requirements we

gathered from the network. Flow analysis is the techniques of defining the traffic flows on the

network, where the traffic should apply, the levels of device and application performance with

consideration to device location and network size. The reason for the flow analysis is to depict

the kind of traffic that will have a great effect on the network, architecture and design ( Heinz-

Gerd H. et al, 1999) and (McCabe, 2007). Flow analysis can be viewed as an end to end network

performance with the combination of delay, capacity and reliability, maintainability and

adaptability (RMA), flow analysis can aid the selection of technology, we use several mechanisms

to develop flow model, like sources to destination approach. Flow analysis can be individual,

composite and sometime critical flaws, also, it can be built to building, devices to devices and all

these can be derived from our requirements gathering and determine how the system flows

should be based on the requirements of the user, application and device.

However, during flow analysis, the architect and the designer can choose the approach(s) to use

when considering implantation of flows on the network, and these are the basics process for the

network flow analysis. These processes depict in (figure 2) can be used to decide the

implementation process, either to utilize all or some of the structure below.

FIGUR 2: The Procedure for Categorizing and Developing Flows.

Adopted from (James McCabe)


Applicatio

n

Reliability Capacit

y

Delay Flow

Internet

communic

ation or

Web

Browsing

Email

Applicatio

n service.

File

transfer

services.

Database

transaction

.

99.2% 100Mb/s 100 ms Lab A Floor 1

99.2% 100Mb/s 100 ms Lab B Floor 1

99.2% 100Mb/s 100 ms Lab C Floor 1

99.2% 100Mb/s 100 ms Lab D Floor 1

99.2% 100Mb/s 100 ms Lab E Floor 1

99.2% 100Mb/s 100 ms Lab F Floor 1

99.2% 100Mb/s 100 ms Lab G Floor 1

99.2% 100Mb/s 100 ms Lab H Floor 1

TABLE 7: Flows specifications.

NETWORK DESIGN AND CONFIGURATION PROCESS

NETWORK LOCATION MAP

As the requirements analysis, it will be necessary to have knowledge of the network and the

location of devices in order to know the level of relationship among the network components.

This mapping of network location sometime can be a link between buildings, and device to

device, with this requirement approach one should know the expected position of the clients’

computers, servers, switches and routers, it also helps us to determine how network users,

applications relate and behave as well as the flow of the traffic. This location information aids us

to differentiate the internal network from external networks and to define the performance of the

network components. However, the (figure 3) show a sketched location map of our network with


arrow represent the bidirectional flows of traffic from a corporate campus to the branch, also the

flows from the internet to the local network.

FIGURE 3: Network Devices Location Map Flows.

HIERARCHICAL CLIENT – SERVER MODEL

Traditionally, the most widely used network flow model is a client-server model, which has both

hierarchical and directionality flow models. In this kind of model the flows are bidirectional

among the clients and the server, with the request and response method which can be termed as

an asymmetric flow model. However, as the communication among the client and server

becoming more hierarchical due to additional layers or tiers to the flow model, their

characteristics can be referred and terms as hierarchical client to server flows model. Basically, it

is a client server model, but some cases it can be server to server and server to management

system which can be seen as critical. In this case, the server can serve both source and destination.

The significance of this type of model is, it gives room for additional layers as the network growth

and recognizes server to management and server to server flows scheme.

Further, due to its significances, we decide to implement in our network architecture and design

as the part of future growth plans, in order enable us add more components to our network and

also ease of maintenance, (figure 4) show the graphical representation of our hierarchical client-

server model


FIGURE 4: Server – Client Flow Analysis Hierarchical Model.

LOGICAL DESIGN

Logical network design is one of the essential components which cannot be ignored during the

network design process, since it helps facilitate the construction and layout of network

components a lot easier and some degree of accuracy while designing the network. According to

( Anurag K. et al, 2004) and (McCabe, 2007) logical diagrams reveal the relationship and

connectivity between devices on the network, their interaction with each other, how they may

jointly give support and services to the network. The author further explained, the logical design

that shows how routers connects and links every device on the network such switch, client PC

and firewall are connected to provide services to outside networks. However, in this work we

made a logical design for the department of computer and communication engineer, the logical

diagram shown how the network is structured and the connectivity within the internal network

and the external network such as a connection from the branch campus to corporate campus, as

well as connection to internet. Using hierarchical structure that vividly shows the core,

distribution and the access layer party of the network, the placement of the firewall, servers and

client computers also the IP address blocks that assigned to each subnet of the network. For more

details, see (figure 5)


FIGURE 5: Network logical design diagram.

NETWORK COMPONENTS

In this section we will describe the components used and the reasons behind the choice of these

technologies applied in this work. The following network components are used in designing the

network for the department of computer and communication engineering. We used four (4) Cisco

IOS routers 2811 models with the following specification, MPC860 processor, flash memory 128

MB (connected) / 256 MB (max), IP based gateway, support two Ethernet interfaces with four (4)

serial line sync/async interface, the data rates are of good scalable with these devices

(www.cisco.com, 2014). We used these routers to connect different sub-network as well as

established connection to university, corporate campus and the internet, we decided to use these

routers due to their high quality stander and they supported the addition of serial links in case

the network increase.

Also, we used Cisco catalyst switches 3560-24ps multilayers with processor PC405, 24 Ethernet

ports/IEE 802.3 interface(s), 2 gigabit Ethernet/IEE 802.3 interface(s) and each port is a collision

domain, full duplex communication, security enhancement like access control list (ACL). It can

be used to perform IP routing, quality of service (QoS), multicasting management and it can

handle up to 10/100/1000 Mbps for high productivities. We used in for this network design

because it can scale for a large range of network, it can be able to control heavy on the network


and we used it to host both server-farm and the backup-server (www.cisco.com, 2014). More like

it is 2950-24 model, RC32300 processor, Ethernet ports/IEE 802.3 interface(s), 2 gigabit

Ethernet/IEE 802.3 interface(s) and each port is a collision domain, we this to control each the

terminal at the access layer of the network.

We used four servers with three backup, these servers run email server, Web server, windows

based and file server, and database server, with the same specification like a network interface

card (NIC) 10 base-T and 100 Base-T, core i7 running with windows server 2008, they all have a

backup server, which we placed at university corporate network were all the data from university

branch campus will be backup to, so that if anything happen to the data in the local network, we

can have all the student information stored at corporate campus. Additional slots to upgrade in

the future if there is a need for that in case user increase and load expand than necessary.

Unified threat management is used to control and manage the security of the designed network,

it is an umbrella covered put all the security management into one place for easy management

and to enhance network performance. It contained network firewalling, intrusion prevention,

gateway antivirus, gateway anti-spam, VPN, content filtering and load balancing among others.

Why we decided to use it to maintain the network quality of services, rather than using several

security zones that will end up slowing down our network. This component will give appropriate

monitory to the entire network, and a suitable control will be provided to both university,

corporate campus and the internet, on what students should accessed and what they should not.

All labs are equipped with the client desktop computing devices, with network interface (s) card

(NIC) 10 base-T and 100 Base-T, windows seven (7) core i7, Intel (R), which will be used for

student experiments.

Unshaded twisted paired copper straight-through category six (CAT6) cable is used for

communication media (ebuyer.com, 2014), and it runs 250MHZ and 1000BASE-T Gigabit

Ethernet with high electrical power conductivity international standard organization (ISO)

recommended.


Hardware and Software Descriptions Unit Price Total Price

Seven (7) Email Server, Web

server, Windows and file server,

Database server,

25200Rs 176400Rs

Four (4) Cisco routers 2811 series, 30200Rs 12080Rs

Three (3) multilayers Cisco switches

3560- 24ps

32300Rs 96900Rs

Eight (8) Cisco catalyst switch 2950-24, 27400Rs 219200Rs

160 Client computers + extra 40 for

future use

19750Rs 3950000Rs

1000ft. CAT6 Ethernet Cable 7650Rs 7650Rs

Grand Total 4,462,230Rs

TABLE 8: Hardware and Software Price.

INTERNET PROTOCOL (IP) ADDRESSING AND ALLOCATION SCHEME

The success of IP addressing is depends on the output from the network requirement analysis,

haven take known the number of the users the needed and the devices to be used in the network.

This section presented the addressing system we used for the network and the how we allocate

the IP addresses of the network. We used two classes of the IPV4 address private and public for

this network these are class B and C, the ideal behind the two choices are, firstly, we planned for

future growth and in order to cater for the growth we used a class B address of IPV4 172.16.0.0/16

that has more range of host address of 16,777,216 (224) per network (Douglas, 2000), and is a

private IP address that can be used for internal network only it cannot used on the internet in

order to protect the local network from exposed to public domain for security purposes. This class

of IP address allowed the university to have a long-term plan of adjustment.

Secondly, we used a class C IPV4 address of 192.168.10.0/24 to link all public routes such as serial

lines, connection to university, corporate campus network since it is isolated from branch

campus, and the link to the INTERNET and the web server. It has more number of network range

2,097,152 (221), (Douglas, 2000) whereby if the university decides to expand the network or create

another one this class of IP addresses its large enough cater for expansion to different locations.

This class of IP address is what most organizations used to hide all private IP addresses while

connecting to the internet with the uses of NAT protocol.

We have eight labs with twenty (20) users per terminal, we have server-farm with separate

backup, and we have internet link and university, corporate campus. For more details how we

allocate the blocks of IP addresses to each sub-network after sub-netting and the once that are

reserved for future growth see the (table 9) below.


TABLE 9: Addressing and Allocation.

NETWORK CONFIGURATION

This section shows the configuration process of the entire network topology. After all the

gathering of requirements process and other several steps we embarked in this network designed

till this stage, we chose star topology for the network design and it was done on Packet Tracer

simulator. All the mentioned devices from network components above were used to connect each

other with straight-through cable. Additionally, we used the IP address specified in the above

table to configure the network fast Ethernet interfaces and the serial links with Cisco commands,

we used router information protocol version 2 (RIPV2) to add all the network interfaces to the

routing table


Configuration File Router RA Internal

The following commands in the configuration file for Router RA Internal determine the IP

address for each interface and enable RIP on those interfaces, as well as other configuration

commands:

Configuration File Router RB Internal

The following commands in the configuration file for Router RB Internal determine the IP address

for each interface and enable RIP on those interfaces, as well as other configuration commands:


Configuration File Router RC Internal

The following commands in the configuration file for Router RC Internal determine the IP


commands:

Configuration File Router RD Internal

The following commands in the configuration file for Router RD Internal determine the IP


commands:


NETWORK SIMULATION ON PACKET TRACER AND RESULTS

After the network design and configuration, we run the network simulation on packet tracer

using a simple packet data unit and complex packet data unit (PDU) for several seconds. Ranging

from 10s, 50s, 500s with different packet sizes of 500MB/s and 512MB/s from PC1 Lab A to server-

farm and the backup-server, also simulate the entire network. The sending of packets and the

capturing packets from source to destination (client – server), with different protocols such as

FTP, SMTP, HTTP and SNMP, were successful without much delay on the network. These results

proved the reliability of 99.02% and 100Mb/s capacity of the network stated in table 7 and table 3

of the flow spec and application performance during our requirement analysis.

The screen shot was captured during the first 100s of simulation and at about 500s the second

screen shot was taken, shows how packets were sent over the network. One screen shot shows

the unicast message and the second screenshot captured during the broadcast message. For more

details, see the screen shots that were taken during the simulation runs on packet tracer.


Also, we extended the simulation test to command prompt (CMD) using ping and tracert

command on the CMD to testing the whole network, using source to destination IP address

techniques. The results of the round trip were displayed, which shows the number of packets

sent, the number of the received packets, and the number of the lost packets using ping command.

While tracert command hops the network and display the number of hops and the time. Further,

the statistics of the round trip was given such as the minimum and maximum time it took the

packets to move from source to destination, and the average time was also displayed. For more

information, see the screen shots we took during the ping and tracert.


Pinging from Lab A to farm-servers, web server and backup servers


Pinging from Lab B to farm-servers, web server and backup servers


Pinging from Lab C to farm-servers, web server and backup servers


Pinging from Lab D to farm-servers, web server and backup servers


Pinging from Lab E to farm-servers, web server and backup servers


Pinging from Lab F to farm-servers, web server and backup servers


Pinging from Lab G to farm-servers, web server and backup servers


Pinging from Lab H to farm-servers, web server and backup servers


USING THE TRACEROOT COMMAND FOR TRACING ROOTS

The following are the screen shots of hops count using traceroot commands from Lab A PC1

tracing IP roots to web server, backup server at the corporate campus and the server-farm:


DISCUSSION

In this paper, we designed the network topology on packet tracer after gone through the

requirements analysis, implementing the mythological approach to design. We started by

gathering analysis which led us to five tables, in these table listed out some requirements that can

help us achieved our design successfully. The flow of the network analysis started from user

requirements, application requirement, device requirement and network requirement. The resion

we under we go through all these processes it is because there are the input to network design

that can give a successful output. Failure to adhere to these criteria will eventually lead design

failure. However, after the analysis of the all that network may require, the design, the

configuration and simulation was run on cisco packet tracer in which we run several simulation

as was earlier mentioned above with their results as well as series of screen shots to show the

output we got from the network and the performance.

CONCLUSION

In this work we are asked to design a network for the department of the computer and

communication engineering for the students’ experiments. However, to achieve that we first

gather the requirements, analyzed the user requirement, application, device and network, also

we defined the flows of the network system. Thereafter, we moved into sketch of the location

map, the hierarchical client-server model and the logical design of the network which facilitated

the implantation on packet tracer. After the design on packet tracer we run simulation and the

results shown above. From the results we got, we able to compared them with the network,

application and user requirements in terms of reliability, maintainability and adaptability (RMA).

The result proved that the network should be able to meet the user expectation.

The limitation we have during the design of this network are, inability to implement this network

on the opnet in order to generate the graph for reliability and the capacity, and some other

limitations which we can improve in the future work.


References

Anurag K. et al. ( 2004). Communication Networking: An Analytical Approach. 500 Sansome Street,

Suite 400, San Fransico, CA94111: Morgan Kaufmann INC.

Heinz-Gerd H. et al. (1999). Integrated Management of Networked Systems: Concepts, Architectures,

and their Operational Application. 340 pine street, san fransico CA94104-3205: Morgan

Kaufmann Publishers INC.

Kenneth S. et al. (2008). Designing and Supporting Computer Networks, CCNA Discovery Learning

Guide. US: Wordwise Publishing services, LLC.

Douglas, C. (2000). Internetworking with TCP/IP:Principles, Protocols, and Architectures . Upper

Saddle River : NJ: Prentice Hall.

ebuyer.com. (2014, 04 10). Retrieved from 451091-startech-roll-stranded-utp-cat-6-patch-cable-

305m-blue wirc6patblrl: http://www.ebuyer.com/

McCabe, J. D. (2007). Network Analysis, Architecture, and Design THIRD EDITION Morgan . 30

Corporate Drive, Suite 400, Burlington, MA01803, USA: Kaufmann Publishers is an

imprint of Elsevier.

RFC2119. (1997). https://www.ietf.org/rfc/rfc2119.txt; Key words for use in RFCs to Indicate

Requirement Levels. IETF.

www.cisco.com. (2014, 04 10). Retrieved from catalyst-2950-series-switches/index.html:

http://www.cisco.com/c/en/us/products/switches/catalyst-2950-series-

switches/index.html

www.cisco.com. (2014, 04 10). Retrieved from switches catalyst-3560-series-

switches/product_data_sheet09186a00801f3d7d.html:

http://www.cisco.com/c/en/us/products/collateral/

MIDDLESEX UNIVERSITY (MAURITIUS BRANCH CAMPUS) …...middlesex university muritius campus 2013/2014...

Documents

Transcript of MIDDLESEX UNIVERSITY (MAURITIUS BRANCH CAMPUS) …...middlesex university muritius campus 2013/2014...