Cisco CSS 11000 Series Content Services Switches

How to Manually Upgrade CSS 11000 Images Using a PC Without an FTP Server

Document ID: 22179

Updated: Feb 10, 2006



Cisco periodically releases new software versions for Cisco Content Service Switches (CSS). This document describes how to upgrade the CSS image on your PC or laptop if the PC or laptop does not have a File Transfer Protocol (FTP) server running on it.

If you do not have a FTP server running on your PC or laptop, you cannot configure a FTP record on the CSS to use the automatic upgrade script.

Before You Begin


For more information on document conventions, see the Cisco Technical Tips Conventions.


Before you can upgrade your CSS, make sure you have enough space on the box to complete the upgrade..

A hard-disk-based CSS can contain a maximum of four ArrowPoint Distribution Images (ADIs). A Flash disk-based CSS (CSS 11150 or CSS 11800) can contain a maximum of two ADIs. If the limit has been reached, you must remove one ADI version before you can add a new version.

To display the maximum number of installed versions allowed on your hard disk or Flash, perform the following steps:

  1. Issue the show installed-software version-limit command.

    (config)#show installed-software
  2. Access the boot mode by issuing the boot command.

    (config)# boot       
  3. Issue the remove command to delete an ADI.

    (config-boot)# remove ap0301006

    Note: Do not remove the ADI that is running on the CSS. Issue the version command to see which software version is running.

  4. Download the new CSS software to your PC from the Content Networking Software Center.

  5. Use your customer login and password to access the page. From this location, you can access the page that lists the versions of WebNS software in a compressed .gzip form.

  6. Click an image to download the image. Once the image is downloaded, you can start the manual upgrade.

    Note: You do not need to decompress the .gzip-compressed software. The CSS decompresses it.

Components Used

This document is not restricted to specific software and hardware versions.

The information presented in this document was created from devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If you are working in a live network, ensure that you understand the potential impact of any command before using it.

Step-by-Step Instructions

In this section, you are presented with the information to configure the features described in this document.

Copying New CSS Software from the PC to the CSS

  1. FTP into your CSS box from your PC.

  2. Change the transfer mode to bin.

  3. FTP the image into the CSS box by issuing the put command.

    put filename ../filename
  4. Give the file the same name on the CSS as you had on your PC when you downloaded it.

    Note: Make sure you use ../ to make sure that the image is copied to the c: directory.

Upgrading the CSS

  1. Unpack the file on the CSS by issuing the unpack command.

    CS100(config-boot)# unpack filename

    Note: The file can have either a.adi or .gz extension.

  2. Specify the new ADI as the primary boot file by issuing the primary boot-file command.

    CS100(config-boot)# primary boot-file filename
  3. Save the configuration by going into global configuration mode and issuing the save_config command. This copies the running configuration to the startup-config file, and also archives the startup-config file.

    CS100# save_config
  4. Reboot the CSS by issuing the reboot command.

    CS100# reboot


After you reboot, verify whether the new version loaded.

  1. Verify the version by issuing the version command.

    CSS-11050:# version  
    Version:               ap0410010 (4.10 Build 10)  
    Flash (Locked):        3.10 Build  33  
    Flash (Operational):   4.10 Build 10  
    Type:                  PRIMARY  
    Licensed Cmd Set(s):   Standard Feature Set
  2. Determine if the version is the one you upgraded to.

    Version: ap0410010 (4.10 Build 10)


There is currently no specific troubleshooting information available for this configuration.

Related Information

Updated: Feb 10, 2006
Document ID: 22179