SEO

My current p5 boxes have IBM Feature code 5716
Newer p5+ boxes now ship with Feature code 1977

I plan on doing alt_disk_install to move rootvg from the p5 boxes to
the p5+ servers, and
need to know if the adapters will be a problem. Non rootvg volumes
migrated via replicated SAN software EMC Mirrorview.
I know the 5716 adapter is the Emulex LP10000 from lscfg -vpl fcs0
command:

PLATFORM SPECIFIC

Name: fibre-channel
Model: LP10000
Node: fibre-channel@1
Device Type: fcp
Physical Location: U787A.001.DPM0Y6V-P1-C1-T1

Can anyone with the 1977 adapter run the same command and post the
output?

Will physical location differences of HBA's cause alt_disk_install
issues, or will cfgmgr
resolve them? Other than faster CPU's and additonal memory, both the p5
and p5+ boxes are almost identical. Rootvg contains ONLY IBM info. San
vg's contain ONLY non IBM data.
Rootvg is on IBM internal drives, everything else external on SAN.

What other issues will "almost identical" cause for the rootvg
migration? Is alt_disk_install and/or cloning a valid strategy for this
task? TIA for your time and consideration.

alt_disk_install using a mksysb can be "iffy" depending on how the
mksysb was created. (Did the original system have the drivers
installed on it to permit the creation of a "generic" mksysb.) That
having been said, alt_disk_install does a marvelous job of interpreting
and reassigning devices for you with caveats. You need to appreciate
the fact that each platform is different in addressing adapters. You
can't assume that adapter numbers start on the left and increase on all
systems.

In your case, I would expect that you will need to install the SAN
adapter drivers prior to the creation of the alt_disk_install mksysb or
prior to cloning to ensure that you get "what you need" on the target
system. If not, install them prior to installation.

If you are taking a mksysb of your old system copying it over to your
new system (which is currently running a valid build of AIX "from the
factory" ... in other words ... with all the drivers you need)... then
all should be fine. I believe, the valid build of AIX on the system
can fill-in drivers that are needed which are not included in the
mksysb.

Worst case......
You didn't specify whether your systems were using internal storage for
rootvg. If you are using the SAN for rootvg, my suggestion above may
not work if you don't have driver support for your FC card. In that
case, you could perform an alt_disk_install via NIM (or just a NIM
install for that matter.) Or an alt_disk_install which includes the
installation of additional filesets from a directory on your system.

My two cents....

Chris Young
Consultant for Hire
614-804-8649

Chris wrote:
> alt_disk_install using a mksysb can be "iffy" depending on how the
> mksysb was created. (Did the original system have the drivers
> installed on it to permit the creation of a "generic" mksysb.) That
> having been said, alt_disk_install does a marvelous job of interpreting
> and reassigning devices for you with caveats. You need to appreciate
> the fact that each platform is different in addressing adapters. You
> can't assume that adapter numbers start on the left and increase on all
> systems.
>
> In your case, I would expect that you will need to install the SAN
> adapter drivers prior to the creation of the alt_disk_install mksysb or
> prior to cloning to ensure that you get "what you need" on the target
> system. If not, install them prior to installation.
>
> If you are taking a mksysb of your old system copying it over to your
> new system (which is currently running a valid build of AIX "from the
> factory" ... in other words ... with all the drivers you need)... then
> all should be fine. I believe, the valid build of AIX on the system
> can fill-in drivers that are needed which are not included in the
> mksysb.
>
> Worst case......
> You didn't specify whether your systems were using internal storage for
> rootvg. If you are using the SAN for rootvg, my suggestion above may
> not work if you don't have driver support for your FC card. In that
> case, you could perform an alt_disk_install via NIM (or just a NIM
> install for that matter.) Or an alt_disk_install which includes the
> installation of additional filesets from a directory on your system.
>
> My two cents....
>
> Chris Young
> Consultant for Hire
> 614-804-8649

Thanks for the input. Yes, rootvg is on internal drives. All other vg's
external in SAN.

My goal is to get my p5 boxes in location A, in a state where they
match all the requirements required in location B. (new p5+ servers,
new EMC array)

This includes drivers for the 1977 HBA's, hence the question of
differences between 5716
and 1977. This also includes bringing my p5 software up to spec for the
p5+ systems, from an EMC perspective (EMC ODM filesets, PowerPath, and
Navisphere Agent) PRIOR to making the p5 mksysb backups (or cloned
drives). Location B is 500 miles from location A, and doesn't have a
NIM environment.

The new p5+ severs have 4 internal drives. What I would like to do is
an alt_disk_install
with my p5 mksysb backup on one of the free drives on the p5+, attach
to the new SAN (already replicated and synced via MirrorView), and
importvg the vg's in the SAN. Not sure if taking a cloned hard disk
from the p5 to the p5+ system would be a better idea.
One of my p5 servers has a DVD-RAM drive, the other does not. I guess
it would be possible to create mksysb's for both on DVD, as all p5+
servers in location B have been ordered with DVD-RAM support. (feature
1993)

This is similar to a DR scenario, where the hardware is almost
identical. Unfortunately not having a remote DR provider, procedures
for doing this are not already developed and tested. Comments on how
this is handled by those with hotsite/cold site DR subscriptions
appreciated. TIA