Cisco SGE2000 Reference Guide - Page 23

Understanding Stack Resiliency, Understanding Advanced Stacking, Unit IDs, Stack Master - sge2000p manual

Page 23 highlights

Chapter SGE2000/SGE2000P Gigabit Ethernet Switch Reference Guide 2 3. Power the units on. After a short interval, they will become stack members, but will have automatically-assigned Unit IDs. Assign each such unit its desired Unit ID (using the Stack Management Interface through the console port, by Telnet, or by using the graphical user interface (GUI). 4. Reset the units to make this assignment permanent. NOTE: We recommended that if you manually assign a Unit ID to one unit, you manually assign Unit IDs to all units. Using a mix of both system-assigned and manuallyassigned IDs in your network can impact system performance. The unit that is assigned the Unit ID 1 is the Stack Master, and its front panel "MST" LED lights green. The unit assigned the Unit ID 2 is the Backup Master. Understanding Stack Resiliency Stacks can be configured in ring or chain topologies. We recommend configuring the stack in ring topology, due to the high resiliency in case of unit failure or stacking links failure. Additionally, if a redundant power supply is present, we recommend connecting the Stack Master and Backup Master units to the redundant power supply. Understanding Advanced Stacking To understand advanced stacking, you must understand Unit IDs and how they are allocated, and the stack unit startup process. Unit IDs Each unit in a stack has an assigned unique Unit ID number. The following sections describe the Unit IDs and their characteristics. Stack Master The unit assigned the Unit ID number 1 serves as the Stack Master. All other units are stack members. The Stack Master provides a single point of control, configuration and management for the entire stack, and stores the configuration for all stack members. (Members do not store any configuration information.) Stack Backup Master The unit assigned the Unit ID number 2 is a special stack member that serves as the stack Backup Master. A stack Backup Master assumes the role of Stack Master for the remaining stack members if the stack Master fails or is disconnected. Chapter 2: Managing Device Information 15 Understanding Stack Resiliency

  • 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

15
Chapter 2: Managing Device Information
Understanding Stack Resiliency
SGE2000/SGE2000P Gigabit Ethernet Switch Reference Guide
Chapter
2
3.
Power the units on. After a short interval, they will become stack members, but will have
automatically-assigned Unit IDs. Assign each such unit its desired Unit ID (using the Stack
Management Interface through the console port, by Telnet, or by using the graphical user interface
(GUI).
4.
Reset the units to make this assignment permanent.
The unit that is assigned the Unit ID 1 is the Stack Master, and its front panel “MST” LED lights green.
The unit assigned the Unit ID 2 is the Backup Master.
Understanding Stack Resiliency
Stacks can be configured in ring or chain topologies. We recommend configuring the stack in ring
topology, due to the high resiliency in case of unit failure or stacking links failure.
Additionally, if a redundant power supply is present, we recommend connecting the Stack Master and
Backup Master units to the redundant power supply.
Understanding Advanced Stacking
To understand advanced stacking, you must understand Unit IDs and how they are allocated, and the
stack unit startup process.
Unit IDs
Each unit in a stack has an assigned unique Unit ID number. The following sections describe the Unit
IDs and their characteristics.
Stack Master
The unit assigned the Unit ID number 1 serves as the Stack Master. All other units are stack members.
The Stack Master provides a single point of control, configuration and management for the entire stack,
and stores the configuration for all stack members. (Members do not store any configuration
information.)
Stack Backup Master
The unit assigned the Unit ID number 2 is a special stack member that serves as the stack Backup
Master. A stack Backup Master assumes the role of Stack Master for the remaining stack members if the
stack Master fails or is disconnected.
NOTE:
We recommended that if you manually assign a
Unit ID to one unit, you manually assign Unit IDs to all
units. Using a mix of both system-assigned and manually-
assigned IDs in your network can impact system
performance.