Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

new IOS for cache 5005

we have a cache engine 500 series whose IOS got erased accidently.now i am trying to load new IOS and i am not sure about the procedure.

Please guide

4 REPLIES
Silver

Re: new IOS for cache 5005

Depending on the version of software you have the following URL's cover upgrading the switch:

http://www.cisco.com/warp/customer/117/content_engine/sonomaupgrade.html

http://www.cisco.com/warp/customer/117/mnl_upgrade_cdn_acns.html

New Member

Re: new IOS for cache 5005

thanks sir but i was not able to view these links as i dont have the proper authorisation.

i have backed up the IOS on the TFTP server and want to how to put it back on the cache engine again.

The steps are not same as for routers/access server.

please advice

Silver

Re: new IOS for cache 5005

The contents of the two URL's are icluded below, I hopw one of them is of some use to you:

http://www.cisco.com/warp/customer/117/content_engine/sonomaupgrade.html

Introduction

This document shows you how to upgrade a Cisco Content Engine 507 from CDN Software Enterprise Solution, Release 2.0 or earlier to 2.1 or later.

Step-by-step Procedure

Upgrade

If your Content Engine was part of your network, but the Content Distribution Manager (CDM) was upgraded without the Content Engine, the following instructions allow you to manually upgrade the software.

If your Content Engine has never been connected to the registry and the rest of your system runs release 2.1, please call the TAC for assistance.

Note: If your Content Engine had a MANUAL_UPGRADE channel with release 2.1 in it, go to steps 4-7 after doing the following:

cp /sonoma/state/cache/*image-name.upg.* /sonoma/state/ftp/export/cdn-enterprise-2.1.upg

Procedure

Turn on the Content Engine, and make sure you have a console connection.

Login to the console as root. The default password is default.

Stop the Sonoma software.

/etc/rc.d/rc2.d/K95sonomafs stop

Configure the Ethernet interface.

ifconfig eth0 ip-addr netmask mask broadcast bcast

route add 0.0.0.0/0 gw gateway-address

Clean and mount the filesystems.

fsck /sonoma/sys

fsck /sonoma/state

mount /sonoma/sys

mount /sonoma/state

Copy the upgrade image to /sonoma/state/ftp/export.

cd /sonoma/state/ftp/export

ftp ftpserver-address

binary

prompt

hash

get cdn-enterprise-2.1.upg

bye

Set the date.

date mmddhhmmyyyy (MonthDayHourMinuteYear)

Upgrade the software.

/sonoma/sys/bin/upgrade /sonoma/state/ftp/export/cdn-enterprise-2.1.upg

Reboot the Content Engine.

sync

reboot

Done.

--------------------------------------------------------------------------------

http://www.cisco.com/warp/public/117/content_engine/sonomaupgrade.html

Introduction

This document shows you how to upgrade a Cisco Content Engine 507 from CDN Software Enterprise Solution, Release 2.0 or earlier to 2.1 or later.

Step-by-step Procedure

Upgrade

If your Content Engine was part of your network, but the Content Distribution Manager (CDM) was upgraded without the Content Engine, the following instructions allow you to manually upgrade the software.

If your Content Engine has never been connected to the registry and the rest of your system runs release 2.1, please call the TAC for assistance.

Note: If your Content Engine had a MANUAL_UPGRADE channel with release 2.1 in it, go to steps 4-7 after doing the following:

cp /sonoma/state/cache/*image-name.upg.* /sonoma/state/ftp/export/cdn-enterprise-2.1.upg

Procedure

Turn on the Content Engine, and make sure you have a console connection.

Login to the console as root. The default password is default.

Stop the Sonoma software.

/etc/rc.d/rc2.d/K95sonomafs stop

Configure the Ethernet interface.

ifconfig eth0 ip-addr netmask mask broadcast bcast

route add 0.0.0.0/0 gw gateway-address

Clean and mount the filesystems.

fsck /sonoma/sys

fsck /sonoma/state

mount /sonoma/sys

mount /sonoma/state

Copy the upgrade image to /sonoma/state/ftp/export.

cd /sonoma/state/ftp/export

ftp ftpserver-address

binary

prompt

hash

get cdn-enterprise-2.1.upg

bye

Set the date.

date mmddhhmmyyyy (MonthDayHourMinuteYear)

Upgrade the software.

/sonoma/sys/bin/upgrade /sonoma/state/ftp/export/cdn-enterprise-2.1.upg

Reboot the Content Engine.

sync

reboot

Done.

--------------------------------------------------------------------------------

Silver

Re: new IOS for cache 5005

Apologies I posted the content of same URL twice, here is the second one:

http://www.cisco.com/warp/customer/117/mnl_upgrade_cdn_acns.html

Introduction

This procedure is used to manually upgrade CDN Enterprise equipment from ECDN 2.X and 3.X to ACNS. The safe procedure for upgrading ECDN is by using the manual upgrade procedure as laid out in the ACNS documentation on CCO.

In some circumstances you may need to upgrade without having access to the GUI. In these cases follow this step-by-step procedure for either CDM or CE. If your Content Engine does not have a CDM available, or for some reason you received a CE5?0-CDN when you should have received a CE5?0, you will want to use this procedure.

If your CDM failed to upgrade, and the HTTP process will not allow the use of the GUI to perform the upgrade, you will want to use this procedure.

Prerequisites

Readers of this document should be familiar with the following:

Basic Unix/Linux

ECDN

ACNS

Components Used

This process has been tested with:

CE560-CDN CDN software 3.0.3rc4

CE560-CDN CDN software 3.0.2rc10

Going to:

ACNS 4.1.1

This procedure will work with the following hardware:

CE-507-CDN

CE-560-CDN

CE-590-CDN

CDM-4650

CDM-4630

This procedure will work with the following software:

2.1.X ECDN

3.X ECDN

Step-by-Step Instructions

The procedure for the upgrade is below. Each step must be followed or the upgrade will fail. Please allow 30-60 minutes to complete.

Connect your Content Engine's ethernet interface to a network.

Turn on the Content Engine, and make sure you have a console connection.

Login to the console as root. The default password is default.

Stop the Sonoma software.

/etc/rc.d/rc2.d/K95sonomafs stop

Configure the Ethernet interface.

ifconfig eth0 ip-addr netmask mask broadcast bcast

route add 0.0.0.0/0 gw gateway-address

Clean and mount the filesystems.

fsck /sonoma/dist

fsck /sonoma/state

mount /sonoma/dist

mount /sonoma/state

Copy the upgrade image to /sonoma/state/ftp/export. And verify file integrity

cd /sonoma/state/ftp/export

ftp ftpserver-address

binary

prompt

hash

get ecdn-acns.upg

bye

spdist -t ecdn-acns.upg

Type:

sync

reboot

login again using the root username and password default

Set the date.

date mmddhhmmyyyy (MonthDayHourMinuteYear)

Indicate we are doing an upgrade.

touch /tmp/manual-upgrade

Upgrade the software.

/sonoma/sys/bin/upgrade /sonoma/state/ftp/export/ecdn-acns.upg

Note: There will be some error messages if upgrading from 2.x software, but not from 3.0.x software. Your output may appear to be similar to the following:

upg-ruby-install: Start upgrade to ruby installation

Run preinstall to install wmt packagepreinstall...

and next you should see the lines:

upg-ruby-move: Total free space: 14174164, required: 7340032

upg-ruby-setupflashdevice.sh: Done setting up flash device.

Added linux

Added ruby *

Reboot the Content Engine.

Important Note: It is very important not to disturb the CE during this reboot, and allow lots of time for it to finish. This is where most of the critical upgrade process occurs.

sync

reboot

You will see the bootup which should include:

Cisco CE Booting From Flash.

LI

LILLOO bboooott::

LLooaaddiinngg rruubbyy..................................

and then the login prompt for "Cisco Content Delivery Network..."

and more messages, followed by a "." every few seconds....

CAUTION: DO NOT DISTURB THIS PROCESS.

After about 20-minutes, this should be done.

When you are presented with a prompt:

Cisco Content Engine Console

Username:

you will know that you are finished.

Now that you have a ACNS 4.0.1 box, you will want to adjust the partition sizes by following the instructions in Configuring and Maintaining Disk Storage.

--------------------------------------------------------------------------------

120
Views
0
Helpful
4
Replies
CreatePlease to create content