cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
496
Views
0
Helpful
1
Replies
DanLaden
Beginner

Cannot perform manual upgrade

I am looking to perform a manual upgrade as detailed in this document.  I am not using a USB drive but copying the file to the /bootflash folder via sftp.  ACI 3.2o. 
When i upload the 4.1 binary, i see my disk storage above 50%. A moment later, the file is gone. I am being impacted by a known bug. The work around is to delete files until
space is available. I do not want to delete the current os as I want to be able to recover if needed from loader. I can/did move the auto-s file to /tmp. The file was recreated
after a reboot. I dont know what will happen if i have the old and new os and the auto-s is recreated after reboot.

Anyone run into this before and what was your resolution.


TOTD: HOW DO YOU PERFORM A FIRMWARE UPGRADE ON SPINE SWITCHES WITHOUT AN APIC?

https://community.cisco.com/t5/data-center-documents/totd-how-do-you-perform-a-firmware-upgrade-on-spine-switches/ta-p/3162792

 

ACI switch upgrade fails due to /bootflash cleanup script when usage is >50%

CSCvg78578

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvg78578

Description

Symptom:
++ ACI Switch upgrade fails due to new image not being present on bootflash
++ File /mnt/pss/core_control.log indicates the new image being deleted due to Bootflash Usage is higher than 50%

Conditions:
++ new image being in bootflash causing bootflash directory usage to be higher than 50%
++ Check using command
df -h /bootflash

Workaround:
++ Cleanup /bootflash directory so that new image does not cause /bootflash to exceed 50% usage

 

(none)# ls
CpuUsage.Log auto-s libmon.logs mem_log.txt
aci-n9000-dk9.13.2.2o.bin diag_bootup lost+found
aci-n9000-dk9.14.1.1i.bin disk_log.txt lxc

(none)# df -h /bootflash
Filesystem Size Used Avail Use% Mounted on
/dev/sda4 7.3G 4.3G 2.7G 62% /bootflash
(none)#


[2019-10-15 00:03:15.687033] Bootflash Usage is higher than 50%!!
[2019-10-15 00:03:15.689367] File: libmon.logs removed !!
[2019-10-15 00:03:15.721124] File: disk_log.txt removed !!
[2019-10-15 00:03:15.754153] File: mem_log.txt removed !!
[2019-10-15 00:03:16.293039] File: aci-n9000-dk9.14.1.1i.bin removed !!


(none)# df -h /bootflash
Filesystem Size Used Avail Use% Mounted on
/dev/sda4 7.3G 2.7G 4.3G 38% /bootflash
(none)# ls
CpuUsage.Log auto-s disk_log.txt lxc
aci-n9000-dk9.13.2.2o.bin diag_bootup lost+found mem_log.txt
(none)#

(none)# ls -l
total 2573252
-rw-rw-rw- 1 root root 701975 Oct 15 00:01 CpuUsage.Log
-rw------- 1 root root 1444061449 Oct 14 20:26 aci-n9000-dk9.13.2.2o.bin
-rw-r--r-- 1 root root 1190165769 Oct 14 23:55 auto-s
-rw-rw-rw- 1 root root 2 Oct 14 23:58 diag_bootup
-rw-r--r-- 1 root root 54 Oct 15 00:15 disk_log.txt
drwx------ 2 root root 16384 Oct 14 20:27 lost+found
drwxr-xr-x 4 root root 4096 Oct 14 20:42 lxc
-rw-r--r-- 1 root root 31920 Oct 15 00:10 mem_log.txt
(none)#

 

 

 

 

 

 

 

1 REPLY 1
Gaurav Gambhir
Cisco Employee

Deleting the old firmware version is recommended way to getting around this issue so the bootflash usage is not going over 50%.

Another option is to disable the bootflash monitoring.

 

add 'disable_bootflash_monitor' in /bootflash/platform.inf