Release 12 Upgrade

[bignose21]

Just trying to nail down the steps to upgrade a 11.1.3.2 IP Office Server Edition using Avaya supplied servers for Primary/Secondary and some IP500v2 expansions to release 12.1.0.1

Looking at the documentation the order is Secondary then Primary then expansions, the steps for the servers to R12.0 are in the "Upgrading Linux based IP Office Systems to R12.0" but the steps from there to upgrade the expansions and the servers up to 12.1 SP1 are not so clear.

Can you move the servers directly from 12.0 to 12.1.0.1 using an ISO upgrade from Web Manager?
Can the IP500v2 Gateways be upgraded from 11.1.3.2 directly to 12.1.0.1 using an ISO upgrade from Web Manager?

 

[bignose21]

Found a web site that details the need to step through the Major Releases so I would imagine the process to be

Start point is everything on 11.1.3.2

1. upgrade secondary server to 12.0 using the ISO put on a USB key and copy over the avaya_autoupgrade.conf to the root directory
2. upgrade primary server to 12.0 using the ISO put on a USB key and copy over the avaya_autoupgrade.conf to the root directory
3. upgrade the expansion IP500v2 Gateways (guessing Web Manager upgrade should be possible? or Manager Upgrade? I am remote from these gateways)
4. as there are no further FP or SP on 12.0 continue to 12.1
5. upgrade secondary server to 12.1.0.1 using the ISO put on a USB key and copy over the avaya_autoupgrade.conf to the root directory (I figure like when you upgraded to 11.1 you could jump directly to FP1 and SP1 when coming from 11.0.4)
6. upgrade primary server to 12.1.0.1 using the ISO put on a USB key and copy over the avaya_autoupgrade.conf to the root directory
7. upgrade the expansion IP500v2 Gateways

Obviously remote backups at the start and at 12.0 for the devices in case rollback is required.

 

[mhoxie]

I would not upgrade to 12 yet on a server edition. It's half baked. 12 licenses work on 11.1.

If you really have to, the best way is to save the config, create a usb stick, and do a fresh install. 12 uses rocky linux and is a completely separate OS from 11.1, hence the upgrade hassle.

I have had no issue upgrading 500 v2 control units to 12.

 

[bignose21]

so with the IP500v2 just jump 11.1.3.2 straight to 12.1.0.1? and using what method Manager, Web Manager, or are you doing the SD Card?

Need to go 12 just for the Vulnerabilities on 11.1

 

[mhoxie]

Legit question, what vulnerabilities? If you don't have to open ports to the public you shouldn't have any issues. I do IPO server editions for 24/7 customers so we cant afford the jank with the networking. But most of these systems aren't open to the internet, and if they are, its for a sip trunk that you whitelist the IP on the firewall so literally only 5060 from that IP is allowed. Seriously, 12 is bad. Don't say i didnt warn you.

As for the control units. You can do an upgrade with manager on a PC. The fastest way is to install the full version 12 manager on your pc, and recreate the SD card, then copy the config. You save a config in manager and move it to the SD card and make sure its named "config.cfg". You can also do the "upgrade" option from the manager program on a live system. This is slower as it has to transfer all the files. Remember, control units are only 100MB not gig, transfers take forever.

You could do the web manager upgrade AFTER the server is updated, but it takes forever and I would only do 2 a time. Again, I'm usually doing installs with like 8 control units. So it's faster to just swap the SD card. But if its a 9-5 customer and you have remote access you could just do it through web manager.

 

[bignose21]

I know what you mean with the vulnerabilities and we are driven by the security group in the customer, they scan from the management VLAN's ensuring they are not blocked at all so unrealistic I know but its what I have to put up with. As the 11.1 OS packages have not moved in quite some time there are quite a few vulnerabilities most centred on tomcat.

For the servers am I right in two step approach 11.1.3.2 to 12.0.0.0 then 12.0.0.0 to 12.1.0.1