cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2096
Views
0
Helpful
5
Replies

ASR9K 5.3.3 version failed to Upgrade ISM FPD

rendy.nugroho
Level 1
Level 1

Hi All,

 

I'm having an issue on my ASR9K 5.3.3 version. I've just upgrade the RSP linecard from 4.3.2 to 5.3.3 version. I have ISM running on my 4.3.2 version. When I insert the RSP linecard with the 5.3.3 version and do the FPD auto upgrade, I found that one of my ISM FPD which is fpga2 not upgraded yet. 

 

image.png

So I decided to upgrade it with the manual method, but I got this error message:

RP/0/RSP0/CPU0:CGR-IGW-02(admin)#upgrade hw-module fpd fpga2 location 0/2/CPU0
Fri Nov 17 02:19:29.366 WIB

***** UPGRADE WARNING MESSAGE: *****
* This upgrade operation has a maximum timout of 160 minutes. *
* If you are executing the cmd for one specific location and *
* card in that location reloads or goes down for some reason *
* you can press CTRL-C to get back the RP's prompt. *
* If you are executing the cmd for _all_ locations and a node *
* reloads or is down please allow other nodes to finish the *
* upgrade process before pressing CTRL-C. *

% RELOAD REMINDER:
- The upgrade operation of the target module will not interrupt its normal
operation. However, for the changes to take effect, the target module
will need to be manually reloaded after the upgrade operation. This can
be accomplished with the use of "hw-module <target> reload" command.
- If automatic reload operation is desired after the upgrade, please use
the "reload" option at the end of the upgrade command.
- The output of "show hw-module fpd location" command will not display
correct version information after the upgrade if the target module is
not reloaded.
NOTE: Chassis CLI will not be accessible while upgrade is in progress.
Continue? [confirm]


FPD upgrade in progress on some hardware, reload/configuration change
on those is not recommended as it might cause HW programming failure
and result in RMA of the hardware.


Starting the upgrade/download of following FPD:
=========== ==== ======= ======= =========== =========
Current Upg/Dng
Location Type Subtype Upg/Dng Version Version
=========== ==== ======= ======= =========== =========
0/2/CPU0 lc fpga2 upg 0.01 2.13
------------------------------------------------------
LC/0/2/CPU0:Nov 17 02:19:31.831 : linux_maint_fpd_agent[255]: %PLATFORM-FPD-2-MEM_ERR : fpd-err: Not enough disk space available to uncompress fpga image to /net/node0_RSP0_CPU0/disk1a:/fpd
FAILED to upgrade fpga2 for A9K-ISM-100 on location 0/2/CPU0 from 0.01 to 2.13
LC/0/2/CPU0:Nov 17 02:19:31.833 : lc_fpd_upgrade[252]: %PLATFORM-UPGRADE_FPD-3-OPERATION_FAILED : Failed to update FPD : FPD Programming action failed on this card


FPD upgrade has ended.

 

The message tell me that I didn't have enaough space in my disk1a: directory, which is when I check the disk1a: I only find this:

RP/0/RSP0/CPU0:CGR-IGW-02#dir disk1a:
Fri Nov 17 02:20:07.438 WIB

Directory of disk1a:

418 -r-- 25088 Thu Jan 1 07:03:12 1970 .bitmap
17 -r-- 8192 Thu Jan 1 07:03:12 1970 .inodes
18 -rw- 0 Thu Jan 1 07:03:12 1970 .boot
19 -rw- 0 Thu Jan 1 07:03:12 1970 .altboot
423 -r-- 0 Thu Jan 1 07:03:12 1970 .longfilenames
424 drwx 4096 Tue Nov 13 13:42:05 2012 LOST.DIR
425 -rw- 264 Fri Nov 17 01:49:00 2017 powerup_info.puf

102760448 bytes total (102709248 bytes free)

 

I also have been run the force method to upgrade the FPD but it doesn't work either, and I got the same messages. I need to upgrade the FPD due to the requirement before install the ISM Linux Install-Kit 5.3.3 version.

 

If you having the similiar problem and know how to solve it please put your comment below. Thank you

5 Replies 5

xr-escalation
Level 1
Level 1
Hey rendy.nugroho



This looks to me that your RSP disk1a don't have enough space to perform the activity.



Can you please check if there is enough memory in the harddiska? All you need is to clean the harddiska: and then try FPD operation.



Thanks

Nitin Pabbi (npabbi)


Hi Nitin,

 

As you can see there is 100mb free spaces of 100mb total in my disk1a:

418 -r-- 25088 Thu Jan 1 07:03:12 1970 .bitmap
17 -r-- 8192 Thu Jan 1 07:03:12 1970 .inodes
18 -rw- 0 Thu Jan 1 07:03:12 1970 .boot
19 -rw- 0 Thu Jan 1 07:03:12 1970 .altboot
423 -r-- 0 Thu Jan 1 07:03:12 1970 .longfilenames
424 drwx 4096 Tue Nov 13 13:42:05 2012 LOST.DIR
425 -rw- 264 Fri Nov 17 01:49:00 2017 powerup_info.puf

