Insights On-Premises Upgrade
  • Dark
    Light
  • PDF

Insights On-Premises Upgrade

  • Dark
    Light
  • PDF

As part of the on-premises upgrade, you need to upgrade your IOP environment. This article covers upgrade instructions for your OVA-based or Linux-based IOP servers.

When should you use this upgrade guide?

  • You use IOP either as an OVA-based or Linux-based deployment. Upgrade instructions for both types are covered in this article.

  • Your IOP server uses static IP addresses. If the network settings of your IOP server(s) are assigned via DHCP, contact our support team.

  • Prior to the IOP upgrade, you should have already upgraded your ControlUp On-premises environment. Follow the upgrade instructions in the On-Premises Upgrade Guide before starting the IOP upgrade.

  • To upgrade an OVA-based IOP deployment, click here.

  • To upgrade a Linux-based IOP deployment, click here.

IOP Upgrade for OVA-based Deployments

Upgrade a Standalone IOP Machine

In this section, we will go through a complete upgrade for a standalone IOP machine that uses a static IP address.

To upgrade your IOP standalone machine

  1. Open a vCenter Client and log in with a user that is assigned to the Administrator role.
  2. Install a new IOP server by using the OVA file. Make sure you install the new IOP server with the same template settings as the old IOP machine. For example, if you used these template settings for the deployment in the previous version of IOP machine, then you need to use the same settings for the installation of your new IOP server.
    IOP_TemplateSettings_8_5
  3. Wait until the import of the new virtual appliance is finished. It is important that you do not turn on the machine yet.
  4. SSH into your old IOP server with the root user.
    Note

    The root user is deactivated in version 8.6 or higher. Use the cuadmin user instead.

  5. Run iopcmd stop to stop all running IOP containers.
    InsightsStopContainers
  6. Note the storage that your old IOP machine uses
    IOP_MachineStorageNoticeBeforeUpgrade
  7. Shut down the machine by running shutdown -P 0
  8. Select the Datastores view on the old IOP machine and browse to the Files tab. You can see all virtual files that are currently used by your IOP machine.
    IOP_VirtualFilesUsedForIOPMachine
  9. Select the vmdk file that has the format [VirtualMachineName] _1.vmdk and click Copy to.
    IOP_CopyVMDKFile
  10. In the Select Destination window, select the new IOP server and click OK. This copies the virtual disk from the old to the new IOP server. Make sure you have enough free disk space on the destination datastore before you copy the vmdk file to the new IOP machine.
    IOP_CopyVMDKFileToDestination
  11. Wait until the file has been completely transferred. You can click the Monitor tab > Tasks to see the status of the copy process.
  12. Navigate to the Host and Clusters view in your vCenter client, right-click the new IOP server > Edit Settings.
  13. Under Hard disk 2, click the X icon to remove this disk.
    IOP_RemoveHardDisk2OnNewIOPServer
  14. Check the Delete files from datastore checkbox and confirm by clicking OK.
  15. Right-click the new IOP server and select Edit Settings. Click ADD NEW DEVICE and choose Existing Hard Disk.
    IOP_AddHardDiskFromOldIOPServer
  16. In the Select File screen, select the vmdk that you copied in Step 10. Click OK to confirm.
    IOP_SelectHardDisk
  17. The new hard disk is shown in the settings. Confirm by clicking OK and wait until the hard disk is created.
Note

The size of the new hard disk must be the same as the size of the exported HDD. If the old hard disk had a capacity of 50 GB, then you have to change the size of the new hard disk to 50 GB as well

  1. As the old IOP machine is powered off, you can now power on the new IOP machine and wait until the machine is booted.

Verify that the upgrade was successful by checking if old data is shown in the portal:

  1. Open your Real-Time Console which should already run with the updated COP version and click the ControlUp Insights button in the Home ribbon.
  2. Log into the portal and check if data that existed before the upgrade is shown in the portal. This data is retrieved from the vmdk file that we copied before.

If you followed the upgrade procedure COP in the correct order, you should not have any IOP Forwarders installed on your ControlUp Monitor machines. It is time to install the IOP Forwarder on all monitor machines. This ensures that new data is transferred to the new IOP server. Follow the installation instructions from the IOP forwarder installation guide.

Once you haved installed new IOP Forwarders on the ControlUp Monitor machines, verify that new data is shown in the Insights portal.

Note

As the IOP Forwarder usually creates activity files every 10 minutes, wait at least 15 minutes to check if new data is coming in.

In case the new data is shown in the Insights portal, you can now remove the old IOP server. To delete the machine, open the vSphere client, right-click the old IOP virtual machine, select Delete from Disk and click YES to delete the disk.

Upgrade IOP Cluster Machines

This section describes the upgrade in a cluster environment that uses static IP addresses. As a reminder, a clustered environment is made of one master node and multiple data nodes. First, you need to upgrade your master node and then each data node.

Upgrade Master Node

The first component in your clustered environment that you need to upgrade is the master node. Make sure you complete the instructions below before you move on to the upgrade of your data nodes.

