Model Interfaces: FDDI
Packet Formats: FDDI
The following table lists the packet formats used in the FDDI model suite.
Table 50: FDDI Packet Formats
| name | description |
|---|---|
| fddi_llc_fr | Used for frames generated by the fddi_gen process and passed to fddi_mac_v4 process. These frames are encapsulated in the “info” field of the fddi_mac_fr frames that travel on the FDDI ring. |
| fddi_mac_fr | Used for frames formed by the fddi_mac_v4 process. These frames are passed between MAC modules on the FDDI ring. |
| fddi_mac_tk | Used to represent a token that circulates on the FDDI ring. |
ICI Formats: FDDI
The following table lists the interface control information (ICI) formats used in the FDDI model suite.
Table 51: FDDI ICI Formats
| name | description |
|---|---|
| fddi_mac_ind | Specifies the source and destination addresses passed by the MAC module to the Higher Layer module. |
| fddi_mac_req | Control information passed by the Higher Layer module to the MAC module when transmission requests are generated. |
FDDI Addressing and Ring Identifiers
Each ring has a unique identifier, specified by the ring_id attribute of the fddi3_mac process model. All FDDI 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 fddi3_mac process model. FDDI 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.