Opnet modeller lab booklet

OPNET Modeller lab booklet- Keith Sharp Glasgow Caledonian University - edited 2012 To do the labs in the Opnet Modeler Introductory Lab Manual requires some additional files which can be downloaded from the following location, or can be issued to you by your lab instructor during a lab session.

Keith Sharp Glasgow Caledonian University - edited 2012

OPNET Modeller lab booklet

Lab Files for Opnet Modeler – Introductory Lab Manual

To do the labs in the Opnet Modeler Introductory Lab Manual requires some

additional files which can be downloaded from the following location, or can be issued to you by your lab instructor during a lab session

At present the lab files can be downloaded from the following location:

Blackboard->Course Documents->Opnet Labs-> Week 1->Labs

From here download the zip file – intro_modeler_labs.zip

Extract the contents of this folder and you will find two folders:

 Hotel_Net

 project_environment

To get started with the labs in the Introductory Lab Manual proceed with the

following steps

1 Start Opnet Modeler via VMware player in the usual way (see the Handout entitled:

“Working with Opnet and VMware Player at GCU ” for instructions on how to do

this)

2 Once you have initialized Opnet Modeler you will see that the following three

folders will be added to the Desktop of the virtual machine:

 op_models

 op_admin

 op_reports

Typically these folders are not found on the desktop for the application so we must

associate these folders with Opnet Modeler so that the application knows to look in

these folders Before we can associate the folders with the application we first follow these steps

i) Copy the folders Hotel_net and project_environment you extracted from the zip

file and put them into the newly created op_models folder on the virtual desktop Note

that files must be dragged and dropped to and from VMware player to action a copy

and paste operation, cutting and pasting alone will not work

Keith Sharp Glasgow Caledonian University - edited 2012

ii) Go to the main console screen for Opnet Modeler

Select File->Manage Model Files->Add Model Directory

Once you click Add Model Diretory the following screen will appear, locate the

op_models folder on your VMware desktop and select it

Click OK to add the directory, the following Confirm Model Directory screen will

appear, select the check box named “Include all sub-directories” only and Click OK

And, finally, from the main menu select:

File -> Manage Model Files -> Refresh Model Directories, to update the

application‟s environment variables

Keith Sharp Glasgow Caledonian University - edited 2012

3 BEFORE STARTING THE LABS PLEASE NOTE:

When doing the introductory labs you may be required to open an existing project at

some point, i.e from the files you downloaded

The default view you will see on doing a File->Open may look like this:

(Please note that the below screenshot will be visible only when you will select the op_models from desktop by clicking on the Look in)

Please note that this is the default view for opening files and projects in Opnet

Modeler 16.1, however the traditional File->Open view for Opnet Modeler can be

switched to by clicking on the Switch to file chooser organized by model directories

button:

which is located in the bottom left of the default File-Open view

To change to the traditional view – which is what we will be using and referring to in the lab material for this course – click this button and the view will change to the following screen view below

When you change to this view you can now see that the Model directories now

associates the folder C:\Documents and Settings\Student\Desktop\op_models

with the application

When you expand this directory you will see that the Hotel_net and project_environment sub-directories, which are the project folders you extracted from

the downloaded zip files, are also listed under the model directories

To change back to the previous view click on the Switch to general file chooser

button:

Important: When you create a new Project in Opnet Modeler it will automatically

create a folder with the name you give your project, make sure you select this folder when saving your project – try and keep all your projects organised in your

op_models directory This will make things easier if you wish to save your work

between labs

Remember: It is up to you to save your work between lab sessions Save your lab

files to either a portable storage device, such as a USB memory stick – or you can

save your lab files (i.e the folders op_admin, op_models, op_reports) each week to your student H: drive on the GCU network You must drag and drop these folders

to/from the VMware player to copy them across from/to your chosen storage location If you do save your work each week in this way then any preferences you

alter in Opnet Modeler can be maintained and the above procedure can be reduced to

simply refreshing the model directories

Opnet Modeler projects can become quite large and so each student should have an

increased quota for their H: drive disk space – this should be around 500MB If you have any problems storing projects to your student H: drive/personal storage device ask your lab instructor for assistance

Keith Sharp Glasgow Caledonian University - edited 2012

LAB 3

Simulation of Computer Networks Lab 3: LAN Switching

Lab Objectives:

In this lab you will implement switched local area networks and examine the

performance of different scenarios connecting LANs with switches and hubs

Here you will set up LANs using two different switching devices: hubs and switches Remember that a hub forwards packets which arrive on any of its inputs to all of its outputs A switch on the other hand will forward incoming packets to one or more outputs depending on the destination of packets In the lab below you are going

to study how the throughput and collision of packets in a switched network are affected by the configuration of the network and the type of switching devices used

Overview:

Computer networking involves understanding limitations of equipment and technology, be they physical (number of interfaces on a device) or logical (number of usable IP addresses within a subnet) There is a limit to how many hosts can be attached to a single network and to the size of the geographical area that a network can serve (e.g the physical limitations of transmission media -cabling, wireless signal etc) The most common form of network infrastructure in terms of Local Area Networks (LANs) is a switched Ethernet environment A switch is a device with several inputs and outputs leading to and from the hosts that the switch interconnects Switches allow for the intercommunication between one host and another The central role of the switch in the LAN is to take packets that arrive on an input and forward (or switch) them to the correct output so that they will reach their required destination One key issue with a switch is that it must cope with the finite bandwidth of its outputs If packets for a certain output arrive at the switch and their arrival rate is greater than the capacity of the switch output then we have a problem of contention The switch will be forced to queue, or buffer, packets until the contention lessens If the contention lasts for too long, then the switch will run out of buffer space and will have to discard packets If packets are discarded too frequently, we end up with a congested switch and this makes for an inefficient network

PART 1 - Creating the Project

1. Start Opnet Modeler – Choose File, New, Project, then click OK

2 Name the project <you_initials>_SwitchedLAN, and the scenario HubOnly and then click OK

Keith Sharp Glasgow Caledonian University - edited 2012

PART 2 - Building the Network Model

To create the switched LAN:

1 From the Project Editor choose Topology - > Rapid Configuration… Then from the drop down menu select Star and click Next

2 Click the Select Models… button in the Rapid Configuration dialogue box From the Model List drop down menu choose ethernet and click OK

3. In the Rapid Configuration dialogue box set the following values:

a Center Node Model = ethernet16_hub

b Periphery Node Model = ethernet_station

c Link Model = 10BaseT

d Number = 16

e X = 50, Y = 50

f Radius = 42

Click OK once you have entered the values (note: the 10BaseT link represents

an Ethernet connection operating at 10Mbps)

4 Right-click on node_16, which is the hub -> Edit Attributes and change the name attribute to “Hub1” and click OK

5 Save your project From the Project Editor, File -> Save then you should already

have a folder listed <your_initials>_SwitchedLAN.project in the left hand pane (in

file chooser mode) of the Save As dialogue box, click on this folder and then keeping the File name as <your_initials_SwitchedLAN> click Save

6 Now that you have created the network it

should look similar to the one pictured here:

PART 3 - Configuring the Workstations

Here you will configure the workstations to generate traffic

1 Right click on any of the 16 workstations (node_0 to node_15) – and from

the menu Select Similar Nodes All the workstations in the workspace will

be selected when you do this

2 Right click on any of the 16 stations, Edit Attributes:

Check the Apply Changes to Selected Objects check box - this an important feature

to use to prevent you configuring each node individually

3 Expand the Traffic Generation Parameters attribute, and the Packet Generation Arguments in the hierarchy Set the following 4 values by clicking in

the Value field and selecting Edit:

ON State Time: (exponential) 100

OFF State Time: (constant) 0.0

Interarrival Time (seconds): (exponential) 0.02

Packet Size (bytes): (constant) 1500

Keith Sharp Glasgow Caledonian University - edited 2012

compound attribute called “Traffic Generation Parameters” which lets the modeller

generate streams of “generic packets” (i.e not linked to any specific network

application layer or layer 3 protocol) Consequently this method of traffic generation

is often used to study Layer 2 technologies such as Ethernet, Frame Relay, and ATM, but there are traffic generating workstation nodes for IP also (however here we are investigating Ethernet traffic)

PART 4 – Choosing Statistics for Collection

Now that we have configured the nodes to generate traffic within the LAN we now need to choose the traffic-related statistics we wish to collect during the simulation

To choose statistics to be collected during the simulation:

1) Right click anywhere in the project workspace and select from the menu Choose

Individual DES Statistics

2) In the Choose Results dialogue box, choose the following 4 statistics:

Ethernet Delay: Global Statistics->Ethernet->Delay (sec)

The Ethernet Delay represents the end to end delay of all packets received by all the stations

Traffic Received: Global Statistics->Traffic Sink->Traffic Received (packets/sec)

Represents the amount of traffic received by all the sinks across all the nodes in the network, a sink is where a packet terminates, on termination any associated statistics are updated for example the Traffic Received global statistic would be incremented (Double-click on a workstation node, how many sinks does a workstation have?)

Traffic Sent: Global Statistics->Traffic Source->Traffic Sent (packets/sec)

Represents the amount of traffic sent by the traffic sources (in this case all the packet generating nodes we set in the scenario, i.e all the ethernet workstation nodes)

Collision Count: Node Statistics->Ethernet->Collision Count

This is the total number of collisions 1 encountered by the hub (or hubs) during packet transmissions within the scenario

3) Click OK to apply these statistics collection

settings to your scenario

Next step now is to configure the simulation

parameters

Keith Sharp Glasgow Caledonian University - edited 2012

collisions, the event of a collision causes the Ethernet to undergo a recovery procedure.

PART 5 – Configure the Simulation

Here we configure the duration of the simulation:

a) Click on the Configure/Run Simulation button in the Toolbar on the

Project Editor or alternatively click on DES->Configure/Run Discrete Event

Simulation in the Project Editor Menu bar

b) Set the duration to be 2.0 minutes

c) Click Apply to keep this setting and then close the window (Note we are NOT running the simulation at this point merely configuring the parameters for simulation)

PART 6 – Duplicate the Scenario

The network we just created utilizes only one hub to connect the 16 workstations

We need to create another network that utilizes a switch and see how this will affect the performance of the network To do that we will create a duplicate of the current network:

1) Select from the Scenarios menu select Duplicate Scenario … and set the name of

it to HubAndSwitch – then Click OK

Note: It is important to note that when you are comparing network scenarios, to try and

change as few elements as possible between the scenarios In general any simulation study experiments should be controlled so that any change in the simulation output, which is invoked by a change in the simulation model, should be easily accounted for If too many parameters are altered between each simulation, or each instance of a simulation model, then it becomes more difficult to build confidence in what has caused the change in the resultant output of the model

2) Open the Object Palette by clicking on the icon in the tool bar on the Project

Editor or select from the Project Editor menu Topology->Open Object Palette –

and locate the Ethernet in Shared Object Palettes

Note: you can switch between icon view (below left) and tree view (below right)

Keith Sharp Glasgow Caledonian University - edited 2012

3) We need to place an additional hub and a switch in the new scenario:

a To add the Hub double-click on its icon in the object palette

ethernet16_hub if in tree view, or single click if in icon view, then move

your mouse pointer over the project workspace and click to drop at the

location you select Right click to stop deploying hub objects

b Repeat the same procedure to add the Switch – ethernet16_switch

(Question: what is the significance of the number 16 in the model name?)

c Close the Object Palette

4) Right click on the new hub, select Set Name, rename to Hub2

5) Right click on the new switch, select Set Name, rename to Switch

6) Reconfigure the network of the HubandSwitch scenario so that is looks like the following one:

To remove a link, select it and choose

Cut, from the Edit

menu (or simply hit the

Delete key) You can

select multiple links by

Shift+left clicking

successive links and then you can delete them all at once

To add a new link,

use the 10BaseT link

available in the

Object Palette

Use the View->Layout-

>Scale Node Icon Interactively feature

in the project Editor

to scale individual or groups of icons to better utilise your workspace

The new HubandSwitch scenario only comprises of two new objects, an additional

hub and a switch The network has the switch interconnecting two ethernet hubs

each with 8 ethernet workstations attached

7) Save your project

PART 7 – Run the Simulation

To run the simulations for both scenarios together follow these steps:

1 Select from the Scenarios menu Manage Scenarios

2 Change the values under the Results column to <collect> (or <recollect>) for both scenarios Compare with the following screenshot:

3 Click OK to run the two simulations Note that depending on the speed

of your processor, this may take a few minutes to complete

4 Click on View Details in bottom left corner of DES Execution Manager

Dialogue Box After the two simulations run complete (they will run in

succession), one for each scenario, click the Close button

[If you get error messages then check your model is configured correctly, as above,

or ask your lab instructor for assistance.]

PART 8 – View the Results

To view the results (i.e the statistics you selected for gathering during the

Keith Sharp Glasgow Caledonian University - edited 2012

almost identical on average in the preview panel

Note: To view statistics collected during

simulation across different scenarios select them from here The select results are then previewed in the panel to the right.

2 To display the results as a graph you must click the Show button at the

bottom right of the Compare Results window

3 Deselect the previously selected statistics to clear the preview panel

4 Select the Traffic Received

(packet/sec) statistic (under

Global Statistics > Traffic Sink

-> Traffic Received packets/sec)

and click

Show (for both scenarios

HubOnly and HubAndSwitch)

The resulting graph should

resemble the one shown here As

you can see the traffic received in

the second scenario,

HubAndSwitch, is higher than

that of the HubOnly scenario:

Question: Why do think this

is the case?

5 Again deselect the

previously selected statistics

and select the Delay (sec)

statistic for both scenarios and

click Show The resulting

graph should resemble the one

here ( Note: Your results may

differ slightly to this due to

different node placement –

since Delay takes physical

distance into consideration)

6 Again deselect the previously selected statistics from the Compare Results

window and now select under the Object Statistics:

Office Network -> Hub 1-> Ethernet -> Collision Count

- From both scenarios, HubOnly and HubAndSwitch

Office Network -> Hub 2-> Ethernet -> Collision Count

- From the HubAndSwitch scenario only

Keith Sharp Glasgow Caledonian University - edited 2012

- When you have selected the above then click Show to display the graph

Question: Why does the Switch in the HubAndSwitch scenario not have

a Collision Count statistic associated with it?

7 The resultant graph should resemble the one below:

8 Save your project

[END OF LAB]

Keith Sharp Glasgow Caledonian University - edited 2012

Glasgow Caledonian University – Keith Sharp 2012

LAB 4

Keith Sharp Glasgow Caledonian University - edited 2012

Simulation of Computer Networks Lab 4: Building Network ModelsLab Objectives:

In this lab you will build a larger network model in which you will learn more about

how Opnet Modeler represents computer networks In addition you will revise some

basic networking concepts including IP addressing, subnetting, and the OSI model The lab demonstrates how Opnet Modeller performs subnetting You will be configuring a fairly complex LAN topology using different networking devices (including, workstations, hubs, bridges, switches, routers, and network cloud models)

Reminder:

IP addresses (specifically IPv4) are traditionally given classes There are five standard

classes named simply A,B,C,D and E – which essentially are used to determine the host part and network part of an IP address

An IP, is simply a number, whose basic representation is a binary number, typically written in dotted decimal notation for e.g

For e.g the above network address is a Class C address and so has a subnet mask of

24 bits and would be written as: 192.168.10.1/24, subnet mask /24 = 255.255.255.0 (The leading 24 binary digits in the mask = 1 for representing the network, the last eight = 0 determining the host portion)

The network address is the first 24 bits of the IP address = 192.168.10.0

The host address is represented in the last 8 bits = 1 = 00000001 (binary), 1 (decimal)

Below is a summary of the IPv4 address Classes:

(you should be familiar with the first 3 classes)

Class Leading Start End address Default Subnet Mask Total #of host

PART 1 - Creating the Project

5. Start Opnet Modeler – Choose File, New, Project, and then click OK

6 Name the project <your_initials>_Subnetting, and the scenario

ComponentsOnly and then click OK

7. In the Startup Wizard: Initial Topology dialogue box, ensure that Create

Empty Scenario is selected Click Next, then choose Campus from the

Network Scale list (leaving the defaults), -> Click Next, three times – and then

finally click Finish

8 Close the Object Palette when your empty project opens

PART 2 – Preparing the workspace

1 Change the background properties in the Project Editor as follows

View->Background- >Set Properties…

The following properties should be set to:

Units: Kilometres

Drawing: Dashed

Division: 1

2 Now you will collect the components from the Object palette you will require to

build the LAN topology

In the ComponentsOnly scenario workspace you will place and organise the

following objects in the project workspace by following these steps

4 Open the Object Palette if it is not already open

5 In the Object Palette take the following components from the

Sm_Int_Model_List palette and drop them into the project work space

Keith Sharp Glasgow Caledonian University - edited 2012

3 x CS_7505_5s_e6_fe2_fr4_sl4_tr4 routers (under Cisco 7505)

Note: that the Cisco 7505 series routers have the wrong icon associated with them, this is

a bug in Modeler 16.1, but the model is right one which you can confirm by right clicking

the router icon and choosing edit attribute In front of make you can confirm the router model

n.b the graphical icon of a model does not affect its behaviour in any way

3 From the object ethernet palette take:

4 x ethernet16_bridge bridges 8 x

ethernet16_hub hubs

1 x IP Attribute Config object

ether

4 From the 3Com palette take:

1 x 3C_SSII_3900_4s_ae36_ge3 switch (in the 3Com SSII 3900-36 folder)

5 From the internet_toolbox palette take:

2 x ppp_server servers

1 x ip32_cloud Internet cloud model

3 Now rename the nodes you have collected to the names in figure 2.1 We need 23

workstation nodes using simply the names 1,2,3,…,23 – however we do not want to rename these all individually 23 times The simplest way to create consistently named objects in Opnet is to name one first and then copy that instance multiple times The copy operation is smart enough to know to increment the number portion of the name

Try this out for yourself:

Rename the Sm_Int_wkstn to simply the number „1‟, then copy this object by selecting it and hit Ctrl+C to copy the node, and then press Ctrl+V, your pointer

should now change its appearance to a box shape – by left clicking in the workspace

you will have dropped a copy of the Sm_Int_ wkstn model with the name „2‟ Repeat the Ctrl+V then Left-click operation another 21 times to obtain 23 copies of the model (Similarly if you named the model instance PC1, it would be pasted as PC2, PC3, PC4 etc on subsequent paste operations.)

Keith Sharp Glasgow Caledonian University - edited 2012

The following figure is what you should have in your ComponentsOnly scenario:

Figure 2.1

Your initial scenario should have the above components, named and numbered as

shown in figure 2.1

PART 3 – Duplicate the scenario

Duplicate the ComponentsOnly Scenario and call the new scenario NetworkModel via the Project Editor Menu: Scenarios- >Duplicate Scenario…

PART 4 – Building the Network Model

Using the example in figure 2.2 as a guide place , connect and rename the

network nodes in the topology shown, the links to use are discussed below:

Keith Sharp Glasgow Caledonian University - edited 2012

Figure 2.2 – Network Model Topology

Keith Sharp Glasgow Caledonian University - edited 2012

Building the Network Model (continued):

a) Use 10BaseT for all the links except servers

b) Use PPP_DS1 links for any links to the servers and the Internet cloud

Note: these links are available together in the internet_toolbox palette

Changing Link Appearance

Sometimes network models can be made clearer by assigning different colours

and widths to the links in the network (this has been done in Figure 2.2) To do

this with your links, select the links you wish to change and right click on one of

them and select Edit Attributes (Advanced) -making sure if you have selected

more than one link to check the Apply changes to selected objects check box:

To change the colour of a link edit the color attribute – note the colours are stated in Hex format (if you are have used web design packages you will be familiar with this) – the colour of the text in this attribute is the same as the link

Edit the color by clicking on the Value field and select your chosen colour

To change the width of your link edit the thickness attribute by entering a

decimal value into the Value field for this attribute (measured in number of

pixels)

Additionally links do not need to be restricted to straight line connections between nodes By clicking at intermediate points between nodes when drawing a link, you can influence the path of the link between network objects In the real world network cables are rarely laid in straight lines between network nodes We simply deploy them here without this consideration for convenience

c) Change the appearance of all the workstation nodes:

Your workstations may just be currently represented by a generic node icon or blue circle To make this more representative of a network object change the icon of all the workstations by doing the following:

i) Right-click on any of the workstations in the NetworkModel scenario and

click on

Select Similar Nodes – to highlight all the Sm_Int_wkstn nodes

ii) Now Right-click on one of the selected nodes then select Edit

Attributes (Advanced) and check the Apply changes to selected objects

checkbox

iii) Click in the Value field of the icon_name attribute, then making sure that the symbolic icon palette is selected in the drop down box of the Icon Palette find the wkstn_windows icon, click on it, and then click OK to apply the change

to all the workstations Use View->Layout->Scale Nodes Interactively to scale

the workstations to a smaller size (50%)

Keith Sharp Glasgow Caledonian University - edited 2012

Part 5 – Configuring the Network Model

Now that you have built the basic topology and altered the appearance of your nodes you are now ready to configure the network

The first task we are going to do is configure IP addressing for our network objects, namely:

1 Configuring network address parameters for the workstations

2 Configuring network addresses parameters for the Cisco 7505 routers

3 Configuring network addresses parameters for the Cisco 7000 routers

4 Configuring IP addresses for all network interfaces

1 Configuring network addresses for the workstations:

a) Click on any workstation in the NetworkModel scenario, and use Select

Similar Nodes from the right-click menu to select all the workstations

b) Now all the workstations are selected, click on one and from the right-click

menu select Edit Attributes, make sure and check Apply Changes to Selected Objects to change the parameters for all workstations at once:

Change the following values for the workstations:

IP->IP Host Parameters->Interface Information->Address: Auto Assigned IP->IP Host Parameters->Interface Information->Subnet Mask: Class C

(natural)

2 Configuring network addresses for the Cisco 7505 routers:

a) For the Cisco 7505 routers (Router1,2,3)

Use the following values:

When you select Edit the following screen will appear:

Click on the Rows box in the bottom left corner and change the number 0 to 1,

by clicking inside the Rows box

The loop back interface LB0 will be created for the router – set the following

parameters for this interface by clicking on its associated fields in the Table:

Address: AutoAssigned

Subnet Mask: Class C (natural)

Click OK twice – making sure you have checked the Apply to selected objects

check box

3 Configuring network addresses for the Cisco 7000 routers

Repeat the same steps as in 2 above for the Cisco 7000 routers (i.e Router 4 and 5)

4 Configuring IP addresses for all network interfaces

Before configuring IP addresses on all the interfaces duplicate the NetworkModel

scenario (it is always a good idea to save larger projects in stages, scenarios give a natural facility to enable this) From the Project Editor:

Scenarios- >Duplicate Scenario…

Call the duplicated Scenario – AutoAssignIPv4

Keith Sharp Glasgow Caledonian University - edited 2012

Part 6 – Assigning Services to Servers

To assign services to the servers in the topology follow these steps:

a) Right-click on a server and then click on Edit Attributes->Applications->

