Updating Aura Communication Manager - 7.1.3

[t2true]

Aura Communication Manager 7.1.0

I want to update my CM to 7.1.3. I upgraded the Avaya Utility Server using CLI commands – move the file to /tmp; removed the old patch; install new patch; done. I want to use CLI to update CM as well. But the “Upgrading Avaya Aura® Communication Manager” (05/2018) document only addresses Solution Deployment Manager (SDM).

Is there a way to apply this update using CLI? If so, what document should I be looking for?

Furthermore, are System Manager and Session Manager required to be updated as well?

 

[kyle555]

SMGR needs to be at 7.1.3 to manage any element at 7.1.3 and you need to do an init sync on the CM after upgrading.

Look in the VMware only docs for CM. The old fashioned way was to dump your patches in /var/home/ftp/pub and use commands like 'update_unpack' and 'update_activate'.

System Platform and maybe even CM's SMI had ways to make it more pointy clicky, but you can certainly patch CM from a CLI

 

[t2true]

Thanks for the response Kyle.

How I understand what you are saying is that SMGR needs to be updated first before CM and SM. Correct?
Can that be done via CLI? I've looked at its doc as well, but no mention of CLI commands.

Any idea what the VMWare only doc for CM is entitled?

 

[dialtonebone]

t2true, just go to the support site and filter by Installation/upgrade documents

The CLI commands can be found with "dhelp", the ones you are looking for are the "update_......" commands.

Technically, in all Avaya upgrades SMGR needs to go first. This is specifically true if you are trying to update CM using SDM in SMGR (hasn't worked for me yet).

Upgrade Order:

https://downloads.avaya.com/css/P8/documents/101038555

Page 28

Apply patches via web interface:

https://documentation.avaya.com/bun...ManageronAWS_r7.1.3/page/ApplyingCMPatch.html

<<I know you wanted the command line options, but here is also the web option

 

[ken07734]

I have always used the web gui to update the CM 7.x. You just download the patches then unpack and activate them one at a time making sure you wait at least 2 minutes between patches. Previous versions had different ways of updating depending on PSN's or PCN's

 

[t2true]

Yeah, I have the install doc. It just doesn't address updating using CLI - at least, not the ones for 7.1.3.
I found the list of "update_" commands. Thanks for that. I am just not sure which ones to use, in what order. I found a doc (Avaya Aura® Communication Manager Change Description for Release 5.2.1 - 2011) that addresses Kernal updates. (I don’t know if 7.1.3 is a kernel update.) But, it’s for 5.2.1, not 7.1.

update_unpack
update_show
update_activate <kernel_name>
update_show
statapp
update_commit​

Is that still applicable today? Is that also how it should be done for SMGR?

Good stuff on the upgrade order.

 

[kyle555]

SMGR used to be just executing a .bin. Might have a special command like upgradeSMGR filenameofupgradething.bin

Otherwise, the docs spell it out. Upgrade_unpack and it'll show all the ones in /var/home/ftp/pub - like KERNEL-2.6.8.tar or something. If that's item 1, press 1
Then update_show will show you the updates on the system, if they're unpacked or activated etc
update_activate KERNEL-2.6.8 (with no file suffix) is the command to install the patch.

Kernel patches in particular need a update_commit after the reboot just in case you did something wrong and your OS kernel is so bad it can't run the PBX anymore.

If you haven't done it before, please be very careful and try in a lab first. Especially on a duplex pair. If you do it right on a duplex pair, in the same minor release, you can avoid dropping CM.
If you do it wrong, you get stuck with a patch 'activating' forever and you either beg avaya or reinstall.

 

[t2true]

Thanks again for the feedback. I do have a lab environment in which I will attempt first. It is also running on VMWare. So, I'll capture a snapshot of the image first.