Table Of Contents
Table Of Contents

Scenario Scripting


The INET Framework contains scripting support to help the user express scenarios that cannot be adequately described using static configuration. You can schedule actions to be carried out at specified simulation times, for example changing a parameter value, changing the bit error rate of a connection, removing or adding connections, removing or adding routes in a routing table, shutting down or crashing routers, etc. The aim is usually to observe transient behaviour caused by the changes.

INET supports the following built-in actions:

  • Create or delete module

  • Create or delete connection

  • Set module or channel parameter

  • Initiate lifecycle operation (startup, shutdown, crash) on a network node or part of it


The ScenarioManager module type is for setting up and controlling simulation experiments. In typical usage, it has only one instance in the network:

network Test {
        scenarioManager: ScenarioManager;

ScenarioManager executes a script specified in XML. It has a few built-in commands, while other commands are dispatched (in C++) to be carried out by other simple modules.

An example script:

    <set-param t="10" module="host[1].mobility" par="speed" value="5"/>
    <set-param t="20" module="host[1].mobility" par="speed" value="30"/>
    <at t="50">
        <set-param module="host[2].mobility" par="speed" value="10"/>
        <set-param module="host[3].mobility" par="speed" value="10"/>
        <connect src-module="host[2]" src-gate="ppp[0]"
                 dest-module="host[1]" dest-gate="ppp[0]"
            <param name="datarate" value="10Mbps" />
            <param name="delay" value="0.1us" />
    <at t="60">
        <disconnect src-module="host[2]" src-gate="ppp[0]" />

The above script probably does not need much explanation.

The built-in commands of ScenarioManager are: <connect>, <disconnect>, <create-module>, <delete-module>, <initiate>, <shutdown>, <startup>, <crash>, <set-param>, <set-channel-attr>, <at>.

All commands have a t attribute which carries the simulation time at which the command has to be carried out. You can group several commands to be carried out at the same simulation time using <at>, and then only the <at> command needs to have a t attribute.

More information can be found in the ScenarioManager documentation.

The script is usually placed in a separate file, and specified like this:

*.scenarioManager.script = xmldoc("scenario.xml")

Short scripts can also be written inline:

*.scenarioManager.script = xml("<x><shutdown t='2s' module='Router2'/></x>")