HAAst upgrade procedure (major version upgrade)

Installing HAAst, prerequisites, getting HAAst started, and troubleshooting performance and technical issues. As well, upgrades to HAAst and any underlying software.
Post Reply
User avatar
CRM User
Posts: 132
Joined: Sun Nov 27, 2016 3:41 pm

HAAst upgrade procedure (major version upgrade)

Post by CRM User » Fri Feb 24, 2017 1:34 pm

I will be upgrading from an older version of HAAst to the latest (2.3.5) and I see in the release notes (change log) that the peerlink version has changed, and the license version has changed. Does that affect how I must upgrade my cluster?
Account for questions transferred from CRM system
User avatar
Telium Support
Posts: 170
Joined: Sun Nov 27, 2016 3:27 pm

Re: HAAst upgrade procedure (major version upgrade)

Post by Telium Support » Fri Feb 24, 2017 1:43 pm

Since the Peerlink protocol verion has changed, the peers will not be able to talk to each other (over Peerlink) until both peers are upgraded. So if both peers are online at the same time they will not be able to communicate - and both peers will try to take over as active. Consequently, your upgrade procedure must ensure both peers are NOT online at the same time.

Since the license version has changed, you will need to request new licenses from Telium. To avoid bringing down the entire cluster you should upgrade and re-license one peer at a time.

The overall steps to performing such an upgrade are:

  1. Upgrade A
    1. Stop HAAst on peer A, wait for stop
    2. Run the install_files/updatefiles.sh script from the newly downloaded package
    3. Unplug the network connection from A
    4. Restart HAAst on peer A
    5. Request and apply new license to A if required, then restart A
  2. Switchover
    1. Stop HAAst on peer B, wait for stop
    2. Replug the network connection to A, ensure A takes over as active
  3. Upgrade B
    1. Run the install_files/updatefiles.sh script from the newly downloaded package
    2. Restart HAAst on peer B, ensure cluster forms
    3. Request and apply new license to B if required, then restart B
  4. Fallback to preferred peer (optional)
    1. Use the telnet/web interface to make the preferred peer active. (Or wait for automatic fallback during the maintenance window if enabled in the haast.conf file)
Post Reply