Netgear GS748TS GS7xxTS User Manual - Page 47

Inserting a Stacking Member, Exchanging Stacking Members

Page 47 highlights

GS700TS Smart Switch Software Administration Manual to a topology failure, the stacking member is no longer connected to the stack. The device can be booted, but it cannot be managed through the Stacking Master. The network manager can either reset the device defaults, or correct the topology failure, and then reconnect the unit to the stack. Configuration files are changed only through explicit user configuration. Configuration files are not automatically modified when: • Units are added • Units are removed • Units are reassigned Unit Numbers • Units toggle between Stacking Mode and Standalone Mode Each time the system reboots, the Startup Configuration file in the Master unit is used to configure the stack. If a stack member is removed from the stack, and then replaced with a unit with the same Unit No., the stack member is configured with the original device configuration. Only ports that are physically present are displayed in the GS700TS web screens, and can be configured through the web management system. By default, Unit Numbers are assigned automatically. However, you can use the browser to assign a specific Unit No.; for example, the same Unit No. as the unit which was recently removed. Inserting a Stacking Member When a stacking member is inserted into a running stack, it is automatically assigned a unit number. Note that a unit should not be powered up until it has been connected to the stack. If the user has already configured a Unit No. for the new unit, a Unit No. is not assigned automatically by the system. Exchanging Stacking Members If a stack member with the same Unit No. replaces an existing Unit No. with the same Unit No., the previous device configuration is applied to the inserted stack member. If the new inserted device has either more than or less ports than the previous device, the relevant port configuration is applied to the new stack member. Managing System Settings v1.0, June 2009 3-12

  • 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

GS700TS Smart Switch Software Administration Manual
Managing System Settings
3-12
v1.0, June 2009
to a topology failure, the stacking member is no longer connected to the stack. The device can be
booted, but it cannot be managed through the Stacking Master. The network manager can either
reset the device defaults, or correct the topology failure, and then reconnect the unit to the stack.
Configuration files are changed only through explicit user configuration. Configuration files are
not automatically modified when:
Units are added
Units are removed
Units are reassigned Unit Numbers
Units toggle between Stacking Mode and Standalone Mode
Each time the system reboots, the Startup Configuration file in the Master unit is used to configure
the stack. If a stack member is removed from the stack, and then replaced with a unit with the same
Unit No., the stack member is configured with the original device configuration. Only ports that
are physically present are displayed in the GS700TS web screens, and can be configured through
the web management system. By default, Unit Numbers are assigned automatically. However, you
can use the browser to assign a specific Unit No.; for example, the same Unit No. as the unit which
was recently removed.
Inserting a Stacking Member
When a stacking member is inserted into a running stack, it is automatically assigned a unit
number. Note that a unit should not be powered up until it has been connected to the stack. If the
user has already configured a Unit No. for the new unit, a Unit No. is not assigned automatically
by the system.
Exchanging Stacking Members
If a stack member with the same Unit No. replaces an existing Unit No. with the same Unit No.,
the previous device configuration is applied to the inserted stack member. If the new inserted
device has either more than or less ports than the previous device, the relevant port configuration is
applied to the new stack member.