Cisco SSM On-Prem Upgrade procedure
This is another blog post for Cisco SSM On-Prem server where I’m showing the upgrade process. Before any upgrade, it is advised to snap shot the virtual machine to have a working backup installation (see Cisco SSM On-Prem password recovery procedure)
The next step is to verify the version. My test drive installation has the version 8-202010 and I’m going to upgrade to the latest version 8-202108.
Before the upgrade the downloaded files must be moved and extracted on a server which supports SCP (SecureCopy). Typically any Linux server with SSH/SCP enabled (default) will do.
The extracted upgrade.sh and upgrade.sh.sha256 files should then copied with scp to the Cisco SSM On-Prem server.
After the login to the Cisco SSM On-Prem server the so-called onprem-console should be started. The onprem-console provides some CLI commands to manage the SSM On-Prem server including the command database_backup.
Based on Cisco’s documentation a database backup should be performed when SSM On-Prem server is running as virtual machine. When the database backup is completed, the onprem-console can be exited with the command quit.
The files upgrade.sh and upgrade.sh.sha256 can be copied by SCP from the Linux server to the SSM On-Prem server. The syntax of the SCP command can look like this:
$ scp [user]@[host]:/[[path_to_file]/file.bin file.bin
Ensure the files upgrade.sh and upgrade.sh.sha256 are copied to the SSM On-Prem server correctly with ls -l.
Become root by entering su plus the password and add the “execute” file attribute to the upgrade files with chmod +x.
Run the upgrade.sh script. The upgrade.sh script will take between 5 and 15 minutes depending on the virtual environment and virtual machine setup. When the upgrade process is completed, the Cisco SSM On-Prem server should be restarted with the reboot command.
After the reboot the installed version of Cisco SSM On-Prem should be verified. The version 8-202108 should now be installed.