Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
20584
Views
0
Helpful
22
Replies

ASR9006 upgrade IOS XR fail

nicolay1974
Level 1
Level 1

‎09-24-2013 03:18 AM

Hi

After upgrade ASR9006 from 4.2.0 to 4.3.2 the line card do not boot up properly.

I tryed to upgrade FPD on line card, but had not success. What i can do now?

RP/0/RSP0/CPU0:LAB-9k-440#sh plat
Tue Sep 24 17:53:20.083 UTC
Node            Type                      State            Config State
-----------------------------------------------------------------------------
0/RSP0/CPU0     A9K-RSP440-TR(Active)     IOS XR RUN       PWR,NSHUT,MON
0/0/CPU0        A9K-40GE-L                BRINGDOWN        PWR,NSHUT,MON
0/2/CPU0        A9K-MOD80-TR              IN-RESET         PWR,NSHUT,MON

RP/0/RSP0/CPU0:LAB-9k-440(admin)#upgrade hw-module fpd rommon location 0/0/CPU0

Tue Sep 24 17:57:56.274 UTC

***** 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]

1 person had this problem
Labels:
0 Helpful
22 Replies 22

rortizal
Cisco Employee
Cisco Employee
In response to smailmilak

‎04-14-2016 12:23 AM

yeap i want to upgread from the 5.1.3 to 5.3.3 but my files are in the harddisk 0/RSP1/CPU0 but i dont want to do switchover from the RSP0 to RSP1 u know  answer for this ??

regards

0 Helpful

smailmilak
Level 4
Level 4
In response to rortizal

‎04-14-2016 12:42 AM

Easiest way is to install add from FTP/TFTP server.

I tried to install from TAR once and never again. It takes just too long and you will also get packages that you don't need.

It's better to unzip the tar file and install add individual packages. 

Something like this.

admin ---> install add ftp://10.100.13.133/asr9k-mini-px.pie-4.3.4 ftp://10.100.13.133/asr9k-doc-px.pie-4.3.4 ftp://10.100.13.133/asr9k-fpd-px.pie-4.3.4

Check what packages are active with admin show install active summary and add the same packages. You should also deactivate packages that are not in use.

e.q. asr9k-mcast-px-5.1.3 if you do not use multicast.

You should also check this doc.
http://www.cisco.com/web/Cisco_IOS_XR_Software/pdf/ASR9k_Upgrade_Downgrade_Procedure_IOSXR_Rel_512.pdf

0 Helpful

rortizal
Cisco Employee
Cisco Employee
In response to smailmilak

‎04-14-2016 12:47 AM

i know the process from FTP/TFTP but i want to know if is possible install from the harddisk RSP1 from the RSP0 active. why? My TAR file its in harddisk of RSP1 but i dont know how to call this file in the command install add

regards

0 Helpful

Eddie Chami
Cisco Employee
Cisco Employee
In response to rortizal

‎04-14-2016 01:01 AM

Just sent you the steps on your post. Smail Milak is correct, its a little slow on 5.1.3, from 5.3.3 onwards with RSP440 and new gen RSPs, the install add of a TAR should take no more then a few mins, we improved the write speed by about 500%. You need to be on 533 though. 

Eddie.

0 Helpful

smailmilak
Level 4
Level 4
In response to rortizal

‎04-14-2016 01:02 AM

Well it looks like that you can not specify the location (RSP1) from where you want to install add the tar file.

0 Helpful

Eddie Chami
Cisco Employee
Cisco Employee
In response to smailmilak

‎04-14-2016 01:16 AM

Please see my previous post:

https://supportforums.cisco.com/discussion/12961376/upgrade-asr9k-533

Eddie.

0 Helpful

mivens
Level 1
Level 1
In response to smailmilak

‎04-14-2016 01:54 AM

The issue with the speed used to be that the file was transferred twice when doing an install add from a remote filesystem. Don't know if this is still the case with more recent releases.

The way I have always done it is to make my own tar file containing only the PIEs that I want then sftp it to harddisk:/ (only one transfer) then do the install add from the local filesystem. 

If you transfer in-band rather than via MgmtEther you can also greatly speed it up by increasing the LPTS policer limits.

0 Helpful

EA-6901000101
Level 1
Level 1
In response to nicolay1974

‎02-02-2018 10:48 AM

Hi Nicolay, I'm facing the same issues, in the show logs I saw similar messages, from your post I understood is requiered a SW Upgrade in the nodes, that's right?

 

