Communication Mgr System Platform 6.3.7

[dignoffo]

Avaya just released System Platform 3.6.7 which is an ISO file at 1.4 GB in size. I have not been able to upload the file from the System Platform web console upload page due to the ISO file format. Avaya documentation states it must be burned to a CD to reboot the server to apply.

Does this sound correct or is there a way to modify the file format in the SP web console?

 

[kyle555]

Typically, patches within the same minor release are .tar.gz files, and you would apply them through "Patch Management" in the System Platform server - be they for System Platform or CM or whatever other product is hosted on that System Platform.

6.3.0-->6.3.4-->6.3.x would fit that bill.

When upgrading between minor releases - be it System Platform or the template, you'd use either a "Platform Upgrade" or a "Template Upgrade" to accomplish that task, and that is typically done with an ISO.

Avaya's verbiage seems to indicate that going to SP 6.3.7 needs a template upgrade - and because it supports the new S8300E, I can see why there might be that deviation from that nrom.

Avaya Aura® System Platform 6.3.7.0 (Service Pack 7)
Use this System Platform .iso installation file to create a DVD. Use the DVD to boot the server and for a fresh install of the underlying operating system and System Platform. The DVD can also be used to upgrade an earlier version of System Platform R6.x running on a server. Servers running earlier versions of System Platform R6.0.x require an upgrade to R6.0.3.4.3 (or greater) before upgrading to System Platform R6.3.7.

I think if you WinSCP the ISO to /home/admin in CDOM and then either move it to /vsp-template or mount it to say /home/admin/systemplatformcd and mkdir /vsp-template/systemplatformcd and cp -r * /home/admin/systemplatformcd /vsp-template/systemplatformcd that when you try to "Platform Upgrade" you can select "System Platform Server" and it looks in /vsp-template for files it can use to upgrade.

 

[dignoffo]

kyle555,

Thank you. I will try your suggestion.

 

[specialk196]

Avaya Aura System Platform Upgrade to 6.3.7.0.05001

The following steps outline the process to upgrade System Platform remotely
The following steps are service affecting so use caution when performing
Full System Platform Remote Backup is highly recommended before continuing
1. Copy the System Platform ISO image and System Platform patch (if needed) to /tmp on cdom using ssh
In this example WinSCP was used for the file transfer


2. From cdom use command "ls" to verify they are there
3. [admin@LabCM6HPDL360Cdom tmp]$ ls
vsp-6.2.1.0.9.iso
vsp-patch-6.2.2.09001.0.noarch.rpm


4. Switch to sroot using "su - sroot"
5. move the System Platform ISO image and System Platform patch (if needed) to /vspdata. The /vspdata directory will keep files after an upgrade and has more storage capacity.
6. [root@LabCM6HPDL360Cdom tmp]# mv vsp-6.2.1.0.9.iso /vspdata
7. [root@LabCM6HPDL360Cdom tmp]# mv vsp-patch-6.2.2.09001.0.noarch.rpm /vspdata
8. Change directory to /vspdata
9. [root@LabCM6HPDL360Cdom tmp]# cd /vspdata
10. Use command "ls" to verify flies are in /vspdata
11. [root@LabCM6HPDL360Cdom vspdata]# ls
vsp-6.2.1.0.9.iso
vsp-patch-6.2.2.09001.0.noarch.rpm

12. Now create a folder in /vsp-template
13. [root@LabCM6HPDL360Cdom vspdata]# mkdir /vsp-template/vspUpgrade
14. Now within /vspdata mount the System Platform upgrade ISO to the /vsp-template/vspUpgrade directory using command below
15. Mount -o loop /vspdata/vsp-6.2.1.0.9.iso /vsp-template/vspUpgrade

16. Now log into the cdom webconsole and choose platform upgrade under server management

17. Next choose SP Server and leave the platform upgrade URL path as the default /vsp-template/

18. Now choose VSP.ovf and hit select

19. verify the new Console domain and Domain-0 version and choose upgrade

20. Monitor the progression status to ensure upgrade completes

21. After the Console domain reboots log back in webconsole and choose to commit and complete the upgrade