Model Architecture
The following figures show the underlying architecture of the RPG workstation node models:
Figure 445: ethernet_rpg_station Node Model

Figure 446: ppp_rpg_workstation Node Model

Figure 447: ethernet_rpg_wkstn Node Model

Each RPG node has an “rpg” module. The rpg module contains a dispatcher process that spawns a child process, called a manager process, for each arrival process used by the self-similar traffic source node. The following table lists the process models used by the RPG module.
Table 188: RPG Process Models
| Process | Description |
|---|---|
rpg_dispatcher |
This process dispatches an RPG manager process for each row (arrival process) specified in the RPG Traffic Generation Parameters table. |
rpg_mgr |
This process spawns traffic source child processes. Each child process represents an independent traffic source. The type of child process generated (flow, ON-OFF, etc.) depends on which arrival process is used, while the number of child processes generated depends on the input parameters of that arrival process. |
rpg_flow |
This process is used by flow-based arrival processes to generate the packets within a flow. |
rpg_onoff_source |
This traffic source child process is used for all ON-OFF arrival processes. |
rpg_source |
This traffic source child process is used to generate packets in the Sup-FRP processes and to generate flows in the F-FSNDP processes. |