Exit Zen
110
../../protocols/ethernet.rst:373
English
Port state
0/100 · 10
111
../../protocols/ethernet.rst:373
English
Receives BPDUs
0/140 · 14
112
../../protocols/ethernet.rst:373
English
Sends BPDU
0/100 · 10
113
../../protocols/ethernet.rst:373
English
Handles data frames
0/190 · 19
114
../../protocols/ethernet.rst:375
English
Blocked
0/100 · 7
115
../../protocols/ethernet.rst:375 • ../../protocols/ethernet.rst:376 • ../../protocols/ethernet.rst:376 • ../../protocols/ethernet.rst:377 • ../../protocols/ethernet.rst:377 • ../../protocols/ethernet.rst:377
English
yes
0/100 · 3
116
../../protocols/ethernet.rst:375 • ../../protocols/ethernet.rst:375 • ../../protocols/ethernet.rst:376
English
no
0/100 · 2
117
../../protocols/ethernet.rst:376
English
Root
0/100 · 4
118
../../protocols/ethernet.rst:377
English
Designated
0/100 · 10
119
../../protocols/ethernet.rst:382
English
To illustrate the operation of the `Spanning Tree Protocol`, let us consider the simple network topology in the figure below.
0/1250 · 125
120
../../protocols/ethernet.rst:389
English
A simple Spanning tree computed in a switched Ethernet network
0/620 · 62
121
../../protocols/ethernet.rst:391
English
Assume that `Switch4` is the first to boot. It sends its own `BPDU = <4,0,4,1>` (resp. `BPDU = <4,0,4,2>`) on port 1 (resp. port 2). When `Switch1` boots, it sends `BPDU = <1,0,1,1>`. This `BPDU` is received by `Switch4`, which updates its `BPDU` and root priority vector tables and computes a new `BPDU = <1,3,4,1>` (resp. `BPDU = <1,3,4,2>`) on port 1 (resp. port 2). Indeed, there is only one root priority vector and hence, it is the best one. Port 1 of `Switch4` becomes the `Root` port while its second port is still in the `Designated` state.
0/5490 · 549
122
../../protocols/ethernet.rst:393
English
Assume now that `Switch9` boots and immediately receives `Switch1` 's `BPDU` on port 1. `Switch9` computes its own `BPDU = <1,1,9,1>` (resp. `BPDU = <1,1,9,2>`) on port 1 (resp. port 2) and port 1 becomes the `Root` port of this switch. The `BPDU` is sent on port 2 of `Switch9` and reaches `Switch4`. `Switch4` compares the priority vectors. It notices that the last computed vector (i.e., `V[2] = <1,2,9,2,2>`) is better than `V[1] = <1,3,1,1,1>`. Thus, `Switch4`'s `BPDU` is recomputed and port 2 becomes the `Root` port of `Switch4`. `Switch4` compares its new `BPDU = <1,2,4,p>` with the last `BPDU` received on each port (except for the `Root` port). Port 1 becomes a `Blocked` port on `Switch4` because the `BPDU=<1,0,1,1>` received on this port is better.
0/7630 · 763
123
../../protocols/ethernet.rst:395
English
During the computation of the spanning tree, switches discard all received data frames, as at that time the network topology is not guaranteed to be loop-free. Once that topology has been stable for some time, the switches again start to use the MAC learning algorithm to forward data frames. Only the `Root` and `Designated` ports are used to forward data frames. Switches discard all the data frames received on their `Blocked` ports and never forward frames on these ports.
0/4760 · 476
124
../../protocols/ethernet.rst:397
English
Switches, ports and links can fail in a switched Ethernet network. When a failure occurs, the switches must be able to recompute the spanning tree to recover from the failure. The `Spanning Tree Protocol` relies on regular transmissions of the `BPDUs` to detect these failures. A `BPDU` contains two additional fields : the `Age` of the `BPDU` and the `Maximum Age`. The `Age` contains the amount of time that has passed since the root switch initially originated the `BPDU`. The root switch sends its `BPDU` with an `Age` of zero and each switch that computes its own `BPDU` increments its `Age` by one. The `Age` of the `BPDUs` stored on a switch's table is also incremented every second. A `BPDU` expires when its `Age` reaches the `Maximum Age`. When the network is stable, this does not happen as `BPDU` s are regularly sent by the `root` switch and downstream switches. However, if the `root` fails or the network becomes partitioned, `BPDU` will expire and switches will recompute their own `BPDU` and restart the `Spanning Tree Protocol`. Once a topology change has been detected, the forwarding of the data frames stops as the topology is not guaranteed to be loop-free. Additional details about the reaction to failures may be found in [IEEE802.1d]_.
0/12600 · 1260
125
../../protocols/ethernet.rst:402
English
Virtual LANs
0/120 · 12
126
../../protocols/ethernet.rst:404
English
Another important advantage of Ethernet switches is the ability to create Virtual Local Area Networks (VLANs). A virtual LAN can be defined as a `set of ports attached to one or more Ethernet switches`. A switch can support several VLANs and it runs one MAC learning algorithm for each Virtual LAN. When a switch receives a frame with an unknown or a multicast destination, it forwards it over all the ports that belong to the same Virtual LAN but not over the ports that belong to other Virtual LANs. Similarly, when a switch learns a source address on a port, it associates it to the Virtual LAN of this port and uses this information only when forwarding frames on this Virtual LAN.
0/6850 · 685
127
../../protocols/ethernet.rst:406
English
The figure below illustrates a switched Ethernet network with three Virtual LANs. `VLAN2` and `VLAN3` only require a local configuration of switch `S1`. Host `C` can exchange frames with host `D`, but not with hosts that are outside of its VLAN. `VLAN1` is more complex as there are ports of this VLAN on several switches. To support such VLANs, local configuration is not sufficient anymore. When a switch receives a frame from another switch, it must be able to determine the VLAN in which the frame originated to use the correct MAC table to forward the frame. This is done by assigning an identifier to each Virtual LAN and placing this identifier inside the headers of the frames that are exchanged between switches.
0/7210 · 721
128
../../protocols/ethernet.rst:413
English
Virtual Local Area Networks in a switched Ethernet network
0/580 · 58
129
../../protocols/ethernet.rst:415
English
IEEE defined in the [IEEE802.1q]_ standard a special header to encode the VLAN identifiers. This 32 bit header includes a 12 bit VLAN field that contains the VLAN identifier of each frame. The format of the [IEEE802.1q]_ header is described below.
0/2470 · 247