Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CM6.3 install tips/tricks?

Status
Not open for further replies.

lopes1211

Technical User
Jan 11, 2002
2,835
US
Anyone have any tips/tricks to speeding this up? I have quite a few of these to do an it seems like timing myself for:

sys plat
sys plat patch
cm template
kernel patch
plat patch
cm service pack

It's putting me at about 3.5 hours. Does that seem to be the norm or are they any speedier tips for the base install?

-CL
 
I have the same issue with a bunch of these to do. Is your list above the actual order in which to do everything? I was looking for that as well.
 
That's the order I've been using but open to any suggestions.

-CL
 
Are you just upgrading existing or are they brand new? I have existing 6.0.1's , but have some spare s8300's and a GW, so was going to build one, ship to site, swap, reformat the one that comes back etc..
 
Some new, some 5.2's which is essentially the same as a new install. none are existing R6.

Oh, the joy continues. I was doing the Kernal patch last but I'm working on a system in the order above. All was well and got to the Kernal install. Went fine, committed and shows active in CM and system plat. I went to move on to the other CM patches but now when I go to "download files", the option to "install this file on local server" is missing. Just rebooted CM and no change. Will rollback the kernel patch and see what happens. uggg.

-CL
 
You can use the old way of patching CM to not use the System Platform webpage. I find it a bit quicker
 
I'm still training myself on this but I think you can only do the CM Service Pack via the CM patching interface. The CM Kernel and PLAT gives an error in CM saying something like "this must be installed via system platform"

-CL
 
The AVAYA notes on installation of these is pretty easy to follow. At least for the things I've done so far.. upgrade SP and SMGR templates. Haven't done a CM yet with all those patches.
 
There is no way to speed this up on a s8300D it is what it is... the new system platform patch 6.3.4 is brutal, that alone takes about an hour.

 
Just trying to nail down the exact file sequence. Are you just installing base cm6.3 or going to 6.3.6?

SP -- 6.3.0.0.18002
CM -- 6x.03.0.124.0

This is where I'm confused based on your order above.. The Kernel patch: KERNEL-2.6.18-348.AV5 looks like it has to be installed over the base CM install running on the base SP install. The PLAT patch also looks like it gets installed on top of the base installs.

The service packs then look like they upgrade SP to vsp-patch-6.3.4.08007.0 and CM to (03.0.124.0-21591



 
My 3rd item is the CM template (after system platform and it's vsp patch). That's the base CM install. Then the kernel, PLAT, and Service Pack.

I'm going to reload another over the weekend. I see on another working S8300 from yesterday that was installed as Service Pack, PLAT, then Kernel, the "install files on server" checkbox disappeared from that CM as well. I registered both of these to my lab CM 5.2.1. I'm starting to wonder if this gets disabled after registering to a pre-R6 CM since this type of configuration is just used to aid in a migration and not something that should/would be patched after already getting a CM5 translation file. Will post back on Monday with the results.

-CL
 
even if the "install files on server" disappeared, winscp to /var/home/ftp/pub with the appropriate permissions and you can "update_unpack" and "update_activate". I've done it without problem.
 
it just seems from reading all the release notes that the kernal and PLAT install over the base SP/CM install. I didn't see in the docs about the SP vsp being installed 2nd. It references 6.3.0.0.18002. Probably doesn't matter.
 
99.99% sure it can't/doesn't matter. If it did work that way, you would only be able to patch the kernel and plat once while you had a base install. Once CM and system platform was updated....then 3 months goes by.....you certainly you would not reload a base system platform and CM template when the next kernel or plat update was released. Loading another 8300 now to test some theories.

-CL
 
Kernel and platform patches are for the underlying linux redhat OS running the CM virtual machines. They're purpose is to address known vulnerabilities. The CM service packs actually affect how CM processes calls.

All the System Platform patch management page does is load your patches into cdom and run them on the virtual machines they're intended for. You can run/apply/execute those patches on each virtual machine on your own. In CM, it's update_unpack and update_activate, in System Manager, you just execute the smgr-patch.bin file, in cdom for system platform you "rpm -ivh vsp-patch-noarch.rpm". I've applied most of these patches lately, and haven't had any issues executing them independently on each virtual machine.

So, to lopes's original question of how to speed it up - I do it by not executing them consecutively through System Platform, I execute them concurrently on each virtual machine.
 
From a very trusted AVAYA tech, just to add additional opinion:

1. System Platform base – 6.3.0.0.18002
2. System Platform Service Pack – vsp-patch-6.3.4.08007.0
3. CM Template base – 6x.03.0.124.0
4. CM Service Pack – 03.0.124.0-21591
5. Kernel Patch – 2.6.18.348.AV5
6. PLAT – PLAT –rhel5.3.3014.tar


Also, is anyone running 6.3.6? is it safe, if that's the correct word?


 
wpetilli's order is good. We just updated 32 S8300Ds from 6.0 to 6.3.6 using that order with no issues. I found that removing the CM template and loading it fresh to be a faster process than upgrading it. You will just have to reprogram the template and the CM settings, which is not a big deal.
 
Ok, I've just finished my first of these. You were not kidding that this took hours. I did a complete reformat, instead of an inplace upgrade. Swapped this newly upgraded blade with one of my production ones, came right up, registered and took translations from the main. What I am noticing though is System Platform (Cdom)is much slower than my previous version. Anyone notice this? To switch to different sections on the web interface is just really slow. Logging directly into CM is fine.. it flies, but SP.. geez
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top