05-17-2016 02:11 PM
Hi Guys,
I have a ASR9010 with IOS XR 5.2.2 and we are wanting to upgrade it to 5.3.3. This is my first time doing this.
Due to limited disk space, its not enough to store 2 IOS XR, so I want to know what files are safe to delete in order to free up some space?
Also is it required to install the FPD package when doing an upgrade? asr9k-fpd-px.pie-5.3.3
Is it ok to remove SP or PX to free up space?
8186692 drwx 4096 Mon May 18 21:23:49 2015 asr9k-fpd-5.2.2
9502408 drwx 4096 Mon May 18 21:23:53 2015 asr9k-fpd-px-5.2.2
9502413 drwx 4096 Mon May 18 21:27:05 2015 asr9k-fwding-5.2.2.sp1-1.0.0
13197886 drwx 4096 Mon May 18 21:27:52 2015 asr9k-os-mbi-5.2.2.sp1-1.0.0
13197894 drwx 4096 Mon May 18 21:28:01 2015 iosxr-fwding-5.2.2.sp1-1.0.0
13910827 drwx 4096 Mon May 18 21:28:07 2015 iosxr-mpls-5.2.2.sp1-1.0.0
13910878 drwx 4096 Mon May 18 21:28:12 2015 asr9k-base-5.2.2.sp1-1.0.0
See below:
Default Profile:
SDRs:
Owner
Active Packages:
disk0:asr9k-fwding-5.2.2.sp1-1.0.0
disk0:asr9k-os-mbi-5.2.2.sp1-1.0.0
disk0:iosxr-fwding-5.2.2.sp1-1.0.0
disk0:iosxr-mpls-5.2.2.sp1-1.0.0
disk0:asr9k-base-5.2.2.sp1-1.0.0
disk0:asr9k-doc-px-5.2.2
disk0:asr9k-k9sec-px-5.2.2
disk0:asr9k-mini-px-5.2.2
disk0:asr9k-mpls-px-5.2.2
disk0:asr9k-fpd-px-5.2.2
disk0:asr9k-px-5.2.2.CSCut30136-1.0.0
Inactive Packages:
No packages.
Committed Packages:
disk0:asr9k-fwding-5.2.2.sp1-1.0.0
disk0:asr9k-os-mbi-5.2.2.sp1-1.0.0
disk0:iosxr-fwding-5.2.2.sp1-1.0.0
disk0:iosxr-mpls-5.2.2.sp1-1.0.0
disk0:asr9k-base-5.2.2.sp1-1.0.0
disk0:asr9k-doc-px-5.2.2
disk0:asr9k-k9sec-px-5.2.2
disk0:asr9k-mini-px-5.2.2
disk0:asr9k-mpls-px-5.2.2
disk0:asr9k-fpd-px-5.2.2
disk0:asr9k-px-5.2.2.CSCut30136-1.0.0
Superceded Packages:
No packages.
Wed May 18 09:08:06.489 NZST
Directory of disk0:
6298 -r-- 401404 Thu Jan 1 13:03:30 1970 .bitmap
17 -r-- 1875968 Thu Jan 1 13:03:30 1970 .inodes
18 -rw- 0 Thu Jan 1 13:03:30 1970 .boot
19 -rw- 0 Thu Jan 1 13:03:30 1970 .altboot
6303 -r-- 98304 Thu Jan 1 13:03:30 1970 .longfilenames
6304 drwx 4096 Tue Aug 9 08:24:50 2011 LOST.DIR
6305 drwx 4096 Sat Jan 2 21:12:34 2016 aaa
6306 drwx 4096 Sat Jan 2 21:13:05 2016 config
6307 drwx 4096 Sat Jan 2 21:13:45 2016 snmp
6308 drwx 4096 Sat Jan 2 21:13:46 2016 eem_rdsfs
14762832 drwx 4096 Mon May 18 20:52:34 2015 asr9K-doc-supp-5.2.2
6310 drwx 4096 Sat Jan 2 21:39:55 2016 instdb
1997954 drwx 4096 Mon May 18 20:52:36 2015 asr9k-doc-px-5.2.2
1997960 drwx 4096 Mon May 18 20:53:01 2015 iosxr-security-5.2.2
1998123 drwx 4096 Mon May 18 20:53:04 2015 asr9k-k9sec-supp-5.2.2
1998136 drwx 4096 Mon May 18 20:53:06 2015 asr9k-k9sec-px-5.2.2
1998144 drwx 4096 Mon May 18 21:05:33 2015 iosxr-infra-5.2.2
4670893 drwx 4096 Mon May 18 21:09:53 2015 iosxr-fwding-5.2.2
13337153 drwx 4096 Mon May 18 21:10:29 2015 iosxr-routing-5.2.2
13493696 drwx 4096 Mon May 18 21:10:32 2015 iosxr-diags-5.2.2
13493735 drwx 4096 Mon May 18 21:10:48 2015 iosxr-ce-5.2.2
13627099 drwx 4096 Mon May 18 21:11:21 2015 asr9k-os-mbi-5.2.2
13627107 drwx 4096 Fri May 22 01:06:45 2015 asr9k-base-5.2.2
20169134 drwx 4096 Mon May 18 21:14:57 2015 asr9k-fwding-5.2.2
33369 -rw- 126 Sat Jan 2 21:14:07 2016 sam_crldb
6324 drwx 4096 Sat Jan 2 21:12:54 2016 license
6325 -rw- 0 Tue Aug 9 08:50:14 2011 tar_report.txt
7600939 drwx 4096 Mon May 18 21:15:01 2015 asr9k-diags-supp-5.2.2
7600956 drwx 4096 Mon May 18 21:15:03 2015 asr9k-scfclient-5.2.2
7600961 drwx 4096 Mon May 18 21:15:20 2015 asr9k-cpp-5.2.2
7731738 drwx 4096 Mon May 18 21:15:25 2015 asr9k-ce-5.2.2
7854915 drwx 4096 Mon May 18 21:15:28 2015 asr9k-mini-px-5.2.2
7854943 drwx 4096 Mon May 18 21:17:25 2015 iosxr-mpls-5.2.2
8186687 drwx 4096 Mon May 18 21:17:29 2015 asr9k-mpls-px-5.2.2
8186692 drwx 4096 Mon May 18 21:23:49 2015 asr9k-fpd-5.2.2
9502408 drwx 4096 Mon May 18 21:23:53 2015 asr9k-fpd-px-5.2.2
9502413 drwx 4096 Mon May 18 21:27:05 2015 asr9k-fwding-5.2.2.sp1-1.0.0
13197886 drwx 4096 Mon May 18 21:27:52 2015 asr9k-os-mbi-5.2.2.sp1-1.0.0
13197894 drwx 4096 Mon May 18 21:28:01 2015 iosxr-fwding-5.2.2.sp1-1.0.0
13910827 drwx 4096 Mon May 18 21:28:07 2015 iosxr-mpls-5.2.2.sp1-1.0.0
13910878 drwx 4096 Mon May 18 21:28:12 2015 asr9k-base-5.2.2.sp1-1.0.0
6344 drwx 4096 Sat Jan 2 21:12:33 2016 onepk_cli_rdsfs
6345 drwx 4096 Fri May 22 01:08:00 2015 sla
6346 drwx 4096 Sat Jan 2 21:13:46 2016 sm_rdsfs
6347 drwx 4096 Fri May 22 01:10:03 2015 var
6348 drwx 4096 Fri May 22 01:10:03 2015 virtual-instance
21528140 drwx 4096 Wed Oct 7 11:33:16 2015 iosxr-infra-5.2.2.CSCut30136-1.0.0
13910992 drwx 4096 Wed Oct 7 11:33:19 2015 asr9k-px-5.2.2.CSCut30136-1.0.0
6351 drwx 4096 Sat Jan 2 21:13:47 2016 cepki
13911002 -rw- 10171 Sat Jan 2 21:14:07 2016 sam_certdb
5416099 drwx 4096 Thu Feb 13 21:53:29 2014 np
Solved! Go to Solution.
05-17-2016 03:14 PM
Deactivating SP will add additional time during the upgrade.
To avoid additional downtime we can do a re-partition of disk0: to free up 300MB of space. https://supportforums.cisco.com/discussion/12928502/asr9k-repartitioning-cscub41271-xr-432-xr-532 has more details on it.
fpd pie will be required to upgrade fpd of the hardwares. It is required during upgrade incase we have auto fpd upgrade enabled.
lets try re-partition first, with this the disk0: will have ~980 MB space available. With this we will not require deactivate any pies.
Thanks,
Santosh
05-17-2016 02:21 PM
How much is the free space available in disk0:.
You can try following steps:
1. Install deactivate 5.2.2.SP1 and disk0:asr9k-doc-px-5.2.2
2. install remove 5.2.2.SP1 and disk0:asr9k-doc-px-5.2.2
3. add 5.3.3 mini, mpls, k9sec, fpd pies
4. activate the 5.3.3 pies
5. install commit and remove 5.2.2 pies
6. Activate 5.3.3.SP1
Thanks,
Santosh
05-17-2016 02:26 PM
Hi Santosh,
Have about 685MB free space
6345 drwx 4096 Fri May 22 01:08:00 2015 sla
6346 drwx 4096 Sat Jan 2 21:13:46 2016 sm_rdsfs
6347 drwx 4096 Fri May 22 01:10:03 2015 var
6348 drwx 4096 Fri May 22 01:10:03 2015 virtual-instance
21528140 drwx 4096 Wed Oct 7 11:33:16 2015 iosxr-infra-5.2.2.CSCut30136-1.0.0
13910992 drwx 4096 Wed Oct 7 11:33:19 2015 asr9k-px-5.2.2.CSCut30136-1.0.0
6351 drwx 4096 Sat Jan 2 21:13:47 2016 cepki
13911002 -rw- 10171 Sat Jan 2 21:14:07 2016 sam_certdb
5416099 drwx 4096 Thu Feb 13 21:53:29 2014 np
1644150784 bytes total (685877760 bytes free)
I am looking to install the following 5.3.3:
asr9k-doc-px.pie-5.3.3
asr9k-fpd-px.pie-5.3.3
asr9k-k9sec-px.pie-5.3.3
asr9k-mini-px.pie-5.3.3
asr9k-mpls-px.pie-5.3.3
asr9k-optic-px.pie-5.3.3
*******
So is it safe to deactivate 5.2.2 SP and remove them? As I want to preload the 5.3.3 files on to the disk to save time during the change window.
Also is FPD-px Pie required to upgrade to 5.3.3?
Thanks
05-17-2016 03:14 PM
Deactivating SP will add additional time during the upgrade.
To avoid additional downtime we can do a re-partition of disk0: to free up 300MB of space. https://supportforums.cisco.com/discussion/12928502/asr9k-repartitioning-cscub41271-xr-432-xr-532 has more details on it.
fpd pie will be required to upgrade fpd of the hardwares. It is required during upgrade incase we have auto fpd upgrade enabled.
lets try re-partition first, with this the disk0: will have ~980 MB space available. With this we will not require deactivate any pies.
Thanks,
Santosh
05-17-2016 03:41 PM
Hi Santosh,
Thank you, I think I know what to do now.
Just one last question, with regards to deactivating the running 5.2.2 FPD PX mentioned from the above link.
So if I deactivate the 5.2.2 fpd px and remove the file which means i would have enough disk space for 5.3.3 (including 5.3.3 fpd px) .
Does that mean auto fpd upgrade still works to 5.3.3?
05-17-2016 03:47 PM
for auto-fpd upgrade we need both 5.2.2 fpd pie as well as 5.3.3 fpd pies.
05-17-2016 03:51 PM
Thank you for the response.
I think i will go with the deactivating and removing the 5.2.2 fpd-px route and upgrade to 5.3.3 fpd manually as repartitioning disk seems to have a lot of risk involve.
05-18-2016 06:54 PM
Hi Santosh,
I tried to turboboot a lab 9k from 4.2.3 to 5.2.2 and everything is working ok.
But the standby RSP is currently stuck in IOS XR PREP state?
Is that normal? Been like this for around 30-45 minutes already
Tried to console in and have the following log:
This (D)RP Node is not ready or active for login /configuration
Here is the show redundancy output from the active RSP:
Tue May 19 13:53:10.483 NZST
Redundancy information for node 0/RSP0/CPU0:
==========================================
Node 0/RSP0/CPU0 is in ACTIVE role
Node 0/RSP0/CPU0 has no valid partner
Group Primary Backup Status
--------- --------- --------- ---------
dsc 0/RSP0/CPU0 N/A Not Ready
dlrsc 0/RSP0/CPU0 N/A Not Ready
central-services 0/RSP0/CPU0 N/A Not Ready
v4-routing 0/RSP0/CPU0 N/A Not Ready
netmgmt 0/RSP0/CPU0 N/A Not Ready
mcast-routing 0/RSP0/CPU0 N/A Not Ready
v6-routing 0/RSP0/CPU0 N/A Not Ready
Process Group Details
---------------------
Current primary rmf state: Not Ready
<jid> <node> <name> <group> Reason for backup not ready
374 0/RSP0/CPU0 rmf_svr dsc No location for backup set
Not ready set Thu May 19 12:16:29 2016:
374 0/RSP0/CPU0 rmf_svr dlrsc No location for backup set
Not ready set Thu May 19 12:16:38 2016:
374 0/RSP0/CPU0 rmf_svr central-services No location for backup set
Not ready set Thu May 19 12:18:49 2016:
374 0/RSP0/CPU0 rmf_svr v4-routing No location for backup set
Not ready set Thu May 19 12:18:49 2016:
374 0/RSP0/CPU0 rmf_svr netmgmt No location for backup set
Not ready set Thu May 19 12:18:49 2016:
374 0/RSP0/CPU0 rmf_svr mcast-routing No location for backup set
Not ready set Thu May 19 12:18:49 2016:
374 0/RSP0/CPU0 rmf_svr v6-routing No location for backup set
Not ready set Thu May 19 12:18:49 2016:
Current primary rmf state for NSR: Ready
All backup not-ready NSR bits clear - backup should be NSR-ready
Reload and boot info
----------------------
A9K-RSP-4G reloaded Tue May 19 12:11:19 2015: 1 hour, 41 minutes ago
Active node booted Tue May 19 12:11:19 2015: 1 hour, 41 minutes ago
Active node reload "Cause: Turboboot completed successfully"
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide