Network Object Attribute Descriptions
altitude modeling
This attribute determines how the Simulation Kernel interprets an object altitude attribute. Three settings are possible
- relative to subnet–The altitude setting is interpreted as the object altitude above the current subnet.
- absolute–The altitude setting is the object altitude above global sea level.
- relative to terrain–The altitude setting is the object altitude above the underlying terrain (mountain, valley, ocean, etc.)
This attribute appears only if the Wireless module is in use.
| Editing | Simulation | |
|---|---|---|
| Data Type | enumerated | enumerated |
| Access | read/write/promote | read |
| Default Value | relative to subnet | |
| Units | ||
| Constraints | see description |
Application Configuration
This attribute sets the traffic characteristics for the different applications to be supported on this client.
| Editing | Simulation | |
|---|---|---|
| Data Type | compound | compound |
| Access | read/write | read/write |
| Default Value | Off | |
| Units | ||
| Constraints |
arrowheads
This attribute specifies whether arrowheads appear at the ends of the object when depicted in the Project Editor.
| Editing | Simulation | |
|---|---|---|
| Data Type | enumerated | string |
| Access | read/write | read |
| Default Values | simplex point-to-point link: “tail” duplex point-to-point link: “head and tail” bus tap: “head and tail” path: “head and tail” demand: “tail” |
|
| Units | ||
| Constraints | head and tail, head, tail, none |
attribute promotion
This attribute allows you to control the display of promoted attributes. When enabled, promoted attributes of objects contained in the subnet appear in the subnet attribute list. When disabled, promoted attributes do not appear in the list, nor do they promote to the parents of the subnet.
The attribute is most useful when a model contains many levels of nested subnets, each with many nodes and many promoted attributes. In this case, displaying the Attributes dialog box of any subnet (especially the top subnet), or scrolling through the list of attributes, can be slow and cumbersome. It is recommended that you set “attribute promotion” to disabled except when you need to display or modify the value of a promoted attribute on a subnet.
Although promoted attributes do not appear in the subnet attribute list when the attribute value is “disabled”, they still must be resolved at simulation run time.
| Editing | Simulation | |
|---|---|---|
| Data Type | toggle | not applicable |
| Access | read/write | not applicable |
| Default Value | disabled | |
| Units | ||
| Constraints |
ber
This attribute can be used to specify the probability of bit errors in packets that are transmitted over a link. Typically, the ber is translated into bit errors by the error model of the link’s pipeline. For example, with a ber of 0.1, packets with a length of 100 bits will average 10 bit errors.
If this attribute is set to NONE, the pipeline stage is skipped and the Simulation Kernel uses a default value, as described in “Pipeline Stage Definition” on page 356.
See Chapter 9 “Communication Mechanisms” on page 331 for details on the transceiver pipeline.
| Editing | Simulation | |
|---|---|---|
| Data Type | double | double |
| Access | read/write/promote | read/write |
| Default Value | 0.0 | |
| Units | errors/bit | |
| Constraints | 0.0 <= ber <= 1.0 |
bundle display
This attribute sets the link bundling option for the specified link. When “network_visualization.auto_link_bundling” preference is activated, set the “bundle display” attribute to override the preference.
The “bundle display” attribute settings are
- include in bundle and display fanned out – Specifies to include the link in a bundle. Additionally, by default, display the link in an expanded bundle.
- include in bundle and display collapsed – Specified to include the link in a bundle. Additionally, by default, display the link in a collapsed bundle.
- exclude from bundle – Specifies to exclude the link from any bundle.
| Editing | Simulation | |
|---|---|---|
| Data Type | enumerated | not applicable |
| Access | read/write | not applicable |
| Default Value | include in bundle and display collapsed | |
| Units | ||
| Constraints | include in bundle and displayed fanned out, include in bundle and display collapsed, exclude from bundle. |
channel count
This attribute specifies the number of channels in the link. To achieve link consistency, this must be the same number of channels supported by the transmitters and receivers of nodes attached to the link.
| Editing | Simulation | |
|---|---|---|
| Data Type | integer | integer |
| Access | read/write | read |
| Default Value | 1 | |
| Units | ||
| Constraints | >= 1 |
For more information about link consistency, see Chapter 7 “Network Domain” on page 292.
closure model
This attribute specifies the name of a compiled pipeline procedure capable of determining the connectivity between any transmitter and receiver on the bus. The purpose of this stage is to allow the user to impose restrictions on which transmitter-receiver pairs can communicate. The default assignment for this pipeline stage is the base model dbu_closure which allows closure between all transmitters and receivers.
If this attribute is set to NONE, the pipeline stage is skipped and the Simulation Kernel uses a default value, as described in “Pipeline Stage Definition” on page 356.
| Editing | Simulation | |
|---|---|---|
| Data Type | typed file | string |
| Access | read/write | read |
| Default Values | dbu_closure |
|
| Units | ||
| Constraints |
For more information about dbu_closure, see Chapter 3 “Pipeline Stages/Bus Link” on page 6.
coll model
This attribute specifies the name of a compiled pipeline procedure which is invoked to register that a collision has occurred when two packets are simultaneously present at the same receiver channel on the bus link. The number of collisions a packet experiences is typically recorded in the packet transmission data. Typically, this information is then used by the “error correction” pipeline stage to determine whether to accept or reject a packet at a receiver channel. The default assignment for this pipeline stage is the base model dbu_coll which considers any packets that overlap in time at a bus receiver channel to be collided.
If this attribute is set to NONE, the pipeline stage is skipped and the Simulation Kernel uses a default value, as described in “Pipeline Stage Definition” on page 356.
For a detailed description of dbu_coll, see Chapter 3 “Pipeline Stages/Bus Link” on page 6.
| Editing | Simulation | |
|---|---|---|
| Data Type | typed file | string |
| Access | read/write | read |
| Default Value | dbu_coll | |
| Units | ||
| Constraints |
color
This attribute specifies the color of an instance of the object when displayed in the Project Editor. This attribute has no effect on simulation. Clicking in the Value column for this attribute opens the Color Chooser.
“color” can have values ranging from RGB000 to RGB333, where each digit is an integer between 0 and 3 inclusive. The higher the first digit, the more red, the higher the second digit, the more green, and the higher the third digit, the more blue. Thus, RGB000 corresponds to black, RGB333 corresponds to white, RGB300 corresponds to red, and so on.
| Editing | Simulation | |
|---|---|---|
| Data Type | color | not applicable |
| Access | read/write | not applicable |
| Default Values | point-to-point link: RGB000 bus link: RGB023 bus tap: RGB222 path: RGB003 demand: RGB010 |
|
| Units | ||
| Constraints |
condition
This attribute represents the operational status of the object. A value of “enabled” signifies that the object is active and can perform all usual functions of that object type. A value of “disabled” signifies that the object is unable to perform any functions. For example, disabled links cannot forward packets and attempted transmissions are dropped.
Users interested in the effects of a node becoming disabled can modify the “condition” attribute during simulation using the KP op_ima_obj_attr_set(). Changing the value from “enabled” to “disabled” creates failure interrupts at selected modules. Changing the value from “disabled” to “enabled” creates recovery interrupts at selected modules.
| Editing | Simulation | |
|---|---|---|
| Data Type | toggle | toggle |
| Access | read/write/promote | read/write |
| Default Value | enabled | |
| Units | ||
| Constraints | enabled, disabled |
For more information about modeling failures and recoveries, see “Modeling Node and Link Failure/Recovery” on page 313.
cost
This attribute is a double-precision floating-point number that is primarily intended as a routing parameter. This parameter typically is used by routing APIs that determine the total cost of a route. This value can also be used explicitly by the user in developing a new routing algorithm.
| Editing | Simulation | |
|---|---|---|
| Data Type | double | double |
| Access | read/write/promote | read/write |
| Default Value | 0.0 | |
| Units | ||
| Constraints | cost >= 0.0 |
creation data
This attribute specifies additional information about the creation of the object.
| Editing | Simulation | |
|---|---|---|
| Data Type | string | not applicable |
| Access | read/write | not applicable |
| Default Value | “” | |
| Units | ||
| Constraints |
creation source
This attribute specifies how the object was created.
| Editing | Simulation | |
|---|---|---|
| Data Type | string | not applicable |
| Access | read/write | not applicable |
| Default Value | “Object Palette” | |
| Units | ||
| Constraints |
creation timestamp
This attribute specifies when the object was created.
| Editing | Simulation | |
|---|---|---|
| Data Type | date | not applicable |
| Access | read/write | not applicable |
| Default Value | ||
| Units | ||
| Constraints |
data rate
This attribute specifies the speed of data transmission over the link. This speed applies only to the first channel supported by the link and must match the data rate of channel [0] of the transmitters and receivers in attached nodes. A special value of “unspecified” allows the link to obtain its data rate at simulation run time from the transmitter and receiver channels in attached nodes.
| Editing | Simulation | |
|---|---|---|
| Data Type | double | double |
| Access | read/write/promote | read/write |
| Default Value | 1024.0 | |
| Units | bits/second | |
| Constraints | data rate > 0.0 |
delay
For point-to-point links, this attribute usually specifies an absolute propagation delay, in seconds, that will be experienced by packets sent over the link. This value is used by the propagation delay stage of the pipeline. Typically, the value assigned to “delay” is the total propagation delay across the link, or zero if the effects of propagation delay are considered negligible. If this attribute has the symbolic value “Distance Based”, the propagation delay is determined based on the distance from source to destination and the propagation speed.
For bus links, this attribute is a positive double-precision floating-point number typically used in computing the propagation delay that will be incurred by packets sent over the bus. This value is specified in units of “seconds per meter” and represents the simulated time required for a signal to propagate one meter of distance within the bus. This value is used in the propagation delay (propdel) stage of the bus pipeline. Distance is measured along the path of the bus link as specified by the user, as opposed to a simple distance calculation between the communicating transceivers. The default value of 0.0 implies that all receivers attached to the bus receive transmissions at the same simulation time.
| Editing | Simulation | |
|---|---|---|
| Data Type | double | double |
| Access | read/write/promote | read/write |
| Default Value | 0.0 | |
| Units | point-to-point link: seconds bus link: seconds/meter |
|
| Constraints | delay >= 0.0 |
ecc model
This attribute specifies the name of a compiled pipeline procedure that determines whether or not a packet transmitted over a link can be accepted by the receiver in a destination node. The pipeline procedure can use any application-specific criteria in determining whether a packet is accepted or rejected. However, in general, this decision is based on the quantity of erroneous bits present in the packet.
- For point-to-point links, the default model simply compares the proportion of bit errors present with the value of the ecc threshold attribute for the receiver. If the number of errors exceeds the threshold, the packet is rejected.
- For bus links, the default model first checks if the packet experienced any collisions. If it did, the packet is rejected by the receiver channel. If the packet did not experience any collisions, the default model next checks the number of bit errors in the packet. If the number of errors in the packet exceeds the value of the ecc threshold attribute for the bus receiver, it rejects the packet. If the packet has experienced no collisions and has fewer errors than the ecc threshold, it is accepted by the receiver.
If this attribute is set to NONE, the pipeline stage is skipped and the Simulation Kernel uses a default value, as described in “Pipeline Stage Definition” on page 356.
See Chapter 9 “Communication Mechanisms” on page 331 for information about the transceiver pipeline.
| Editing | Simulation | |
|---|---|---|
| Data Type | typed file | string |
| Access | read/write | read |
| Default Value | point-to-point link: dpt_ecc bus link: dbu_ecc |
|
| Units | ||
| Constraints |
error model
This attribute specifies the name of a compiled pipeline procedure that calculates the number of bit errors in a given packet transmitted over a link. The number of bit errors must be an integer greater than or equal to zero and less than or equal to the number of bits contained in the packet. The default model calculates a total number of bit errors for a packet based on the value of the ber attribute and the length of the packet.
If this attribute is set to NONE, the pipeline stage is skipped and the Simulation Kernel uses a default value, as described in “Pipeline Stage Definition” on page 356.
See Chapter 9 “Communication Mechanisms” on page 331 for more information about the transceiver pipeline.
| Editing | Simulation | |
|---|---|---|
| Data Type | typed file | string |
| Access | read/write | read |
| Default Value | point-to-point link: dpt_error bus link: dbu_error |
|
| Units | ||
| Constraints |
financial cost
This attribute specifies the cost of purchasing or maintaining the object.
| Editing | Simulation | |
|---|---|---|
| Data Type | string | string |
| Access | read/write/promote | read/write |
| Default Value | “0.00” | |
| Units | ||
| Constraints |
hostname
| Editing | Simulation | |
|---|---|---|
| Data Type | string | not applicable |
| Access | read/write/promote | not applicable |
| Default Value | “” | |
| Units | ||
| Constraints |
icon name
This attribute specifies the bitmap used to represent the object in network diagrams. Icons can be created with the Icon Editor. The value of this attribute has no impact on simulation behavior.
| Editing | Simulation | |
|---|---|---|
| Data Type | icon | not applicable |
| Access | read/write | not applicable |
| Default Values | subnetwork: subnet fixed communications node: fixed_comm |
|
| Units | ||
| Constraints |
IP Address Information
Allows the configuration of the following:
- Number of IP interfaces
- IP address for each interface
- Subnet mask for each interface
- MTU for each IP interface
A value of No IP Interfaces means that no IP interfaces have been set up.
| Editing | Simulation | |
|---|---|---|
| Data Type | compound | compound |
| Access | read/write | read/write |
| Default Value | No IP Interface | |
| Units | ||
| Constraints |
IP Forwarding Rate
Number of packets that are processed by the central processor in one second. The service rates for slot processors are specified in the IP Slot Information attribute.
| Editing | Simulation | |
|---|---|---|
| Data Type | double | double |
| Access | read/write | read/write |
| Default Value | 5000.0 | |
| Units | packets/second | |
| Constraints |
IP Processing Scheme
Controls the number of servers (processors) and queues used by IP for packet forwarding. In central processing, one server with one queue is used to process all packets. In slot based processing, in addition to one central server (with its own queue), additional servers, each with its own queue, are used to process packets. The number of additional servers is determined by the number of slots that have been configured. The IP Slot Information model attribute controls the number of slots used by an IP process instance. When used with multiple servers, slot based processing can deliver greater packet throughput.
| Editing | Simulation | |
|---|---|---|
| Data Type | integer | integer |
| Access | read/write | read/write |
| Default Value | Central Processing | |
| Units | ||
| Constraints |
IP Slot Information
Typically, IP routing devices have slots, each with its own slot processor. This attribute allows the modeling of such slotted devices in association with the IP model. The information in this attribute is used only when the Router Processing Scheme attribute is set to Slot Based Processing. The value NOT USED represents zero slots.
| Editing | Simulation | |
|---|---|---|
| Data Type | compound | compound |
| Access | read/write | read/write |
| Default Value | ||
| Units | ||
| Constraints |
label color
Specifies the label color of the corresponding node. You can set the attribute for each node (and subnet) to contrast with the background. The default color is black.
| Editing | Simulation | |
|---|---|---|
| Data Type | color | not applicable |
| Access | read/write | not applicable |
| Default Value | black | |
| Units | ||
| Constraints |
label rotation
Specifies the rotation of link labels. By default, link labels are displayed horizontally. However, you can rotate the label using the link attribute “label rotation”. The “label rotation” attribute can be set to horizontal, vertical, parallel to link, or perpendicular to link.
| Editing | Simulation | |
|---|---|---|
| Data Type | enumerated | not applicable |
| Access | read/write | not applicable |
| Default Value | horizontal | |
| Units | ||
| Constraints |
LAN Background Utilization
Provides a method for creating a baseline load on this object. This load, called background utilization, is specified as a percentage of the data rate. Different values can be specified for different simulation-time duration. Traffic specified by this attribute does not include imported traffic, nor does it include traffic generated explicitly by network sources. Background utilization traffic is included in the total traffic load when calculating statistics.
| Editing | Simulation | |
|---|---|---|
| Data Type | compound | compound |
| Access | read/write | read/write |
| Default Value | ||
| Units | ||
| Constraints |
LAN MAC Address
Address of the Ethernet MAC representing this LAN.
| Editing | Simulation | |
|---|---|---|
| Data Type | integer | integer |
| Access | read/write | read/write |
| Default Value | auto-assigned | |
| Units | ||
| Constraints |
LAN Server Name
Name of the server residing in the LAN. Clients from other LANs can communicate to the server in the LAN by specifying this name as their Server Name.
| Editing | Simulation | |
|---|---|---|
| Data Type | string | string |
| Access | read/write | read/write |
| Default Value | auto-assigned | |
| Units | ||
| Constraints |
LAN Type
Type of Ethernet LAN. Valid LAN types are as follows:
- Ethernet: 10BaseT
- Fast Ethernet: 100BaseT
- Gigabit Ethernet: 1000BaseX
- FDDI: 100Mbps
- Token Ring 4: 4Mbps
- Token Ring 16: 16Mpbs
| Editing | Simulation | |
|---|---|---|
| Data Type | integer | integer |
| Access | read/write | read/write |
| Default Value | Ethernet | |
| Units | ||
| Constraints |
line style
This attribute allows you to modify the line style that represents the link within network diagrams. It has no effect on simulation behavior.
Note: You can only set the “line style” attribute on individual instances of link objects. It does not appear in the link model interfaces, so you cannot set this attribute for link objects on a model-wide basis.
| Editing | Simulation | |
|---|---|---|
| Data Type | enumerated | not applicable |
| Access | read/write | not applicable |
| Default Values | link: solid path: solid demand: dotted |
|
| Units | ||
| Constraints | solid, dashed, dotted |
map
This attribute specifies the name of a cartographic data set file with a “.cds” suffix (the suffix is not included in the attribute value) whose content is depicted in the Project Editor.
This attribute has no effect on simulations.
| Editing | Simulation | |
|---|---|---|
| Data Type | typed file | not applicable |
| Access | read/write | not applicable |
| Default Value | ||
| Units | ||
| Constraints |
minimized icon
This attribute specifies how the subnet will be displayed when scaling would cause it to appear too small to be represented by its original icon.
| Editing | Simulation | |
|---|---|---|
| Data Type | minimized icon | not applicable |
| Access | read/write | not applicable |
| Default Value | subnetwork: “circle/#FF0000” communication node: “circle/#708090” |
|
| Units | ||
| Constraints |
model
This attribute specifies the model on which the object is based. The primary role of the model is to specify how the object’s attributes are configured. The model represents the internal structure and therefore the capabilities of the object and can also cause the object to inherit attributes that have been promoted upwards.
See Chapter 6 “Node Domain” on page 263 to learn more about node models. See Chapter 9 “Communication Mechanisms” on page 331 for more information about link models.
| Editing | Simulation | |
|---|---|---|
| Data Type | enumerated | string |
| Access | read/write | read |
| Default Value | ||
| Units | ||
| Constraints | valid model name |
name
This attribute specifies a string that is used for identification purposes. It is useful for identifying a link in a model report. It is also used during simulation to obtain the link object ID via the KP op_id_from_name(). The object ID is useful for getting attribute values and can also be used for routing or disabling/enabling links dynamically. The Riverbed Simulation Kernel makes no use of this attribute.
| Editing | Simulation | |
|---|---|---|
| Data Type | string | string |
| Access | read/write | read |
| Default Values | subnetwork: “subnet_n”, n >= 0 communication node: “node_n”, n >= 0 simplex point-to-point link: “<src_node> -> <dest_node>” duplex point-to-point link: “<src_node> <-> <dest_node>” bus link: “bus_n”, n >= 0 bus tap: “<bus> - <node>” path: “<src_node> <-> <dest_node>” demand: “<src_node> <-> <dest_node>” |
|
| Units | ||
| Constraints | unique name, no dots, not “top” |
Number of Workstations
Total number of workstations in a given LAN. Each LAN is composed of a number of workstations and a built-in server.
| Editing | Simulation | |
|---|---|---|
| Data Type | integer | integer |
| Access | read/write | read/write |
| Default Value | 10 | |
| Units | ||
| Constraints |
outline color
This attribute specifies the color of a subnetwork perimeter display for the purpose of its depiction in the Project Editor. This attribute has no effect on simulation. Clicking in the Value column for this attribute opens the Color Chooser.
“outline color” can have values ranging from RGB000 to RGB333, where each digit is an integer between 0 and 3, inclusive. The higher the first digit, the more red, the higher the second digit, the more green, and the higher the third digit, the more blue. Therefore, RGB000 corresponds to black, RGB333 corresponds to white, RGB300 corresponds to red, and so on.
| Editing | Simulation | |
|---|---|---|
| Data Type | color | not applicable |
| Access | read/write | not applicable |
| Default Value | RGB133 | |
| Units | ||
| Constraints |
packet formats
This attribute specifies which packet formats are supported by the link. These formats must match the ones being used by the transmitters and receivers in attached nodes; if not, the link will not be operational during simulation. The Project Editor makes use of this attribute as part of a link consistency determination. Link consistency analyzes the compatibility of nodes and links that are connected to each other. See Chapter 7 “Network Domain” on page 292 for more information about link consistency.
| Editing | Simulation | |
|---|---|---|
| Data Type | string | string |
| Access | read/write | read |
| Default Value | “all formatted,unformatted” | |
| Units | ||
| Constraints |
priority
This attribute is used when multiple events are scheduled for the same simulation time, to determine in which order they will be executed. Higher priority events are executed first. Event priority is evaluated hierarchically with subnet priority being weighted higher than node priority, which in turn is weighted higher than module priority. Only the priority of the lowest parent subnet is considered when evaluating the priority of an event occurring at a module.
This attribute is not used by the parallel simulation kernel.
| Editing | Simulation | |
|---|---|---|
| Data Type | integer | integer |
| Access | read/write/promote | read/write |
| Default Value | 0 | |
| Units | ||
| Constraints | Abs value(priority) <= 32,000 |
propdel model
This attribute specifies the name of a compiled pipeline procedure that calculates propagation delay between a transmitter and a receiver communicating via a link. The propagation delay is the simulated time separating the transmission of the first bit of the packet from the reception of the first bit of the same packet.
- For point-to-point links, the default model simply sets the propagation delay equal to the value of the link’s “delay” attribute.
- For bus links, the default model calculates a delay time based on the distance separating the bus transmitter and receiver of interest and the value of the “delay” attribute of the bus link.
If this attribute is set to NONE, the pipeline stage is skipped and the Simulation Kernel uses a default value, as described in “Pipeline Stage Definition” on page 356.
See Chapter 9 “Communication Mechanisms” on page 331 for more information about the transceiver pipeline.
| Editing | Simulation | |
|---|---|---|
| Data Type | typed file | string |
| Access | read/write | read |
| Default Value | point-to-point link: dpt_propdel bus link: dbu_propdel |
|
| Units | ||
| Constraints |
receiver
This attribute specifies a bus receiver in an attached node as the destination for packets arriving over the attached bus. If the value of this attribute is set to NONE or left empty, then this node will not receive packets via this tap. In this case, the tap will graphically appear as a unidirectional tap from the node to the bus link (a transmit only tap).
The value of this attribute is specified as the name of the node, followed by a dot (.) separator, and followed by the name of the bus receiver. An example receiver value is node_0.br_0 where the node is named node_0 and the bus receiver is named br_0.
| Editing | Simulation | |
|---|---|---|
| Data Type | enumerated | string |
| Access | read/write | read |
| Default Value | ||
| Units | ||
| Constraints |
receiver a
This attribute designates which point-to-point receiver within the first attached node receives packets from the duplex point-to-point link. The attribute value must correspond to the name of a point-to-point receiver within the node model for the link to be operational. The value of this attribute is specified as the name of the node, followed by a dot (.) separator, followed by the name of the point-to-point receiver. For example, a valid value is node_0.pr_0, where the node is named node_0 and the receiver is named pr_0.
| Editing | Simulation | |
|---|---|---|
| Data Type | enumerated | string |
| Access | read/write | read |
| Default Value | ||
| Units | ||
| Constraints |
receiver b
This attribute designates which point-to-point receiver within the second attached node receives packets from the duplex point-to-point link. The attribute value must correspond to the name of a point-to-point receiver within the node model for the link to be operational. The value of this attribute is specified as the name of the node, followed by a dot (.) separator, followed by the name of the point-to-point receiver. For example, a valid value is node_0.pr_0, where the node is named node_0 and the receiver is named pr_0.
| Editing | Simulation | |
|---|---|---|
| Data Type | enumerated | string |
| Access | read/write | read |
| Default Value | ||
| Units | ||
| Constraints |
right-angled
This attribute specifies the right-angled property, which is used to draw simplex and duplex point-to-point links. This attribute has no effect on the simulation.
| Editing | Simulation | |
|---|---|---|
| Data Type | toggle | not applicable |
| Access | read/write | not applicable |
| Default Value | disabled | |
| Units | ||
| Constraints | disabled, enabled |
role
This attribute describes the purpose served by the object.
| Editing | Simulation | |
|---|---|---|
| Data Type | string | not applicable |
| Access | read/write/promote | not applicable |
| Default Value | “” | |
| Units | ||
| Constraints |
Server Background Utilization
Specifies mean baseline loads for this server. Delays representing the effects of the background load are calculated for each explicitly-modeled job being serviced.
Each entry in this table has a start time and a background utilization. The utilization applies until the start time of the next entry (or to the end of simulation in the case of the last entry).
| Editing | Simulation | |
|---|---|---|
| Data Type | compound | compound |
| Access | read/write | read/write |
| Default Value | ||
| Units | ||
| Constraints |
Server Configuration
Defines application services supported at this server. Also allows server parameter configuration for each client application.
| Editing | Simulation | |
|---|---|---|
| Data Type | compound | compound |
| Access | read/write | read/write |
| Default Value | ||
| Units | ||
| Constraints |
Server Processing Speed Multiplier
The number of job units the server processes in one second. The server uses this value to compute the request response rate.
| Editing | Simulation | |
|---|---|---|
| Data Type | double | double |
| Access | read/write | read/write |
| Default Value | 1.0 | |
| Units | ||
| Constraints |
Start Time
The start time for each application supported by the node.
| Editing | Simulation | |
|---|---|---|
| Data Type | compound | compound |
| Access | read/write | read/write |
| Default Value | 100 | |
| Units | Seconds | |
| Constraints |
Stop Time
The stop time for each application supported by the node.
| Editing | Simulation | |
|---|---|---|
| Data Type | compound | compound |
| Access | read/write | read/write |
| Default Value | End of Simulation | |
| Units | ||
| Constraints |
Switching Speed
Specifies the rate at which packets are switched from the switch processor to the appropriate output port. Typically, this is the speed of the switch used in a LAN.
| Editing | Simulation | |
|---|---|---|
| Data Type | double | double |
| Access | read/write | read/write |
| Default Value | 500 000 | |
| Units | packets per second | |
| Constraints |
symbol
This attribute specifies a graphical symbol that appears over the midpoint of each segment of the object. It has no effect on simulation behavior.
| Editing | Simulation | |
|---|---|---|
| Data Type | enumerated | not applicable |
| Access | read/write | not applicable |
| Default Value | “none” | |
| Units | ||
| Constraints | none, circle, square, triangle, diamond |
TCP Maximum Segment Size
Maximum Segment Size (MSS) that the underlying network can carry without fragmenting. Used to determine the size of segments sent by TCP.
| Editing | Simulation | |
|---|---|---|
| Data Type | integer | integer |
| Access | read/write | read/write |
| Default Value | 536 | |
| Units | bytes | |
| Constraints |
thickness
This attribute specifies the thickness (in pixels) of the line used to draw the object. It has no effect on simulation behavior.
| Editing | Simulation | |
|---|---|---|
| Data Type | integer | integer |
| Access | read/write | read |
| Default Values | point-to-point link: 1 bus link: 5 bus tap: 1 path: 5 demand: 1 |
|
| Units | ||
| Constraints |
threshold
This attribute affects the object’s display characteristics at different zoom levels. If its value is higher than the current resolution of the map, the object will be displayed as a miniaturized icon. Typically, this attribute is used to ensure that network diagrams do not become cluttered with icons at higher zoom levels. The current resolution of the map can be determined in the Project Editor from the dialog box that appears in response to the View > Background > Set Properties command. In the top subnet level, this attribute is measured in pixels/degree and in all other subnet levels, it is measured in pixels/unit of the subnet.
| Editing | Simulation | |
|---|---|---|
| Data Type | double | not applicable |
| Access | read/write | not applicable |
| Default Value | 0.0 | |
| Units | see description | |
| Constraints |
transmitter
This attribute designates which transmitter in the attached node acts as a source for packets to be put onto the link. The value of this attribute is specified as the name of the node, followed by a dot (.) separator, followed by the name of the bus transmitter. For example, a valid value is node_0.pt_0, where the node is named node_0 and the transmitter is named pt_0.
For bus taps, if the value of this attribute is set to NONE or left empty, the node will not transmit packets via this tap. In this case, the link will graphically appear as a unidirectional tap from the bus link to the node (a “receive only” tap).
| Editing | Simulation | |
|---|---|---|
| Data Type | enumerated | string |
| Access | read/write | read |
| Default Value | ||
| Units | ||
| Constraints | must be unique |
transmitter a
This attribute designates which point-to-point transmitter in the first attached node acts as a source for the duplex point-to-point link. The attribute value must correspond to the name of a point-to-point transmitter within the node model for the link to be operational. The value of this attribute is specified as the name of the node, followed by a dot (.) separator, followed by the name of the point-to-point transmitter. For example, a valid value is node_0.pt_0, where the node is named node_0 and the transmitter is named pt_0.
| Editing | Simulation | |
|---|---|---|
| Data Type | enumerated | string |
| Access | read/write | read |
| Default Value | ||
| Units | ||
| Constraints |
transmitter b
This attribute designates which point-to-point transmitter in the second attached node acts as a source for the duplex point-to-point link. The attribute value must correspond to the name of a point-to-point transmitter within the node model for the link to be operational. The value of this attribute is specified as the name of the node, followed by a dot (.) separator, followed by the name of the point-to-point transmitter. For example, a valid value is node_0.pt_0, where the node is named node_0 and the transmitter is named pt_0.
| Editing | Simulation | |
|---|---|---|
| Data Type | enumerated | string |
| Access | read/write | read |
| Default Value | ||
| Units | ||
| Constraints |
Transport Protocol
The transport protocol for each application supported by the node.
| Editing | Simulation | |
|---|---|---|
| Data Type | compound | compound |
| Access | read/write | read |
| Default Value | Depends on application | |
| Units | ||
| Constraints |
txdel model
This attribute is the name of a compiled pipeline procedure that calculates transmission delay associated with the transmission of a packet over a link, The transmission delay is the simulated time separating the transmission of the first bit of the packet from the transmission of the last bit of the same packet. The default model computes transmission delay based on the channel data rate and the length of the packet.
If this attribute is set to NONE, the pipeline stage is skipped and the Simulation Kernel uses a default value, as described in “Pipeline Stage Definition” on page 356.
See Chapter 9 “Communication Mechanisms” on page 331 of Modeling Concepts for more information on the transceiver pipeline.
| Editing | Simulation | |
|---|---|---|
| Data Type | typed file | string |
| Access | read/write | read |
| Default Value | point-to-point link: dpt_txdel bus link: dbu_txdel |
|
| Units | ||
| Constraints |
unit
This attribute contains the units used by objects within the subnet. The value is one of the OpT_Ima_Obj_Position_Unit_Type values (see Table 68 “Object Position Unit Type Symbolic Constants” on page 19).
| Editing | Simulation | |
|---|---|---|
| Data Type | not applicable | integer |
| Access | not applicable | read |
| Default Value | ||
| Units | ||
| Constraints |
user id
This attribute is an integer that is provided for user-specific identification purposes. Unlike sys id, it does not necessarily have the property of uniqueness, but it is a read/write variable and you can assign it in any way desired.
| Editing | Simulation | |
|---|---|---|
| Data Type | integer | integer |
| Access | read/write/promote | read/write |
| Default Value | 0 | |
| Units | ||
| Constraints |
x position
This attribute specifies the horizontal position of the object. Because these are fixed objects, the value at specification time is also the value throughout the simulation, and this value cannot be changed dynamically. This attribute is specified in the units of the parent subnetwork. When the unit is degrees, this corresponds to longitude. A positive value refers to degrees East longitude and a negative value refers to degrees West longitude.
For communications nodes, this attribute is one of three components specifying position: x position, y position, and altitude. This attribute represents the distance separating the node from the left edge of the enclosing subnet extent.
For subnetworks, this attribute specifies the x-coordinate of the center of the subnetwork extent (which is also the x-coordinate of the position at which the subnetwork icon is displayed in the Project Editor).
| Editing | Simulation | |
|---|---|---|
| Data Type | double | double |
| Access | read/write | read |
| Default Value | ||
| Units | see description | |
| Constraints |
y position
This attribute specifies the vertical position of the object. Because these are fixed objects, the value at specification time is also the value throughout the simulation, and this value cannot be changed dynamically. This attribute is specified in the units of the parent subnetwork. When the unit is degrees, this corresponds to latitude. A positive value refers to degrees North latitude and a negative value refers to degrees South latitude.
For communications nodes, this attribute is one of three components specifying position: x position, y position, and altitude. This attribute represents the distance separating the node from the top edge of the enclosing subnet extent.
For subnetworks, this attribute specifies the y-coordinate of the center of the subnetwork extent (which is also the y-coordinate of the position at which the subnetwork icon is displayed in the Project Editor).
| Editing | Simulation | |
|---|---|---|
| Data Type | double | double |
| Access | read/write | read |
| Default Value | ||
| Units | see description | |
| Constraints |