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

Stack Members, Master-Enabled Units, Unit ID Allocation, Managing Device Information - factory default

Page 24 highlights

Chapter 2 SGE2000/SGE2000P Gigabit Ethernet Switch Reference Guide The Stack Master stores a copy of the active configuration on the Backup Master. This copy is used only if the Backup Master assumes the role of Stack Master. NOTE: Only the configuration file is copied. Any dynamically-filled tables (for example, learned addresses) are not copied from the Stack Master to the Backup Master. If the Backup Master assumes the role of Stack Master, it builds its own dynamic tables. Stack Members The units assigned the Unit IDs 3 through 8 are called stack members. A stack member operates only as a member of the stack under the direction of an operational Stack Master (or a Backup Master that has assumed the Stack Master role). Stack members are not directly manageable and configurable, and must be managed through the Stack Master. They do not contain any meaningful configuration information, including their own configuration. If an operational Stack Master is not present and reachable, these units are not functional. Master-Enabled Units Units that are assigned a Unit ID number of 1 or 2 are called master-enabled units. Only master-enabled units participate in the Master Election process (see below) when they are initialized, are inserted into a new stack, or lose connectivity with the existing Stack Master. Only master-enabled units participate in the Master Election process and can become the Stack Master or Backup Master. (Units that are assigned a Unit ID of 3 through 8 can only become a Stack Master or a Backup Master if they are manually configured by the system administrator or if they are reset to the factory default mode.) Unit ID Allocation Units are shipped from the factory without an assigned Unit ID, and must be assigned a unique Unit ID before they can operate as part of a stack. Unit ID numbers are assigned to units in one of two ways: • Unit ID numbers are assigned by the system administrator, and can be changed only manually by the system administrator. • Unit ID numbers are allocated to a stack member unit by the Stack Master during system initialization. A unit that was assigned a Unit ID will usually keep this number even after it is rebooted. The Stack Master may reallocate Unit IDs during system initialization to resolve duplicate Unit ID conflicts (see below). Manually assigned Unit IDs cannot be changed by the Stack Master, even if there is a conflict. Unit ID assignment or change takes effect only during system initialization and does not take place during system runtime. Units of a stack do not have to be numbered in sequence, and can be interconnected as long as each unit has a unique ID and at least one unit of the stack serves as Stack Master. 16 Chapter 2: Managing Device Information Understanding Advanced Stacking

  • 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

16
Chapter 2: Managing Device Information
Understanding Advanced Stacking
SGE2000/SGE2000P Gigabit Ethernet Switch Reference Guide
Chapter
2
The Stack Master stores a copy of the active configuration on the Backup Master. This copy is used only
if the Backup Master assumes the role of Stack Master.
Stack Members
The units assigned the Unit IDs 3 through 8 are called stack members. A stack member operates only as
a member of the stack under the direction of an operational Stack Master (or a Backup Master that has
assumed the Stack Master role). Stack members are not directly manageable and configurable, and must
be managed through the Stack Master. They do not contain any meaningful configuration information,
including their own configuration. If an operational Stack Master is not present and reachable, these
units are not functional.
Master-Enabled Units
Units that are assigned a Unit ID number of 1 or 2 are called master-enabled units. Only master-enabled
units participate in the Master Election process (see below) when they are initialized, are inserted into a
new stack, or lose connectivity with the existing Stack Master. Only master-enabled units participate in
the Master Election process and can become the Stack Master or Backup Master. (Units that are assigned
a Unit ID of 3 through 8 can only become a Stack Master or a Backup Master if they are manually
configured by the system administrator or if they are reset to the factory default mode.)
Unit ID Allocation
Units are shipped from the factory without an assigned Unit ID, and must be assigned a unique Unit ID
before they can operate as part of a stack. Unit ID numbers are assigned to units in one of two ways:
Unit ID numbers are assigned by the system administrator, and can be changed only manually by
the system administrator.
Unit ID numbers are allocated to a stack member unit by the Stack Master during system
initialization.
A unit that was assigned a Unit ID will usually keep this number even after it is rebooted. The Stack
Master may reallocate Unit IDs during system initialization to resolve duplicate Unit ID conflicts (see
below). Manually assigned Unit IDs cannot be changed by the Stack Master, even if there is a conflict.
Unit ID assignment or change takes effect only during system initialization and does not take place
during system runtime. Units of a stack do not have to be numbered in sequence, and can be
interconnected as long as each unit has a unique ID and at least one unit of the stack serves as Stack
Master.
NOTE:
Only the configuration file is copied. Any
dynamically-filled tables (for example, learned addresses)
are not copied from the Stack Master to the Backup Master.
If the Backup Master assumes the role of Stack Master, it
builds its own dynamic tables.