1. Resonate RFID Reader Management 2.1 Installation Guide
  2. Upgrading the Software
  3. Performing the Upgrade
  • Resonate RFID Reader Management 2.1 Software Installation Guide
Performing the Upgrade

Performing the Upgrade

The following steps describe how to perform the upgrade.
These steps use the
setup.sh
 script to perform the setup tasks. If you need to manually perform the setup tasks that the
setup.sh
 script performs, refer to Manually Setting Up a Resonate Kubernetes Cluster. The
setup.sh
 script is recommended for production deployments because it is efficient and reduces the likelihood of errors. Use the manual process only for educational purposes or when you need to understand each step in detail. Both the automated script and the manual process require internet access.
It is typical for
setup.sh
 to request that you reboot the system to apply updates. After the reboot, you must run
setup.sh
 again, with the exact same options, to continue and complete the setup. If the setup fails during a wait for the system to be ready, it might be due to network speed. Rerun the
setup.sh
 script using the same settings to continue with the setup process.
  1. Prepare for the upgrade.
    2. Download the
      resonate-<NEW-VERSION>.tar.gz
       file that contains the new version of the installer package.
    3. Extract the files from the downloaded file:
      tar xvf resonate-<NEW-VERSION>.tar.gz
      One of the extracted files should be the installer package (
      trifecta-installer-k8s-<NEW-VERSION>.<BUILD-NUMBER>.tar.gz
      ).
    4. Extract the files from the new installer package1. 
      tar xvf trifecta-installer-k8s-<NEW-VERSION>.<BUILD-NUMBER>.tar.gz
    5. Verify that you have extracted the required files:
      trifecta.tar
      ,
      setup.sh
      ,
      lb.yml
      .
  2. Run the
    setup.sh
     script on the primary node.
    Run the script using the same settings used during initial installation. If unsure about your original setup settings, check your shell history (
    history | grep setup.sh
    ); alternatively, refer to Setting Up a Single-Node Cluster or Setting Up a Multi-Node Cluster, depending on your configuration.
    • For single-node configurations:
      sudo -E ./setup.sh
    • For multi-node configurations that use a load balancer:
      sudo -E ./setup.sh -m <NUMBER_OF_NODES> -b <BLOCK_DEVICE>
    • For multi-node configurations that use MetalLB (that is, without an external load balancer):
      sudo -E ./setup.sh -m <NUMBER_OF_NODES> -b <BLOCK_DEVICE> -i <EXTERNAL_IP>
    The following is an example command for a 3-node cluster with a load balancer
    sudo -E ./setup.sh -m 3 -b /dev/nvme1n1
  3. Handle reboot (if requested).
    The
    setup.sh
     script might request a system reboot to apply updates.
    1. If prompted, reboot your system:
      sudo reboot
    2. After reboot, run the
      setup.sh
       script again to complete:
      sudo -E ./setup.sh [same settings as before]
  4. After the setup completes successfully, run the
    install.sh
     script on the primary node.
    1. Switch to the user trif-user:
      sudo su - trif-user
    2. Run the
      installer.sh
       script with your original settings:
      ./install.sh -h <RESONATE SERVER FQDN> -m <MODE> --smtp-server <SMTP SERVER FQDN/IP> --admin-email <EMAIL ADDRESS> [--customer-label-value <CUSTOMER LABEL VALUE>]
      Use the exact same settings that you used during your original installation, especially those listed in the command above. That is:
      • FQDN of the
        Resonate
         server (
        -h
        )
      • Deployment mode (
        -m
        )
      • SMTP server settings (
        --smtp-server
        )
      • Administrator email (
        --admin-email
        )
      • Your customer name if using Zebra's OpsRamp alert monitoring service (
        --customer-label-value
        ). If you specified your customer name during the original installation or manually added it afterward, you must use the
        --customer-label-value
         option to include it in your updated installation; otherwise, your alerts will no longer have your customer name, and OpsRamps will not handle them.
      The following are some common examples:
      • Single-node
        ./install.sh -h trifecta.yourcompany.com -m prod-single-node --smtp-server mail.yourcompany.com --admin-email admin@yourcompany.com
      • Multi-node
        ./install.sh -h trifecta.yourcompany.com -m prod-multi-node --smtp-server mail.yourcompany.com --admin-email admin@yourcompany.com
      • With Custom SMTP Port
        ./install.sh -h trifecta.yourcompany.com -m prod-single-node --smtp-server mail.yourcompany.com --smtp-port 587 --admin-email admin@yourcompany.com
      Your
      Resonate RFID Reader Management
       instance has been successfully upgraded. It should now be running the new version with all your existing data and configurations preserved.
  5. Log in and update the Resonate Agent on the readers through the
    Resonate
     web interface; you can update 100 readers at a time.
    1. On the
      Infrastructure
      Devices
       page of the
      Resonate
       web interface, filter and select up to 100 readers.
    2. Select from the column header at the far right Device Settings
      Device Settings
      Upgrade Agent App
      .
      The
      Upgrade Agent App
       dialog opens.
    3. Select the appropriate upgrade from the dropdown list, and click
      Update
      .
    4. If required, click
      Schedule
       to schedule and run the update at a different time.
      You can see the scheduled operation on the
      Identity
       tab of the reader's
      Edit Devices
       page.
    A failure during a Resonate Agent upgrade results in an error displayed in the device grid. You can verify the version of the agent running on the reader by checking the log files.
Test that your
Resonate RFID Reader Management
 instance is functioning correctly. Also, monitor its performance.
1 Use this file when upgrading an online installation.
Resonate RFID Reader Management
 2.0 did not support an offline installation.