3Com 3C63311 Reference Guide - Page 236

Spanning Tree, Spanning Tree Bridge configuration Protocol Data Units BPDUs are received

Page 236 highlights

224 APPENDIX B: PATHBUILDER S330/S310 MODULE AND APPLICATION OVERVIEW Spanning Tree Spanning Tree (IEEE 802.1d) is a technique that detects loops in a network and logically blocks the redundant paths, ensuring that only one route exists between any two LANs. It eliminates the duplication of packets and provides fault tolerance for resilient networks. As the Spanning Tree is being constructed, bridges exchange information, which is transmitted in packets called Configuration Bridge Protocol Data Units (C-BPDUs). During this process, the Spanning Tree Algorithm and Protocol (STAP) module elects a root bridge in order to establish a stable spanning tree topology. The root bridge determines the spanning tree topology and controls which bridges block packets and which forward packets. Once the topology is stable, all STAP bridges listen for special "Hello" C-BPDUs transmitted from the root bridge at regular intervals (usually every two seconds). If a STAP bridge timer expires before receiving a "Hello" C-BPDU, it assumes that the root bridge, or a link between itself and the root bridge, has gone down. It then initiates a reconfiguration of the Spanning Tree. When a port goes down (for instance, when an ATM VC is deleted), the port card notifies the STAP module of such a change. The STAP module then reinitiates the process of electing a root bridge, and the Spanning Tree calculation process begins all over again. Spanning Tree Operation The Spanning Tree operates as follows: For more detailed information about how the Spanning Tree operates, see IEEE802.1d. n An STAP module runs as a task on the management card. This task is responsible for maintaining all data structures for Spanning Tree operation for all ports and for sending/receiving Spanning Tree configuration packets. n Spanning Tree Bridge configuration Protocol Data Units (BPDUs) are received at Ethernet port cards (on Ethernet and ATM ports) and are sent to the STAP module on the management card. n The management card STAP module examines the packet, reads the MAC address of the sender, and analyzes the costs reported by the sender. n When state of a port changes, the STAP module notifies the port card of the change. n When a port card receives change information for a port, it updates the operational state of the port so as to change the bridging operation on the port. For instance, if a port in a forwarding state (normal operation mode of receiving and forwarding packets) is discovered to be forming a loop, it can be put in a blocking state. Once the port goes in the blocking state, the port card will stop receiving frames on the port.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262

224
A
PPENDIX
B: P
ATH
B
UILDER
S330/S310 M
ODULE
AND
A
PPLICATION
O
VERVIEW
Spanning Tree
Spanning Tree (IEEE 802.1d) is a technique that detects loops in a network and
logically blocks the redundant paths, ensuring that only one route exists between
any two LANs. It eliminates the duplication of packets and provides fault tolerance
for resilient networks.
As the Spanning Tree is being constructed, bridges exchange information, which is
transmitted in packets called Configuration Bridge Protocol Data Units (C-BPDUs).
During this process, the Spanning Tree Algorithm and Protocol (STAP) module
elects a root bridge in order to establish a stable spanning tree topology. The root
bridge determines the spanning tree topology and controls which bridges block
packets and which forward packets.
Once the topology is stable, all STAP bridges listen for special “Hello” C-BPDUs
transmitted from the root bridge at regular intervals (usually every two seconds). If
a STAP bridge timer expires before receiving a “Hello” C-BPDU, it assumes that the
root bridge, or a link between itself and the root bridge, has gone down. It then
initiates a reconfiguration of the Spanning Tree.
When a port goes down (for instance, when an ATM VC is deleted), the port card
notifies the STAP module of such a change. The STAP module then reinitiates the
process of electing a root bridge, and the Spanning Tree calculation process begins
all over again.
Spanning Tree Operation
The Spanning Tree operates as follows:
For more detailed information about how the Spanning Tree operates, see
IEEE802.1d.
n
An STAP module runs as a task on the management card. This task is
responsible for maintaining all data structures for Spanning Tree operation for
all ports and for sending/receiving Spanning Tree configuration packets.
n
Spanning Tree Bridge configuration Protocol Data Units (BPDUs) are received at
Ethernet port cards (on Ethernet and ATM ports) and are sent to the STAP
module on the management card.
n
The management card STAP module examines the packet, reads the MAC
address of the sender, and analyzes the costs reported by the sender.
n
When state of a port changes, the STAP module notifies the port card of the
change.
n
When a port card receives change information for a port, it updates the
operational state of the port so as to change the bridging operation on the
port. For instance, if a port in a forwarding state (normal operation mode of
receiving and forwarding packets) is discovered to be forming a loop, it can be
put in a blocking state. Once the port goes in the blocking state, the port card
will stop receiving frames on the port.