Upgrading from QDX 3.8.1 to 5.3

[David Teh]

Hi folks,

Need suggestions!!!

Currently running QDX 3.8.1 on AIX 5.1.

QDX 3.8.1 is not supported on AIX 5.2.

Machine is IBM P650 which supports AIX 5.1 and 5.2.

New machine is IBM P5 which supports AIX 5.2 and 5.3. AIX 5.1 not supported on this machine, so I can’t install QDX 3.8.1 first.

If I want to be running QDX 5.3 on the new machine, any suggestions on the upgrade path?

Topic

[Steve Carter]

Assuming I remember the App/OS version matrix correctly, I would do the following:

Upgrade 3.8.1 to 5.3 on the current platform.

Upgrade AIX from 5.1 to 5.2.

Cutover to new platform.

I don’t think you have very many choices with the environment that you’re in.

Good luck!

Steve

[David Teh]

Thanks Steve.

Just wondering, if anyone installed QDX 3.8.1 on AIX 5.2, even though not officially supported?

Steve Carter wrote:

Assuming I remember the App/OS version matrix correctly, I would do the following:

Upgrade 3.8.1 to 5.3 on the current platform.

Upgrade AIX from 5.1 to 5.2.

Cutover to new platform.

I don’t think you have very many choices with the environment that you’re in.

Good luck!

Steve

[Russ Ross]

Our servers are IBM P570s running AIX 5.2 and my latest aproach to meeting the challenge of upgrading more than cloverleaf all at once has been to use LPARs.

In lay terms I think of LPARs as virtual machine(s) running on the same physical hardware that PROD is on.

I have found them very handy for this sort of thing.

Russ Ross
RussRoss318@gmail.com

[Richard Hart]

David.

last year we migrated from

  AIX 4.3.3  Cl 3.5.5

to

  AIX 5.3     Cl 5.4.1

Our configuration is to have one Cloverleaf site connected to one application.

For example a PAS application communicates messages to a Cloverleaf ‘pas’ site, which communicates messages to a Cloverleaf ‘data repository’ site (performing the translations) and this communicates messages to the ‘data repository’.

We had about 70 Cloverleaf sites and, in simple terms, we created ‘cross over’ sites and ‘pipe sites’ to aid the migration

The ‘cross over’ site connected Cloverleaf Sites on the two servers.

The ‘pipe’ site’ replaced an ‘application site’ on the old sever – where an application connected to Cloverleaf –  and connected to the application site on the new server.

With this process in place, we were able to migrate Cloverleaf sites to the new server without the need to update many applications that sent or received messages.

All changes were to the ‘cross over’ and ‘pipe’ sites.

We migrated the Cloverleaf sites over one week and then requested applications to migrate to the new server (a new DNS) and we just turned off the appropriate ‘pipe’ site.

[Author]

Replies