Upgrading Site Engine

[Macknkss]

Hi, our site engine is on version 23.11.x which I understand is no longer supported. I've been putting this off for a month as it seems really complex. I know no linux and this will be our first time upgrading.

I've gone through some of the steps and some of the cli commands in the documentation aren't working, don't know if it's the version we're on or what.

Is this easier than it looks? I've never seen an upgrade this complex in my 25 years of IT! This is the framework for the upgrade I got from support. My nightmare is how to revert to a working environment after making all these changes. Seems that once you start there's no going back.

• Upgrade Path: 23.11 >> 24.02.25 >> 24.10.13
• Upgrade from 23.11 to 24.02 will be a regular upgrade. Check this KB for instructions.
• Upgrade from 24.02 to 24.10 involves data migration where you need to build another VM parallelly. Check this link for instructions
• Data migration is only required for XIQ-SE. Control engine/s can be upgraded using the regular upgrade process
• First upgrade XIQ-SE to 24.02 and then the Control engine/s to 24.02. Then upgrade XIQ-SE to 24.10 through database migration procedure and later upgrade the control engine/s to 24.10

[Macknkss]

For the controllers we're on ubuntu 20.04lts (64 bit). When running the command below we're not seeing the /opt partition. Worked out some of the other areas that I was confused about with support

root@ExtremeNAC01:~$ df -lh

Filesystem                 Size  Used Avail Use% Mounted on

udev                       7.8G     0  7.8G   0% /dev

tmpfs                      1.6G  976K  1.6G   1% /run

/dev/mapper/systemvg-root  117G  9.2G  103G   9% /

tmpfs                      7.9G   28K  7.9G   1% /dev/shm

tmpfs                      5.0M     0  5.0M   0% /run/lock

tmpfs                      7.9G     0  7.9G   0% /sys/fs/cgroup

/dev/sda1                  511M  4.0K  511M   1% /boot/efi

tmpfs                      1.6G     0  1.6G   0% /run/user/0

[Robert_Haynes]

Always as best practice perform a snapshot of your virtual machine before any upgrade. It makes restoring back to operation from a potential upgrade failure / post upgrade issue a breeze.

Your XIQ-SE upgrade path is 23.11 -> 24.02.15.05 -> 24.10.12/13. It is a standard .bin-based upgrade from 23.11 -> 24.02. 

You then perform the data migration from 24.02 -> 24.10.13 as you've noted. Yes, this involves setting up a parallel 24.10.13 VM and you are essentially pulling from the working 24.02 VM the database, files, configuration, etc to the new 24.10.13 VM. Once done and operational, simply turn down your old VM (do not yet delete just in case).

The Control engines technically DO NOT have to be upgraded in step. Leave them at 23.11. Get SE upgraded to 24.10. Once SE is upgraded, complete the .bin-based upgrades of Control straight from 23.11 -> 24.10.

If you are not comfortable performing these upgrades Extreme does offer Professional Services to come on site or remote in to perform the upgrades and migrations for you.

I do encourage you however to just read the KB articles and attempt the upgrade yourself to gain familiarity and comfort in the general process.

[Macknkss]

Thank you for your help Robert. I've read the documentation many times and it's confusing because there are so many different pieces involved and multiple upgrades for all of them. Management would be pissed if I asked for money to upgrade our almost brand new wireless system that's only been in place for 6 months 🙂

I think I'm starting to feel more comfortable though, appreciate the response! 

[rmu]

hi

all my customers are using vmware and do a snapshot of every device before upgrading.

with this rollback is super easy.

nr

rmu

[Macknkss]

Yeah thanks just hope any problems would be caught in testing before users are back in the office