Upgrade Bundle failing to download to 5/6 nodes

[NetworkMonkey101]

Having issues upgrading from 3.2 to 3.3 patch 4. The Bundle has downloaded on the PAN but 5/6 have failed.

Upgrade Bundle download failed: Be sure that all your software is working stable, check your system on UI page (Administration > System > Health Checks) Type yes once confirmed that health of the system is good to proceed: (yes/no) [yes] ? % File transfer error Application upgrade preparation Failed

[Arne Bier]

have you run a Healthcheck on those nodes?   

Before you call the TAC, you can also check

• Run Health Check
• Free up some disk space on those nodes
• Try one node reload:   application stop ise, reload 

[NetworkMonkey101]

Done all of the above, and still the same issue

[Arne Bier]

What did the health report say?

If your repository is using SFTP, then ensure that the crypto commands are issued on ALL the nodes' CLI. Chances are you might only have done that on the PAN, but not on the others - that would certainly cause SFTP to fail on those nodes where the crypto keys have not yet been installed.

crypto host_key add host <FQDN/IP of SFTP server - must match the URL in your repo definition>

[NetworkMonkey101]

H

---

@Arne Bier wrote:

What did the health report say?

If your repository is using SFTP, then ensure that the crypto commands are issued on ALL the nodes' CLI. Chances are you might only have done that on the PAN, but not on the others - that would certainly cause SFTP to fail on those nodes where the crypto keys have not yet been installed.

crypto host_key add host <FQDN/IP of SFTP server - must match the URL in your repo definition>

---

Health report shows everything OK and green. I have setup a local repo and downloaded the files to the downloads folders. From that I have added the upgrade files to the local disk direct through the GUI for the PAN which has been successful and show in the local disk list. When attempting to do it to any other node is completes the file transfer but doesn't show in the local disk dir..

[Arne Bier]

If you created a DISK repository (let's call the repo 'localdisk') with a path of "/" on the PAN GUI, then all nodes should have the repo localdisk. That means you should be able to dump any file on any node's "disk:/" path and then have it visible in the command

show repo localdisk

That's expected behaviour and I just tested in the lab (3.3p4) - why this doesn't work for you is unclear to me.  I would get hold of TAC. Enough disk space?