Technical Tip: How to upgrade online super with first verification steps

Follow the next steps for additional checks prior to the upgrade:

1. If the FortiSIEM is behind a proxy: Follow the documentation Upgrade via Proxy.

2. Check the connections to repositories.
3. Download the .zip file for the upgrade at https://support.fortinet.com and note the checksum provided.
4. Verify the MD5sum hash from the downloaded file and make sure that both checksums are matching:
   
   

Get-FileHash FSM_Upgrade_All_7.3.0_build0338.zip -Algorithm MD5 | Format-List

1. Go to Admin -> Health and make sure that super and workers are shown in a normal state in green. If not, do not proceed with the upgrade and fix the super and workers first.
2. Load the file on the super with WinSCP at /tmp.
3. Check the hash file again with:
   
   

cd /tmp

md5sum FSM_Upgrade_All_7.3.0_build0338.zip

1. If FortiSIEM is on VM, take a snapshot of the current state.
2. Uncompress and proceed with the upgrade:
   
   

mkdir -p /opt/upgrade

mv /tmp/FSM_Upgrade_All_7.2.1_build0241.zip /opt/upgrade

yum install -y p7zip

cd /opt/upgrade/FSM_Upgrade_All_7.2.1_build0241

screen -S upgrade

#Run 'screen -r' in case connectivity is lost.

sh upgrade.sh

Wait for the upgrade to proceed. It can take some time along with the size of the databases and resources of the machine.

In case of error: 

• Upgrade logs are /usr/local/upgrade/logs/ansible.log. Check for explicit errors.
• Catch complete logs by following the steps from the article: Technical Tip: How to retrieve logs from FortiSIEM VA and deliver them to support and provide them to the support team when errors are not explicit enough.
• If this state is critical for the business, it is recommended to revert to the previous stable snapshot for VMs or restore with Restoring Hardware from Backup After a Failed Upgrade for hardware devices.