Model Scope and Limitations
The previous section briefly described the basic mechanisms and operational context of the token ring MAC entity. This section discusses the implementation choices made in constructing a model of MAC. Because the model is intended for the purpose of simulation, and particularly for performance estimation, certain parts of the protocol have been simplified or omitted. It is important to understand which mechanisms are modeled in order to gauge whether the model is applicable for a particular simulation study.
The first important restriction is that the ring initialization and recovery processes are not modeled explicitly. While the model could be extended to address these areas (it is provided in source code form), its primary usefulness is in obtaining measurements of steady state performance.
A second restriction has to do with the modeling of error conditions and in general, the role of the NMT entity. In its current form, the model makes no attempt to implement the mechanisms related to the detection of damaged frames, or the reporting of errors to NMT. The interface between MAC and NMT is, in fact, not presently incorporated into the implementation of MAC.
The TR model incorporates a token acceleration feature for modeling the passing of the token from station to station. When the ring experiences an idle period with no transmissions, the token may be passed many times in a very short period, thus generating many simulation events and consuming large amounts of real time while producing data which is of little or no interest. In order to jump over these periods, a procedure is employed whereby MAC modules register their interest in using the token and also yield the token through a centrally managed set of variables. When an idle period is encountered, token passing is blocked. The token is later reinjected into the ring as soon as any station has a need for it.
The model does incorporate the interfaces between MAC and LLC, as well as those between PHY and MAC. In addition, the primary data transfer features of TR are modeled explicitly, including definable priority levels for LLC PDUs, and a 24 bit assured minimum latency. The effects of station latency and propagation delay are also incorporated into the model. The restack operation and the THT are also explicitly modeled. The parameters that may be easily controlled by the user, without having to modify the internals of the provided models include:
- The number of stations attached to the ring
- The address of the station that launches the token as the simulation begins, the “active monitor”
- The delay incurred by frames and tokens as they traverse a station’s ring interface
- The propagation delay separating stations on the ring
- The number of bits per second transmitted by the medium
- The duration of the THT, the amount of time a station may transmit on the ring
- The amount of time it takes a station to modify its priority stacks in a restack operation
Model features include:
- 24-bit assured minimum latency
- Token acceleration
- Modularity—there can be more than one ring in a network model
You can configure port-based VLANs on all generic bridge and switch models, and on any vendor-specific models that support this technology. Token Ring link models allow you to simulate point-to-point trunk links; a single trunk link can carry traffic for multiple VLANs as specified by IEEE 802.1q.
To configure a VLAN, set the VLAN scheme attribute to “Port-based VLAN” on the bridge or switch supporting the VLAN. You can assign VLAN identifiers to specific port numbers in the VLAN Port Configuration Table. (To find a link’s port numbers, use Link Interfaces on the Edit Attributes (Advanced) dialog box.) Note that you can assign only one VLAN identifier to a specific port. However, multiple ports can belong to the same VLAN.