Field Notice: FN - 62765 - CRS: During Software Upgrade From Rel 3.2.x or 3.3.x to 3.4.x, The MSC Bootflash Can Become Full And The Upgrade Can Fail

Available Languages

Updated:April 10, 2007
Document ID:FN62765

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.


Revised April 10, 2007

April 6, 2007

NOTICE:

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.

Products Affected

Products Affected

CRS-16 and CRS-8 Platforms are affected

Problem Description

Following a software upgrade using the 'install add/activate' method, some MSCs will not boot-up correctly and will subsequently be stuck in a rebooting state. This happens when the MSC's bootflash gets full during the upgrade, as both the old and the new software images are retained on the bootflash at the same time.

Note: This issue will not be seen if an emergency recovery procedure, Turboboot, is used.

Background

The bootflash has limited space. Upgrading from Release 3.2.x or 3.3.x to 3.4.x can result in insufficient space on the bootflash. This will depend on the number of packages and SMUs present on the MSC.

Problem Symptoms

In the following example, MSCs in slot 0, 8 and 15 are in the IN-RESET state:

RP/0/RP0/CPU0:router#show platform 
Node Type PLIM State Config State 
----------------------------------------------------------------------------- 
0/0/CPU0 MSC 8-10GbE IN-RESET PWR,NSHUT,MON 
0/7/CPU0 MSC 8-10GbE IOS XR RUN PWR,NSHUT,MON 
0/8/CPU0 MSC 8-10GbE IN-RESET PWR,NSHUT,MON 
0/12/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON 
0/12/0 MSC(SPA) 8X1GE OK PWR,NSHUT,MON 
0/15/CPU0 MSC 8-10GbE IN-RESET PWR,NSHUT,MON 
0/RP0/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON 
0/RP1/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MON

This error message will be seen after attempting the software upgrade:

LC/0/8/CPU0:Mar 13 17:14:01.001 GMT0GMT,M3.5.0/: insthelper[60]: 
%INSTALL-INSTHELPER-3-EXIT_ERROR : Insthelper encountered a fatal error condition, and is exiting: Error value = 0xA2DF101C, Error string = ('Install Helper' detected the 'fatal' condition 'read()/write() failed': No space left on device)

Workaround/Solution

Solution:

Option 1)Apply SMU for DDTS CSCsi20380 (registered customers only)

As part of the .PIE upgrade process, during the reload this SMU will clear out the previously installed software release's packages. This assures that there is sufficient space on the MSC's bootflash to complete the software upgrade.

The SMU is activated as part of the .PIE upgrade procedure from 3.2.x or 3.3.x to 3.4.x as follows:

router(admin)#install add /comp-hfr-mini.pie-3.4.1 /hfr-mcast-p.pie-3.4.1 /hfr-mgbl-p.pie-3.4.1 /hfr-mpls.pie-3.4.1 /hfr-k9sec-p.pie-3.4.1 /hfr-diag-p.pie-3.4.1 /hfr-os-mbi-3.4.1.CSCsi20380.pie to disk0: sync 

router(admin)#install activate disk0:comp-hfr-mini-3.4.1 disk0:hfr-mcast-3.4.1 disk0:hfr-mgbl-3.4.1 disk0:hfr-k9sec-3.4.1 disk0:hfr-mpls-3.4.1 disk0:hfr-diag-3.4.1 disk0:hfr-os-mbi-3.4.1.CSCsi20380-1.0.0 sync

Option 2) If performing a .PIE upgrade from Rel 3.2.x or 3.3.x to 3.4.x, do not enable the diags and fpd .pie files as part of the upgrade to 3.4.x. This will provide sufficient bootflash space for the upgrade to proceed successfully. The diags and fpd packages can then be activated after the router reload has taken place and release 3.4.x is running. Additionally, if MPLS and / or MCAST packages are not being used, deactivate them from the running software using the command:

router(admin)#install deactivate disk0:hfr-mcast-3.2.x disk0:hfr-mpls-3.2.x

Note: With release 3.3, online diags configuration which is present in the admin-plane configuration will need to be removed before performing the upgrade.

How to Identify Free Space on the Bootflash

The free space on a MSC can be viewed using the command dir bootflash: location:

Examples:

  1. IOS-XR Rel 3.2.3 + SMUs

    Dir bootflash: location 0/1/CPU0 

Directory of net/node0_1_CPU0/bootflash: 

5767189 drwx 112 Fri Mar 23 05:10:41 2007 mbis 
14811181 drwx 108 Fri Mar 23 05:11:09 2007 hfr-os-mbi-3.2.3 
14811208 drwx 392 Fri Mar 23 05:11:10 2007 hfr-base-3.2.3 
10485801 drwx 388 Fri Mar 23 05:12:48 2007 hfr-admin-3.2.3 
10289302 drwx 352 Fri Mar 23 05:13:19 2007 hfr-fwdg-3.2.3 
9109572 drwx 456 Fri Mar 23 05:13:26 2007 hfr-lc-3.2.3 
14876767 drwx 284 Fri Mar 23 05:14:14 2007 hfr-mpls-3.2.3 
2818144 drwx 320 Fri Mar 23 05:14:18 2007 hfr-mcast-3.2.3 
3997707 drwx 108 Fri Mar 23 05:44:32 2007 hfr-diags-3.2.3 
3997740 drwx 44 Fri Mar 23 05:44:35 2007 instdb 
8126492 drwx 176 Fri Mar 23 09:41:40 2007 hfr-mpls-3.2.3.CSCsd83826-1.0.0 
8126567 drwx 244 Fri Mar 23 09:43:55 2007 hfr-mpls-3.2.3.CSCse00294-1.0.0 
14024778 drwx 176 Fri Mar 23 10:02:45 2007 hfr-admin-3.2.3.CSCek51590-1.0.0 
14024820 drwx 244 Fri Mar 23 10:02:47 2007 hfr-base-3.2.3.CSCeh52410-1.0.0 
13369396 drwx 108 Fri Mar 23 10:02:47 2007 hfr-mpls-3.2.3.CSCse76535-1.0.0 
10879033 drwx 280 Fri Mar 23 10:15:19 2007 hfr-base-3.2.3.CSCek61756-1.0.0 
11927679 drwx 144 Fri Mar 23 10:15:26 2007 hfr-os-mbi-3.2.3.CSCek61756-1.0.0 
14614580 drwx 208 Fri Mar 23 10:15:27 2007 hfr-os-mbi-3.2.3.CSCsd63325-1.0.0 
14614628 drwx 208 Fri Mar 23 10:15:28 2007 hfr-os-mbi-3.2.3.CSCsg63913-1.0.0 
7929888 drwx 108 Fri Mar 23 10:28:26 2007 hfr-mpls-3.2.3.CSCsg05919-1.0.0 
7929921 drwx 280 Fri Mar 23 10:31:07 2007 hfr-base-3.2.3.CSCei57651-1.0.0 
7930038 drwx 244 Fri Mar 23 10:37:12 2007 hfr-base-3.2.3.CSCek12027-1.0.0 
7536665 drwx 176 Fri Mar 23 10:40:21 2007 hfr-base-3.2.3.CSCek51590-1.0.0 
11075691 drwx 208 Fri Mar 23 10:43:16 2007 hfr-base-3.2.3.CSCsd10378-1.0.0 
7274503 drwx 176 Fri Mar 23 10:46:02 2007 hfr-base-3.2.3.CSCsd24398-1.0.0 
14090313 drwx 108 Fri Mar 23 10:49:32 2007 hfr-base-3.2.3.CSCsd68855-1.0.0 
14090346 drwx 244 Fri Mar 23 10:57:51 2007 hfr-base-3.2.3.CSCse12144-1.0.0 
14090456 drwx 208 Fri Mar 23 11:01:31 2007 hfr-admin-3.2.3.CSCsd79544-1.0.0 
393242 drwx 176 Fri Mar 23 11:06:19 2007 hfr-base-3.2.3.CSCsg41248-1.0.0 
13107274 drwx 244 Fri Mar 23 11:11:02 2007 hfr-base-3.2.3.CSCsg56756-1.0.0 
5832713 -rw- 95 Fri Mar 23 11:56:29 2007 mbi_image 

62390272 bytes total (28996608 bytes free) <<<

  2. .PIE upgrade to 3.4.1

    Dir bootflash: location 0/1/CPU0 

Directory of net/node0_1_CPU0/bootflash: 

