Upgrade ASR9k eXR 6.3.2 64bit

[ituskes]

Dear Support,

We upgrading IOSxr 64 bit 6.3.2 to 6.5.3.

We can not upgrade as the rootfs: has not enough free space.

As a workaround we removed some unecessary packages. (on an other router we had to remove necessary package as well)

After the upgrade we could add the packages again. (only the kernel (ISO) required the space)

It does not occure with other IOS XRs, neither during downgrade.

Is this issue related to 6.3.2 eXR?

It makes the upgrade a bit cumbersome...

Do you have other methode to overcome this issue?

[tkarnani]

can we check the filesystem to see where the space is used?

from xr vm

show media
run df

from admin

show install repository all
show media
run df /misc/disk1
run df -kh

[ituskes]

Dear,
I can not gather more output, I worked for one of our cutomer, and we found this workaround.
I just would like to ensure this is an issue with 6.3.2 and if there is any other/better solution.
I can check the termial logs for more details.

[ituskes]

[bng3:~]$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/vda1 3.8G 1.8G 1.8G 50% /
none 14G 170M 14G 2% /dev
none 14G 530M 13G 4% /dev/shm
none 14G 530M 13G 4% /dev/shm
run 14G 344K 14G 1% /run
run 14G 344K 14G 1% /run/netns
tmpfs 14G 0 14G 0% /var/volatile
tmpfs 14G 0 14G 0% /media/ram
tmpfs 64M 212K 64M 1% /tmp
/dev/vdc 5.5G 1.8G 3.4G 36% /misc/disk1
/dev/vdb1 469M 84M 350M 20% /var/log
/dev/vdb2 469M 2.2M 432M 1% /misc/config
/dev/vdb3 968M 25M 877M 3% /misc/scratch
none 512K 0 512K 0% /mnt
/dev/ram7 15M 15M 1.0K 100% /mnt/ram7
/dev/vdd 3.7G 7.5M 3.5G 1% /eusb
/dev/vde 2.4G 61M 2.2G 3% /misc/app_host
[bng3:~]$

1551652 /misc/disk1/XR653_x64/asr9k-mini-x64-6.5.3.iso
103952 /misc/disk1/XR653_x64/ASR9K-x64-iosxr-px-k9-6.5.3.tar
1655608 /misc/disk1/XR653_x64
24736 /misc/disk1/iedged_6099.by.11.20190331-234940.xr-vm_node0_RSP0_CPU0.7548f.core.gz
25264 /misc/disk1/iedged_653.by.11.20190331-234952.xr-vm_node0_RSP0_CPU0.7548f.core.gz
21404 /misc/disk1/cisco_support/PAM-asr9k-crash-xr_0_RSP0_CPU0-iedged-2019Mar31-235010.tgz
53400 /misc/disk1/cisco_support
25312 /misc/disk1/iedged_846.by.11.20190331-235004.xr-vm_node0_RSP0_CPU0.7548f.core.gz
13500 /misc/disk1/var/log/2019/03
13504 /misc/disk1/var/log/2019
13508 /misc/disk1/var/log
13512 /misc/disk1/var
25368 /misc/disk1/iedged_1652.by.11.20190331-235211.xr-vm_node0_RSP0_CPU0.7548f.core.gz
25288 /misc/disk1/iedged_744.by.11.20190331-234958.xr-vm_node0_RSP0_CPU0.7548f.core.gz
25204 /misc/disk1/iedged_563.by.11.20190331-234947.xr-vm_node0_RSP0_CPU0.7548f.core.gz
1875348 /misc/disk1


/dev/vdc 5.5G 1.8G 3.4G 36% /misc/disk1
8590 lrwxrwxrwx 1 11 Mar 22 09:23 harddisk: -> /misc/disk1



---- from other BNG ----
RP/0/RSP0/CPU0:bng4#sh install repository | utility sort

Thu Apr 4 08:21:28.803 UTC
asr9k-bng-x64-1.0.0.0-r632.x86_64
asr9k-bng-x64-1.0.0.0-r653.x86_64
asr9k-isis-x64-1.1.0.0-r653.x86_64
asr9k-isis-x64-1.2.0.0-r632.x86_64
asr9k-k9sec-x64-2.1.0.0-r653.x86_64
asr9k-k9sec-x64-3.1.0.0-r632.x86_64
asr9k-li-x64-1.1.0.0-r632.x86_64
asr9k-li-x64-1.1.0.0-r653.x86_64
asr9k-m2m-x64-2.0.0.0-r632.x86_64
asr9k-m2m-x64-2.0.0.0-r653.x86_64
asr9k-mcast-x64-2.0.0.0-r632.x86_64
asr9k-mcast-x64-2.0.0.0-r653.x86_64
asr9k-mgbl-x64-2.0.0.0-r653.x86_64
asr9k-mgbl-x64-3.0.0.0-r632.x86_64
asr9k-mini-x64-6.3.2
asr9k-mini-x64-6.5.3
asr9k-mpls-te-rsvp-x64-1.2.0.0-r632.x86_64
asr9k-mpls-te-rsvp-x64-2.1.0.0-r653.x86_64
asr9k-mpls-x64-2.0.0.0-r632.x86_64
asr9k-mpls-x64-2.0.0.0-r653.x86_64
asr9k-optic-x64-1.0.0.0-r632.x86_64
asr9k-optic-x64-1.0.0.0-r653.x86_64
asr9k-xr-6.3.2
23 package(s) in XR repository:
RP/0/RSP0/CPU0:bng4#

[xr-escalation]

Can you please share show media from XR plane and calvados ?
And show install active summary when the upgrade failed ?

[ituskes]

Hello,

It is in the attachement, I belive.

Imre

[narvenka]

I see pretty much all packages in show install active. So just removing 3 packages unblocked you from install ?

What was there in show install inactive?

[ituskes]

RP/0/RSP0/CPU0:bng3#sh install inactive
Thu Apr 4 15:19:25.234 CEST 16 inactive package(s) found:
asr9k-mini-x64-6.5.3
asr9k-xr-6.5.3
asr9k-li-x64-1.1.0.0-r653
asr9k-mpls-x64-2.0.0.0-r653
asr9k-9000v-nV-x64-1.0.0.0-r632
asr9k-eigrp-x64-1.0.0.0-r632
asr9k-k9sec-x64-2.1.0.0-r653
asr9k-optic-x64-1.0.0.0-r653
asr9k-m2m-x64-2.0.0.0-r653
asr9k-mcast-x64-2.0.0.0-r632
asr9k-mgbl-x64-2.0.0.0-r653
asr9k-bng-x64-1.0.0.0-r653
asr9k-mcast-x64-2.0.0.0-r653
asr9k-isis-x64-1.1.0.0-r653
asr9k-mpls-te-rsvp-x64-2.1.0.0-r653
asr9k-ospf-x64-1.0.0.0-r632
RP/0/RSP0/CPU0:bng3#

[tkarnani]

Can we remove the inactive packages and try upgrading?

install remove inactive all

[ituskes]

I was not helped.
To deactivate packages already made space available on rootfs:.
But when upgraded from 6.4.x or downgraded 6.5.3 > 6.3.2, the rootfs: was not touched.