102760448 bytes total (102709248 bytes free) <<<<<

 

and also there is plenty of spaces in the harddiska:

RP/0/RSP0/CPU0:CGR-IGW-02#dir harddiska:
Wed Nov 22 10:23:02.098 WIB

Directory of harddiska:

61746 -r-- 3950076 Thu Jan 1 07:03:13 1970 .bitmap
17 -r-- 8192 Thu Jan 1 07:03:13 1970 .inodes
18 -rw- 0 Thu Jan 1 07:03:13 1970 .boot
19 -rw- 0 Thu Jan 1 07:03:13 1970 .altboot
61751 -r-- 0 Thu Jan 1 07:03:13 1970 .longfilenames
61752 drwx 4096 Tue Aug 27 01:35:42 2013 LOST.DIR
61809 -rw- 574 Tue Aug 27 01:35:31 2013 nvram.dump.0_RSP0_CPU0.new.gz

16179511296 bytes total (16175534592 bytes free) <<<<<<

 

Is there any spesific requirement spaces to upgrade this fpga2 on ISM module?

 

Thanks 

Hey Rendy,


Let me explain a bit here, Problem here is not from ISM but ISM is expecting uncompressed file from RP to perform the upgrade.
During upgrade process we use 2 mem..1 is for meta data and another for transient operations. Though both uses resources from phy memory.
when request for file initiated by system that time for uncompressed the files system tries to use transient memory for operatons.
Which needed minimum 300M for any basic operations and once the operations get complete than it release that temp memory.



I see in your case you have approx. 100m which is not sufficient. I would suggest you to remove inactive packages / protocol sessions ( which are idle BGP sesisons)/ remove log and temp files etc to release space.



Also it seems you have RSP 2G installed, I would suggest you to plan for HW upgrade to avoid such issues :)



Thanks

Nitin Pabbi (npabbi)


We are having the same problem upgrading the FPD on this A9K-ISM-100

Running A9K-RSP-4G with IOS 5.3.4

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

Location Type Subtype Upg/Dng Version Version
=========== ==== ======= ======= =========== =========
0/0/CPU0 lc fpga2 upg 0.01 2.13
------------------------------------------------------
No fpd on location 0/2/CPU0 need upgrade at this time.
FAILED to upgrade fpga2 for A9K-ISM-100 on location 0/0/CPU0 from 0.01 to 2.13
LC/0/0/CPU0:Mar 1 18:14:51.446 : linux_maint_fpd_agent[250]: %PLATFORM-FPD-2-MEM_ERR : fpd-err: Not enough disk space available to uncompress fpga image to /net/node0_RSP0_CPU0/disk1a:/fpd
LC/0/0/CPU0:Mar 1 18:14:51.448 : lc_fpd_upgrade[248]: %PLATFORM-UPGRADE_FPD-3-OPERATION_FAILED : Failed to update FPD : FPD Programming action failed on this card


FPD upgrade has ended.

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

Both disk1a and harddiska seem to be clean:

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

RP/0/RSP0/CPU0:ios(admin)#dir disk1a:
Thu Mar 1 18:18:28.411 UTC

Directory of disk1a:

410 -r-- 24576 Wed Jul 9 07:18:08 2014 .bitmap
17 -r-- 8192 Wed Jul 9 07:18:08 2014 .inodes
18 -rw- 0 Wed Jul 9 07:18:08 2014 .boot
19 -rw- 0 Wed Jul 9 07:18:08 2014 .altboot
415 drwx 4096 Thu Jul 10 04:35:20 2014 LOST.DIR
416 -r-- 0 Wed Jul 9 07:18:08 2014 .longfilenames
417 -rw- 264 Thu Mar 1 17:52:41 2018 powerup_info.puf

100663296 bytes total (100612608 bytes free)
RP/0/RSP0/CPU0:ios(admin)#dir harddiska:
Thu Mar 1 18:18:42.744 UTC

Directory of harddiska:

61746 -r-- 3950076 Thu Jan 1 00:02:46 1970 .bitmap
17 -r-- 8192 Thu Jan 1 00:02:46 1970 .inodes
18 -rw- 0 Thu Jan 1 00:02:46 1970 .boot
19 -rw- 0 Thu Jan 1 00:02:46 1970 .altboot
61751 -r-- 0 Thu Jan 1 00:02:46 1970 .longfilenames
61752 drwx 4096 Sun Apr 29 05:10:16 2012 LOST.DIR

16179511296 bytes total (16175535616 bytes free)
RP/0/RSP0/CPU0:ios(admin)#

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

Any guidance would be appreciated.

Thank you,

Michael.

 

Hi Michael,

 

There is a possibility that the issue above is caused by the RSP module problem (HW problem). Because when I used the different RSP but still use the same ISM, the FPD can be upgraded successfully. 

I proceed RMA for my RSP module (problem one), also this action has taken after me and my TAC engineer do the troubleshoot and suspect that there is a problem with the RSP module.

I think you should contact your Cisco TAC to ensure whether there is a problem with the hardware or not.

 

Hope it can help.

 

Thanks,

Rendi. 

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: