Model Features: Ethernet
The Ethernet MAC model provided with Riverbed Modeler implements the carrier sensing, collision detection, and retransmission mechanisms specified in the IEEE 802.3, IEEE 8-2.3u, and IEEE 802.3z Standard. Explicit modeling is performed for all features other than serialization of bit transfers to and from the physical layer. The following list itemizes the features provided in this model:
- FIFO processing of Transmission Requests
- Propagation Delay based on Distance Between Individual Stations
- Carrier Sensing from Physical Layer
- Collision Detection from Physical Layer
- Truncated Binary Exponential Backoff
- Transmission Attempt Limit of 16
- Interframe Gap Timing for Deference
- Jam Sequence Transmission after Collisions
- 802.3 Minimum and Maximum Frame Sizes
- Frame Bursting (1000BaseX Ethernet operating in half-duplex only)
- Full- and half-duplex transmissions
You can configure port-based VLANs on all generic bridge and switch models, and on any vendor-specific models that support this technology. Ethernet 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.
The Ethernet models also support Fast EtherChannel technology. This allows multiple Ethernet point-to-point links to be bundled into one logical full-duplex channel of up to 800 Mbps (for Fast Ethernet) or 8000 Mbps (for Gigabit Ethernet). You can use a Fast EtherChannel or Gigabit EtherChannel link in place of any regular Ethernet link (10BaseT, 100BaseT, or 1000BaseX). EtherChannel links support flow-based balancing of traffic, and are useful for upgrading bottleneck links in Ethernet LAN networks.
Note: You can only use EtherChannel links when Ethernet is running in full-duplex mode.
The Ethernet models can be deployed either in a bus (10Base2) or a hub (10BaseT, 100BaseT or fast ethernet, and 1000BaseX or gigabit ethernet) configuration. The following list itemizes the main differences between these two configurations:
- Connections from the MAC processes to the hub are via duplex point-to-point links, as opposed to a bus medium.
- Collision Detection in the hub configuration is handled by the hub, rather than individual MAC processes.
- Deference mechanism is handled by the hub, rather than a separate deference process.
- Ethernet hubs cannot be directly connected to one another. Instead, a bridge must be used to link two or more hubs together.