cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
148
Views
0
Helpful
0
Comments
skondala
Cisco Employee
Cisco Employee

RSP2 is limited to 1.9G of disk space if partitioned. If not partitioned one needs to do so, the instruction are listed in the

upgrade instructions for a given release. There are additional steps which can be taken to gain disk space for a successful 

upgrade.

There is a SMU required which will provide a re-partition utility. This is included with the following SMU for bug  CSCub41271.

re-partition is not service impacting.

Repartition SMU status - CSCub41271

4.2.0 Published

4.2.1 Published

4.2.3 Integrated within 4.2.3

4.1.x NO SMU available.

On 4.1.X to re-partition the disk

Type “run repart –d” command from the XR prompt cisco-support privileges are required.

Generally 4.1.x release should  have  enough disk space unless disk0 is loaded with many other files.

"run repart -d" command needs to be executed from a window with no timeout, otherwise you risk interruption if your telnet / console window closes on you.  Even if the script managed to keep running, you would be unable to see when it was complete.  If the script were interrupted by the window closing you could end up with the disks in an inconsistent state, such as being caught still in a mirrored state.

Available choices to conserve disk0: memory

===========================================

1) Remove the superseded SMUs on the release your on before upgrading.

   a) Identify the superseded SMUs

   b) Deactivate the superseded SMUs

   c) Remove the superseded SMUs

This step should give some relief.

2) Upgrade to target release first then install the SMUs for target release in a separate operation.

While its generally recommended that you install the SMUs as well as the target release together in one install operation for a situation like this, you might need to separate the steps.

   a) Upgrade to the target release without installing ANY SMUs, install commit

   b) Install remove the old release

   c) Install the SMUs for the new release that your running

3) Prebake an RSP with 4.2.3+ SMUs use it to upgrade, if downgrade is needed use existing RSP

   a) If a spare RSP is found, pre-bake the spare RSP with the target release and image in the lab

   b) Send the spare RSP to the site, remove old RSP with old image, use new RSP with new image+ SMUs.

4) Turboboot the system if all else fails. This process removes the old image from disk0, to make room for the new image. this process requires a long maintenance window and for the router to be in ROMMON for a period of time.

In the cases above FPD upgrade is needed, it's recommend that auto FPD is enabled.

Appendix I

Turboboot steps.

1. Clear the ROM Monitor environmental variables on all RSPs:

unset BOOT

unset TFTP_FILE

sync

Repeat for each RSP in the system

2. Clear BOOT_DEV_SEQ_OPER and MIRROR_ENABLE ROM Monitor environment variables to disable disk mirroring.

unset BOOT_DEV_SEQ_OPER

unset MIRROR_ENABLE (Make sure you enable mirroring after you are done loading the code, this is important.)

sync

3.Change the default behavior of RP in ROMMON to not reset in 30 minutes

Rommon> priv

Rommon> diswd <- Disable the CPU watchdog

4. On the RSP, set the environment variables that configure the Management Ethernet interface for use in ROM Monitor mode:

IP_ADDRESS=ip_address

IP_SUBNET_MASK=mask

DEFAULT_GATEWAY=ip_address

5. On the RSP, set the TFTP environment variables:

TFTP_VERBOSE=1

TFTP_RETRY_COUNT=4

TFTP_TIMEOUT=6000

TFTP_CHECKSUM=1

TFTP_SERVER=server_ip_addr

TFTP_MGMT_INTF=0

6. Set the Turboboot variables on the RSP:

TURBOBOOT=on,disk0:,format

sync

7. On the RSP, boot the vm image located on the TFTP server: (Works only with the VM image, not the TAR file)

boot tftp://server/directory/filename

8. During the boot process the image is copied first on to the memory(RAM) and is installed from memory(RAM). Once it is insalled from memory, it will copy the image back on to disk0: and reload the device. Wait till you get the message "SYSTEM CONFIGURATION COMPLETED"

After the operation completes you will need to add / activate / commit the additional packages for the release (mpls, mgbl, k9, etc) that are desired / needed but that this operation will not require a reload.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Quick Links