Modeling, Configuration and Performance Analysis of the customized network using OPNETRIVERBED Modeler

ECE 636 Computer Networking Laboratory
FALL 2014
Project
Modeling, Configuration and Performance Analysis of the customized
network using OPNET/RIVERBED Modeler
Instructor: ABBAS KIANI
Submitted by: FATEMA ZOHORA
ID# 31256141
Date of Submission: 12/10/14

Introduction:
The aim of this project is modelling, configuration and performance analysis of the customized network using
RIVERBED modeler. Modeler provides high-fidelity modeling, scalable simulation, and detailed analysis of
a broad range of wired and wireless networks with application traffics. We are going to present the project
with the network simulation software RIVERBED modeler which is able to efficiently analyze the
performance of the protocols and technologies in network infrastructure models of realistic scale.
Objectives:
 To design network using Riverbed Modeler
 To configure the appropriate applications and profiles
 To obtain and analyze the network's performance statistics via simulation
 To study how different design scan respond to the need of services as well as resources provided by a
company
Project Descriptions:
Project is based on the modeling configuration and performance analysis of the customized network which we choose
Enterprise Network to do this project by using the RIVERBED MODELER. The Results will be disclosed by after
configuring the network.
Pre-conditions of Project:
Following are the pre-conditions specified to design the network for a company.
 Having more than 3 LANs connecting to the Internet
 Having at least 15 nodes in each LAN
 Having at least 4 databases, each for one application
 Having at least 3-application traffics among nodes in each LAN (intra-LAN connections)
 Having at least 3-application traffics among nodes in all LANs (inter-LAN connections)
 Having both wired and wireless communications
 Having specified connections (between pairs of specified nodes) and general background
 connections
 Having specified IP addresses for every nodes
 Not limiting to TCP networks
 Applying a link failure

Designand Procedure:
For this project we design an enterprise network. The enterprise we have decided to design is a Retail Store company
SHOPRITEbasedintheUnitedStatesofAmerica.TheRetailstorehasmainofficeinNewJersey,andthree branch offices
inthefollowinglocation:Connecticut,NewYorkandPennsylvania.EachofficeisaLAN.Thereforethissatisfiesourfour
LAN segment requirement. The layout of the network given below:

Each office represents a Local Area Network and has various departments pertaining tothe services offered bythe
company.ThelayoutoftheeachLANaregivenbelowwithprojectrequirements:
SHOPRITE
RETAILSTORE
Main Branch
New Jersey
Management
Sales
HR
Server
New York Branch
Management
Sales
HR
Connecticut
Branch
Management
Sales
HR
Pennsylsvania
Branch
Management
Sales
HR

ImplementationofEnterpriseNetworkDesign:
TheEnterpriseNetworkDesignissimulatedbythesoftwarecalledRIVERBEDMODELERwhichcanbeusedfor
performanceanalysisandtheimplementationofthenetwork.
NetworkModelScenarios:
Step1: WefirstopentheRIVERBEDMODELERsoftwareandstartanewProject.
Step 2: We choose our Project name Final Project LAB 636 with scenario 1.

Step 3: We select an Enterprise Network with its span and choose the default span.

Step 4: After that we choose the network technologies we will be using for our simulation.
Step 5: We can review our selections as shown in the snapshot below.

The following tools are used in the creation of network:
1. Ethernet Hub
2. Wireless LAN and Ethernet Router
3. Nodes/Ethernet workstations
4. Ethernet server
5. Link
6. IP Cloud
7. Application Interface
8. Profile Interface
Step 6: After selection every tool that we needed for Enterprise Network creation. We created a four sub
network for the LAN inside the Enterprise which are connected with IP cloud. Thesub-networks areconnectedto
theIPcloudbyusingPPP28linkswhichcanbefoundinthelinkslistintheobjectpalette.Wealsoplaceapplicationdefinition
and profile definition objects which we will configure further on.

Step 7: In this step we design each of the sub-networks. By double clicking we can be entered in
the sub-network.
Possible Scenarios for creating the sub network with all the requirements:
 Each subnet has a three department –Management, Sales and Human Resource.
 All the Department has five workstations.
 In Main Branch Human Resource department has a wireless connection.
 All the four servers are located in the Main Branch New Jersey.
 All the subnet can be connected to servers through the IP Cloud.
Sub network 1: Main Branch New Jersey
The first subnet serves as the main branch. The main office has three department and all the four
servers (HTTP, FTP, EMAIL and DATABASE) as mentioned before.

 Configuration of all Three Departments and Servers:
We created a LAN for the three departments – Management, Sales and HR of the company and
configured the network elements as described in the table.
Departments IP Address Subnet
Mask
Default Route Workstation Link to
HUB/WLAN
Router
Central node
for each
Department
Management 192.168.1.1
-
192.168.1.5
Class C 192.168.1.254 Ethernet
(fixed mode)
10baseT Ethernet32_hub
Sales 192.168.2.1
-
192.168.2.5
(fixed mode)
HR 192.168.3.1
-
192.168.3.5
Class C 192.168.3.254 wlan_wkstn
(fixed mode)
Wireless Link Wlan_ethernet_
router
The following diagram shows the step to configure the IP and default Route:

We created a four servers in the Main Branch as follows HTTP, FTP, EMAIL and DATABASE
and configured the network elements of servers as described in the table.
Servers IP Address Subnet
Mask
Default Route Workstation Link to HUB Central node
for each
Department
FTP 192.168.4.1 Class C 192.168.4.254 Ethernet
Server
HTTP 192.168.4.2 Class C 192.168.4.254 Ethernet
Server
EMAIL 192.168.4.3 Class C 192.168.4.254 Ethernet
Server
DATABASE 192.168.4.4 Class C 192.168.4.254 Ethernet
Server

The CISCO 3640 router is used to router information between two LAN segments and uses store
and forward routing. The router connects to the IP cloud with the help of a PP28 link. The routing
configuration of the Main branch New Jersey is as shown below:

Sub network 2: New York Branch
The second subnet serves as the New York branch. The New York office has three department
same as like main branch
Mask
HUB/WLAN
Router
Central node
for each
Department
-
192.168.5.5
(fixed mode)
Sales 192.168.6.1
-
192.168.6.5
(fixed mode)
HR 192.168.7.1
-
192.168.7.5
(fixed mode)

configuration of the New York Branch is as shown below:

Sub Network 3: Connecticut Branch
The third subnet serves as the Connecticut branch. The Connecticut office has three department
same as like pervious two branches.
Mask
HUB/WLAN
Router
Central node
for each
Department
-
192.168.9.5
(fixed mode)
Sales 192.168.10.1
-
192.168.10.5
(fixed mode)
HR 192.168.11.1
-
192.168.11.5
(fixed mode)

configuration of the Connecticut Branch is as shown below:

Sub Network 4: Pennsylvania Branch
The fourth subnet serves as the Pennsylvania branch. The Pennsylvania branch office has three
department same as like pervious two branches.
Mask
HUB/WLAN
Router
Central node
for each
Department
-
192.168.13.5
(fixed mode)
Sales 192.168.14.1
-
192.168.14.5
(fixed mode)
HR 192.168.15.1
-
192.168.15.5
(fixed mode)

configuration of the Pennsylvania Branch is as shown below:

 IP Cloud Configuration with all the subnets default gateway
The following diagram shows the step to configure the IP Cloud with all subnets default gateway:

Step 8: Once we have configured all the IP addresses we configure the application and user profiles
for the simulated network by using the Application Config and Profile Config
models.
 Application Configuration
The first step is to drag an Application Config model from the object palette onto our
project workspace. We begin by defining the applications in the Application Config object.
This can be done by right clicking on the model and selecting: Edit attributes-
Application Definitions. The departments I created for the company requires four
servers for the application namely FTP, HTTP, EMAIL and DATABASE.
From the screen shot below we can see that all the applications that we require have already been
defined. We may choose to change the default properties of the defined applications by expanding
the rows further. For this scenario we choose to leave them as they are.

Then we configured the intensity of application usage is selected according to the requirement.
The chosen traffic load are given below for each application:
Application Load
FTP Medium Load
HTTP Heavy Browsing
EMAIL Medium Load
DATABASE Low Load
The selection of load intensity is shown below for one application, FTP:

 Profile Configuration
Now we configure profiles supported in Profile Config. We added the client profiles and
link it with the corresponding servers as shown. The steps are repeated for the other profiles as
shown in below.

Step 9: Now we configure profiles supported by each workstation. We can do this by selecting all
the nodes in each individual department and right clicking and choosing: Edit Attributes-
Application Supported Profiles. For example, we choose all the nodes on in the
Management Department in the Main Branch. We right click on one of the nodes and choose:
edit attributes-Application supported profiles. Now these nodes can use all
the defined applications.
Similarly we define the supported profiles for all the departments in all the sub-networks.
Similarly we define the supported profiles for all the departments in all the sub-networks.

