Upgrade proces to R12 1

[Fr0gg3r - MaartenS]

Hi,

It appears I'm missing some knowledge on the upgrade processes.
I've read through the documentation of the processes:

https://documentation.avaya.com/bun...e/Upgrading_Linux_Base_IP_Office_Systems.html

Physical SE / Appl Server:
What we basically are doing is installing a new image on a physical server.
But there is no mention of the proces of putting the current config of the server back in place?
If I'm installing a new ISO on a physical server, I'd be overwriting the OS that is currently installed. How does the new OS get the correct settings and the IPO configuration?

Same counts for an upgrade in VMWare. put the new disk in place, but no mention of putting the IPO config on the new disk.

I doubt that the automatic upgrade proces "installing a new disk or installing a new ISO" contains a migration thing that automatically puts the old IPO config on the new server.

Any suggestions?

There is no mention of putting an IPO backup back in the new OS..
Or am I just looking over that info?

thank you.


Most likely our way of migrating to R12 will be the same as our migrations from pre R11.0.FP4(centos6) to +R11.0FP4 (centos7).
We've done this multiple times without any problems.

I still believe that this is the best way to upgrade between different OS's:
- deploy a new OVA
- setup a new system with the same ip's and domain name etc ... but in temporary vlan)
- upload licenses
- Save old IPO config to pc
- Upload it to the new server. (same for VMPRO configuration and wave files)
- Upload certificates
- compare 46xxsettings files from both servers.
- Turn off the lan port of old server (you can keep the server running in case you need to go back to the old server.
- Change vlan of new server to operational voice vlan.
- phones will connect immediatly to the new server.
- siptrunks/sbc will connect to new server immediatly.

-> no downtime
-> Takes half time when comparing to first upgrading to latest R11.1, then upgrade to R12.

This also prevents you from having to setup a temporary server where you can backup your full ipo config to to be able to put it back in the new server.

 

[derfloh]

Your process should work as well...

Avaya's process uses the USB drive (>256GB). It boots from USB, takes backups of everything to that USB drive, installs the new ISO (IPO12) and then restores the backup from USB.

If everything works well you will have a running R12 system afterwords.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[Fr0gg3r - MaartenS]

Thanks for that fast feedback

For the usb drive I get that the process can take a backup and restores certain parts of that backup to the new server.
But is there a similar mechanism running for vmware then?

Maarten

 

[derfloh]

Yes... Instead of an USB stick there is a virtual upgrade disk (VMDK file) available. You have to add this 'disk' to the server and boot from that disk. The process is the same as with the USB drive.

Using Avaya's proess always takes a full backup and makes a full restore.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[Fr0gg3r - MaartenS]

thanks, I'll give that a try today.

 

[Fr0gg3r - MaartenS]

To prevent my demo/lab system to corrupt I want to use a clone of the current server to test the upgrade process. I shutdown the server and made a clone on VMWARE for it.

I now notice that:

1: LAN1 is not available after first boot of the clone. After a reboot of the clone it is available​

2: When logging in using manager: the password is reset to default and I get the window to put in new passwords for Administrator/root/service.​

​

It seems the security settings of IPO have been reset in the clone. Also system name has been defaulted.​

Any idea if these symptoms are normal after the cloning of a IPO SE ?

 

[Fr0gg3r - MaartenS]

never mind,

the whole system got defaulted,

security, passwords, ipo config, ... everything is gone.
So the 'upgrading a clone just to be sure' is no option.

deploying a new R11.1 that I will upgrade to R12 as a test

 

[telfire]

FROGGER,

You are probably better off "for lab purposes" deploying a fresh ova of your current version and label that "test upgrade" leaving your production "lab" system alone. I would then rehost my licenses if you actually wanted to use the "test upgrade" system, otherwise you could skip this step. Be prepared to rehost your licenses anyways if you upgrade you production system - this sometimes (rarely) happens.
Whenever you clone a system, snapshot a system or at least when I have using AWS, ESXi or HyperV, it seems there is something is amiss sometimes... whether it is network info (IP's, FQDN, MAC, etc), security settings, the IPO config itself, licensing (which is expected), or SSL certs. You should consider taking a full system backup of the lab server using Web Manager, then grab and save using WinSCP. You could then restore to the lab system if it becomes corrupt during the upgrade process. The last few upgrades I did on Linux to R11.1.x from something lower were done on ESXi and all went smoothly. Also, pay attention to the Definition Offer for R12.0 as ESXi below v7 is "not supported" (but would probably work.

APSS-Midmarket
ACIS-Midmarket
ACSS-Midmarket
ACDS-Midmarket