Application: Supported Services and click in the Value field and select Edit…

When the Table view appears change the value of the Row box from 0 to 1

You should now see a similar view:

Click on the Name field of Row 1 and the following choices will appear:

These choices will appear as long as the

Description field is Supported

To add a service just select one of the predefined

values in the drop down menu (listed here ->)

Keith Sharp Glasgow Caledonian University - edited 2012

For the Print and DB Server add the following services to the server:

File Print (Heavy), Database Access (Light)

For the FTP and Telnet Server add the following services to the server:

File Transfer (Heavy), Telnet Session (Heavy)

Once you have set the services for the servers click OK to apply the changes

Part 7 – Create a ping traffic demand

You will come to learn later about the different mechanisms which can be used to represent traffic in Opnet, but for now just follow the steps given here to define a ping traffic demand, this will allow us to then analyse ping traffic behaviour through our network model we have created

Note: A traffic demand is used to represent traffic flows between two specific nodes

We are now going to create the ping traffic demand for the AutoAssignIPv4 scenario:

a) From the Object Palette select from the internet_toolbox palette the

ip_ping_traffic object and then click on workstation 23 as the starting point, and then

select the FTP and Telnet Server as the traffic end

b) The ip_ping _traffic demand will appear as an arrow from the

starting point object to the end point object of the traffic flow

The ping traffic of course has to traverse the entire network and

cross the Internet cloud to reach the FTP and Telnet Server We

are going to analyse the path of the ping traffic demand in Part

10

To set the parameters of the demand, Right click on the arrow

representing the ping traffic and click on

Edit Attributes:

Set Ping Pattern: Record Route and press OK Now we will be

Keith Sharp Glasgow Caledonian University - edited 2012

Part 8 – Running the Simulation

1 Remaining in the AutoAssignIPv4 scenario click on the Configure/Run

Simulation icon, or select from the Project Editor,

DES->Configure/Ru n Discrete Event Simulation…

Alternatively use the keyboard shortcut Ctrl+R, to set the simulation parameters

2 Set the Duration to 1 hour(s), leaving the other parameters as their defaults and

Click on Run

Part 9 – IP address assignment analysis

In this section you will write down all the IP addresses assigned to each node and

interfaces in the AutoAssignIPv4 scenario - to obtain the IP addresses for your

network objects use the following steps:

Note: Fill in the table provided in this lab document, it has been prepared for this task

i) To obtain the IP addresses of workstations and servers:

-Perform a Right-click on the node

-Select Edit Attributes

-Expand Attribute IP->IP Host Parameters->Interface Information->Address

ii) To obtain the IP addresses of routers:

-Perform a Right-click on the node

-Select Edit Attributes

-Expand Attribute IP->IP Routing Parameters->Interface Information->rows

Where each row represents an interface, since routers can have multiple interfaces

there will be multiple rows for the maximum number of interfaces the device can support, some of these interfaces may support different link technologies Note that only the connected interfaces will be assigned IP addresses by the Auto- Assign

operation performed earlier Clicking the Value field (…) to the right of the Interface

Information Attribute will bring up these row values in a tabular form

1) To make the collection of IP addresses a bit simpler we will use the Network Browser to obtain a listing of the objects in the AutoAssignIPv4 scenario

In the project Editor:

Select View->Show Network Browser, your Project Editor window will change its

appearance with a listing of all the scenario‟s network objects on the left hand side:

The Network Browser view can also be filtered to list individual object types you have in the current scenario you are viewing in the Project Editor You can use the top drop down

box to list the nodes of a certain type in your network (i.e you can use this feature for collecting the IP addresses of the workstations, servers, and routers)

2) Collect the IP addresses for the workstations, servers and routers using the method as

stated in i) and ii) above but right click on the objects via the Network Browser and not the

workspace to make things simpler That way you just work your way down the listed

objects instead of trying to locate them individually within your network model

NB - Use the table below to write down the listed IP addresses

Subnet Mask (e.g IF0, LB0)

1

2

3

4