White Paper

Here is another example showing how to update a FlexStack stack that has a mix of 2960-S and 2960-X models.

The same “archive download-sw” command is used. This time, two Cisco IOS Software images are identified on

the command line. Since the 2960-S runs a different Cisco IOS Software image from the 2960-X, two different

images are required. Even though two separate images are required, it is recommended that both images be on

the same release. Keeping members on the same release is important. In a mixed stack of 2960-S and 2960-X

members, if only one model type is updated, you run the risk at next stack reload of the stack not forming properly

because of “mismatch”.

C2960-48h# archive download-sw tftp://192.168.1.1/c2960s-universalk9-tar.150-

2.SE3 tftp://192.168.1.1/c2960x-universalk9-tar.150-2.SX

If a network connection is not possible, the stack can be upgraded by reading the image file(s) from a USB Flash

drive. A USB Flash drive must be inserted in the USB A slot on the front of the switch. The tar file containing the

Cisco Catalyst 2960-S or 2960-X Cisco IOS Software image must be on the Flash drive. The USB Flash drive is

referenced by the member into which it was inserted. If the USB Flash drive was inserted into member 2, then it will

be referenced as “usbflash2:.” Use the same download command used in the preceding example, except this time

point to the USB Flash instead of the TFTP server:

C2960-48# archive download-sw usbflash2:c2960s-universalk9-tar.150-2.SE3

usbflash2:c2960x-universalk9-tar.150-2.SX

The Cisco IOS Software CLI command “archive download-sw …” is very flexible and yet simple to use. It can

retrieve source images from multiple locations (for example, FTP, TFTP, Flash). The command allows for detailed

control of the upgrade process. For more information about the “archive download-sw” command, see the Cisco

Catalyst 2960-X software configuration guide on Cisco.com.

Preprovisioning Members

FlexStack allows for preprovisioning of future members. This allows the network administrator to configure Ethernet

interfaces for members that have yet to join. In those instances where the network administrator knows how certain

interfaces will be configured, the admin can do so in advance to ease the insertion of the new member into the

stack and into the network. This is useful when all interfaces that will connect to end users will have the same

configuration for every stack member. When new members are added to the stack, if they have been

preprovisioned, then it is not necessary for a network administrator to return to the stack and configure the new

interfaces.

As an example, the network administrator knows that interfaces 49 and 50 on a future member will be connecting

to another Ethernet switch and will be used as uplinks. Interfaces 1-48 will be connecting to end-user desktops.

The network administrator can make sure that VLANs will match the upstream switch by configuring the Ethernet

interfaces 49 and 50 for the proper VLAN membership. The network administrator preprovisions the member

number by matching the member number with a supported switch model. Ideally the admin would choose the next

available member number, but can choose any available member number.

This example shows how to add a fourth switch to an existing stack of three. The next available member number is

4 based on the output from “show switch.” After preprovisioning the member and matching the model, the admin

can configure interfaces Gi4/0/1-Gi4/0/48, Gi4/0/49, and Gi4/0/50. The following are the CLI commands to

implement this preprovisioning. After the switch has been preprovisioned, all interfaces on the future member can

be configured.