Linksys SGE2000 Cisco Small Business SFE/SGE2xxx Series Managed Switches Admin - Page 32

Managing Stacks, Stack Management

Page 32 highlights

Managing Device Information Managing Stacks 2 connection to the stack via the new Unit 4. The old Unit 4 and the new Unit 4 appear to the Master unit as two new, manually numbered units trying to simultaneously join the stack. Therefore, both units are shut down, and thus Units 6, 7 and 8 remain shut down. What happens if the replacement unit is inserted into the stack (in the same position as Unit 3) after first powering off all units and then simultaneously powering on all units? If all units in the stack are reset, the Master unit performs Topology Discovery during the software boot, revealing that there are two duplicate Unit IDs (old and new Unit 4). Since both units are manually numbered, both units are shut down by the Master unit. This, in turn, again leaves Units 6, 7 and 8 disconnected from the Master unit, thus shutting them down also. • A stack is initially configured in a chain topology as follows: Unit 8-Unit 5-Unit 1-Unit 3-Unit 4-Unit 6-Unit 7-Unit 2 Unit 1 is the Master and Unit 2 is the Backup. Unit 3 fails. What happens? The failure of Unit 3 disconnects Units 4, 6, 7 and 2 from the Master unit. Backup Unit 2 senses the loss of the Master and automatically becomes the Master of a stack comprised of Units 2, 4, 6 and 7. Unit 1 remains the Master of the now reduced stack, consisting of Units 1, 5 and 8. Thus the failure of Unit 3 has split the original stack into two smaller stacks. However, while the two stacks continue in operation, this situation may create problems on the network because Unit 2 and Unit 1 have the same Master configuration files. The significance of this is that both stacks share the same IP address, making network communication with either stack ambiguous. Managing Stacks The Stack Management Page allows network managers to configure stacking members on the device and determine to either reset the entire stack or a specific device. Device configuration changes that are not saved before the device is reset are not saved. If the Master unit is reset, the entire stack is reset. To open the Stack Management Page: Cisco Small Business SFE/SGE Managed Switches Administration Guide 23

  • 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
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410

Managing Device Information
Managing Stacks
Cisco Small Business SFE/SGE Managed Switches Administration Guide
23
2
connection to the stack via the new Unit 4. The old Unit 4 and the new Unit 4
appear to the Master unit as two new, manually numbered units trying to
simultaneously join the stack. Therefore, both units are shut down, and thus
Units 6, 7 and 8 remain shut down.
What happens if the replacement unit is inserted into the stack (in the same
position as Unit 3) after first powering off all units and then simultaneously
powering on all units?
If all units in the stack are reset, the Master unit performs Topology
Discovery during the software boot, revealing that there are two duplicate
Unit IDs (old and new Unit 4). Since both units are manually numbered, both
units are shut down by the Master unit. This, in turn, again leaves Units 6, 7
and 8 disconnected from the Master unit, thus shutting them down also.
A stack is initially configured in a chain topology as follows:
Unit 8—Unit 5—Unit 1—Unit 3—Unit 4—Unit 6—Unit 7—Unit 2
Unit 1 is the Master and Unit 2 is the Backup. Unit 3 fails. What happens?
The failure of Unit 3 disconnects Units 4, 6, 7 and 2 from the Master unit.
Backup Unit 2 senses the loss of the Master and automatically becomes the
Master of a stack comprised of Units 2, 4, 6 and 7. Unit 1 remains the Master
of the now reduced stack, consisting of Units 1, 5 and 8. Thus the failure of
Unit 3 has split the original stack into two smaller stacks. However, while the
two stacks continue in operation, this situation may create problems on the
network because Unit 2 and Unit 1 have the same Master configuration files.
The significance of this is that both stacks share the same IP address,
making network communication with either stack ambiguous.
Managing Stacks
The
Stack Management Page
allows network managers to configure stacking
members on the device and determine to either reset the entire stack or a specific
device. Device configuration changes that are not saved before the device is reset
are not saved. If the Master unit is reset, the entire stack is reset.
To open the
Stack Management Page
: