Node Editor

5Node Editor
Node Editor
In a local area network (LAN), each computer plus its network interface is a node within the network. In a satellite network supporting television broadcasting, each satellite is a node; other nodes in the network include the TV stations that originate the broadcast signals, earth stations with satellite dishes that perform satellite uplink and downlink, and microwave and cable-based relay stations that provide for local boosting and re-transmission of the signals. In a private corporate telephone network, each building or facility with its own PBX might be considered a node. In general terms, a node is a facility or resource in which data either originates and is transmitted, or is received and processed, or both. From this definition, it follows that a node has at least some of the following internal capabilities in relation to messages and data that messages contain: creation transmission reception storage internal routing internal processing, modification, and/or enhancement (such as content analysis, queuing, multiplexing, and error detection and correction) Typically, a node has both hardware and software components that support these capabilities. The Node Editor provides the resources necessary to model the internal functioning of nodes. Within the Node Editor, you can access different modules. Each kind of module serves to model some internal aspect of node behavior, such as data creation, data storage, data processing or routing, data transmission, etc. A single node model is usually comprised of multiple modulessometimes dozens or even hundreds of modules. Connecting the modules are packet streams and statistic wires. Packet streams carry packets of data between modules in a node. Statistic wires provide the ability for one module to monitor a varying quantity within another module. The combined use of modules, packet streams, and statistic wires provides the ability to create highly realistic simulations of node behavior. Additionally, you can specify that specific receivers and transmitters be treated as a tightly-associated pair of modules.
Modeler/Release 14.0 www.cadfamily.com EMail:cadserv21@hotmail.com The document is for study only,if tort to your rights,please inform us,we will delete
ER-5-1
5Node Editor
The following figure shows an example of a typical node model. In addition to the model itself, the figure shows the dialog boxes used to edit attributes of objects, such as modules and statistic wires.
Figure 5-1 Node Model and Related Dialog Boxes
For more information about node modeling techniques, see Node Domain on page MC-6-1.
ER-5-2 www.cadfamily.com EMail:cadserv21@hotmail.com The document is for study only,if tort to your rights,please inform us,we will delete
Modeler/Release 14.0
5Node Editor
Menus
The Node Editor provides operations for creating and working with network models. Access these operations from the Node Editor menu bar, which contains the menus listed in the following table.
Table 5-1 Node Editor Menus
Menu File Description Contains operations that relate to high-level functions such as opening and closing projects, saving scenarios, importing models, and printing graphics and reports Contains operations that allow you to edit the preferences that control program operation and to manipulate text and objects Contains operations that allow you to edit a node models interfaces to other nodes and to the project as a whole Contains operations for creating modules in a node Reference File Menu on page ER-2-2
Edit
Edit Menu on page ER-2-5.
Interfaces
Interfaces Menu on page ER-5-4
Objects
Objects Menu on page ER-5-5 Windows Menu on page ER-2-7 Help Menu on page ER-2-8
Windows
Lists all open editor windows and allows you to make one active Provides access to context-sensitive help, the product documentation and tutorials, and information about the program
Help
End of Table 5-1
NoteThe editor menus on your machine might vary from those described here, particularly if there has been any UI customization or use of ETS.
ER-5-3
5Node Editor
In addition to the menu bar menus, pop-up menus are available within the Node Editor, as listed in the following table.
Table 5-2 Node Editor Pop-Up Windows
Menu Workspace Description Contains zoom operations There is also one additional operation: No Zoom returns the display to the initial display: the zoom level that existed when you first opened the model. The Node Editor does not save zoom levels, so the initial display does not change from one session to the next. The Project Editor, by contrast, does save zoom levels, so it lacks the No Zoom operation. Object Contains operations related to setting object attributes and showing module connectivity Reference Pop-Up Menus on page ER-3-25
Edit Attributes on page ER-3-252 Show Module Connectivity on page ER-5-21
End of Table 5-2
There is an operation available within the Node Editor that does not appear on a menu: Open Process Modelthis operation automatically opens the corresponding process model when you double-click on a module in the node.
Interfaces Menu
The Interfaces menu includes operations that allow you to edit a node models interfaces to other nodes and to the project as a whole.
Table 5-3 Interfaces Menu Summary
Menu item Model Attributes Description Edits the nodes model-level attributes. Reference Model Attributes on page ER-5-6 Node Interfaces on page ER-5-7
Node Interfaces
Controls various aspects of attribute promotion to the Network level. Only applies to attributes originating in the nodes objects, not the nodes model attributes. Promotes selected module statistics to the node level so that they can be probed without knowledge of node internal structure Sets information about a node that is used to match node models from an imported topology.
Node Statistics
Node Statistics on page ER-5-11
Self Description
Self Description on page ER-5-11
End of Table 5-3 ER-5-4 www.cadfamily.com EMail:cadserv21@hotmail.com The document is for study only,if tort to your rights,please inform us,we will delete Modeler/Release 14.0
5Node Editor
Objects Menu
The Objects menu includes operations for creating modules in a node.
Table 5-4 Objects Menu Summary
Menu item Create Processor Description Creates a processor module. Reference Create <module> on page ER-5-14 Create <module> on page ER-5-14 Create Packet Stream on page ER-5-16 Create Statistic Wire on page ER-5-18 Create Logical Tx/Rx Association on page ER-5-15 Create <module> on page ER-5-14 Create <module> on page ER-5-14 Create <module> on page ER-5-14 Create <module> on page ER-5-14 Create <module> on page ER-5-14 Create <module> on page ER-5-14 Create <module> on page ER-5-14 Create <module> on page ER-5-14 Show Module Connectivity on page ER-5-21
Create Queue
Creates a queue module.
Create Packet Stream
Creates a packet stream.
Create Statistic Wire
Creates a statistic wire.
Create Logical Tx/Rx Association
Allows a transmitter and a receiver to be treated as a tightly associated pair of modules that should not be separated when attaching nodes to links. Creates a pt-pt receiver module.
Create Pt-Pt Receiver
Create Pt-Pt Transmitter
Creates a pt-pt transmitter module.
Create Bus Receiver
Creates a bus receiver module.
Create Bus Transmitter
Creates a bus transmitter module.
Create Radio Receiver
Creates a radio receiver module (requires Wireless module). Creates a radio transmitter module (requires Wireless module). Creates a radio antenna module (requires Wireless module). Creates an external system module.
Create Radio Transmitter
Create Antenna
Create External System
Show Module Connectivity
Summarizes the packet streams and statistic wires entering and exiting a module.
End of Table 5-4
ER-5-5
5Node Editor
Toolbar Buttons
The Node Editor has toolbar buttons for frequently-used operations. For each toolbar buttonthe name appears as a tooltip when you rest the cursor on the button. To configure the toolbar buttons, see Configuring the Toolbar on page ER-1-6.
Interfaces Menu Operations