RP/0/RSP1/CPU0:Feb  2 08:45:34.783 : canb-server[155]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/RSP0/CPU0 , WDOG SReset (0x06000000)
RP/0/RSP1/CPU0:Feb  2 08:45:50.789 : canb-server[155]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/RSP0/CPU0 , WDOG HReset (0x07000000)
RP/0/RSP1/CPU0:Feb  2 08:45:51.797 : canb-server[155]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/RSP0/CPU0 , WDOG Power Cycle (0x08000000)
RP/0/RSP1/CPU0:Feb  2 09:15:54.870 : canb-server[155]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/RSP0/CPU0 , WDOG SReset (0x06000000)
RP/0/RSP1/CPU0:Feb  2 09:16:10.875 : canb-server[155]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/RSP0/CPU0 , WDOG HReset (0x07000000)
RP/0/RSP1/CPU0:Feb  2 09:16:11.871 : canb-server[155]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/RSP0/CPU0 , WDOG Power Cycle (0x08000000)
RP/0/RSP1/CPU0:Feb  2 09:46:14.939 : canb-server[155]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/RSP0/CPU0 , WDOG SReset (0x06000000)
RP/0/RSP1/CPU0:Feb  2 09:46:30.993 : canb-server[155]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/RSP0/CPU0 , WDOG HReset (0x07000000)
RP/0/RSP1/CPU0:Feb  2 09:46:31.989 : canb-server[155]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/RSP0/CPU0 , WDOG Power Cycle (0x08000000)
RP/0/RSP1/CPU0:Feb  2 10:16:35.075 : canb-server[155]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/RSP0/CPU0 , WDOG SReset (0x06000000)
RP/0/RSP1/CPU0:Feb  2 10:16:51.056 : canb-server[155]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/RSP0/CPU0 , WDOG HReset (0x07000000)
RP/0/RSP1/CPU0:Feb  2 10:16:52.064 : canb-server[155]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/RSP0/CPU0 , WDOG Power Cycle (0x08000000)
RP/0/RSP1/CPU0:Feb  2 10:46:55.135 : canb-server[155]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/RSP0/CPU0 , WDOG SReset (0x06000000)
RP/0/RSP1/CPU0:Feb  2 10:47:11.141 : canb-server[155]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/RSP0/CPU0 , WDOG HReset (0x07000000)
RP/0/RSP1/CPU0:Feb  2 10:47:12.161 : canb-server[155]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/RSP0/CPU0 , WDOG Power Cycle (0x08000000)
RP/0/RSP1/CPU0:Feb  2 11:09:00.462 : shelfmgr[404]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 UNKNOWN state:UNPOWERED
RP/0/RSP1/CPU0:Feb  2 11:09:03.768 : shelfmgr[404]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-8X10GE state:POWER UP
LC/0/0/CPU0:Feb  2 11:09:04.590 : lda_server[65]: %L2-SPA-5-STATE_CHANGE : SPA in bay 0 type A9K-MPA-8x10GE Initing
RP/0/RSP1/CPU0:Feb  2 11:09:08.412 : shelfmgr[404]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/1 UNKNOWN state:UNPOWERED
RP/0/RSP1/CPU0:Feb  2 11:09:10.632 : shelfmgr[404]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-8X10GE state:INITIALIZED
RP/0/RSP1/CPU0:Feb  2 11:09:11.701 : shelfmgr[404]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/1 A9K-MPA-8X10GE state:POWER UP
RP/0/RSP1/CPU0:Feb  2 11:09:11.836 : invmgr[258]: %PLATFORM-INV-6-IF_OIRIN : xFP OIR: 0/0/0 port_num: 0 is inserted, state: 1
LC/0/0/CPU0:Feb  2 11:09:12.226 : lda_server[65]: %PLATFORM-UPGRADE_FPD-4-DOWN_REV : fpga8 instance 0 is down-rev (V1.05), upgrade to (V1.07). Use the "upgrade hw-module fpd" CLI in admin mode.
LC/0/0/CPU0:Feb  2 11:09:12.504 : lda_server[65]: %L2-SPA-5-STATE_CHANGE : SPA in bay 1 type A9K-MPA-8x10GE Initing
RP/0/RSP1/CPU0:Feb  2 11:09:13.432 : invmgr[258]: %PLATFORM-INV-6-IF_OIRIN : xFP OIR: 0/0/0 port_num: 1 is inserted, state: 1
RP/0/RSP1/CPU0:Feb  2 11:09:15.025 : invmgr[258]: %PLATFORM-INV-6-IF_OIRIN : xFP OIR: 0/0/0 port_num: 2 is inserted, state: 1
RP/0/RSP1/CPU0:Feb  2 11:09:16.285 : shelfmgr[404]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-8X10GE state:OK
RP/0/RSP1/CPU0:Feb  2 11:09:16.623 : invmgr[258]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/0, state: OK
RP/0/RSP1/CPU0:Feb  2 11:09:16.627 : invmgr[258]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/0/0 Sn: FOC2123NHSQ inserted
RP/0/RSP1/CPU0:Feb  2 11:09:16.632 : invmgr[258]: %PLATFORM-INV-6-IF_OIRIN : xFP OIR: 0/0/0 port_num: 3 is inserted, state: 1
LC/0/0/CPU0:Feb  2 11:09:16.877 : ifmgr[209]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/0/0, changed state to

0 Helpful
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:

Customers Also Viewed These Support Documents