Model Construction Rules

The previous three topics present information on the objects, attributes, constants, and data type operators that can be defined via EMA to construct Riverbed models. However, these topics have not presented the whole story, in that not every combination of the objects that can be defined through EMA necessarily defines an Riverbed model that makes sense. This section presents some guidelines for building models with EMA, as well as tips about potential errors, organized by model type.

Network Model

  • A subnet object named “top” must be defined. This object represents the environment that initially appears in the Project Editor.
  • Subnets, nodes, and links must have their subnet attribute set, either to point to the top subnet object, or another created subnet object.
  • Nodes that reference node models not present in the model directories will be ignored when read by the Project Editor, op_mksim, and the network simulation.
  • Links and taps that reference transceiver modules that do not exist in the relevant node models will be ignored when read by the Project Editor, op_mksim, and the network simulation.
  • Links and taps will be projected to the nearest icon edges of the nodes they reference when displayed by the Project Editor.
  • Subnet, node, and link position coordinates should be specified in terms of the “subnet grid unit”, which is defined by the surrounding subnet’s grid unit attribute.

Node Model

  • Compound value objects such as subqueues and channels must have at least one defined compound object (sub-object) that is assigned to their respective list attribute.
  • Arbitrary coordinates may be assigned to modules via EMA, whereas modules created in the Node Editor are “snapped” to an invisible grid. Therefore, modules created by the Node Editor may not be able to align with modules previously created with EMA.
  • It is possible to specify graphical positions and orientations for streams and statistics wires that do not correspond to their logical function in the node model. For instance, a connection from processor “A” to processor “B” can be specified so that it appears to run from processor “A” to processor “C”. This can lead to confusion and should be avoided.
  • Values assigned to module attributes in EMA should be based on the units that appear in the attribute tables in Models, Objects, and Attributes (these are typically the same as those that appear in editor menus). For instance, the delay attribute of the duplex point-to-point link object has the units of seconds.

Process Model

  • Exactly one of the state objects must have the toggle attribute named “initial” enabled.
  • Arbitrary coordinates may be assigned to states via EMA, whereas states created in the Process Editor are “snapped” to an invisible grid. Thus states created by the Process Editor may not be able to align with states previously created with EMA.
  • It is possible to specify graphical positions and orientations for transitions that do no correspond to their logical function in the node model. For instance, a transition from an idle state to an active state can be specified so that it appears to be a transition from the idle state to itself. This can lead to confusion and should be avoided.

External System Definition

  • The simulator attribute for the external system object is required and is not promotable.
  • The direction indicates flow of data relative to the external simulator (that is, an Out interface receives data from the external simulator while an In interface sends data to the external simulator). The type attribute specifies the type of data that can be placed onto the interface.
  • The dimension attribute of interface objects refers to vector interfaces. The default value of zero means that the interface is not a vector interface. See Chapter 8 “External System Domain” on page 331 for more information about vector interfaces.

本站文档由 北京智网畅联科技有限公司 整理、翻译并提供 · Documentation compiled and provided by Beijing ZNetLink Technology Co., Ltd.

交流群 · QQ Group:OPNET/智网妙算网络仿真交流群(群号 486383494)

原文档 © 2017 Riverbed Technology · 本站为公益翻译,由 AI 辅助完成,请仔细甄别

Original documentation © 2017 Riverbed Technology. Community translation, AI-assisted. Contact: jiazequn@znetlink.com