1|P ag e
COMP 1609 Network and Internet Technology and Design
***Coursework*** By Aiman Athambawa (000591100/ aa955)
Submission Date 12/12/2010
2|P ag e
CONTENTS Cover page................................................................................... ........................1 Contents................................................................................................................2 Introduction...........................................................................................................3 Scenario 1.............................................................................................................3 New York subnet- Scenario1................................................................................4 Beijing subnet - Scenario1....................................................................................5 London subnet- Scenario1....................................................................................6 Scenario2..............................................................................................................7 New York subnet- Scenario2................................................................................8 Beijing subnet- Scenario2.....................................................................................9 London subnet- Scenario2..................................................................................10 Global Application..............................................................................................11 Global Profile......................................................................................................11 Workstation Configuration.................................................................................13 Server Configuration...........................................................................................14 T1 Link Utilization.............................................................................................15 FTP Download response time.............................................................................18 HTTP page response time...................................................................................19 Behaviour of Voice and video application.........................................................20 Collusion counts on hubs....................................................................................23 Ethernet Delay....................................................................................................24 Recommendation................................................................................................25 Conclusion..........................................................................................................25
3|P ag e
INTRODUCTION RRPS Technology’s headquarter is located in London. They have recently opened regional offices in New York and Beijing. The main services provided by New York and Beijing will be gathered and distribute monthly and annual reports describing sales handled by the main office. RRPS needs a network that includes their three offices and they want to analyse the network performance before they actually build the proposed network. In order to achieve the goal OPNET, network simulation software used to simulate proposed network. The analysis proposed in two scenarios. Scenario 1: Network model that connects all users with switch Scenario 2: Network model that splits the users in two sections and connect each section with hubs and connect hubs to a centralised switch Scenario1 This Scenario designed in the world map which states New York, London and Beijing. These three subnets connect with IP cloud via the T1 link. Also the application configuration and profile configuration created as global. Each subnet design discussed further under separate headings.
4|P ag e
New York subnet- Scenario1 The New York subnet contains 25 users working on workstations which connect to the switch via 100baseT link. They are locally having Email server, Database server and Ethernet printer. It is also connect via 100baseT link. The network model made up with star topology. This design comprises three switches where Switch1 is 32 ports (Ethernet-32 switch) and switch2 and switch3 are 16 ports (Ethernet-16 switch). The switch3 connected to a router in order to connect all three offices connect through IP cloud. The switch2 specially dedicated for four special users who can access to voice and video Applications. The model can be made up with a single switch, but in real world it is not possible. The special users may be sitting in a separate room and servers and router must be kept at secure place in different room such as server room. It will reduce the wiring complexity. Include supported Services Email server: Heavy Access Database server: Light Access Ethernet printer: Heavy Access
5|P ag e
Beijing subnet - Scenario1 The Beijing subnet contains 40 users working on workstations which connect to the switch via 10baseT link. They are locally having Email server, Database server and Ethernet printer. It is connected via 100baseT link. The network model made up with star topology. This design comprises three switches where Switch1 is 64 ports (Ethernet-64 switch). And switch2 and switch3 are 16 ports (Ethernet-16 switch). The switch3 connected to a router in order to connect all three offices connect through IP cloud. The switch2 specially dedicated for ten special users who can access to voice and video Applications. Include supported Services Email server: Heavy Access Database server: Heavy Access Ethernet printer: Heavy Access
6|P ag e
London subnet- Scenario1 The London subnet comprises four servers such as FTP server, Web server, Voice server, and Video server. They are provided to give services for New York office and Beijing office. All servers and router connected with a 16port (Ethernet-16 switch) switch by 100baseT link. Also the router connected by the T1 link with IP cloud will be able to connect New York and Beijing office.
Include supported Services FTP server: Light Access. Web server: Heavy Access and Light Access. Voice server: VOIP (PCM quality) Video server: Video Conferencing (Light)
7|P ag e
Scenario2 This Scenario designed in the world map which states New York, London and Beijing. These three subnets connect with IP cloud via the T1 link. Also the application configuration and profile configuration created as global. Each subnet design discussed further under separate headings. This network model that splits the users in two sections where the scenario1 has and connect each section with two hubs and that will connect to a centralised switch. The all configuration on scenario1 is unchanged apart from workstation connection to hub instead of connection with switch.
8|P ag e
New York subnet- Scenario2 The New York subnet configurations unchanged from scenario1. But the workstations are split in two sections and removed the dedicated switch from the special users’ workstations. Section 1: 13 Workstations (Node 0 to Node 12) separated and assign to Hub1. Section 2: 12 Workstations (Node 13 to Node 24) separated and assign to Hub2 where the four special users (Node 21 to Node 24) who can access to voice and video Applications. Include supported Services Email server: Heavy Access Database server: Light Access Ethernet printer: Heavy Access
9|P ag e
Beijing subnet- Scenario2 The Beijing subnet configurations unchanged from scenario1. But the workstations are split in two sections and removed the dedicated switch from the special users’ workstations. Section 1: 20 Workstations (Node 0 to Node 19) separated and assign to Hub1. Section 2: 20 Workstations (Node 20 to Node 39) separated and assign to Hub2 where the ten special users (Node 30 to Node 39) who can access to voice and video Applications.
Include supported Services Email server: Heavy Access Database server: Heavy Access Ethernet printer: Heavy Access
10 | P a g e
London subnet- Scenario2 The London subnet remains the same configurations of senario1 without any single change.
Include supported Services FTP server: Light Access. Web server: Heavy Access, Light Access. Voice server: VOIP (PCM quality) Video server: Video Conferencing (Light)
11 | P a g e
Global Application Global application set as default where it has 16 predefined application definitions. These definitions have been called in every workstations, servers and printer in all three offices.
Global Profile Global profile configuration settings created in 12 rows and in each row one application definition selected depend on the need of configuration. It is listed below. Profile
Application definition
Profile
Application definition
Profile
Application definition
NY_Email
Email (Heavy)
Beijing_ Email
Email (Heavy)
Voice
VOIP call (PCM Quality)
NY_Database
Database (Light)
Beijing_ Database
Database (Heavy)
Video
Video conferencing (light)
NY_FTP
FTP(Light)
Beijing _FTP
FTP(Light)
NY_Web
Web Browsing (Light http)
Beijing_Web
Web Browsing (Heavy http)
NY_Print
File Print (Heavy)
Beijing_ Print
File Print (Heavy)
12 | P a g e
13 | P a g e
Workstation Configuration Workstations on New York and Beijing particularly configured depend on application accessibility. It has configured destination preferences and supported profiles. Below image shows the example. (New York node 24 selected to show the configurations: node 24 has the access of Voice and video).
14 | P a g e
Server Configuration Servers in New York, Beijing and London configured depend on the requirement. It will be configured in application supported services attribute. There are 8 servers and 2 printers in place to offer services. Server / Printer
Supported Service
NY_EmailServer
Email (Heavy)
NY_DatabaseServer
Database (Light)
Beijing_EmailServer
Email (Heavy)
Beiging_DatabaseServer
Database (Heavy)
London_FTPServer
FTP(Light)
London_WebServer
Web Browsing (Light http) Web Browsing (Heavy http)
London_VoiceServer
VOIP call (PCM Quality)
London_VideoServer
Video conferencing (light)
NY_Printer
File Print (Heavy)
Beiging_Printer
File Print (Heavy)
Out of 10 configurations only 2 displays here.
15 | P a g e
T1 Link Utilization Link utilizations measured to see how the network traffic made during simulation. Especially T1 utilization results have been collected for analysis from both scenarios while it’s simulated for one hour. As the T1 link data rate 1.5Mbps, it has more utilization inbound and outbound traffic.
T1 link utilization – New York to IP cloud
> The utilization of T1 link between New York and IP cloud is analysed on both scenarios. Expected: Both inbound and outbound average utilization should be higher in scenario1. Observed: The outbound average utilization is lower in scenario1 and inbound average utilization is higher in scenario1. The outbound traffic carries the data from the New York Network with only 25 users’ data but the inbound traffic getting the data from other networks such as London and Beijing network with 40 users in Beijing. Therefore the switched network got more utilization than the network with hub. Because of the hubs which makes more delays on network traffic than switch.
16 | P a g e
T1 link utilization- London to IP cloud
> The utilization of T1 link between London and IP cloud is analysed on both scenarios. Expected: Both inbound and outbound average utilization should be higher in scenario1. Observed: scenarios.
Both inbound and outbound average utilization appears to be same in both
The results received are unexpected and it appears all the utilization on T1 link between London and IP cloud appears same. During the simulation time the traffic in inbound and outbound may have equal flow.
17 | P a g e
T1 link utilization- Beijing to IP cloud
>
The utilization of T1 link between Beijing and IP cloud is analysed on both scenarios. Expected: Both inbound and outbound average utilization should be higher in scenario1. Observed: As expected. But inbound traffic has more utilization than outbound. The outbound traffic carries the data from the Beijing Network with 40 users’ data but the inbound traffic getting the data from other networks such as New York and London network with 25 users in New York. Therefore inbound traffic got more utilization on both scenarios. The switched network got more utilization than the network with hub. Because, hubs make the delays on network traffic but switches does not.
18 | P a g e
FTP Download response time FTP server located in London and it is configured as light access. This server has the access of 25 users in New York and 40 users in Beijing. The scenario with hubs has to have delay on the network. Because, hubs will not transfer data as quick as the switches does.
Expected: Download response time should be more on scenario2. Observed: as expected. The scenario2 with split network and hub has got more delay on the network. The average download response time stability takes up to 160 second to get a packet from FTP server. But the scenario1 with switch took less than 110 second to get a packet from FTP server. However the average download response time initially start up like in 1-2 second in scenario1 and after 21 second in scenario2. It also proves that the hub makes delay on network.
19 | P a g e
HTTP page response time Web Server located in London with a configuration of light access to New York and heavy access to Beijing. This server has to provide the service to 25 users in New York and 40 users in Beijing.
Expected: HTTP page response time should be more on scenario1 Observed: After 10-13 Minutes the results falsifying the expectation The scenario2 with split network and hub has to have more delay on the network. The simulation is after 10-13 minutes changing its results upside down. After 13 minutes the HTTP page responding time stability takes over to 150 second on scenario2 and over 270 second takes on scenario1. However, when analysed further on probable value of HTTP page response time, initially start up takes in 0.15 second in scenario1 and after 0.25 second in scenario2. So the variance is very small.
20 | P a g e
Behaviour of Voice and video application
Voice Application The voice application is setup with a voice server in London. It has 4 users in New York and 10 Users in Beijing. The VOIP service is setup with PCM quality.
Video Application The video application is setup with a video server in London. It has 4 users in New York and 10 Users in Beijing. The Video conferencing service is setup with light resolution service. When it was created with the higher resolution it wasn’t work. The simulation stopped in certain time, after that whole network design crashed. Analysis on Voice and video user with normal user The analysis made on both scenarios on voice/video user (node24) and normal user (node0). It shows the higher Ethernet delay on node24. When compare to scenario1 and scenario2 the scenario2 shows more delay than the senario2 due to the delay by the hubs.
Ethernet delay Scenario1: node24 Vs node0
Ethernet delay Scenario2: node24 Vs node0
21 | P a g e
Voice application packet delay Variation and packet end-to-end delay
>
22 | P a g e
Video application packet delay Variation and packet end-to-end delay
23 | P a g e
Collusion counts on hubs
The collusion count results collected on two hubs. On the scenario2 the special users (4 Users in New York and 10 users in Beijing) assign to Hub2. As the result graph shows above the Hub2 has more collusion count in New York and Beijing. Therefore the voice and video applications are providing more collusion on the network.
24 | P a g e
Ethernet Delay New York Ethernet has got 25 users and Beijing Ethernet has got 40 users. The Ethernet delay must be high when:1. High number of users 2. High number of services 3. Using hubs on the network 4. Using less speed links on the network. (Eg: 10baseT)
Expected: Ethernet Delay should be more on scenario2 Observed: As expected. The Ethernet network with hub has got more delay when compare to switched network. Because, the hub is distribute the packet in every nodes regardless of which node going to receive that packet. But the switches send the packet to particular node which supposes to receive that particular packet.
25 | P a g e
RECOMMENDATION
The Scenario2 (network with hub) must be avoided in the larger network. The hubs are broadcasting the packet to every node and making delay and providing more collusion on the network. But, Switch is sending the packet to particular destination. Therefore switch is recommended when compare to hub
Beijing network workstations have been setup with 10baseT. It is not enough for voice and video application runs with. It must be changed as 100baseT.
The T1 link is not enough to connect with larger network via IP cloud since the T1 link data rate is 1.5Mbps. The link must be changed as T3 link. Or this will provide much faster and gives more link utilization when compare to T1 link.
There is no security provided on the network. It must have some sort of security mechanism must be enabled. Eg. firewall
CONCLUSION RRPS Technology’s proposed network designed in 2 scenarios where a scenario with switches and another scenario with switch and hubs. These 2 scenarios simulated in 1 hour to get the good results on the entire network. After the simulation identified that network with hubs has got more delay and voice and video applications enabled more traffic in the network The network has been analysed and investigated in T1 link utilization, average FTP response time, HTTP page response Time, behaviour of voice and video application and Ethernet delay. The all analysis found that the scenario2 is not suitable for larger network where it have more delay on the network. Voice and video applications has been created for 4 users in New York network and 10 users in Beijing network where the Beijing workstations connect with 10baseT link and New York workstations connect with 100baseT link. Since the voice and video applications distribute more traffic within the network the Beijing network can be setup with 100baseT at least. The video application initially setup with heavy (high resolution) configuration. The network simulation crashed in several time. There after it has changed as light (low resolution) in order to keep the network in place. The video application is not recommended for larger network where it is accommodating more traffic and delay on the network. Overall network can be implementable with few changes as recommended above.
