Dell Force10 S2410-01-10GE-24P SFTOS Configuration Guide - Page 95

Copying SFTOS Software to a Member Switch

Page 95 highlights

For more on downloading SFTOS, see Downloading a Software Image on page 45 in the Getting Started chapter. See also the command syntax for the set of Dual Software Image Management commands in that section of the System Configuration Commands chapter in the SFTOS Command Reference. The purpose of the two "image" bins is to enable you to easily specify which image to invoke on the next reboot. You do that with the command boot system [unit] {image1 | image2} before executing the reload command. Note that it is possible to download new software into the bin currently occupied by the currently running version. The replacement would only take effect on the next reboot and only if you specified that bin with the boot system command. The reload [unit] command now provides selective rebooting of stack members. Combined with the ability in SFTOS 2.5.1 to select which software image is invoked in a reboot, you have various options in choosing which software is launched in specific stack members. For example, you might choose to reboot a particular member without installing the new code copied to it. Copying SFTOS Software to a Member Switch As described above, downloading SFTOS software to the management switch automatically propagates that software to all stack members. In addition, with SFTOS 2.5.1, the copy command provides the following way to manually copy an image from the management switch to a selected stack member, typically one that does not yet have the software version set to be installed in the next reboot: copy {image1 | image2} unit://unit/{image1 | image2} For unit, enter a specific member number as an integer from 1 to 6. An asterisk (* ) indicates that the image should be copied to all members: unit://*/{image1 | image2} Note: This operation can take several minutes. T For more on copy command options, see Downloading and Uploading Files on page 44, above. Configuration example: Upgrading software on a new member switch In the following case, a switch has been moved into a stack after you have installed new software to the management unit and to the new member. You have installed the new software in the management unit but not yet in the new member. Notice, in Figure 5-62, that show switch reports Unit 2, but show stack does not, because all stack members are required to run the same code, and the software running in Unit 2 is not current: Stacking S-Series Switches | 95

  • 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

Stacking S-Series Switches
|
95
For more on downloading SFTOS, see
Downloading a Software Image on page 45
in the Getting Started
chapter
.
See also the command syntax for the set of Dual Software Image Management commands in that
section of the System Configuration Commands chapter in the
SFTOS Command Reference
.
The purpose of the two “image” bins is to enable you to easily specify which image to invoke on the next
reboot. You do that with the command
boot system
[
unit
] {
image1
|
image2
} before executing the
reload
command.
Note that it is possible to download new software into the bin currently occupied by the currently running
version. The replacement would only take effect on the next reboot and only if you specified that bin with
the
boot system
command.
The
reload
[
unit
] command now provides selective rebooting of stack members. Combined with the ability
in SFTOS 2.5.1 to select which software image is invoked in a reboot, you have various options in
choosing which software is launched in specific stack members. For example, you might choose to reboot
a particular member without installing the new code copied to it.
Copying SFTOS Software to a Member Switch
As described above, downloading SFTOS software to the management switch automatically propagates
that software to all stack members. In addition, with SFTOS 2.5.1, the
copy
command provides the
following way to manually copy an image from the management switch to a selected stack member,
typically one that does not yet have the software version set to be installed in the next reboot:
copy
{
image1
|
image2
}
unit://
unit
/{
image1
|
image2
}
For
unit
, enter a specific member number as an integer from 1 to 6.
An asterisk (* ) indicates that the image should be copied to all members:
unit://*/
{
image1
|
image2
}
For more on
copy
command options, see
Downloading and Uploading Files on page 44
, above.
Configuration example: Upgrading software on a new member switch
In the following case, a switch has been moved into a stack after you have installed new software to the
management unit and to the new member. You have installed the new software in the management unit but
not yet in the new member.
Notice, in
Figure 5-62
, that
show switch
reports Unit 2, but
show stack
does not, because all stack
members are required to run the same code, and the software running in Unit 2 is not current:
T
Note:
This operation can take several minutes.