I noticed that the data rates of my transmitter, receiver, and links were not identical, but the simulation kernel did not give any warnings about the mismatch. Why not?

Categories:
Solution Number:
S20776
Last Modified:
2013-08-20
Issue

I noticed that the data rates of my transmitter, receiver, and links were not identical, but the simulation kernel did not give any warnings about the mismatch. Why not?

Solution

This is intentional; the simulation kernel will not perform consistency checks between the data rate attributes on transceivers and links.You can manually check consistency by clicking on the Verify Links button in the project editor. It is recommended that you perform this check before performing any discrete-event or flow analysis simulation.For point-to-point and bus topologies, it is recommended that you set the transmitter and receiver channel data rate attribute to the special value unspecified. In this situation the data rate of the link associated with that channel will be used instead.It is common to use only the transmitter's data rate to compute transmission delay; in such an approach, the receiver's data rate is not used at all.For wireless transmitters and receivers, it is common to have rxgroup or closure pipeline stages ignore transceivers with mismatching data rates. In other words, through the transceiver pipeline stages, you can prevent such communication from taking place.---More information about link consistency and the unspecified data rate is available in the Modeler product documentation, vol. Modeling Concepts, ch. Network Domain, sec. Network Objects, subsec. Communication Links, subsubsec. Link Consistency.More information about

Environment

Attachments
NOTICE: Riverbed® product names have changed. Please refer to the Product List for a complete list of product names.
Can't find an answer? Create a case