To upgrade your master node:

  1. Open a vCenter Client and log in with a user that is assigned to the Administrator role.
  2. Install a new IOP master node by using the latest version of the OVA file. Make sure you install the new IOP master node with the same template settings as the old IOP master node. For example, if you used these template settings for the deployment of your master node in the previous IOP version, then you need to use the same settings for the installation of your new IOP master node. As this is the master node you have to select the type MASTER at the end of the template settings window.
    IOP_TemplateSettings_8_5_MasterNode
  3. Wait until the import of the new virtual appliance is finished. It is important that you do not turn on the machine yet.
  4. SSH into your old IOP master node with the root user.
  5. Run iopcmd stop to stop all running IOP containers on the master node.
    IOP_StopContainer_Master
  6. Note the storage that your old IOP machine uses
    IOP_MachineStorageNoticeBeforeUpgradeMaster
  7. Shut down the machine by running shutdown -P 0
  8. Select the Datastores view on the old IOP machine and browse to the Files tab. You can see all virtual files that are currently used by your IOP machine.
    IOP_SelectHardDiskForMaster
  9. Select the vmdk file that has the format [VirtualMachineName] _1.vmdk and click Copy to.
    IOP_CopyVMDKFileMaster
  10. In the Select Destination window, select the new IOP server and click OK. This copies the virtual disk from the old to the new IOP server. Make sure you have enough free disk space on the destination datastore before you copy the vmdk file to the new IOP machine.
    IOP_CopyVMDKFileToDestinationMaster
  11. Wait until the file has been completely transferred. You can click the Monitor tab > Tasks to see the status of the copy process.
  12. Navigate to the Host and Clusters view in your vCenter client, right-click the new IOP master node > Edit Settings.
  13. Under Hard disk 2, click the X icon to remove this disk.
    IOP_RemoveHardDisk2OnNewIOPMaster
  14. Check the Delete files from datastore checkbox and confirm by clicking OK.
  15. Right-click the new IOP server and select Edit Settings. Click ADD NEW DEVICE and choose Existing Hard Disk.
    IOP_AddHardDiskFromOldIOPMaster
  16. In the Select File screen, select the vmdk that you copied in Step 10. Click OK to confirm.
    IOP_SelectCopiedHDD
  17. The new hard disk is shown in the settings. Confirm by clicking OK and wait until the hard disk is created.
Note

The size of the new hard disk must be the same as the size of the exported HDD. If the old hard disk had a capacity of 50 GB, then you have to change the size of the new hard disk to 50 GB as well. Make sure you follow the hard disk sizing recommendation in the prerequisites guide. A general rule of thumb: The larger the disk size, the better.

  1. As the old IOP master node is powered off, you can now power on the new IOP master and wait until the machine is booted.

Upgrade Data Nodes

You must complete the master node upgrade instructions before continuing with the data node upgrade. You can upgrade your data nodes only after your master node has been upgraded. It's the same as upgrading the master node. For each new data node deployed, you need to select DATA in the template settings.

To upgrade your data nodes:

  1. Open a vCenter Client and log in with a user that is assigned to the Administrator role.
  2. Install new IOP data nodes by using the latest version of the OVA file. Make sure you install the new IOP data nodes with the same template settings as the old IOP data nodes. For example, if you used these template settings for the deployment of the previous version of your data nodes, then you need to use the same settings for the installation of your new IOP data node. As this is the data node you have to select the type DATA at the end of the template settings window and provide the IP address of the master node.
    IOP_TemplateSettings_8_5_DataNode1_2
  3. Wait until the import of the new virtual appliance is finished. It is important that you do not turn on the machine yet.
  4. SSH into your old IOP data node with the root user.
  5. Run iopcmd stop to stop all running IOP containers on the data node.
  6. Note the storage that your old IOP machine uses
    IOP_StorageData
  7. Shut down the machine by running shutdown -P 0
  8. Select the Datastores view on the old IOP machine and browse to the Files tab. You can see all virtual files that are currently used by your IOP machine.
    IOP_DataNodeFiles
  9. Select the vmdk file that has the format [VirtualMachineName] _1.vmdk and click Copy to.
    IOP_CopyVMDKFileData
  10. In the Select Destination window, select the new IOP server and click OK. This copies the virtual disk from the old to the new IOP server. Make sure you have enough free disk space on the destination datastore before you copy the vmdk file to the new IOP machine.
    IOP_CopyVMDKFileToDestinationData
  11. Wait until the file has been completely transferred. You can click the Monitor tab > Tasks to see the status of the copy process.
  12. Navigate to the Host and Clusters view in your vCenter client, right-click the new IOP data node > Edit Settings.
  13. Under Hard disk 2, click the X icon to remove this disk.
    IOP_RemoveHardDisk2OnNewIOPData
  14. Check the Delete files from datastore checkbox and confirm by clicking OK.
  15. Right-click the new IOP server and select Edit Settings. Click ADD NEW DEVICE and choose Existing Hard Disk.
    IOP_AddHardDiskFromOldIOPData
  16. In the Select File screen, select the vmdk that you copied in Step 10. Click OK to confirm.
    IOP_SelectHardDiskForData
  17. The new hard disk is shown in the settings. Confirm by clicking OK and wait until the hard disk is created.
