Model Interfaces
Packet Formats
The following table lists the packet formats used in the Token Ring model suite.
Table 227: Token Ring Packet Formats
| name | description |
|---|---|
| tr_mac_fr | Represents a Token Ring frame. It is used to encapsulate an LLC layer packet. It carries source and destination address information, in addition to the type and priority of the frame. |
| tr_mac_tk | Represents a token. A MAC can only send a frame after it receives a token with the appropriate priority. The token type and the reservation value are also carried in the token. |
ICI Formats
The following table lists the interface control information (ICI) formats used in the Token Ring model suite.
Table 228: Token Ring ICI Formats
| name | description |
|---|---|
| tr_mac_req | Used in conjunction with packet transfers from the LLC to the MAC layer. The destination address and priority of the frame are carried in this ICI. |
| tr_mac_ind | Used in conjunction with packet transfers from the MAC to the LLC layer. The source and destination address information is carried in this ICI. |
Token Ring Addressing and Ring Identifiers
Each ring has a unique identifier, specified by the ring_id attribute of the tr_mac_op_v2 process model. All Token Ring MAC entities on the same ring must agree on the value of this identifier. The ring IDs can be specified to be automatically assigned to meet these requirements.
Each MAC entity has a physical address, specified by the station_address attribute of the tr_mac_op_v2 process model. Token Ring addresses must be consecutive (no gaps in numbering) and increase in the direction of the point-to-point links along a ring. In addition, when using these models in conjunction with the Spanning Tree Bridge models, the addresses must be unique across the entire network to support correct bridge address learning. The addresses can be specified to be automatically assigned to meet these requirements.