System Platform upgrade 6.3.7

[wpetilli]

2 questions:
1. If running on an LSP CM6.3.5 on top of SP 6.3.1.08002.0 and want to upgrade to CM6.3.13 / SP6.3.7 is there a way to remotely upgrade SP? The doc has you downloading the .iso, burning to dvd and doing a platform upgrade. These sites are all remote and looking for a way to get this done painlessly?

2. I inherited a new site that is LSP'd off my core and running what looks like cm6.3.100. If all my other sites are on or close to 6.3.13 does this site require the template to be deleted and the correct one installed? or is it permitted/possible to bring it to 6.3.113 with the core CM running 6.3.13?

 

[kyle555]

Not sure about #2, but for #1 and template upgrades...

If you copy the .iso to /home/admin, then as root...
mkdir CMDISC
mount -o loop /home/admin/yourCD.iso /home/admin/CMDISC
mkdir /vsp-template/VSP
cp -r /home/admin/CMDISC /vsp-template/VSP

That's how I've done platform upgrades remotely for 6.0-->6.2 and 6.3. Haven't tried this latest SP, but I can't see why anything would be different.

 

[dleuen]

You can perform a Platform Upgrade remotely via HTTP if you have an HTTP server available which is accessible from the LSPs.

On the HTTP server:
Mount the cdrom image and copy the VSP.ova directory to somewhere on your HTTP server.

mount -o loop yourCD.iso /tmp/cd
cp -r /tmp/cd/VSP.ova /var/

http://www/html/sysplat/6.3.7

(or wherever your webserver locates its files, check with a browser to be sure you can see the VSP.ova directory)
umount /tmp/cd

Then from the LSP cdom webconsole
Server Management->Platform Upgrade
Select HTTP as the "From" drop down menu and enter the URL to the VSP.ova directory you copied above, click search then select VSP.ovf as the upgrade template.

I would recommend that you do not copy the ISO image nor any other large files to /home/admin if you do follow kyle555's advice because any files in /home/admin will get added to your backup and that can obviously make backups very slow or run you out of space. I think there is an exclusion now for .iso files but not sure.

 

[wpetilli]

I copied the .iso to a web server running IIS. I pointed a website to the vsp.ova directory and I'm unable to browse to this. Previously this website was being used for 96xx phones to pull fw and 46xx.settings file. When I point the website back to the original files I can browse directly to the 46xx.settings file.

 

[dleuen]

Were you able to select the VSP.ovf file from System Platform's Platform Upgrade menu and perform the upgrade?

 

[kyle555]

this is why i just mount the iso in cdom and copy it to /vsp-template!

 

[wpetilli]

I don't get to the point of selecting the file. I put in the url of my webserver and it fails to find it. Even from my own web browser I don't see any content.

I'll try your way Kyle555.. I had read in the doc they don't recommend doing that, but these are remote site LSP's and I don't do SP backups of them.

 

[kyle555]

just make sure to md5 everything and umount the iso and rm -rf the .iso from /home/admin before doing it so the backup doesn't run out of space.

 

[wpetilli]

Thanks, I got it working. The first attempt the upgrade process started and froze. I wasn't able to hit the web browser, but was able to reboot via CDOM CLI. After the reboot I was prompted to commit the upgrade, but there was nothing there. Started it again and that time it went through the process, but failed on the backup step (I didn't unmount and remove the .iso in time). The 3rd attempt went smooth.

For CM, I originally had the base 6.3.0.0.1105 with the 03.0.124.0-21460 patch (6.3.5). I just installed the 6.3.13.0-SP13 patch over the current. After going into patch management I see the -21460 patch went 'not installed', the CM6.3.13 patch as 'active' and then another patch that I didn't apply appeared -22038 'Make CMSA changes permanent' as active. Is that normal?

 

[wpetilli]

If connected via the services port of the s8300 and connecting to 192.13.11.6, is that CM, CDOM or SDOM? I want to do an upgrade to this unit w/o being on the network and when logging in with WINSCP I don't know what I'm actually connected to. I'm trying to upgrade SP, so want to be on CDOM.

 

[losfep]

you will be connected to CDOM via the services port if ip forwarding was enabled when system platform was installed.

 

[kyle555]

cat /etc/hosts in whatever you're in, or do an ifconfig - you'll know by IP. But, like losfep said, with IP forwarding enabled, and you using 192.11.13.6 as the gateway on your laptop, you should be able to reach cdom via the corp LAN IP defined.

 

[wpetilli]

Ok, thanks. I copied an .ISO to /home/admin, created a new directory... basically followed the above steps all the way through and when launching the webbrowser and choosing platform upgrade the new directory/OVF is not there. Worked on all the other sites I've done this way, only this is the first time I'm doing this via the services port and while the unit is not on the network.

 

[wpetilli]

I attempted upgrading SP 6.3.4 to 6.3.7 on a DL360 G7. I used a CD and did a platform upgrade.. the process completed successfully, rebooted and once I re-logged into the web there was an acknowledgement that the upgrade was rolled back because the system failed to boot properly. Went through the process a 2nd time,, got all 100% completes for all the steps and after the reboot I received the same message. Scouring around and not finding anything on this one. Anyone seen this before?

 

[kyle555]

What System Platform 6.3.4 release?

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

 

[wpetilli]

that psn references that issue is fixed in a 6.3.4 patch, which I installed successfully. I then re-attempted the 6.3.7 platform upgrade and got the same message about system failed to boot properly. Should I just keep installing the smaller incremental patches? This is a spare server I'm playing with to prepare to upgrade an ESS. The ESS is running SP 6.0.3.9.3, which the docs shows I can go straight to 6.3.7. Since that is a prod system, i'm trying to avoid running into this kind of thing.

 

[montyzummer]

Noticed that you started off saying you are on a LSP to begin with , here is the issue you may face with the base load on a S8300 that you ref

https://support.avaya.com/ext/index?page=content&id=SOLN285517&group=UG_ENTITLED_CUSTOMER

Specifically between 6.3.0.0.18002 to 6.3.6

Then further down you ref you are looking at an ESS going on SP 6.0.3.9.3 to 6.3.7 , on that basis there are also upgrade paths you need to follow, the advice that the guys have given you about copying files to the specific directorys and mounting etc all look good to me , i always copy to the /tmp dir first (already been suggested) and mount from there , so i really think you have an upgrade path issue that anything else.
Can you let us know what your actual prod upgrade will be ...from what to what on which platform and from there a correct suggestion can be made , as there are succinct differences in regards to what to apply and where based on LSP/ESS , i just don't want you to go round the houses as Avaya are stipulating different things based on individual platform type ....and also based on going from what to what , unless i have missed something we seem to have both two different platforms and build to build mentioned.


ACSS (UC/SBCE/SM/SME)

Not that they mean a thing anymore , get a brain dump pass the test crash the system.

 

[wpetilli]

The very beginning of the thread was upgrading LSP s8300's, which the process everyone posted works great. I now have a spare DL360 server that has an old SMGR template with SP 6.3.4. I want to remove the SMGR template, upgrade SP to 6.3.7 and then install a CM ESS template. For this I have physical access to the server, so I'm inserting the SP 6.3.7 disc and running a platform upgrade. It goes all the way through the process, reboots and when I get access to the CDOM I'm getting the rollback message and the error I posted.

While it's not apples to apples I do have an upcoming prod upgrade of a current ESS that is running on a dl360 with SP 6.0.3.9.3/ CM 6.0.1 that I was planning to upgrade to SP 6.3.7 the same way.

 

[jimbojimbo]

There have been a variety of issues with System Platform upgrades. Especially around 6.3.4-6.3.6. From 6.3.4 upgrade to 6.3.5 then upgrade to 6.3.7. This should work. I have had to go in and manually remove the RPM on several servers since Tomcat breaks and you lose access to the CDOM console completely.

Before running the upgrade, clean up any directories such as /home/admin and run a df -h to see what you have for partition space. Look to place the ISO image on a partition with sufficient space.

Also look at the actual hardware version and disk size. There are a few "one off" servers with smaller drives. These should be early R1 versions of the S8300D (since you are on 6.3.4 you should be on a D). You may not be able to upgrade them. I don't think I ever saw a PSN on this.

 

[wpetilli]

Thanks- will give that a go. So any pre-SP6.3.4 should be cleared to go to 6.3.7? I guess I can try it and rebuild an s8300, but this work I'm doing is on a dl360 g7.