Note

The size of the new hard disk must be the same as the size of the exported HDD. If the old hard disk had a capacity of 50 GB, then you have to change the size of the new hard disk to 50 GB as well. Make sure you follow the hard disk sizing recommendation in the prerequisites guide. A general rule of thumb: The larger the disk size, the better.

  1. As the old IOP data node is powered off, you can now power on the new IOP data node and wait until the machine is booted.
  2. Repeat the steps from this chapter for all remaining data nodes.

Once you complete the upgrade of all data nodes, verify that the upgrade was successful by checking if old data is shown in the portal:

  1. Open your Real-Time Console which should already run the update COP version and click the ControlUp Insights button in the Home ribbon.
  2. Log into the portal and check if data that existed before the upgrade is shown in the portal. This data is retrieved from the vmdk file that we copied before.

If you followed the upgrade procedure COP in the correct order, you should not have any IOP Forwarders installed on your ControlUp Monitor machines. It is time to install the IOP Forwarder on all monitor machines. This ensures that new data is transferred to the new IOP server. Follow the installation instructions from the IOP forwarder installation guide.

Once you have installed new IOP Forwarders on the ControlUp Monitor machines, verify that new data is shown in the Insights portal.

Note

As the IOP Forwarder usually creates activity files every 10 minutes, wait at least 15 minutes to check if new data is coming in.

In case the new data is shown in the Insights portal, you can now remove the old IOP data nodes. To delete the machines, open the vSphere client, right-click the old IOP virtual machine, select Delete from Disk and click YES to delete the disk.

IOP Upgrade for Linux-based Deployments

In this section, we show you how to upgrade your IOP machine(s) to the latest version. As an example, we will use IOP files for version 8.6.5. This may vary in your case, depending to which version you want to upgrade.

Upgrade a Standalone IOP Machine

  1. Download iop_8.65_images_stable.tgz and iopcmd-8.65.822.66.tgz to your Windows machine.
  2. Copy both files to your user profile under the /home/ directory on your IOP machine.
  3. SSH into your IOP server and browse the path to where you copied both tgz files.
  4. Move both files to /opt
    sudo mv iop_8.65_images_stable.tgz /opt/
    
    sudo mv iopcmd-8.65.822.66.tgz /opt/
    
  5. From the /opt directory, extract iopcmd-8.65.822.66.tgz.
    sudo tar zxvf iopcmd-8.5.733.34.tgz
    
    This creates a new directory iopcmd and two files, iopcmd and iopcmd.conf.
  6. Move the iop_8.65_images_stable.tgz file to iop_8.65_images_stable.tgz:
    sudo mv iop_8.65_images_stable.tgz /opt/iopcmd/iop_8.65_images_stable.tgz
    
  7. From the /opt/iopcmd/ folder, start the upgrade script. As this is a standalone upgrade, use the following parameters when upgrading:
    -t node type
    -pwd password. Provide the password from the previous IOP installation.
    -p with the location of the iop_images.
    -f to confirm the upgrade.
    sudo ./iopcmd upgrade local -t standalone -pwd Qa123456 -f -p /opt/iopcmd/iop_8.65_images_stable.tgz
    

The upgrade is done and you can access Insights again.

Upgrade IOP Cluster Machines

Upgrading a clustered environment is similar to upgrading the standalone server.

  1. Download iop_8.65_images_stable.tgz and iopcmd-8.65.822.66.tgz to your Windows machine.
  2. Copy both files to your user profile under the /home/ directory on your IOP machine.
  3. SSH into your IOP server and browse the path to where you copied both tgz files.
  4. Move both files to /opt
    sudo mv iop_8.65_images_stable.tgz /opt/
    
    sudo mv iopcmd-8.65.822.66.tgz /opt/ 
    
  5. cd /opt/
  6. From the /opt directory, extract iopcmd-8.65.822.66.tgz.
    sudo tar zxvf iopcmd-8.65.822.66.tgz
    
    This creates a new directory iopcmd and two files, iopcmd and iopcmd.conf.
  7. Move the iop_8.65_images_stable.tgz file to iop_8.65_images_stable.tgz:
    sudo mv iop_8.65_images_stable.tgz /opt/iopcmd/iop_8.65_images_stable.tgz
    
  8. From the /opt/iopcmd/ folder, start the upgrade script.
    -t node type
    -pwd password. Provide the password from the previous IOP installation.
    -p with the location of the iop_images.
    -f to confirm the upgrade.
    For the master node, use the -t parameter with the value master
    sudo ./iopcmd upgrade local -f -t master -pwd Qa123456 -p /opt/iopcmd/iop_8.65_images_stable.tgz
    
    For each data node, run the same command. Provide the IP or DNS of the master node in the -m parameter.
    sudo ./iopcmd upgrade local -f -t data -m 192.168.0.101 -pwd Qa123456 -p /opt/iopcmd/iop_8.65_images_stable.tgz
    

You can access Insights again after upgrading the master and all data nodes.


Was this article helpful?