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

Unit ID Conflict Resolution, Automatic Unit ID Assignment - user manual

Page 26 highlights

Managing Device Information Managing Stacking 2 Unit ID as the switch being replaced. The newly inserted switch is identified by the Master unit by its Unit ID. Since the configuration of the original switch is also stored in the Master and Backup units by Unit ID, the new switch automatically receives the configuration of the old switch. This eliminates the need to configure the new switch and reduces the system downtime. The advantage of manual vs. automatic unit numbering is illustrated in the following example: A stack consists of Units 1,2,4,6,7. Unit 7 fails and an identical replacement unit is inserted. If the replacement unit is manually pre-set to be Unit 7, it can be inserted into the stack and inherit the configuration of the replaced (failing) Unit 7. However, if the replacement unit is not preset but is inserted in factory default mode (Unit 0), it is automatically renumbered to Unit 3 because that is the lowest available Unit ID in the stack. The new Unit 3 now inherits the previous unit 3 configuration. Otherwise, the system administrator must manually configure all the ports of the new Unit 3. Unit ID Conflict Resolution If two or more stacking members have the same valid Unit ID, the Master attempts to resolve the conflict by awarding the contested Unit ID to one of the units. For stacking members that are not granted the unit ID, the Stacking Master either: • Automatically resets the Unit ID to 0. The Stacking members become eligible to be reassigned another Unit ID by Automatic Unit ID Assignment. • The units are shut down. A unit that is automatically shut down remains powered on, but it is not operational, indicated by the solid red port Led. It is not a member of the stack and its connections are effectively disconnected from its immediate neighbors in the stack. If the stack is initially connected in a ring topology, the shutdown unit changes the topology into a chain. However, if the stack is initially configured in a chain topology, the shutdown unit breaks the chain. Depending on the particular configuration, may lead to other units being shut down. An automatically shut down unit remains shut down until the system administrator, manually renumbers the stacking member or removes the stacking member from the stack. A message is sent to the user that a unit failed to join the stack. The Master unit attempts to resolve Unit ID conflicts by applying the following rules: Cisco Small Business SFE/SGE Managed Switches Administration Guide 17

  • 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 Stacking
Cisco Small Business SFE/SGE Managed Switches Administration Guide
17
2
Unit ID as the switch being replaced. The newly inserted switch is identified by the
Master unit by its Unit ID. Since the configuration of the original switch is also
stored in the Master and Backup units by Unit ID, the new switch automatically
receives the configuration of the old switch. This eliminates the need to configure
the new switch and reduces the system downtime.
The advantage of manual vs. automatic unit numbering is illustrated in the
following example:
A stack consists of Units 1,2,4,6,7. Unit 7 fails and an identical replacement unit is
inserted. If the replacement unit is manually pre-set to be Unit 7, it can be inserted
into the stack and inherit the configuration of the replaced (failing) Unit 7. However,
if the replacement unit is not preset but is inserted in factory default mode (Unit 0),
it is automatically renumbered to Unit 3 because that is the lowest available Unit ID
in the stack. The new Unit 3 now inherits the previous unit 3 configuration.
Otherwise, the system administrator must manually configure all the ports of the
new Unit 3.
Unit ID Conflict Resolution
If two or more stacking members have the same valid Unit ID, the Master attempts
to resolve the conflict by awarding the contested Unit ID to one of the units. For
stacking members that are not granted the unit ID,
the Stacking Master either:
Automatically resets the Unit ID to 0.
The Stacking members become eligible to
be reassigned another Unit ID by
Automatic Unit ID Assignment
.
The units are shut down. A unit that is automatically shut down remains
powered on, but it is not operational, indicated by the solid red port Led. It is
not a member of the stack and its connections are effectively disconnected
from its immediate neighbors in the stack. If the stack is initially connected in a
ring topology, the shutdown unit changes the topology into a chain. However, if
the stack is initially configured in a chain topology, the shutdown unit breaks the
chain. Depending on the particular configuration, may lead to other units being
shut down. An automatically shut down unit remains shut down until the system
administrator, manually renumbers the stacking member or removes the
stacking member from the stack. A message is sent to the user that a unit failed
to join the stack.
The Master unit attempts to resolve Unit ID conflicts by applying the following
rules: