AIX

Thank you very much.
Yes I can get downtime for cluster

---------- Post updated 05-07-14 at 08:31 AM ---------- Previous update was 05-06-14 at 02:01 PM ----------

Hi,

Thank you ver much.
Yes i can get a downtime for the cluster

You do not even need a downtime for the cluster, provided that your SAN disks allow for concurrent access (check with "lsvg <vgname>" if it is "enhanced concurrent capable" and if it is opened in concurrent mode).

If this is indeed the case:

- attach the new disks to both nodes, run "cfgmgr" on both nodes to create the new devices. Check with "lspv".

- add the new volumes to your VGs on the active node:

Code:

extendvg <volumegroup> <hdisk-device>

- mirror the old disks to the new disks. Switch off automatic sync and do a "syncvg" afterwards, it is usually much faster. Use the "-P" switch to let it run in parallel:

Code:

mirrorvg -s <volumegroup> <hdisk-device>
syncvg -P <##> -v <volumegroup>

- after the syncing is finished do a "learning import" on the passive node. The passive node knows only the old disk to be in the VG so far, so use this to reimport the VG definition from:

Code:

importvg -L <volumegroup> <old hdisk-device>

- on the active node unmirror the VG, removing the mirror on the old disk, then move that old disk out of the VG:

Code:

unmirrorvg <volumegroup> <old hdisk-device>
reducevg <volumegroup> <old hdisk-device>

- again do a "learning import" on the passive node to sync the VG definition across cluster nodes, this time from the new disk:

Code:

importvg -L <volumegroup> <new hdisk-device>

Remove the zones from the fabric and delete the old hdisk-devices. When running "cfgmgr" again they should not be discovered any more.

I hope this helps
bakunin

Hi,

consider the 3par Implementation Guide for AIX.

302 Moved Temporarily

Also check your environment with HP SPOCK site:
HP Storage Single Point of Connectivity Knowledge - SPOCK

thank you