Insights On-Premises Upgrade for Linux
    • Dark
      Light
    • PDF

    Insights On-Premises Upgrade for Linux

    • Dark
      Light
    • PDF

    Article Summary

    As part of the on-premises upgrade, you need to upgrade your IOP environment. The following article covers upgrade instructions for your Linux-based IOP Servers.

    When should you use this upgrade guide?

    • You can use IOP either as an OVA-based or Linux-based deployment. This article covers upgrade instructions for a Linux-based deployment only. For upgrade instructions for an OVA-based deployment, see ControlUp On-Premises Upgrade Guide.
    • 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 (COP) environment. Follow the upgrade instructions in the On-Premises Upgrade Guide before starting the IOP upgrade.

    IOP Upgrade for Linux-based Deployments

    Follow the steps below to upgrade your IOP machine(s) to the latest version. As examples, we use IOP files from version 8.6.5. Use the proper files according your upgrade version.

    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?