Copying Sftos Software To A Member Switch; Configuration Example: Upgrading Software On A New Member Switch - Dell Force10 S2410-01-10GE-24P Configuration Manual

For more on downloading SFTOS, see
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
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 [ ] command now provides selective rebooting of stack members. Combined with the ability
reload
unit
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
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
For , enter a specific member number as an integer from 1 to 6.
unit
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

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
members are required to run the same code, and the software running in Unit 2 is not current:
Downloading a Software Image on page 45
boot system
/{ |
unit:// image1 image2
unit
}
Downloading and Uploading Files on page
show switch reports Unit 2, but
[ ] { |
image1 image2
unit
copy
}
show stack
in the Getting Started
} before executing the
command provides the
44, above.
does not, because all stack
Stacking S-Series Switches | 95
reload