Executing a Simulation with HLA
Depending on which RTI you have, use one of the following procedures to execute an Riverbed Modeler HLA simulation.
Procedure 2: Executing an HLA Simulation—MÄK RTI
-
Set the following environment variables:
Variable Value Example RTI_RID_FILE <workdir>\rid.mtlWindows: C:\my_sim_dir\rid.mtl
Linux:/usr/my_sim_dir/rid.mtlRTI_HOME <base location of RTI software>Windows: C:\MAK
Linux:/usr/localRTI_BUILD_TYPE <path version of RTI>makRti3.1.2 -
Edit your preferences file to include additional build information:
Windows
comp_flags_common : " /I<RTI_HOME>\<RTI_BUILD_TYPE>\include /DDT_USE_DLL /DRTI_USES_STD_FSTREAM"Linux
comp_flags_common : " -I<RTI_HOME>/<RTI_BUILD_TYPE>/include -DDT_USE_DLL -DRTI_USES_STD_FSTREAM"where
<RTI_HOME>and<RTI_BUILD_TYPE>are replaced by the appropriate paths (as set in step 1). -
Configure the simulation either through the Modeler user interface (choose DES > Configure/Run Discrete Event Simulation) or by preparing an environment file. See “Project Editor” on page 89 in the Editors Reference manual or “Preferences” on page 30 in the External Interfaces manual for details.
-
Start the Modeler simulation program by choosing Run Simulation from the Simulation menu or via the command line, referencing the environment file.
When the Modeler simulation begins, models are loaded into memory and the HLA-PM performs its initialization.
Procedure 3: Executing an HLA Simulation—Pitch pRTI
-
Remove any Pitch-related references from the PATH and CLASSPATH environment variables.
-
Add the following values to the beginning of these environment variables:
Variable Value to Add PATH Windows: C:\Program Files\prti1516\lib;C:\Program Files\prti1516\lib\vc71CLASSPATH Windows: C:\Program Files\prti1516\lib\prti1516.jar;C:\Program Files\prti1516\lib\hirestimer.jar;c:\Riverbed\18.6\sys\utilities\hla\ophla_time_pitch.jar
Linux:/opt/prti1516/lib/prti1516.jar:/opt/prti1516/lib/hirestimer.jar:/usr/riverbed/18.6/sys/utilities/hla/ophla_time_pitch.jar -
Edit your preferences file to include additional build information:
Windows
comp_flags_common : " /IC:\\Progra~1\\prti1516\\include /DDT_USE_DLL /DRTI_USES_STD_FSTREAM"bind_shobj_flags : "/libpath:C:\\Progra~1\\prti1516\\lib\\vc71"bind_shobj_libs : prti1516.libLinux
comp_flags_common : " -I/opt/prti1516/include -DDT_USE_DLL -DRTI_USES_STD_FSTREAM"bind_shobj_flags : "/libpath:/opt/prti1516/lib/gcc34"bind_shobj_libs : librti1516.so -
Configure the simulation either through the Modeler user interface (choose DES > Configure/Run Discrete Event Simulation) or by preparing an environment file. See “Project Editor” on page 89 in the Editors Reference manual or “Preferences” on page 30 in the External Interfaces manual for details.
-
Start the Modeler simulation program by choosing Run Simulation from the Simulation menu or via the command line, referencing the environment file.
When the Modeler simulation begins, models are loaded into memory and the HLA-PM performs its initialization.
Procedure 4: Executing an HLA Simulation—DMSO RTI
-
Delete or hide the following files:
- Windows:
ACE.dlland everyTAO*.dllin<reldir>\sys\pc_intel_win32\bin - Linux:
libACE.soandlibTAO.soin<reldir>/sys/pc_intel_linux/lib
(HLA and Riverbed use different versions of these files. The Riverbed versions you are removing are needed only for VNE import.)
- Windows:
-
Configure the simulation either through the Modeler user interface (choose DES > Configure/Run Discrete Event Simulation) or by preparing an environment file. See “Project Editor” on page 89 in the Editors Reference manual or “Preferences” on page 30 in the External Interfaces manual for details.
-
Start the Modeler simulation program by choosing Run Simulation from the Simulation menu or via the command line, referencing the environment file.
When the Modeler simulation begins, models are loaded into memory and the HLA-PM performs its initialization.
Note: As a result of the oms_sar package and recent enhancements in the TCP model, it is possible to make Riverbed’s TCP model send and receive real application traffic. Refer to “Sending and Receiving Real Payload at the TCP Layer” on page 13 for more information.