NODE MODELING

Exp.No Aim: To Configure and Analyze the Performance of Node Modeling Software Used OPNET Modeler Date:

Purpose:
Using the Packet Format Editor to create a new packet format. Using the Node Model Editor to create new node models. Using the Link Model Editor to create a new link model.

Overview:
This lab models the flow of bank transactions (represented as packets) from Washington, D.C. to Philadelphia. In order to measure the performance of this simple network in a meaningful manner, the user must define specific questions that their model is designed to answer. Design the lab to answer the following questions: Does the queue size of the WDC transmitter steadily increase? What is the throughput (in bits/second) at the WDC transmitter? What is the throughput (in bits/second) at the Philadelphia receiver? What is the utilization of the DC to Philadelphia link?

Description:
Bank transactions originate in Washington, D.C. (WDC) and are routed to Philadelphia via a telephone line and modem capable of transmitting 9,600 bits/second. The size of a transaction varies according to a normal distribution with a mean size of 3,200 bits and a variance of 400 bits. Transactions are modeled as exponential interarrivals, with a mean interarrival time of 0.5 sec/trans. The goal is to analyze performance of a system in steady state.

Page 1

 Create a transaction packet with 2 fields, source node, and destination node. Each field has a size of 64 bits. Step 1: Creating the packet format 1) Select File / New / Packet Format. 2) Left-click on the Create New Field button and left-click in the workspace to create a field. Create two fields in this manner. Right-click to release the mouse pointer. 3) Right-click on field_0 to access its attributes; set the name to Source Node, and the size to 64 bits. 4) Click OK. 5) Right-click on field_1 to access its attributes; set the name to Destination Node, and the size to 64 bits. 6) Click OK.

7) Save the packet: select File / Save As and name the packet <initials>_trans_pkt. 8) Close the packet format editor. Step 2: Creating the transmitter node model 1) Select File / New / Node Model.

2) Create a generator: press the Create processor button on the toolbar and left-click in the workspace. Right-click to release the mouse pointer.

3) Create a point-to-point transmitter: press the Create point-to-point transmitter button on the toolbar and left-click in the workspace. Right-click to release the mouse pointer.
Page 2

4) Create packet stream: press the Create packet stream button on the toolbar and leftclick each of the two modules. Right-click to release the mouse pointer.

5) Configure Node Interfaces. Select Interfaces / Node Interfaces. In the Node Type table, set: mobile= no satellite 6) Click OK. 7) Save the node model file: select File / Save As and name the model transmitter_nd. Step 3: Setting Attributes values for the generator module 1) Set attributes of generator: Right-click the processor module and enter these values: name = gen process model = simple_source Packet Interarrival Time Distribution Name = exponential Mean outcome = .5 Packet Size Distribution Name = normal Mean outcome = 3200 Variance = 400 packet format = <initials>_trans_pkt = no

Page 3

2) Click OK. Step 4: Setting attributes values for the transmitter module 1) Set attributes of transmitter: right-click the transmitter module and enter these values: name channel: data rate = trans = unspecified

2) Press Enter. Left-click under packet formats. Click check box: Supports All Packet Formats (this will un-support all formatted packet formats). Click check box: Supports Unformatted Packets (this will un-support all unformatted packet formats, so now no packet formats are supported). Scroll down to <initials>_trans_pkt and toggle status to supported (this will cause only your packet format to be supported).
Page 4

3) Click OK three times. 4) Save file: select File / Save. Step 5: Creating the receiver node model 1) Select File / New / Node Model.

2) Create a point-to-point receiver: press the Create point-to-point receiver button on the toolbar and left-click in the workspace. Right-click to release the mouse pointer. 3) Create a sink: press the Create processor button on the toolbar and left-click in the workspace. Right-click to release the mouse pointer. 4) Create packet stream: press the Create packet stream button on the toolbar and leftclick each of the two modules. Right-click to release the mouse pointer.

5) Configure Node Interfaces. Select Interfaces / Node Interfaces. In the Node Type table, set: 6) Click OK. 7) Save the node model file: select File / Save As and name the model receiver_nd. Step 6: Setting Attributes values for the receiver module 1) Set attributes of receiver: right-click the receiver module and select edit attributes. mobile = no satellite = no

Page 5

Enter these values: Name channel: data rate packet format 2) Click OK. = rec = unspecified = <initials>_trans_pkt

3) Click OK again. Step 7: Setting Attributes values for the sink processor module 1) Set attributes of the sink: right-click the processor module and enter this value: name = sink 2) Click OK.

3) Save file: select File / Save. Step 8: Selecting Node Statistics 1) In the transmitter_nd node editor window select Interfaces / Node Statistics.

Page 6

2) Left-click in the first field of the Orig. Name column. 3) Select the statistic: point-to-point transmitter:trans.channel [0].queue size (bits) 4) Click Promote. 5) Click OK.

6) Select File / Save. 7) Close the transmitter_nd Node Editor window. 8) In the receiver_nd node editor window select Interfaces / Node Statistics. 9) Left-click in the first field of the Orig. Name column. 10) Select the statistic: point-to-point receiver:rec.channel [0]. throughput (bits/sec) 11) Click Promote

Page 7

13) Click OK. 14) Select: File / Save. 12) Close the receiver_nd Node Editor window. Step 9: Creating a new link model 1) Select File / New / Link Model. 2) Change yes to no for the bus and bus tap link types. 3) Click on the attribute data rate, and type in 9600 4) Set the following models: a.ecc model b.error model c.propdel model d.txdel model = dpt_ecc = dpt_error = dpt_propdel = dpt_txdel

5) Save the new link model; press File / Save, and name the file pt_base_9600.

Page 8

6) Click OK. 7) Select File / Close, and close the link model editor. Step 10: Creating a new project 1) Create a new project: select File / New / Project from the pull-down menu. 2) Name the new project bank_net. Name the initial scenario Baseline. 3) When the Startup Wizard appears, select Quit. 4) Set background map: select View / Background / Set Border Map / USA. 5) Zoom in on Wash/Phil. Region: press Zoom button and draw box around region. 6) Create a custom object palette: Press the Object Palette button; press the Configure Palette button in the object palette; press Clear button. 7) Select Node Models and include the receiver_nd and transmitter_nd; Click OK. 8) Select Link Models and include pt_base_9600; Click OK.

Page 9

9) Select Save in the Configure Palette window. When prompted, name the palette bank_net_palette. Click OK (Save window). Click OK again (Configure Palette window). 10) Place nodes and link: a.Place a transmitter_nd near Washington D.C. b.Place a receiver_nd near Philadelphia. c.Name the two WDC_src and Philly_dest respectively. d.Draw a simplex link (pt_base_9600) from Washington to Philadelphia.

Page 10

11) Close the object palette. 12) Verify links: press Verify Links button. Click OK. 13) Save the project: press File / Save As. 14) Name the project bank_net. Click OK. Step 11: Choosing Statistics to be collected 1) In the Project Editor select Simulation / Choose Individual Statistics. 2) Select the following: a.Node Statistics i.point-to-point receiver / throughput (bits/sec) ii.Point-to-point transmitter / queue size (bits) b.Link Statistics i.point-to-point / utilization 3) Click OK.

Page 11

4) Select Simulation / Choose Statistics (Advanced). Using Choose Statistics (Advanced) automatically sets the network model to bank_net in the Probe Editor.

5) Add a Node Statistic Probe. Select Create Node Statistic Probe.

Page 12

6) Right-click on the probe that is created and select Edit Attributes. 7) Set the name attribute to DC_thruput. Click OK. 8) Right-click on the probe and select Choose Probed Object. 9) Notice that a subwindow appears. Click on the plus next to WDC_src. This expands the options. Click on trans. Click OK. 10) Right-click on the probe and select Edit Attributes. 11) Set the submodule attribute to channel[0]. 12) Click OK. 13) Right-click the probe and select Choose Statistic. 14) Select the statistic: a.point-to-point transmitter.throughput (bits/sec) 15) Click OK. 16) Select File / Save. Close the Probe Editor. Step 12: Configuring the Simulation 1) From the menu select Simulation / Configure Simulation. 2) Configure the simulation as follows: a.Duration = 2000 seconds 3) Click Run. 4) When the simulation completes click Close in the simulation sequence window. 5) Select Results / View Results and select the average filter for the following graphs: a.Object Statistics/Philly_dest/point-to-point receiver/throughput (bits/sec) b.Object Statistics/WDC_src/point-to-point transmitter/queue size c.Object Statistics/WDC_src/trans/channel [0]/point-to-point transmitter/throughput (bits/sec) d.Object Statistics/WDC_src->Philly_dest [0]/point-to-point /utilization

Page 13

To figure answers, we need to look at the load offered to the 9600 baud modem at the WDC node. Load = (1 pk/ 0.5 sec)(3200 bits/pk + (64 bits/field)(2 fields)) = 6656 bits/sec. 1. Does the queue size of the WDC transmitter steadily increase? a.NO. Clearly, 6656 bits/sec is less than 9600 bits/sec.] In a later lab, we'll learn how to filter the raw data and take a time average of this data to see if it is really increasing or not. 2. What is the throughput (in bits/second) at the WDC transmitter? a.6656 bits/second Since the load is less than data rate of transmitter, throughput = load 3. What is the throughput (in bits/second) at the Philadelphia receiver? a.6656 bits/second Whatever is transmitted, is received. For point to point links, throughput at a transmitter should always equal throughput at the respective receiver. 4. What is the utilization of the D.C. to Philadelphia link? a.69% [Calculated by figuring load over capacity, (6656 bits/sec) / (9600 bits/sec).

Page 14