Rick <rmunn@eastlink.ca> wrote in message news:<A90Rb.3811$Ja2.51225@nnrp1.uunet.ca>...
> Hey Pete, a quick thought...did you assign a unique SCSI ID to your SCSI
> cards? (e.g. Node1 SCSI ID 6. Node 2 SCSI ID 5)
>
> Rick
>
> Pete's wrote:
>
> > Vital Info:
> > 2 Node cluster, p660-6h1's running AIX 4.3.3 ml09 with HACMP 4.4.1.
> > It has shared SCSI disks using 2 2104-DU3's with 10 total Physical
> > Volumes. Note, I know that my OS and HA software is unsupported right
> > now and I am planning on upgrading.
> >
> > Currently 'Node 1'(which is the primary node) has the cluster
> > resources and is running fine.
> >
> > 'Node 2'(which is the secondary) is in the cluster, but, has lost all
> > information regarding the shared disk, i.e. PVID's and Volume Group
> > information is gone. Just a note, was troubleshooting via diag and it
> > had issues with a scsi card which happened to be attached to shared
> > disk. Diag recommended to remove the device and run cfgmgr which I
> > did and should not have(I knew better not too). Ok, I need to get the
> > configuration corrected and the following is how I plan on doing it:
> >
> > On Node 2
> > 1. Assign PVID's to the shared disk since they no longer have any
> > assigned.
> > 2. Shutdown the cluster software.
> > On Node 1
> > 3. Shutdown the cluster software
> > 4. exportvg vg01
> > On Node 2
> > 5. importvg vg01
> > 6. varyoffvg vg01
> > On Node 1
> > 7. importvg vg01
> > 8. varyoffvg vg01
> > 9. Start the cluster software.
> > On Node 2
> > 10. Start the cluster software.
> >
> > I tried this before except that the PV's did not have id's assigned
> > and it failed(I'm assuming it failed because of no pvid's).
> >
> > Question(s), Am I missing anything in the steps outlined above?
> > Should assign the pvid's, skip the exportvg/importvg and try a
> > failover and see if the 'Lazy Update' update the volume group
> > information? Is there anything I should watch out for?
> >
> > TIA
> > Pete's

Yep, if you don't and you boot up, spurious events start happening
when Node1 has the disk resources. Ran into this on one card when I
first brought up this cluster because I forgot to change it on one
adapter, that was about 1.5yrs ago.

Thanks,
Pete's