This section contains descriptions and procedures for using the operations available from the Interfaces menu in the Node Editor. The items that appear on this menu are described below in alphabetical order: Model Attributes on page ER-5-6 Node Interfaces on page ER-5-7 Node Statistics on page ER-5-11 Self Description on page ER-5-11
Model Attributes
This operation defines the attributes of a node model. Typically, model attributes represent characteristics of the node as a whole, as opposed to characteristics of specific objects within it. An objects or models attributes can transcend modeling domains so that they appear to be associated with a higher-level object. This is called attribute promotion and the attribute is said to be promoted to the next modeling domain. In the context of this editor, node model attributes are acquired by node objects that are instances of the node model. The attributes appear on the object as soon as it is created at the network level. When this operation is invoked, a dialog box is presented which supports the definition of attributes. The set of attributes forms a table, with each attribute occupying an individual row. For each attribute, you can specify its name, group, type, units, and default value. Attribute types can be integer, double (real number), string, toggle (boolean), typed file, or compound. See Modeling Framework on page MC-4-1 for more information about attribute types and their common applications. For a description of attribute groups, see Custom Attribute Organization on page ER-5-22. During the simulation, node model attributes are accessed in the same manner as built-in attributes of nodes. If the attributes are not assigned values in the Project Editor (that is, if they are left as promoted values), they become attributes of the simulation model and can be set at simulation run time. See Modeling Framework on page MC-4-1 for more information about attribute promotion.
5Node Editor
Node Interfaces
A node models attribute interface is a collection of information that determines how the models attributes behave when the model is used either to create a node instance or to derive a new model. In either case, the attribute interfaces specify which attributes of the node are externally visible, how the attributes can be manipulated, and how they are presented. The attributes that are presented on a node object are the result of conscious choices, made by the developer, of the objects underlying node model. The model developer can exercise the following control over the attributes of the node object: Promote attributesBy promoting an attribute, the model makes it available on the object with no assignment. The objects value appears as promoted. This means that the modeler is making no assumptions about what value might be appropriate for the attribute and is deferring this decision to the individual creating the instance of the model. Each separate instance of the model can independently specify its own value of the attribute. Pre-Assign AttributesThis is also known as setting attributes at the level of the model. This mechanism is similar to promotion (described above) in that the attribute appears on the object and can be modified there. However, when the object is created, the attribute automatically receives an assignment determined by the model. This is usually done if the model developer can anticipate reasonable values for all uses of the model. The model user need not assign a value to the attribute, but can override its initial value if necessary. Hide AttributesWhen an attribute is hidden by a model, it is still present on the object, but no longer appears in the objects attribute list. Its value is set to a specified initial value, as in the case of pre-assignment, described above. However, it can no longer be set on the object itself via the user interface. This is a useful mechanism to shield model users from complex or uninteresting attributes that are known to always require a specific value for the model being considered. Rename AttributesA model can rename attributes to simplify or customize their presentation as they appear on the object. Change PropertiesThe properties of an attribute determine aspects of its operation. Some of these include: Constraints on its assignments Special values (known as symbols) that can simplify or customize the assignment process A default value Descriptive comments
ER-5-7
5Node Editor
The mechanisms described above for configuring attributes allow a model to control attributes that originate within its structure, and also to affect certain built-in attributes of the object itself. For example, the icon attribute of a fixed node object is usually specified using the pre-assignment mechanism to suggest a particular way of representing the object. In fact, this pre-assignment also determines the icon that represents the model in the Project Editors object palette. Because pre-assignment is used, you can still override the selected icon for each object in the Project Editor. This operation uses a complex dialog box to support configuration of attributes as well as several other aspects of the node models interface. The dialog box, appears below followed by a description of these additional model interfaces:
Figure 5-2 Node Interfaces Dialog Box
Renaming and Merging of AttributesThe renaming mechanism accessible through this operation allows you to assign a new name to an attribute. The merging mechanism allows you to replace a group of similar attributes with a single attribute that represents them. Both of these mechanisms are useful to simplify the attribute interface offered by a node model. Renaming of attributes is typically done to avoid complex attribute names, particularly names that contain the name of a module or another node internal object as a prefix. Users of the model at the network level typically have no interest in the objects that sourced attributes, only in the attributes relevance to the behavior of the node. For instance, a node that is an ATM switch might have a module called atm_sw_fabric with a user-defined attribute called processing rate. Left promoted, but unmodified, this attribute would appear on a node object at the network level as
5Node Editor
atm_sw_fabric.processing rate. However, to a user of the node model who knows this is an ATM switch, but is unaware of its internal structure, it is probably more meaningful to represent the attribute as Switch Speed or another similarly intuitive and appropriate name. Merging of node model attributes is useful to reduce the number of attributes that a node object inherits from its node model. This mechanism is appropriate in particular cases where it is known that a set of attributes function in an identical manner and are essentially tied together. A common example of this occurs when a node contains many pairs of transmitters and receivers which form ports of the nodes, to which links can attach. If the data rate attributes of the transmitter and receiver channel objects are promoted to allow flexible assignment of this value at the network level, then many such attributes appear on the node object. However, if it is known that all of these data rate attributes must be configured to have the same value (i.e., all ports have the same speed), then merging them into a single attribute not only reduces the specification effort on each instance of the model, but also enforces the consistency across all ports. This section presents an example detailing the steps necessary to merge data rate attributes for multiple transceiver objects in a node model. Model Keyword DeclarationThe keywords of a node model allow it to be selectively displayed in the Project Editor object palette. A model can declare any number of keywords that represent characteristics that it has. These keywords are compared to those requested when configuring the object palette to determine whether to offer the model as a choice. The objective of this mechanism is to allow the user to reduce the number of models presented in the object palette, while presenting only those models that are of interest for the current application. For more information about model keywords, see Project Editor on page ER-3-1. Model Comment SpecificationEach model contains a set of comments that describe its characteristics, potential applications, and any information that might be of interest to a user of the model. Because not all users have access to node model internals, the comments can provide the primary available information about the models capabilities and interfaces. Embedding documentation on the models interfaces, as an intrinsic part of the model itself, provides convenient access to information for model users, and helps to ensure that model documentation remains consistent with a model as it evolves through different phases of development.
ER-5-9
5Node Editor
Node DocumentationThis operation lets you associate two kinds of documentation with the node model: help cardan Adobe Acrobat documentation file located in one of your mod_dirs directories. The dialog box includes a pull-down list of available help cards. tooltipa text string that appears when the cursor rests on an instance of the node in the Project Editor. Node Type SupportA node model supports one or more types. The possible types are fixed, mobile, and satellite (mobile and satellite nodes require the Wireless functionality). To specify which subset of these three types is supported, choose Node Interfaces from the Interfaces menu. It is possible to support one, two, or all three types of nodes for a given node model. When the model is displayed in the Project Editor object palette, one icon appears for each model type that it supports.
Procedure 5-1 Creating and Merging Data Rate Attributes 1 In the Node Editor, create several receiver modules, as follows: 1.1 Click the Create Pt-Pt Receiver toolbar button. 1.2 Click in the tool area several times, creating receiver modules. 1.3 Right-click to end the operation. 2 Select all receiver modules by drawing a selection box around them. 3 Promote the data rate for the receivers, as follows: 3.1 Right-click on one of the receivers to display the Attributes dialog box. 3.2 Click on the Apply Changes to Selected Objects checkbox to select it. 3.3 Click on the Value of the channel attribute to display the Compound Attribute Table dialog box. 3.4 Promote the data rate by left-clicking on the value, then clicking on the Promote button. 3.5 Click OK to close the channel dialog box. 3.6 Click OK to close the Attributes dialog box. 4 Merge the data rate attributes, as follows: 4.1 Choose Node Interfaces from the Interfaces menu. 4.2 Click the Rename/Merge Attributes button. 4.3 Type data_rate in the Auto fill Promotion Name field. 4.4 Move all the data rate attributes in the Unmodified Attributes column to the Modified Attributes column (for example: :pr_0.channel [0].data rate). 4.5 Click OK to close the dialog box.
ER-5-10 www.cadfamily.com EMail:cadserv21@hotmail.com The document is for study only,if tort to your rights,please inform us,we will delete Modeler/Release 14.0
5Node Editor
4.6 Notice that there is now only one data rate attribute in the Edit Node Model dialog box; it is named data_rate and its status is promoted. 5 Click OK to close the Edit Node Model dialog box. End of Procedure 5-1
Node Statistics
This operation promotes selected module statistics to the node level. When you click on the Original Name field, a pop-up menu displays all the statistics available for all modules in the node model. By default, the Promotion Name for a statistic is the same as the original name, but you can edit the Promotion Name to be shorter or more meaningful. You can also enter customized comments for this statistic. When the statistic appears in the Probe Editor as an available statistic for a node, the Promotion Name and Comments you specify here are presented.
Self Description
This operation allows you to set the information about a node that is used to match node models to the nodes in an imported topology. The self description (see Self Description Components on page ER-5-11) specifies information such as what type of machine the node represents (such as a workstation or hub), how many ports it has, and what interfaces the ports support (see Ports on page ER-5-12).
Figure 5-3 ethernet_wkstn_adv Model and Self Description Dialog Box
Self Description Components
A self description has three basic parts: PriorityDuring topology import, if more than one node model matches an imported node, the model with the highest priority is used.
ER-5-11
5Node Editor
RequirementsThese specify the node model characteristics that are used to match against the characteristics of nodes in an imported topology. Each characteristic has a value and a comparator. The comparator specifies what relationship must exist between the values of a characteristic for the node model and a node in the imported topology for a match to occur, as listed in the following table.
Table 5-5 Requirements Comparators
Comparator Equals One-of Meaning The imported nodes value must equal that of the node model. The imported nodes value must equal one of the values listed for the node model. The imported nodes value must be in the range (numeric or alphanumeric) specified for the node model. The imported nodes value must contain that of the node model.
Range
Contains End of Table 5-5
AssignmentsThese specify attributes that are assigned to the node model when it is chosen to represent an imported node.
Ports
A node model self description should include information about all ports supported by the node. Each transmitterreceiver pair must be described, although multiple ports can be described by one port icon if they have the same description and have consecutive port numbers.
Procedure 5-2 Creating a Node Self Description 1 Choose Interfaces > Self Description. The Self Description dialog box opens. New models (without a self description) have only a Core icon. Models that already have a self description also have one or more Port icons. 2 Set the priority for the node. 3 Describe the core model: 3.1 Right-click the Core icon to open the Core Self Description dialog box.
5Node Editor
Figure 5-4 Core Self Description Dialog Box
3.2 Specify any requirements and assignments for the node model. 3.3 Click OK to close the Core Self Description dialog box. 4 Describe the ports: 4.1 If necessary, click the Add Port button to create a Port icon. 4.2 Right-click the Port icon to open the Port Self Description dialog box. Figure 5-5 Port Self Description Dialog Box
ER-5-13
5Node Editor
4.3 Enter the names of a transmitterreceiver pair. To specify multiple transmitterreceiver pairs with consecutive port numbers, use <n> instead of a port number in the name (for example, hub_tx_<n>_0) and enter the minimum and maximum port numbers in the Range fields. 4.4 Specify any requirements and assignments for the node model. Port assignment attribute names can contain the <n> wildcard described in the preceding step. 4.5 Click OK to close the Port Self Description dialog box. 5 Click OK to close the Self Description dialog box. End of Procedure 5-2
Objects Menu Operations