14811181 drwx 108 Fri Mar 23 05:11:09 2007 hfr-os-mbi-3.2.3 
14811208 drwx 392 Fri Mar 23 05:11:10 2007 hfr-base-3.2.3 
10485801 drwx 388 Fri Mar 23 05:12:48 2007 hfr-admin-3.2.3 
10289302 drwx 352 Fri Mar 23 05:13:19 2007 hfr-fwdg-3.2.3 
9109572 drwx 456 Fri Mar 23 05:13:26 2007 hfr-lc-3.2.3 
14876767 drwx 284 Fri Mar 23 05:14:14 2007 hfr-mpls-3.2.3 
2818144 drwx 320 Fri Mar 23 05:14:18 2007 hfr-mcast-3.2.3 
3997707 drwx 108 Fri Mar 23 05:44:32 2007 hfr-diags-3.2.3 
3997740 drwx 44 Fri Mar 23 05:44:35 2007 instdb 
8126492 drwx 176 Fri Mar 23 09:41:40 2007 hfr-mpls-3.2.3.CSCsd83826-1.0.0 
8126567 drwx 244 Fri Mar 23 09:43:55 2007 hfr-mpls-3.2.3.CSCse00294-1.0.0 
14024778 drwx 176 Fri Mar 23 10:02:45 2007 hfr-admin-3.2.3.CSCek51590-1.0.0 
14024820 drwx 244 Fri Mar 23 10:02:47 2007 hfr-base-3.2.3.CSCeh52410-1.0.0 
13369396 drwx 108 Fri Mar 23 10:02:47 2007 hfr-mpls-3.2.3.CSCse76535-1.0.0 
10879033 drwx 280 Fri Mar 23 10:15:19 2007 hfr-base-3.2.3.CSCek61756-1.0.0 
11927679 drwx 144 Fri Mar 23 10:15:26 2007 hfr-os-mbi-3.2.3.CSCek61756-1.0.0 
14614580 drwx 208 Fri Mar 23 10:15:27 2007 hfr-os-mbi-3.2.3.CSCsd63325-1.0.0 
14614628 drwx 208 Fri Mar 23 10:15:28 2007 hfr-os-mbi-3.2.3.CSCsg63913-1.0.0 
7929888 drwx 108 Fri Mar 23 10:28:26 2007 hfr-mpls-3.2.3.CSCsg05919-1.0.0 
7929921 drwx 280 Fri Mar 23 10:31:07 2007 hfr-base-3.2.3.CSCei57651-1.0.0 
7930038 drwx 244 Fri Mar 23 10:37:12 2007 hfr-base-3.2.3.CSCek12027-1.0.0 
7536665 drwx 176 Fri Mar 23 10:40:21 2007 hfr-base-3.2.3.CSCek51590-1.0.0 
11075691 drwx 208 Fri Mar 23 10:43:16 2007 hfr-base-3.2.3.CSCsd10378-1.0.0 
7274503 drwx 176 Fri Mar 23 10:46:02 2007 hfr-base-3.2.3.CSCsd24398-1.0.0 
14090313 drwx 108 Fri Mar 23 10:49:32 2007 hfr-base-3.2.3.CSCsd68855-1.0.0 
14090346 drwx 244 Fri Mar 23 10:57:51 2007 hfr-base-3.2.3.CSCse12144-1.0.0 
14090456 drwx 208 Fri Mar 23 11:01:31 2007 hfr-admin-3.2.3.CSCsd79544-1.0.0 
393242 drwx 176 Fri Mar 23 11:06:19 2007 hfr-base-3.2.3.CSCsg41248-1.0.0 
13107274 drwx 244 Fri Mar 23 11:11:02 2007 hfr-base-3.2.3.CSCsg56756-1.0.0 
196610 -rw- 1 Fri Mar 23 12:04:19 2007 mbi_image 
6422531 drwx 388 Fri Mar 23 12:05:03 2007 hfr-admin-3.4.1 
4980795 drwx 424 Fri Mar 23 12:06:50 2007 hfr-base-3.4.1 
1310845 drwx 284 Fri Mar 23 12:10:36 2007 hfr-diags-3.4.1 
3932207 drwx 140 Fri Mar 23 12:10:40 2007 hfr-fpd-3.4.1 
3932329 drwx 140 Fri Mar 23 12:10:42 2007 hfr-os-mbi-3.4.1 
3932386 drwx 140 Fri Mar 23 12:10:45 2007 hfr-os-mbi-3.4.1.CSCsi20380-1.0.0 
1310736 drwx 388 Fri Mar 23 12:10:52 2007 hfr-fwdg-3.4.1 
10420295 drwx 460 Fri Mar 23 12:11:24 2007 hfr-lc-3.4.1 
14745609 drwx 136 Fri Mar 23 12:21:10 2007 hfr-mcast-3.4.1 

62390272 bytes total (139068 bytes free) <<<<

DDTS

To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.

DDTS

Description

CSCsi20380 (registered customers only)

When the MSC BootFlash is full, Software upgrades can fail.

Revision History

Revision

Date

Comment

1.1

10-APR-2007

Products affected: Changed comment to reflect CRS-16 & CRS-8 Platforms being affected (CRS-4 is not affected) / Problem Symptom: reworded 1st sentence In the following example the MSCs in slot 0, 8 and 15 are in the IN-RESET state: / Workaround: complete re-write

1.0

06-APR-2007

Initial Public Release

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco