Linksys SGE2000 Cisco SGE2000, SGE2000P Gigabit Ethernet Switch Reference Guid - Page 35

Understanding Stacking Cable Failure, Inserting Too Many Units into a Stack - factory reset

Page 35 highlights

Chapter SGE2000/SGE2000P Gigabit Ethernet Switch Reference Guide 2 We recommend that when combining two stacks, you reset the switches in one stack to factory default mode and then add the switches as described in "Adding Units to a Running Stack" in the "Building Automatically-Configured Stacks" section. • If one of the merged stacks had neither a Stack Master unit nor a Backup Master unit, then units belonging to this group are inserted into the stack as described in "Replacing a Failed Member Stack Unit in an Operational Stack." The Master either connects the running units to the stack using the current Unit ID numbers or renumbers them. NOTE: Any time two stacks are combined into one stack, there is no way to maintain the configuration for both sets of switches. All dynamic information of the units that belong to the portion of the stack that was not re-elected to be the Stack Master is relearned. Understanding Stacking Cable Failure If the stacking connection cables fail and cause a stack split, the scenario described in "Merging Two Stacks" applies. This occurs only if the stack uses a chain topology. Single stacking cable failure will not cause a stack split if a ring topology is used. Inserting Too Many Units into a Stack If you try to insert too many units into a stack, when all units (existing and newly inserted) are powered on at the same time, the following occurs: 1. A Stack Master is elected following the Master Discovery and Master Election processes. 2. All other units are shut down. NOTE: Occasionally, due to a race condition during the boot process, some of the units might be connected and join the stack. When a running group of units is added to an existing stack and each one of the stack groups has an elected Stack Master, and the total of existing units and inserted units exceeds the maximum allowed number of units (8) in a stack: • The Master Detection and Master Election processes determine the Stack Master out of one of the two combined stacking groups. • When switches are added to a running stack, the Unit ID Allocation and Duplicate ID conflict resolution processes detect an error if too many switches are present in the stack, and no changes are made to units that originally belonged to the group managed by the newly-elected Stack Master. The original switches retain their ID assignments and configurations. The units that originally belonged to the group managed by the Stack Master that lost its "mastership" are shut down. Chapter 2: Managing Device Information 27 Stack Troubleshooting and Maintenance

  • 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

27
Chapter 2: Managing Device Information
Stack Troubleshooting and Maintenance
SGE2000/SGE2000P Gigabit Ethernet Switch Reference Guide
Chapter
2
We recommend that when combining two stacks, you reset the switches in one stack to factory default
mode and then add the switches as described in “Adding Units to a Running Stack” in the “Building
Automatically-Configured Stacks” section.
If one of the merged stacks had neither a Stack Master unit nor a Backup Master unit, then units
belonging to this group are inserted into the stack as described in “Replacing a Failed Member
Stack Unit in an Operational Stack.”
The Master either connects the running units to the stack
using the current Unit ID numbers or renumbers them.
Understanding Stacking Cable Failure
If the stacking connection cables fail and cause a stack split, the scenario described in “Merging Two
Stacks” applies. This occurs only if the stack uses a chain topology. Single stacking cable failure will not
cause a stack split if a ring topology is used.
Inserting Too Many Units into a Stack
If you try to insert too many units into a stack, when all units (existing and newly inserted) are powered
on at the same time, the following occurs:
1.
A Stack Master is elected following the Master Discovery and Master Election processes.
2.
All other units are shut down.
When a running group of units is added to an existing stack and each one of the stack groups has an
elected Stack Master, and the total of existing units and inserted units exceeds the maximum allowed
number of units (8) in a stack:
The Master Detection and Master Election processes determine the Stack Master out of one of
the two combined stacking groups.
When switches are added to a running stack, the Unit ID Allocation and Duplicate ID conflict
resolution processes detect an error if too many switches are present in the stack, and no changes
are made to units that originally belonged to the group managed by the newly-elected Stack
Master. The original switches retain their ID assignments and configurations. The units that
originally belonged to the group managed by the Stack Master that lost its “mastership” are shut
down.
NOTE:
Any time two stacks are combined into one stack,
there is no way to maintain the configuration for both sets of
switches. All dynamic information of the units that belong
to the portion of the stack that was not re-elected to be the
Stack Master is relearned.
NOTE:
Occasionally, due to a race condition during the
boot process, some of the units might be connected and join
the stack.