This section contains descriptions and procedures for using the operations available from the Objects menu in the Node Editor.
Figure 5-6 Objects Menu (Node Editor)
These items appear in the menu only when the Wireless functionality is available.
Create <module>
Each module creation operation allows you to create one or more new modules of the selected type within the node model. A module is a functional block that has: Inputs (packet streams and statistic wires) Outputs (packet streams and statistic wires) State memory
5Node Editor
Internal processes. Internal processes provide the logic to determine the modules outputs, based on the applied inputs and state memory. For processor and queue modules, the internal logic is provided by a process modeleither one from the library or one designed by the user in the Process Editor. For an external system (or esys) module, the internal logic is provided by an ESD model (specified in the External System Definition Editor), a process model (designed in the Process Editor), and an external simulation program. All other types of modules are managed in a pre-defined way by the Simulation Kernel. The behavior of these modules can only be controlled by their attributes. For more information about each module type and its capabilities, see Node Domain on page MC-6-1. For more information about external systems, see External System Domain on page MC-8-1. For more information about process models, see Process Domain on page MC-5-1. Each type of module is characterized by a set of attributes that specify its behavior. Attributes are assigned default values by the Node Editor when the module is created. After a module is created, its attributes can be modified using the Edit Object Attributes operation.
Create Logical Tx/Rx Association

This operation creates an association between a transmitter module and a receiver module in a node model. The transmitter and receiver module must correspond to the same link type. That is, a bus transmitter can only be associated with a bus receiver, and a point-to-point transmitter can only be associated with a point-to-point receiver. The purpose of creating an association between transmitters and receivers is to tightly couple them to attach them to links. Frequently, a node model might make assumptions that the packet streams going to and from transmitters and receivers, respectively, are connected to the same link at the network level. However, because the Project Editor automatically chooses transmitters and receivers when attaching links to nodes, and because there can be multiple transmitters and receivers of each type in a node, it is possible that an attachment will be made that separates a transmitter and a receiver that belong together. The logical association between a transmitter and a receiver indicates to the Project Editor that it should treat the two modules as a unit and attach them to the same link.
ER-5-15
5Node Editor
While it is possible for users to override transmitter and receiver assignments for links, users of other OPNET solutions cannot. (These solutions have no visibility into node models and their users are not aware of particular transmitters and receivers). Therefore, the logical transmitter/receiver association is particularly important to ensure that links will be correctly attached to nodes when node models are used in other solutions. Logical associations are shown by a dashed line segment (or series of segments) connecting the two modules. The line has an arrow at both ends. Only point-to-point and bus transmitters support logical associations, and they must be paired with receivers of the same type. An error message displays if the selected source or destination module is not valid.
Multi-Segment Logical Tx/Rx Associations
It is possible to draw logical associations with more than one line segment. The presence of additional line segments does not affect the node model behavior in any way.
Procedure 5-3 Drawing a Multi-Segment Logical Association 1 Click on the transmitter module. 2 Move the cursor to a chosen location within the Node Editora location not covering a moduleand left-click. This creates a vertex in the multi-segmented logical association. 3 Continue left-clicking at each desired vertex. A rubber band line extends from the last vertex to the current location of the pointer. 4 Left-click on the receiver module to complete the logical association. End of Procedure 5-3
Create Packet Stream

This operation creates packet streams between modules in the Node Editor. A packet stream carries packets (arbitrarily-sized collections of data) from the output of a source module to the input of a destination module. It is depicted by a solid line segment (or a series of segments) connecting the icons of two modules. An arrow at the end of a packet stream indicates the direction of data flow.
5Node Editor
A given packet stream can carry data in only one direction. Therefore, if two modules are to send messages back and forth, at least two packet streams must be created. It is not always possible to create a packet stream between two modules for the following reasons: Some types of modules can only be sources for packet streams, while others can only be destinations. The Node Editor will not allow you to originate/terminate a packet stream at a module that cannot serve as a source/destination. Some types of modules can only serve to originate or terminate exactly one packet stream. The following table lists the support provided by each type of module for packet stream connections.
Table 5-6 Support for Packet Stream Connections by Module Type
Module Type Processor Queue Pt-Pt Receiver Pt-Pt Transmitter Bus Receiver Bus Transmitter Esys End of Table 5-6 Source or Destination Both Both Source Destination Source Destination Both # of input streams User-defined User-defined None User-defined None User-defined User-defined # of output streams User-defined User-defined User-defined None User-defined None User-defined
Assigning Source and Destination Streams
Source and destination stream index values are automatically assigned when a packet stream is created. Source and destination stream numbers are typically not re-assigned afterwards. However, they appear as the src stream and dest stream attributes of the packet stream object and can be modified if necessary. When editing these attributes, the Node Editor only allows selection of source and destination streams that have not yet been used.
Multi-Segment Packet Streams
It is possible to draw packet streams with more than one line segment. The presence of additional line segments does not affect the streams operation in any way.
ER-5-17
5Node Editor
Procedure 5-4 Drawing a Multi-Segment Stream 1 Click on the source module. 2 Move the cursor to a chosen location within the Node Editora location not covering a moduleand left-click. This creates a vertex in the multi-segmented packet stream. 3 Continue left-clicking at each desired vertex. A rubber band line extends from the last vertex to the current location of the pointer. 4 Left-click on the destination module to complete the packet stream. End of Procedure 5-4
Error: Invalid initial point selected
This error message appears when an invalid module was selected to act as the source of the packet stream. The module might not be capable of supporting any outgoing streams, or might already be attached to the maximum number of outgoing packet streams that it can support.
Error: Invalid intermediate point
This error message appears when an invalid module was selected to act as the destination of the packet stream. The module might not be capable of supporting any incoming streams, or might already be attached to the maximum number of incoming packet streams that it can support.
Create Statistic Wire

This operation creates statistic wires between source modules and destination modules in a node model. A statistic wire conveys information about the source module to the destination module; the information is the value of a single varying numerical quantity. This quantity, or statistic, can represent a metric of the source module. It can also be a discrete set of flags (representing the state of the source module) that is shared as part of a signaling protocol with the destination module. The statistic is wired from the source module to the destination module to make the statistic available for monitoring by the destination module, and possibly to trigger a response in that module.
5Node Editor
Statistic wires can communicate values to the destination modules in a silent mode, wherein the destination module can simply read the statistic when it needs knowledge of its most current value. Or, statistic wires can be configured to generate a special type of interrupt (a statistic interrupt) at the destination module, in response to particular types of changes in the statistic. For instance, a statistic wire can generate an interrupt for the destination module when its statistic exceeds a specified threshold. See Node Domain on page MC-6-1 for more information about statistic wires and statistic interrupts. Statistic wires are graphically depicted by a dashed line segment (or series of segments) connecting the two modules. An arrow at the end of a statistic wire indicates the direction of information flow. Each type of module has its own unique set of built-in statistics; in addition, user-defined statistics are supported by processors and queues. Built-in statistics are automatically updated by the Simulation Kernel as the state of the source module changes. In the case of processor or queue modules, the process model executing within the module can modify the values of user-defined output statistics by calling the Kernel Procedure op_stat_write(). Any kind of module can be the source of a statistic wire. However, only processor modules and queue modules can be the destinations for a statistic wire. The user-defined processes associated with a processor or queue can use the interrupts and values provided by the statistic wire to adjust their behavior dynamically. A single statistic wire can carry only one statistic. Moreover, a given statistic wire can carry statistical information in only one direction. When the wire is created, default statistics are assigned to be carried from the source module. From the same source module, the same statistic can be carried to more than one destination module. However, a separate statistic wire is required for each destination module. Thus, a statistic can fan out from a source module.
Figure 5-7 Statistic Wires
A given destination module (that is, a given queue or processor) can have any number of input statistics. Each input statistic can be assigned to one, and only one, input statistic wire. For a description of the specific types of statistics available from each module, and for further general information about statistics and statistic wires, see Node Domain on page MC-6-1.
ER-5-19
5Node Editor
Statistic Wire Attributes
Each statistic wire is a node model object which possesses attributes that configure its behavior. All attributes can be edited using the Edit Object Attributes operation, which is activated by right-clicking on any part of the statistic wire. This section describes some important statistic wire attributes. The submodule attribute appears only for statistic wires whose sources are transmitters, receivers, or queues. It is, by default, assigned to channel(0) for transmitters and receivers, but can be modified to refer to any channel that the source module supports. For queues, the submodule attribute is initially given the value NONE, indicating that the statistic belongs to the queue module as a whole, and not to any particular subqueue. The attribute value can be overridden to specify that a subqueue act as the source of the statistic. When a statistic wire is created, the Node Editor automatically chooses a value for the statistic attribute from the set of available statistics provided by the source module. You can edit the statistic attribute to specify a different statistic that you are interested in communicating to the destination module. Statistic wires are equipped with six types of triggers, which control the interrupt generation associated with changes in the statistic during simulation. Each trigger is represented by an attribute, as shown in the statistic wire attribute dialog box shown below. Each trigger specifies whether a particular type of change in the statistic should generate an interrupt for the destination module. If the value of the trigger is set to disabled, then the corresponding change in the statistic does not result in an interrupt. Similarly, if the value is enabled for any of the triggers corresponding to the change, then an interrupt is delivered to the destination module. The last two statistic triggers, high threshold and low threshold, specify interrupt generation when the statistic value exceeds or becomes less than a specified real number.
Figure 5-8 Statistic Wire Attribute Dialog Box
For more information about statistic wire triggers, see Node Domain on page MC-6-1.
ER-5-20 www.cadfamily.com EMail:cadserv21@hotmail.com The document is for study only,if tort to your rights,please inform us,we will delete Modeler/Release 14.0
5Node Editor
Multiple-Segment Statistic Wires
You can create multi-segment statistic wires and drag them using the mouse (the end segments change to reflect the new location). The presence of additional line segments does not affect the statistic wires operation.
Procedure 5-5 Drawing a Multi-Segment Statistic Wire 1 Click on the source module. 2 Move the cursor to a chosen location within the Node Editora location not covering a moduleand left-click. This creates a vertex (turning point) in the multi-segmented statistic wire. 3 Continue left-clicking at each desired vertex. A rubber band line extends from the last vertex to the current location of the pointer. 4 Left-click on the destination module to complete the statistic wire. End of Procedure 5-5
Error: Invalid intermediate point
This error message appears when the selected destination is not valid. Only queues and processors can be the destination modules for statistic wires.
Open Annotation Palette

This operation adds objects to the model that call attention to or label other model elements, as described in Open Annotation Palette on page ER-3-158.
Show Module Connectivity

This operation (called Show Connectivity on the Object pop-up menu) presents a summary of the packet streams and statistic wires entering and exiting a module within the node model. The summary lists both the source and destination modules for each attached packet stream, statistic wire, and logical association. Also, for each packet stream or statistic wire, the summary displays the index of the associated input or output stream, or the name of the associated input and output statistics, respectively. You cannot use this operation to modify a modules connections or to edit the information presented. To modify a modules connectivity with other modules, right-click on the object and edit its attributes.
ER-5-21
5Node Editor
Custom Attribute Organization

Model developers can customize the way a nodes attributes appear in the Edit Attributes dialog box. For example, you can organize attributes into logical groups such as Application, Frame Relay or Routing Protocols. Grouping attributes can help model users navigate an attribute tree and find attributes of interest more easily. Grouped attributes appear similar to sub-attributes in the attribute hierarchy. In both cases, related attributes appear as child attributes within the parent attribute or group name. This customization affects only how attributes appear in the Edit Attributes window, and has no effect on simulation behavior.
Grouping Methods: Logical Grouping and Structural Grouping

A model developer can use two methods for grouping attributes: logical grouping structural grouping Using logical grouping, the developer assigns a group name and (optionally) one or more sub-groups to a node or process attribute. When a model user opens Edit Attributes, all attributes with the same group name appear within the specified group/subgroup hierarchy. You can use this method to organize attributes into logical groups such as ATM, Application Traffic, and Routing Protocols. Figure 5-9 shows how grouped attributes are organized in the Edit Attributes window. This node has a process model with two attributes related to application traffic: Destination Preferences and Source Preferences. Using logical grouping, the process model developer can group the two attributes to indicate that they are related.
Figure 5-9 Using Logical Grouping to Group Attributes
Structural grouping involves renaming and merging attributes in the Node Editor. This method is useful for grouping attributes based on the internal structure of a node model. For example, suppose you create a server node model that contains four CPU modules. All four modules use the same process model, which has an attribute called background utilization. In an ungrouped organization, the attributes would appear as shown in the following figure.
5Node Editor
Figure 5-10 Using Structural Grouping to Group Attributes
Using structural grouping, you can rename and regroup these attributes so they appear like this:
Figure 5-11 Using Structural Grouping to Rename and Regroup Attributes
Structural grouping is most useful when you want to organize process attributes in a node model. Using this method, you can access and organize all the nodes attributes and organize them based on the internal structure of model. Logical grouping is most useful within individual process models. In a process model, you can often determine logical relations between attributes. However, you cannot always determine how the attributes will appear in a node that uses the process model. Note that structural grouping overrides logical grouping and determines the final attribute organization as it appears in the Edit Attributes dialog box.
Logical Grouping of Attributes
Procedure 5-6 Grouping Attributes Logically Within a Node or Process Model 1 Open the node or process model containing the attribute you want to group. 2 Choose Interfaces > Model Attributes in the Process Editor or the Node Editor. 3 In the Model Attributes dialog box, specify a group name in the Group field using the convention <group_name>.<subgroup1_name>.<subgroup2_name>
4 Click OK to close the Model Attributes dialog box. End of Procedure 5-6
ER-5-23
5Node Editor
Structural Grouping of Attributes
Procedure 5-7 Organizing Attributes Based on the Structure of a Node Model 1 Open the node model containing the attribute you want to group. 2 Choose Interfaces > Node Interfaces. 3 In the Node Interfaces dialog box, click Rename/Merge Attributes. Figure 5-12 Rename/Merge Attributes Dialog Box
Unmodified attributes Renamed /merged attributes
Click here to move a selected attribute from the Unmodified Attributes table (left) to the Modified Attributes table (right)
Original attribute name as it appeared in process or node model
Final attribute name and location as they appear in Edit Attributes
The Rename/Merge Attributes has two tables that list unmodified attributes (left table) and attributes with renamed attribute and/or group names (right table). The modified-attributes table has three columns: Modified Attributes (left column)This shows the original attribute name as it appears in the node or process model. If the attribute is a process attribute associated with a specific module, the name appears as <module_name>.<attribute_name>. Promotion Name (center column)This is the final attribute name as it appears in the Edit Attributes dialog box. Promotion Group (right column)This specifies the group hierarchy for the attribute. You can specify a multi-level hierarchy by entering multiple groups separated by periods (for example, Protocols.Routing.IP). 4 If the attribute you want to group is listed in the Unmodified Attributes table (left), select it and click the shift-right button (>>); this moves the attribute into the Modified Attributes table (left). 5 Specify the final attribute name and group/subgroup location in the Promoted Name and Promoted Group fields.
5Node Editor
6 Click OK to close the Rename/Merge Attributes dialog box, then OK to close the Node Interfaces dialog box. End of Procedure 5-7
ER-5-25
5Node Editor

Node Editor

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Node Editor

Uploaded by

Copyright:

Available Formats

5Node Editor

Edit Menu on page ER-2-5.

Interfaces Menu on page ER-5-4

End of Table 5-1

Edit Attributes on page ER-3-252 Show Module Connectivity on page ER-5-21

End of Table 5-2

Node Statistics on page ER-5-11

Self Description on page ER-5-11

Creates a queue module.

Create Packet Stream

Creates a packet stream.

Create Statistic Wire

Creates a statistic wire.

Create Logical Tx/Rx Association

Create Pt-Pt Receiver

Create Pt-Pt Transmitter

Creates a pt-pt transmitter module.

Create Bus Receiver

Creates a bus receiver module.

Create Bus Transmitter

Creates a bus transmitter module.

Create Radio Receiver

Create Radio Transmitter

Create External System

Show Module Connectivity

End of Table 5-4

Interfaces Menu Operations

Self Description Components

Contains End of Table 5-5

Figure 5-4 Core Self Description Dialog Box

Objects Menu Operations

Create Logical Tx/Rx Association

Create Packet Stream

Assigning Source and Destination Streams

Error: Invalid initial point selected

Create Statistic Wire

Statistic Wire Attributes

Multiple-Segment Statistic Wires

Error: Invalid intermediate point

Open Annotation Palette

Show Module Connectivity

Custom Attribute Organization

Grouping Methods: Logical Grouping and Structural Grouping

Figure 5-10 Using Structural Grouping to Group Attributes

Structural Grouping of Attributes

Original attribute name as it appeared in process or node model

Final attribute name and location as they appear in Edit Attributes

You might also like