1532 LabManual OPNK2004

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !
PI
Co-Simulation Demo
Overview
Collectively, we will simulate a project containing several scenarios. Each computer station will run a different scenario in that project. The scenarios represent different sections of a large, international network. Using co-simulation, nodes in a particular scenario may communicate with nodes in other scenarios. The key to this is that the simulations communicate with a central software component running on the instructors machine. Using the co-simulation package and native sockets, each simulation sends packets to the central command. The central command then routes these packets to the appropriate destination simulator. ll of this is done in a synchroni!ed manner.
Objective
"ntroduce the co-simulation capa#ilities of $%&ET
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART. Copyrigh !""# OPNET T$%h&o'ogi$(, I&%.
P)g$ * o+ !*
1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI
Instructions
Gather information '. Each computer will have #een given a num#er. %lease write that num#er here( )))))* +. The instructor will announce the name of the server. %lease write that name here( )))))))))))))))))))))**
Run the co-simulation '. $pen an $%&ET console a. ,indows -tart menu . %rograms . $%&ET /odeler ''.0 . $%&ET Console ''.0 +. Change to the c:\op_models directory. cd op_models 1. 2un the following at the prompt( 1532-[*enter your number here].dev32.i0.sim server [**server machine] ef 1532-[*enter your number here] 3. $nce everyone has joined the co-simulation, the co-simulation will #egin. %lease #e patient as we wait for others to join. 4. a. a.
P)g$ ! o+ !*
Lab 1: Introduction to Co-Simulation Elements

Overview
5ou are going to adapt the co-simulation model that was presented in a demo earlier. "nstead of having the simulation communicate with other simulations, you will have it communicate with you, the user. 5ou will control the rate at which the simulation advances, and also dynamically o#tain from it the num#er of packets sent out onto the esys interface. 6or this first la#, rather than sending the packets out, you will write the running total of packets scheduled to #e sent.
Objective
-ynthesi!e the various elements of the co-simulation package.
Note
6or the ne7t two la#s, you may use the reference models as an alternative to running the la#s. To do so, change the primary model directory to c:/op_models/1532_ref. The primary model directory is the topmost directory in your mod_dirs environment preference, to which you may navigate in /odeler after choosing Edit . Preferences. "n addition, where the la#s mention the c:\op_models directory, use instead c:\op_models\1532_ref.
P)g$ , o+ !*
Instructions
Create the simulator description (.sd) file '. +. $pen the simulator descriptor file 1532_simdesc. This is the simulator descriptor used in the earlier demo. a. Using ,indows e7plorer 8right-click on -tart menu and choose E7plore9, navigate to c:\op_models. #. :ou#le-click on 1532_simdesc.sd. c. ,hen prompted, choose to open this file in &otepad. 1. /odify the file so that we link in the e7ternal o#ject lab1_1532.obj instead of the sim)manager and comm)support o#jects. a. delete the two lines that follow use_esa_main: no #. "n their place, add the line(
bind_obj: lab1_1532.obj
3. -ave the file as lab1_1532.sd. a. File . Save As #. Change Save as type to All Files. c. Type lab1_1532.sd and click Save.
Create the ESD model The E-: model will define the esys interface youll use in the modified network. 2ecall that what we want to write on this interface is the num#er of packets sent out. '. -tart /odeler, or if already started, refresh the model directories. d. File . Model Files . efres! Model "irectories +. Create a new E7ternal -ystem :efinition model. a. File . #e$ . E%ternal System "efinition #. Click &'.
P)g$ # o+ !*
1. 1. ;ave this E-: model use the simulator description file you just created. a. Click on #&#E ne7t to Sim(lator "escription. #. "n pull-down menu, choose lab1_1532. 3. Create a single interface named o(t from $%&ET to the e7ternal code, of type integer. This integer represents the num#er of packets sent out. a. Click the first row in )nterfaces ta#le #. Change the name to o(t. c. Click 2eturn to make sure this change registers. d. <erify that *ype is set to integer e. <erify that "irection is set to &P#E* to +osim 4. -ave the E-: model as lab1,1532. a. File . Save #. Type lab1,1532 and Click Save. =. Completed E-: model should look like this(
P)g$ - o+ !*
>.
Close the editor.
P)g$ . o+ !*
Set up the project to use the ESD model '. $pen project 1532. a. File . &pen #. -et Files of *ype to Project. c. "n the op_models directory, dou#le-click on 1532. +. :uplicate the scenario that the project opens to, and name it lab1. a. Scenarios . "(plicate Scenario #. Enter lab1 and press Enter. 1. :ou#le-click on the router node, -_ro(ter. This #rings up the routers node model. 3. -ave the node model as 1532_ro(ter_lab1. a. File . Save As #. Enter 1532_ro(ter_lab1 and press Enter. 4. Change the esd model attri#ute of the esys module to lab1,1532 . a. 2ight-click on the esys module 8named esys9 and select Edit Attrib(tes. #. 6ind the attri#ute esd model. &ote that it is currently set to esd_1532. c. Click on esd_1532, and in the pull-down menu, select lab1,1532. d. Click the Edit ES" Model #utton in the lower-left of the dialog #o7. e. <erify that the E-: model you created earlier appears. Close the E-: model. f. Click &' to close the Edit Attrib(tes dialog #o7. =. :ou#le-click on the esys module. This #rings up the process model associated with the esys. >. -ave the model as esys_1532_lab1. a. File . Save As #. Enter esys_1532_lab1 and press Enter. ?. Create a new glo#al varia#le p._co(nt, initiali!ed to 0. a. $pen the /eader 0loc. #y clicking on the /0 #utton. #. t the end of the file, type(
int p _count ! 0"
P)g$ / o+ !*
@. -ave the /eader 0loc. a. %ress Ctrl-- or File . Save. '0. /odify the function process_strm12 so that whats written to the esys interface, is the packet count 8rather than the packet9. a. $pen the F(nction 0loc. #y clicking on the F0 #utton. #. :elete lines '0-'1. c. "n the call to op_esys_interface_val(e_set12, i. Change the second argument from op_sim_time12 to &P+_ES3S_#&*)F3_#E4E . This means that, although the value is updated immediately, the manager side is not notified that the value has changed, and thus no call#ack is issued. The manager will read the updated value when it is told to. ii. Change the third argument from p._vvec to 55p._co(nt. d. The final result should look like this(
e. -ave the F(nction 0loc. ''. Compile the process model and close it. a. +ompile . +ompile +ode, or click the Compile Code action #utton. #. Click the +lose #utton. c. File . +lose '+. -et the process model associated with the esys module to esys_1532_ lab1. a. "f not already up, #ring up the node model 1532_ro(ter_lab1. #. 2ight-click on the esys module and select Edit Attrib(tes.
P)g$ 0 o+ !*
c. &ote that the process model attri#ute is set to esys_1532. d. Click on esys_1532 and in the pull-down menu, select esys_1532_lab1. e. Click &'. '1. -ave and close the node model. a. File . Save #. File . +lose '3. -et the node model associated with the router to 1532_ro(ter_lab1. a. Aring up the 1532 project. <erify that you are in the lab1 scenario. #. 2ight-click on the router node 8-_ro(ter9 and select Edit Attrib(tes. c. &ote that the model attri#ute is set to 1532_ro(ter. d. Click on 1532_ro(ter. "n the pull-down menu, click Edit6 e. "n the new pull-down menu, select 1532_ro(ter_lab1. f. Click &'. '4. -ave and close the project. a. File . Save #. File . +lose 5ou have completed all the elements on the $%&ET side. "t is now time to create the e7ternal code elements.
P)g$ 1 o+ !*
Examine and modify external code that implements the user interface '. $pen and e7amine the file lab1_1532.c. Using ,indows E7plorer, in c:\op_models, dou#le-click on lab1_1532.c. This should open up the file in /icrosoft <isual CBB.
&ote that there are two functions, main#$ and user_prompt#$. user_prompt#$ o#tains the instructions from the user and main#$ uses this information to advance the simulation. "n particular, you may wish to e7amine the call to %sa_%&ecute_'ntil#$. +. Uncomment E- initiali!ation code Cook for the comment /( ')*+,,%)- initiali.ation code (/. 2emove the comments around the ne7t lines. These lines of code perform the initiali!ation of the simulator.
/(%sa_,ain #ar/c0 ar/v0 0$" %sa_1nit #ar/c0 ar/v0 %23*_+4-2_)+)%0 5esa_6andle$" %sa_7oad #esa_6andle0 %23*_+4-2_)+)%$"(/
1. Uncomment code that will o#tain a handle to the esys interface you defined earlier. Cook for the comment /( ')*+,,%)- obtain interface (/. 2emove the comments around the ne7t line. This line of code will o#tain all esys interfaces across all esys modules in the simulator.
/(%sa_1nterface_8roup_8et #esa_6andle0 5interfaces0 5num_interfaces$"(/
3. Uncomment code that will read the packet count off the interface. Cook for the comment /( ')*+,,%)- read pac et count (/.
P)g$ *" o+ !*
2emove the comments around the ne7t line. This line of code will o#tain the packet count 8i.e., 55pac.et_co(nt9 that was earlier written to the esys interfaces .
/(%sa_1nterface_9alue_8et #esa_6andle0 5status0 iface0 5num_p s$"(/
P)g$ ** o+ !*
4. 4. -ave the file. File . Save
Compile the simulation and run it '. $pen up an $%&ET Console from the ,indows -tart /enu. +. Change directory to c:\op_models. 1. Compile the e7ternal code.
*7 /c lab1_1532.c /1*:\pro/ra:1\opnet\11.0.3\s;s\include /<_=>?_
3. 6orce compile the static simulation.

op_m sim net_name 1532-lab1 -c
4. 2un the simulation.

1532-lab1.dev32.i0.sim
=.
t the command prompt, type 6elp to see the list of commands availa#le.
Lab Questions
'. "s the co-simulation structured as an $%&ET simulation in a larger program, or as an e7ternal li#rary linked into an $%&ET simulationD +. ,hat is the final packet countD 1. ;ow many packets are sent out on the interface #y time 0.'D 3. ,hy do you think that many are sent out #y that timeD 8&ote( this will reEuire study of the network model.9 4. 95ou may have noticed that after the initial spike, the packet count increments #y ' each time a message appears 8e.g., F1.2>: 4ac et sent to @.1 A 10@.11133?G9. ;owever,
P)g$ *! o+ !*
#etween time '00 and +00, there are two such messages #ut the packet count is only incremented once. ,hy might this #e soD
Extra Credit
5ou may have noticed that there is a feature in the help menu for resetting the packet count to !ero. "mplement this option. ;ints( 5ou will have to alter the esys interface and modify the process_es;s#$ function to support this feature. "n the e7ternal code, you will have to use the function %sa_1nterface_9alue_2et#$ with immediate notification.
P)g$ *, o+ !*
Inter ace Callbac!s and "ac!et Conversion