Step 10: Now we configure the servers. While the workstation themselves can be configure to act
as a server, for this scenario we chosen to use node model for each server. We place four servers
in the Branch office at New Jersey. These servers are dedicated servers and each of these servers
creates to one application.
FTP SERVER CONFIGURATION
FTP server is configures to run the FTP services by right clicking on the server model and
choosing: Edit attributes-Application Supported Services-FTP server. This is illustrated in the
given figure.

HTTP SERVER CONFIGURATION
HTTP server is configures to run the HTTP services by right clicking on the server model and
choosing: Edit attributes-Application Supported Services-HTTP server. This is illustrated in the
given figure.

EMAIL SERVER CONFIGURATION
EMAIL server is configures to run the EMAIL services by right clicking on the server model and
choosing: Edit attributes-Application Supported Services-EMAIL server. This is illustrated in the
given figure.

DATABASE SERVER CONFIGURATION
DATABASE server is configures to run the DATABASE services by right clicking on the server
model and choosing: Edit attributes-Application Supported Services-DATABASE server. This is
illustrated in the given figure.

Step 11: After all configuration Enterprise Network of Shoprite is all set for communication.

After all setup we checked the link connection to all nodes subnets and the routers.
 Link Connection Check
All links and paths are connected properly.

Discrete Event Simulation:
 Results and Graphs
We configured everything in the Enterprise Network. Before run the program we choose the
individual statistics we wish to observe. First we choose the global statistics for all servers,
Ethernet and IP with parameters like Traffic sent/received, page response time, download response
time, load and throughput. After that we will choose node statics and link statistics.
1. GLOBAL STATISTICS

After that we run the command from toolbox is used to run the network model. The time can be
set for the simulation to be performed.
Then by click the view result we can observe the statistics. Now the graphs for each application
are shown below.

Statistics of FTP Application
The traffic sent/received and the download response time of the FTP application is given below.
Statistics of HTTP Application
The traffic sent/received and object/page response time of the HTTP application is given below.

Statistics of EMAIL Application
The traffic sent/received and the download response time of the EMAIL application is given
below.
Statistics of DATABASE Application
The traffic sent/received of the DATABASE application is given below.

Statistics of ETHERNET:
The traffic delay of Ethernet is given below.
Statistics of IP:
The traffic dropped of IP is given below.

2. NODE STATISTICS
The node statistics are chosen as shown below

Then by click the view result we can observe the statistics. Now the graphs for each application
for MAIN BRANCH NEW JERSEY shown below.

Comparison of parameters of different application
FTP,HTTP, EMAIL and DATABASE applications comparison of different parameters like
traffic load, traffic received/sent results are given below:
Ethernet Delay Load requests/sec
Packet Received Packet Sent
From the picture we can observe that all output is high in MAIN BRANCH because all the servers
is located in the MAIN BRANCH.

3. LINK UTILIZATION AND THROUGHPUT
PP28 Link between IP Cloud and Main Branch

PP28 Link between IP Cloud and New York Branch

PP28 Link between IP Cloud and Connecticut Branch

PP28 Link between IP Cloud and Pennsylvania Branch

Comparison of Throughout and Utilization
By overlaying all statistics and comparing we can see that maximum link utilization and
throughput are on the links between the IP cloud and the Main office New Jersey.

4. LINK FAILURE
Fail the link to the EMAIL server by right clicking on the link and choosing –fail this link

After running the Discrete Event Simulation again, we got the new results below.
We observe that no Email traffic is sent or received which green color in the figure. Email cannot
be accesses or sent until this link is recovered.

Conclusion:
Through this project we have studied, and attained experience about the use of RIVERBED
MODELER a network simulation tool. By using this simulation tool we develop proprietary wired
and wireless protocols and technologies, evaluate the servers in using different applications and
finally test and demonstrate design in realistic scenarios.
We have also learned how to design a small Enterprise Network and comprehended the analyze
the network in a different perspectives.

Modeling, Configuration and Performance Analysis of the customized network using OPNETRIVERBED Modeler

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

En vedette

En vedette (11)

Similaire à Modeling, Configuration and Performance Analysis of the customized network using OPNETRIVERBED Modeler

Similaire à Modeling, Configuration and Performance Analysis of the customized network using OPNETRIVERBED Modeler (20)

Modeling, Configuration and Performance Analysis of the customized network using OPNETRIVERBED Modeler