Documente Academic
Documente Profesional
Documente Cultură
Procedure:
Take a piece of CAT5 Cable and strip of the plastic cover from about one inch from the
open end Unbind the twisted pairs and arranged the wires in the following sequence :-
1) White Orange
2) Orange
3) White Green
4) Blue
5) White Blue
6) Green
7) White Brown
8) Brown
Insert the wires into the RJ45 Connector and crimp using a crimper.
Repeat the process for the other end keeping the order of wires exactly same.
Test the wire using a cable tester.
WHITE ORANGE
WHITE ORANGE
ORANGE ORANGE
BLUE BLUE
GREEN GREEN
BROWN BROWN
Practical No: 2
Aim: To make and test a cross over cable
Introduction:
A cross over cable is a LAN Cable i.e. used to connect two similar devices, Such as a
computer to computer, router to router and hub to hub. This cable is made using CAT5 UTP
Wire and RJ45 Connector. This cable is also called non-modem as it is used to transfer data
between two computers without connecting them to a modem.
Material Required:
Procedure:
Take a piece of CAT5 Cable and strip of the plastic cover from about one inch from the
open end Unbind the twisted pairs and arranged the wires in the following sequence :-
1) White Orange
2) Orange
3) White Green
4) Blue
5) White Blue
6) Green
7) White Brown
8) Brown
Insert the wires into the RJ45 Connector and crimp using a crimper.
To make a cross over cable the pin configuration is similar to the straight through cable but
for the other end. We swap pin1 with pin 3 and pin2 with pin 6.
Test the wire using a cable tester.
WHITE ORANGE WHITE GREEN
ORANGE GREEN
BLUE BLUE
GREEN ORANGE
BROWN BROWN
Practical No: 3
Aim: To make and test a roll overcable
Introduction:
A roll over cable is a network cable i.e. used to connect a computer to the console port to
the network router this cable is also called a yost cable and it enables the network engineer
to perform the programming operation on a router.
Material Required:
Procedure:
Take a piece of CAT5 Cable and strip of the plastic cover from about one inch from the
open end Unbind the twisted pairs and arranged the wires in the following sequence :-
1) White Orange
2) Orange
3) White Green
4) Blue
5) White Blue
6) Green
7) White Brown
8) Brown
Insert the wires into the RJ45 Connector and crimp using a crimper.
To make a roll over cable the pin configuration is reverse of both ends.
Test the wire using a cable tester.
WHITE ORANGE BROWN
Lab Description:
A network is created with a 5-routers-ring-backbone and 2 workstations (A and B) directly
opposite. A will send an ECHO REQUEST to B, and B will answer with an ECHO REPLY.
Well check out that the REQUEST packet went through the three routers between peers,
and the REPLY packet came back using the same path (the routing protocol for this Lab is
RIP). In a second scenario, one of this links will fail, and we will study how this change the
ping traces.
Creating the Scenario:
1) Open a new Project in OPNET IT Guru Academic Edition (File New Project) using the
following parameters (use default values for the remainder):
Press Next several times to end the Start up Wizard. The Project Editor will be launched
with a blank Grid.
3) Insert two workstations Sm_Int_wkstn and connect each other with 10BaseT
wires:
Connect the two workstations to the two routers directly opposite using 10BaseT
wires from the same palette.
Now the network is complete and is time to set the ICMP traffic. The first step is to
place an IP Attribute Config control. This can be found in the internet_toolbox
palette.
Edit the control properties (right click Edit Attributes). The parameters to be set
can be found in IP Ping Parameters row 0 (Pattern: Default):
a) Interval (sec): 90
b) Count: 1000
c) Record Route: Enabled
Press OK to accept the changes
1) Click on configure/run simulation at the Project Editor, and set this values:
a) Duration: 1 hour(s).
b) In the Global Attributes tab,
RIP Sim Efficiency: Disabled. RIP messages will be sent all the time during the
simulation.
RIP Stop Time: 10000. Routing Tables will be updated during all the simulation
(the simulation is finished before RIP stops).
IP Routing Table Export/Import: Export. We will export routing tables to a file
at the end.
2) Click on Run.
Results analysis:
Once the simulation is over,
1. Exit the simulation window by clicking on Close.
2. At the Project Editor, click Results Open Simulation Log. Review the ECHO
and ECHO REPLY paths, and the routers the packets have gone through. All this
information is at the PING REPORT, as seen at the picture below:
Output:
with failure
Without failure
Without failure
With failure
Practical No: 5
Aim: To study RIP routing protocol and create timed link failures and recoveries.
Introduction:
The RIP Protocol (Routing Information Protocol) is, in a nutshell:
Designed to reach a stable routing table with the less Administrator management as
possible.
The messages that routers send each other are sent to the multicast address to
reduce the hosts processing load.
It is a Intra-Domain and Vector-Distance protocol based in the Bellman-Ford
algorithm.
Uses the hop count metric.
It is used in middle-size networks with no more than 15 hops.
RIP messages are encapsulated inside UDP (port 520) and are sent once every 30
seconds, even if there are no changes in the network.
No authentication is required.
It was released in BSD Unix for the first time. The first version was RIPv1, a
classful routing protocol. RIPv2 extended it using classless routing and other
advantages.
It is defined in RFC 1058 (RIPv1) and RFC 2453 (RIPv2). The RFC 2091 supports
Triggered Extension.
All routers in the network have a routing table to indicate the link to forward IP packets .
Every 30 seconds, all routers send UDP messages to the surrounding routers, indicating the
distance, expressed in hops, to the other routers.
The router that receives the UDP message increases 1 unit the distance and will lookup in
its tables if theres a shortest path to the destination. If theres no shorter link then the
routing tables will be updated.
After several iterations the protocol will converge, and every router in the network will
know how to route each IP packet it receives, and this route will be the shortest.
Lab Description:
Four routers are connected each other in a ring topology. Each router has two LANs
attached. We are going to design three scenarios: No Failure, where all the links will work;
With Failure, with a specific link that is going to fail during the simulation and stops
working in the future: With Failure And Recovery, where the link that failed is recovered
later, and restarts working as before.
The purpose of this scenario is to represent with a bar chart the routing table updates and to
see the evolution of the routing tables.
Creating the Scenario:
1) Open a new project in OPNET IT Guru Academic Edition (File New Project) with the
following parameters (leave default values for the remainder):
Project Name: mukesh023_RIP
Use the Next button in the Start up Wizard until the end. A new blank grid shall open in the
Project Editor.
2) Deploying devices and controls upon the Grid:
The following table summarizes all the nodes that have to be deployed in the scenario, and
the Object Palette where can be found.
In the Project Editor, click on configure/run simulation , and use the following
parameters:
a) Duration: 10 minute(s).
b) On the Global Attributes tab,
IP Dynamic Routing Protocol: RIP. This sets RIP protocol for all the routers in the
scenario. We can do this also in the Project Editor doing Protocols IP Routing
Configure Routing Protocols and setting RIP in all interfaces.
IP Interface Addressing Mode: Auto Addressed / Export
RIP Sim Efficiency: Disabled. If this attribute is enabled, the RIP protocol will stop
after the Stop Time. But instead of this, we want it to continue updating the routing
tables when there are changes. This is precisely what we will do in the second scenario,
by programming a controlled link failure to study routing changes.
RIP Stop Time: 10000 will ensure that the tables wont stop updating during the
simulation.
IP Routing Table Export/Import: Export. This will export the routing tables to a file
when the simulation ends.
The IP addresses of all the interfaces are generated automatically during the
simulation. When we set IP Interface Addressing Mode: Auto
Addressed/Export we made all this information to be able for analysis. We will
export this data into a Generic Data File (gdf).
(a) On the System window, choose File Model Files Refresh Model Directories. OPNET
will search the models directory and update the file list.
Dont forget that the System window can be open in the Project Editor if its
closed (Windows System).
In the System window: File Open, and choose Generic Data File. Use the filename
<your_name>_RIP-NoFailure-ip_addresses. This file is generated automatically
during the simulation. Click OK.
a) An editor will pop up with the Generic Data File we choose. This contains the
IP addresses of all the active interfaces in our network model.
3) Comparing the routing tables:
Steps to visualize the routing tables of a router, for instance Router 1, for the two
scenarios :
In the Project Editor, Results Open Simulation Log.
Click on the COMMON ROUTE TABLE entry for the router.
The routing tables export is not saved until the end, because we are using the
Once at End of Simulation option.
Output:
Traffic sent:
Traffic received
PRACTICAL NO. 6
Aim: To configure and analyze the performance of the Open Shortest Path First
(OSPF) routing protocol.
Overview:
OSPF introduces another layer of hierarchy into routing by allowing a domain to be
partitioned into areas. This means that a router within a domain does not necessarily
need to know how to reach every network within that domainit may be sufficient for
it to know how to get to the right area. Thus, there is a reduction in the amount of
information that must be transmitted to and stored in each node. In addition, OSPF
allows multiple routes to the same destination to be assigned the same cost and will
cause traffic to be distributed evenly over those routers.
Procedure:
Create a New Project
1. Start Riverbed Modeler Academic Edition Choose New from the File menu.
2. Select Project and click OK mukesh023_OSPF, and the scenario No_Areas
Click OK.
3. In the Startup Wizard: Initial Topology dialog box, make sure that Create Empty
Scenario is selected Click Next Select Campus from the Network Scale list
Click Next three times Click Finish.
Create and Configure the Network
Initialize the Network:
1. The Object Palette dialog box should now be on top of your project workspace. If it
is not there, open it by clicking . Select the routers item from the pull-down menu on
the object palette.
a. Add to the project workspace eight routers of type slip8_gtwy. To add an object
from a palette, click its icon in the object palette Move your mouse to the workspace
and click to place the object You can keep on left-clicking to create additional
objects. Right-click when you are finished placing the last object.
2. Switch the palette configuration so it contains the internet_toolbox. Use bidirectional
PPP_DS3 links to connect the routers. Rename the routers as shown below.
3. Close the Object Palette and then save your project.
4. Select RouterA and RouterB only Select the Protocols menu IP Routing
Select Export Routing Table Click Selected nodes on the Export Routing dialog
box Click OK on the Status dialog box.
5. Click somewhere in the project workspace to disable the selected routers and select
the Protocols menu IP Addressing Select Auto-Assign IP Addresses... Click
OK on the Auto-Assign IP Addresses dialog box.
6. Save your project.
Configure the Simulation Here we need to configure some of the simulation
parameters:
1. Click on and the Configure Simulation window should appear.
2. Set the duration to be 10.0 minutes.
3. Click Run and then save your project.
Duplicate the Scenario
In the network we just created, all routers belong to one level of hierarchy (i.e., one
area). Also, we didnt enforce load balancing for any routes. Two new scenarios will be
created. The first new scenario will define two new areas in addition to the backbone
area. The second one will be configured to balance the load for the traffic demands
between RouterB and RouterH.
The Areas Scenario:
1. Select Duplicate Scenario from the Scenarios menu and give it the name Areas
Click OK.
2. Area 0.0.0.1:
i. Select the three links that connect RouterA, RouterB, and RouterC by shiftclicking on
them Select the Protocols menu OSPF Configure Areas Assign the value
0.0.0.1 to the Area Identifier, as shown Click OK.
ii. Right-click on RouterC Edit Attributes Expand the IP Routing Parameters
hierarchy Expand the OSPFv3 Parameters hierarchy Expand the Loopback
Interfaces hierarchy Set Number of Rows value to 1 Expand the row hierarchy
Set Status value to Enabled Assign 0.0.0.1 to the value of the Area ID attribute
Click OK.
3. Area 0.0.0.2:
i. Click somewhere in the project workspace to disable the selected links and then
repeat step 2-i for the three links that connect RouterF, RouterG, and RouterH but
assign the value 0.0.0.2 to their Area Identifier.
Aim: To study the role of firewalls and virtual private networks (VPNs) in providing
security to shared public networks such as Internet.
OVERVIEW
A firewall is a specially programmed router that sits between a site and the rest of the
network. It forwards packets from one network to another, but it also filters the
packets that flow through it. A firewall allows the system administrator to implement a
security policy in one centralized place.
A VPN is an example of providing a controlled connectivity over a public network.
VPNs utilize a concept called an IP tunnel-a virtual point-to-point link between a pair
of nodes that are actually separated by an arbitrary number of networks. The virtual
link is created within the router at the entrance to the tunnel by providing it with the IP
address of the router at the far end of the tunnel.
CREATE AND CONFIGURE THE NETWORK
1 Create new project. project Name :mukesh023_VPN
Scenario Name :NoFirewall
Click quit on the set up wizard.
2INITIALIZE THE NETWORK
i Add following objects : Application Config, Profile Config,
IP32_Cloud, One PPP_server, three Ethernet 4_slip8_glwy routers &
two ppp_wkatn hosts.
ii Rename the objects and connect them using PPP DS1 links.
3 CONFIGURE THE NODES
i Assign Default to the Application Definitions Attributes of Application
node.
ii Assign Sample Profiles to Profile Configuration Attribute of profiles
node.
iii Assign all to Application: Supported Services attribute of the Server
node.
iv Set Prefix Name = Sales Person to Application : Supported profiles
attribute for Sales A and Sales B nodes.
CHOOSE THE STATISTICS
1
Choose Individual Statistics & check the following:
i Global Statistics DB Query Response Time (sec)
ii Global Statistics HTTP- Page Response Time(sec)
2 Choose Individual Statistics of sales A node & check the following:
i Client DB Traffic Received (bytes/sec)
ii Client Http Traffic Received (bytes/sec)
3 Repeat Step 2 for Sales B node &Save project.
`FIREWALL SCENARIO
1
Select Duplicate Scenario & name it Firewall.
2
Assign Ethernet2_slips_firewall to the model attribute for router C.
3
Expand the hierarchy of the proxy server Information attribute. Expand row
1, for the Database application & assign No to the proxy server deployed
attribute. Click OK.
FIREWALL_VPN SCENARIO
1 Select Duplicate Scenario & name it Firewall_VPN.
2 Remove the link between router C & the server.
3 Add one Ethernet 4_slip8_gtwy and one IP VPN config.
4 Use two PPP DS1 links to connect the new router to router C and to the
server.
5 Rename the new router to router D & IP VPN config object to VPN.
Output:
Average DB Query Response Time:
Average Point-to-point throughput of the link:
Fig.1
6. Make sure to save your project. Configure the network nodes
Here you will configure the traffic generated by the stations.
1. Right-click on any of the 16 stations (node_0 to node_15) . Select Similar Nodes. Now all
stations in the network are selected.
2. Right-click on any of the 16 stations . Edit Attributes.
a. Check the Apply Changes to Selected Objects check box. This is important to avoid
reconfiguring each node individually.
3. Expand the hierarchies of the Traffic Generation Parameters attribute and the Packet
Generation Arguments attribute . Set the following four values:
Fig 2
Hints:
To remove a link, select it and choose Cut from the Eidt menu (or simply hit
the Delete key). You can select multiple links and delete them all at once.
To add a new link, use the 10BaseT link available in the Object Palette.
10. Save the Project. Run the Simulation
To run the simulation for both scenarios simultaneously:
1. Select Manage Scenarios from the Scenarios menu.
2. Change the values under the Results column to <collect> (or <recollect>) for both
scenarios. Compare to the following figure.
Fig 4
3. Click OK to run the two simulations.
4. After the two simulations runs complete, one for each scenarios, click Close.
5. Save your project. View the Results
To view and analyze the results:
1. Select Compare Results from the Results menu. (Or right click in the workspace).
2. Change the drop-down menu in the lower-right part of the Compare Results dialog box
from As Is to time_average.
3. Select the Traffic Sent (packets/sec) statistics and click Show.
4. Select the Traffic Received (packets/sec) statistics and click Show.
5. Select the Delay (packets/sec) statistics and click Show.
6. Select the Collision Count (packets/sec) statistics and click Show.
7. On the resulting graph right-click anywhere on the graph area . Choose Add Statistics .
Expand the hierarchies as shown below . Select the Collision Count statistics for Hub2 .
Change As Is to time_average . Click Add.
8. Save your project.
PRACTICAL No. 9
1. Right-click on Application Config node . Edit Attributes . Change the name attribute to
Applications . Change the Application Definitions attribute to Default . Click OK.
2. Right-click on the Profile Config node .Edit Attributes . Change the name attribute to
Profiles . Change the Profile Configuration attribute to Sample Profiles . Click OK. Sample
Profiles provides patterns of applications employed by users such as engineers, researchers,
salespeople, and multimedia users.
Configure a subnet:
1. Right-click on the subnet node . Edit Attributes . Change the name attribute to Engineering
and click OK.
2. Double-click on the Engineering node. You get an empty workspace, indicating that the
subnet contains no objects.
3. Open the Object Palette and make sure it is still set to internet_toolbox.
4. Add the following items to the subnet workspace: 10BaseT LAN, ethernet16Switch, and a
10BaseT link to connect the LAN with the Switch . Close the palette.
5. Right-click on the 10BaseT LAN node . Edit attributes . Change the name attribute to LAN
.observe that the Number of Workstations attribute has a value of 10. Click in the Value
column for the Application: Supported Profiles attribute, and select Edit. You should get a
table in which you should do the following:
a. Set the number of rows to 1
b. Set the Profile Name to Engineer. Note: Engineer is one of the sample profiles provided
within the Profile Config object.
c. Click OK twice. The object we just created is equivalent to a 10-workstation star topology
LAN. The
traffic generated from the users of this LAN resembles that generated by engineers.
6. Rename the ethernet16Switch to Switch
7. The subnet should look like the one in figure below.
1. Now you have completed the configuration of the Engineering Department subnet. To go
back to the main project space, click the Go to the higher level button .
2. Make three copies of the Engineering subnet we just created. Click on the Engineering
node . From the Edit menu, select Copy .from the Edit menu select Paste three times, placing
the subnet in the workspace after each, to create the new subnets.
3. Rename (right-click on the subnet and select Set Name) and arrange the subnets as
shown below:
4. Double-click the Research node . Edit the attributes of its LAN . Edit the value of the
Application: Supported Profile attribute . Change the value of the Profile Name from
Engineer to Researcher . Click OK twice .go to the higher level by clicking the button.
5. Repeat step 4 with the Sales node and assign to its Profile Name the profile Salesperson.
6. Repeat step 4 with the E-Commerce node and assign to its Profile Name the profile E-
Commerce Customer.
7. Save the project.
Configure the Servers:
Now we need to implement a subnet that contains the servers. The servers have to support the
applications defined in the profiles we deployed. You can double-check these applications by
editing the attributes of our Profile node. Inspect each row under the Applications hierarchy,
which in turn, is under the Profile Configuration hierarchy. You will see that we need servers
that support the following applications: Web browsing, Email, Telnet, File Transfer, Database,
and File Print.
1. Open the Object Palette and add a new subnet .rename the new subnet to Servers . double-
click the Servers node to enter its workspace.
2. From the Object Palette, add three ethernet_servers, one ethernet16_switch, and three
10BaseT links to connect the servers with the switch.
3. Close the Object Palette
4. Rename the servers and the switch as follows:
5. Right-click on each one of the above servers and Edit the value of the Application:
Supported Services attribute.
a. For the Web Server add four rows to support the following services: Web Browsing (Light
HTTP1.1), Web Browsing (Heavy HTTP1.1), Email (Light) and Telnet Session (Light)
b. For the File Server add two rows to support the following services: File Transfer (Light)
and File Print (Light).
c. For the Database Server add one row to support the following service: Database Access
(Light).
6. Go back to he project space by clicking the Go to the higher level button.
7. Save the project
5. Click OK
6. Repeat step 4 and 5 for defining the background load in the opposite direction your
window of background load table should look like below.
8. Save your project
Run the Simulation
To run the simulation for both scenarios simultaneously:
1. Go to the Scenarios menu . Select Manage Scenarios.
2. Change the values under the Results column to <collect> for both scenarios. Compare to
the following figure.
1. Open the Object Palette dialog box. Make sure that the internet_toolbox item is selected
from the pull-down menu on the object palette.
2. Add to the project workspace the following objects from the palette: Application Config,
Profile Config, QoS Attribute Config, five ethernet_wkstn, one ethernet_server, and two
ethernet4_slip8_gtwy routers.
Note that The QoS Attribute Config node defines attribute configuration details for protocols
supported at the IP layer. These specifications can be referenced by the individual nodes
using symbolic names. It defines different queuing profiles such as FIFO, WFQ, priority
queuing, and custom queuing.
1. Right-click on the FTP Client _ Edit Attributes _ Expand the Application: Supported
Profiles hierarchy _ Set rows to 1 _ Set Profile Name to FTP Profile _ Click OK.
2. Right-click on the Video Client _ Edit Attributes _ Expand the Application: Supported
Profiles hierarchy _ Set rows to 1 _ Set Profile Name to Video Profile _ Click OK.
3. Right-click on the VoIP West _ Edit Attributes.
i) Expand the Application: Supported Profiles hierarchy _ Set rows to 1 _ Set Profile Name to
VoIP Profile.
ii) Edit the Application: Supported Services value _ Set rows to 1 _ Set Service Name to VoIP
Application _ Click OK twice.
4. Right-click on the VoIP East _ Edit Attributes.
i) Expand the Application: Supported Profiles hierarchy _ Set rows to 1 _ Set Profile Name to
VoIP Profile.
ii) Edit the Application: Supported Services value _ Set rows to 1 _ Set Service Name to VoIP
Application _ Click OK twice.
5. Right-click on the FTP Server _ Edit Attributes _ Edit the Application: Supported Services
value _ Set rows to 1 _ Set Service Name to FTP Application _ Click OK twice.
6. Right-click on the Video Server _ Edit Attributes _ Edit the Application: Supported
Services value _ Set rows to 1 _ Set Service Name to Video Application _ Click OK twice.
7. Save your project.
Configure the Routers:
1. Click on the link connecting the East and West routers to select it _ From the Protocols,
menu choose IP . QoS . Configure QoS.
2. Make sure the selected items are as shown in the following QoS Configuration dialog box
_ Click OK.
Note: Since the Visualize QoS Configuration radio button is checked, the link is colored
based on the QoS scheme used.
3. Save your project.
Choose the Statistics
To test the performance of the applications defined in the network, we will collect one of the
many available statistics as follows:
1. Right-click anywhere in the project workspace and select Choose Individual Statisticsfrom
the pop-up menu.
2. In the Choose Results dialog box, select the following global statistic:
i) IP=>Traffic Dropped (packets/sec)
ii) FTP=> Traffic received (packets/sec)
iii) Video Conferencing => Traffic received (Bytes/sec)
iv) Voice=> Packet Delay variation, Packet End-to-End delay, Traffic received (Bytes/sec)
3. Click on the link that connects east Router to West Router. Right click and choose
Individual DES statistics. Under the point-to-point hierarchy, choose (queuing delay ..)
4. Click OK and then save your project.
Configure the Simulation
Here we need to configure the duration of the simulation:
1. Click on and the Configure Simulation window should appear.
2. Set the duration to be 200 seconds.
3. Click Apply and then save your project.
Duplicate the Scenario
In the network we just created, we used the FIFO queuing discipline in the routers. To
analyze the effect of different queuing disciplines, we will create two more scenarios to test
the Priority Queuing (PQ) and Weighted Fair Queuing (WFQ) disciplines.
A. Select Duplicate Scenario from the Scenarios menu and give it the name PQ _ Click OK.
1. Click on the link connecting the East and West routers to select it _ From the Protocols
menu choose IP . QoS . Configure QoS.
2. Make sure the selected items are as shown in the following QoS Configuration dialog box
_ Click OK.