Overview
5ou are going to adapt the co-simulation model so that it sends out a reEuest packet on the esys interface and receives a FresponseG #ack. The reEuest is intended for a node outside the network. The e7ternal code will read this packet 8in vvec form9 off the interface, convert it to native values, swap the -rc and :est fields, then send it #ack to the simulation. To the simulation, it will appear that a response packet has arrived, even though this is not the case.
Objective
Hain familiarity with advanced co-simulation data e7change mechanics. These are the types of operations upon which interfacing multiple simulators relies.
P)g$ *# o+ !*
Instructions
Create the packet format. '. a. +. "n /odeler, open the lab2_1532_p. %acket 6ormat model. a. File . &pen #. -et Files of *ype to Pac.et Format. c. "n the op_models directory, dou#le-click on lab2_1532_p.. 1. %lace three fields in the workspace. a. Click on the +reate #e$ Field #utton 8top left9. #. Click three times in the workspace to generate three packet fields. 3. &ame the first field Src, a 1+-#it integer with conversion method defa(lt_convert. a. 2ight click on the first field and select Edit Attrib(tes. #. Change name to Src. c. d. e. f. Change conversion met!od attri#ute to defa(lt_convert. g. Click &'. 4. &ame the second field "est, a 1+-#it integer with conversion method defa(lt_convert. a. 2ight-click on the second field and select Edit Attrib(tes. #. Change name to "est. h. Change conversion met!od attri#ute to defa(lt_convert.
P)g$ *- o+ !*
c. Click &' . =. g&ame the third field +reation, a =3-#it floating point with conversion method defa(lt_convert. a. 2ight click on the third field and select Edit Attrib(tes. #. Change name to +reation. c. Change type to floatin7 point. d. e. Change si!e to 89. f. Change conversion met!od attri#ute to defa(lt_convert. g. Click &'. >. <erify the packets #inary conversion method is defa(lt_convert. a. )nterfaces . 0inary +onversion #. &ote that +onversion met!od is set to defa(lt_convert. c. Click &'. ?. -ave and close the model. a. File . Save #. File . +lose
P)g$ *. o+ !*
odify the esys process model '. $pen the scenario 1532,lab2. a. File . &pen #. -et Files of *ype to Project. c. "n the op_models directory, dou#le-click on 1532. d. Scenarios . S$itc! *o Scenario . lab2. +. :ou#le-click on the -_ro(ter node to enter the &ode Editor. 1. :ou#le-click on the esys module. 3. ;ave this process model support the packet format you just modified. a. File . "eclare Pac.et Formats #. Cocate and click lab2_1532_p.. c. Click &'. 4. E7amine and uncomment the code that converts the packet to a vvec and writes the vvec to the esys interface a. $pen the 6unction Alock #y hitting the F0 #utton. #. E7amine lines '+-'3, which convert the packet to a vvec packet, o#tains the vvec from the vvec packet, then sets this vvec on the esys interface, for use #y the manager code. c. 2emove the comments that #racket these lines. =. E7amine and uncomment the code that retrieves a vvec from the esys interface and converts it to a packet of the format you created earlier. a. E7amine lines +@-1=, which o#tains a vvec from the esys interface 8placed there #y manager code9, converts it #ack to an $%&ET packet, and then sets the creation time on the packet #ased upon the FCreationG field in the packet. #. 2emove the comments that #racket these lines. >. -ave the 6unction Alock. a. %ress +trl,S or File : Save. ?. Compile then close the process model. a. +ompile : +ompile +ode or click the +ompile +ode #utton. #. Click the +lose #utton. c. File : +lose @. Ho to the 1532_ro(ter_lab2 node model. '0. E7amine the E-: model on which the esys interfaces are defined.
P)g$ */ o+ !*
a. 2ight-click on the esys module and select Edit Attrib(tes. #. Click the Edit ES" Model #utton. &otice that there is a 0idirectional esys interface of type bit and dimension 12;. &ote that you just modified the process model so that it creates a '+?-#it vvec out of a '+?-#it packet. The cosimulation side will receive it as an array of '+? #its 8represented as chars9. ''. t this point, you may e7it /odeler without saving. Examine and modify external code '. $pen the file lab2_1532.c a. Using ,indows E7plorer, in c:\op_models, dou#le-click on lab2_1532.c. This should open up the file in /icrosoft <isual CBB. &ote that there are two functions, main#$ and p _received_6andler#$. main#$ registers p _received_6andler#$ as the call#ack function that is called whenever something is written to the esys interface. main#$ then kicks off the simulation. +. 6ill in main#$, #y looking for comments that #egin with /( ')*+,,%)- and removing the relevant comments. a. Uncomment E- interface call#ack registration code. i. Cook for the comment /( ')*+,,%)- callbac ii. 2emove the comments around the call#ack registration(
/(%sa_1nterface_*allbac _Be/ister #esa_6andle0 5status0 iface0 00 p _received_6andler0 0$"(/
re/istration (/
#. Uncomment code tells the sim to e7ecute a single event. i. Cook for the comment /( ')*+,,%)- command to e&ecute a sin/le event (/. ii. 2emove the comment around the event stepping routine(
/(%sa_%&ecute_'ntil #esa_6andle0 5status0 time0 %23*_')-17_+)%_%9%)-0 5finis6_time0 5num_events$"(/
P)g$ *0 o+ !*
c. Uncomment code that terminates the simulation. i. Cook for the comment /( ')*+,,%)- code to terminate t6e simulation (/. ii. Enter the following #elow the comment(
/(%sa_-erminate #esa_6andle0 %23*_-%B,1)3-%_)+B,37$"(/
1. 6ill in pk)received)handler89, #y looking for comments that #egin with .* U&C$//E&T and removing the relevant comments. a. ,rite the #it array to the E-: interface. i. ii. Cook for the comment /( ')*+,,%)- code to inject t6e arra; into t6e simulation after a dela; (/. Uncomment the code that writes data to the interface(
/(%sa_1nterface_3rra;_2et #esa_6andle0 5status0 iface0 time C dela;0 bits0 0$"(/
P)g$ *1 o+ !*
3. 3. -ave and close the file. a. File . Save #. File . +lose Compile the simulation and run it '. $pen up an $%&ET Console from the ,indows -tart /enu. +. Change directory to op_models . 1. Compile the e7ternal code.
*7 /c lab2_1532.c /1*:\pro/ra:1\opnet\11.0.3\s;s\include /<_=>?_
3. 6orce compile the simulation.

op_m sim net_name 1532-lab2 -c
4. 2un the simulation.

1532-lab2.dev32.i0.sim ef 1532-lab2
Lab Questions
'. +. 1. "n the main#$ function, instead of the while loop, could you write a single call to %sa_%&ecute_'ntil#$ that would have the same effectD fter the process model creates the packet and sends it out on the esys interface, what happens to the packetD "f you had changed the encoding attri#ute of the packet fields, would the simulation still workD Either way, what would have changedD
Extra Credit
P)g$ !" o+ !*
Aecome more familiar with the vvec to value routines. fter converting the packet to a vvec, try converting the vvec to native values using op)vvec)to)value89. 5ou should pay attention to the slide on matching the the vvec conversion arguments with the packets encoding, type and si!e.
P)g$ !* o+ !*

1532 LabManual OPNK2004

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

1532 LabManual OPNK2004

Загружено:

Авторское право:

Доступные форматы

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI

Lab 1: Introduction to Co-Simulation Elements

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI

Close the editor.

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI

/(%sa_1nterface_9alue_8et #esa_6andle0 5status0 iface0 5num_p s$"(/

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI

4. 4. -ave the file. File . Save

3. 6orce compile the static simulation.

4. 2un the simulation.

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI

Inter ace Callbac!s and "ac!et Conversion

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI

3. 6orce compile the simulation.

4. 2un the simulation.

1532 Interfacing Multiple Simulators Using the OPNET Co Simulation !PI

Вам также может понравиться