Using NIM in AIX 5.3 I am wanting to update my current nim resources (lpp_source, spot) with a new technology level.  Can someone help me with the steps to do this?

I'm thinking that I would do...  smitty nim > perform nim admin tasks > manage resources > Perform Operations on Resources >   select my lpp resource i want to update> select update from the following menu > select add > then put the path to the directory containing the TL with all the .bff files?

Then I'd probably need to update my spot object as well?  not sure how to do this as I've only made NIM resources from disk so far.


Any help is appreciated

Thanks,

I finaly got the xclock and graphical smit to show up connecting with cygwin to my aix partition. thanks for your help.

i'm now trying to lauch CDE (installed by default) or another cool graphical interface.

thanks for any further help.

Well this is Linux (Suse)and not AIX
We have the 2 vio servers

But I already have found (after 2 weeks searching on the internet) the solution (on the redhat site the solution for SuSe, RH is the best  ).

You must mount by device=id and not by-name. Furthermore you have to put dm-multipath at the INITRD_MODULES in the /etc/sysconfig/kernel file.
Run mkinitrd and maybe run lilo (don't forget to change the root name in device-id instead og by-name)

Well why can't this be standard on linux on Power (maybe it is for RH)

Greetz

Raoul

For MPIO supporting AIX virtual scsi client partitions we generally have two VIO servers setup, each VIO Server provides one path, so the client partition has two vscsi adapters, one for each VIO server.

The VIO servers both see the same LUNS. One vital element is that the "reserved" access to the LUNS needs to be disabled so both VIO Servers have access to the LUNS at all times.

Properly setup the command lspath (AIX) shows e.g. hdisk0 vscsi0, hdisk0 vscsi1 as output

In summary, I would like to know more about how your VIO server is setup, virtual scsi setups, lsmap output, etc..

Does oslevel -s give the expected level after the upgrade. If yes, you should be all right. However, it is not giving the expected level, you still have some corrective work that needs to be done - as you are probably half way there.

I suspect "half-way" is where you are as you removed only the failed software, not the entire update, and committed the parts of the update that you could install.

Please verify installed versus expected software levels.

wganesh - any update on this?

1) I agree with hellonair - that it is not a good idea to be using shared storage for rootvg maintenance.
2) iirc (if I recall correctly) we advise to bring a nods being updated into a dawn status - move any active resources to the remaining node(s), stop hacmp, and start updates.

Before starting any updates on a HACMP node you need to verify that your application/service is supported in the new environment. We have situations discussed here where applications did not work after an update.

With HACMP (PowerHA) I strongly recommend doing an alt_disk_install plus update, so that should the application and update not work as expected you just need to reboot the node to restore the old situation.

Re: 3G in rootvg left. I guess I wonder how large your rootvg disks are - assumming they are mirrored. For an update, that should be plenty - as temporary storage. I generally only have 1G set aside for an update. However, I am wondering a bit about what else you have in your rootvg - if it is filling up. Applications and data should not be in rootvg, but in seperate volume groups.

I do not think it is good idea to keep the TL on the shared storage of the cluster while doing the upgrade on passive node. I hope you are going to stop the HACMP on passive node before the upgrade.

Better you keep it on a DVD or on a NFS share.

Note down your desktop IP address where you running cygwin
Open cygwin console
Run startx
This will open an xterm for you
Allow access by using the command "xhost +"
ssh to your aix system by typing
ssh <username>@<aix system name or Ipadress>
Enter your password when it prompts
Once you have connected export the display as follows
export DISPLAY=<your desktop ip>:0.0
Now try running xclock or just smit

It would better to check and confirm "lppchk -v" gives a clean output
and there are no filesets showing BROKEN state in the "lslpp -l" output

I also suggesting checking that the fileset which you have removed are no more required.