Updating connection manager on-premises

Edit online

You can update your connection manager offline to the latest version to get the latest fixes and enable it to continue monitoring your connections. Update your connection manager to the latest version in offline mode using a locally mounted update image file. This can be useful if you have multiple connection managers and you do not want each of them to separately download updates from the internet. You can instead download a single update image file and use it to manually update each of your connection managers.

Before you begin

Download the connection manager update image, see Updating connection manager offline.

Note:

Before you proceed with the update, make sure that you take a backup of your connection manager. In the event of a disaster where the connection manager is lost, the backup can be restored to a newly redeployed connection manager. For more information, see Backing up and restoring connection manager.
Before you perform an update, ensure that the root partition of the connection manager host has at least 10 GB free space available.

Procedure

To update the connection manager, complete the following steps:

Copy the IMG file to the connection manager by using SCP or SFTP and place it in the /home/defender or /tmp directory. Alternatively, for a VM-based connection manager, you can upload the IMG file to a datastore in your vCenter and attach it to the virtual CD-ROM device of the connection manager that is on VM.
Login to the connection manager using SSH as the IBM® Storage Defender® user.
To create a temporary directory to use as the mount point, issue the following command:
```
mkdir /tmp/imgmount
```
Mount the IMG to the temporary directory. If you have copied the IMG file locally, mount it as a loopback device by issuing the following command:
```
sudo mount -o loop defender-cm-update-<version>.img /tmp/imgmount
```
Alternatively, if you have attached IMG to the virtual CD-ROM device, mount it by issuing the following command:
```
sudo mount /dev/cdrom /tmp/imgmount
```
Run the following command under the mounted IMG to start the update process:
```
/tmp/imgmount/defender_update.sh
```
The update process can take several minutes and run through multiple stages. The process first updates the operating system, and then updates the connection manager components. Progress is displayed on the screen and is also captured in a log file for which the path is displayed at the end of the operation.
When the update is complete, a reboot might be necessary if the operating system kernel has been updated. The following prompt is displayed only if a kernel update has occurred:
```
A reboot is required to load the updated kernel.
Do you want to reboot the system now? [Y/N]
```
Enter Y to reboot automatically, or enter N if you want to reboot manually at a later time.
If the system has not been rebooted, run the following command to unmount the IMG:
```
sudo umount /tmp/imgmount
```
Note: If the system has been rebooted, the IMG is unmounted automatically and is not remounted after reboot.
Clean up the temporary mount point directory by issuing the following command:
```
rmdir /tmp/imgmount
```
Advanced Options

The update process supports the following optional flags:
- --summary – Specify this flag to display a summary of the available updates without installing them.
- --noprompt – Specify this flag to skip interactive confirmation prompts and accept the defaults. This is useful if you are running the update in non-interactive / unattended mode. Note that specifying this flag does not automatically reboot the system at the end of the update process.
- --reboot – Specify this flag to reboot automatically at the end of the update if necessary. The reboot is performed only if a kernel update has occurred.
Examples
- ```
./defender_update.sh --summary
```
```
./defender_update.sh --noprompt --reboot
```