D-Link DWS-3250 Product Manual - Page 73

Understanding the Stack Topology, Stacking Failover Topology, Stacking Members and Unit ID

Page 73 highlights

DXS/DWS 3200 Series User Guide Understanding the Stack Topology The 32XX series Stacked devices operate in a Ring topology. A stacked Ring topology is where all devices in the stack are connected to each other forming a circle. Each stacked device accepts data and sends it to the device to which it is physically connected. The packet continues through the stack until it reaches the destination port. The system automatically discovers the optimal path on which to send traffic. Figure 33: Stacking Ring Topology Most difficulties incurred in Ring topologies occur when a device in the ring becomes non-functional, or a link is severed. In a stack, the system automatically switches to a Stacking Failover topology without any system downtime. An SNMP message is automatically generated, but no stack management action is required. However, the stacking link or stacking member must be repaired to ensure the stacking integrity. After the stacking issues are resolved, the device can be reconnected to the stack without interruption, and the Ring topology is restored. Stacking Failover Topology If a failure occurs in the stacking topology, the stack reverts to Stacking Failover Topology. In the Stacking Failover topology, devices operate in a chain formation. The Stacking Master determines where the packets are sent. Each unit is connected to two neighboring devices, except for the top and bottom units. Stacking Members and Unit ID Stacking Unit IDs are essential to the stacking configuration. The stacking operation is determined during the boot process. The Operation Mode is determined by the Unit ID selected during the initialization process. For example, if the user selected stand-alone mode, the device boots as a stand-alone device. The device units are shipped with the default Unit ID of the stand-alone unit. If the device is operating as a standalone unit, all stacking LEDs are off. Once the user selects a different Unit ID, the default Unit ID not erased, and remains valid, even if the unit is reset. Unit ID 1 and Unit ID 2 are reserved for Master enabled units. Unit IDs 3 to 8 can be defined for stack members. When the Master unit boots or when inserting or removing a stack member, the Master unit initiates a stacking discovering process. Page 72

  • 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
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372

DXS/DWS 3200 Series User Guide
Page 72
Understanding the Stack Topology
The 32XX series Stacked devices operate in a Ring topology. A stacked Ring topology is where all devices in the
stack are connected to each other forming a circle. Each stacked device accepts data and sends it to the device to
which it is physically connected. The packet continues through the stack until it reaches the destination port. The
system automatically discovers the optimal path on which to send traffic.
Figure 33:
Stacking Ring Topology
Most difficulties incurred in Ring topologies occur when a device in the ring becomes non-functional, or a link is
severed. In a stack, the system automatically switches to a Stacking Failover topology without any system down-
time. An SNMP message is automatically generated, but no stack management action is required. However, the
stacking link or stacking member must be repaired to ensure the stacking integrity.
After the stacking issues are resolved, the device can be reconnected to the stack without interruption, and the
Ring topology is restored.
Stacking Failover Topology
If a failure occurs in the stacking topology, the stack reverts to Stacking Failover Topology. In the Stacking Failover
topology, devices operate in a chain formation. The Stacking Master determines where the packets are sent. Each
unit is connected to two neighboring devices, except for the top and bottom units.
Stacking Members and Unit ID
Stacking Unit IDs are essential to the stacking configuration. The stacking operation is determined during the boot
process. The Operation Mode is determined by the Unit ID selected during the initialization process. For example,
if the user selected stand-alone mode, the device boots as a stand-alone device.
The device units are shipped with the default Unit ID of the stand-alone unit. If the device is operating as a stand-
alone unit, all stacking LEDs are off. Once the user selects a different Unit ID, the default Unit ID not erased, and
remains valid, even if the unit is reset.
Unit ID 1 and Unit ID 2 are reserved for Master enabled units. Unit IDs 3 to 8 can be defined for stack members.
When the Master unit boots or when inserting or removing a stack member, the Master unit initiates a stacking dis-
covering process.