NIM & spot 2

[reneford]

I have a master that is at AIX 5200-05 and his "nim spot" is at AIX 5200-04. I want the "nim spot" at AIX 5200-05 so I will be able to instal my new server at AIX 5200-05.

Is there a way to "upgrade" the nim spot?
Or, the only way is to unconfigure the master and recreate the spot?

Any help will be appreciate.

 

[hfaix]

I'm new to NIM, so this is just a thought...

Can you create an lpp spot of the ML5 media. Apply the -04 spot, then apply the ML5 spot (using the lpp_source for ML5).?

 

[reneford]

Yes, what you said is working. I made it.

But, my real problem is that I want to boot my NIM client in maintenance mode using NIM. When I boot from network, I always enter in KDB (Kernel DeBugger) mode.

I think it's because my nim client is at AIX 5200-05 and the spot on my nim master(AIX 5200-05) is at AIX 5200-04).

 

[kHz]

Everything you need for NIM:

http://www.redbooks.ibm.com/redbooks/pdfs/sg245524.pdf

 

[reneford]

Is there a more recent version of this document? Because I have already this guide.

 

[plamb]

go to NIM ;perform admin tasks; mangae resources;perform operations on resources; select your lpp_source ; update just follow the rest then do the same for the spot when your done the lpp_souce and spot will have the updates; don't forget lppmgr it cleans up the lpp_source

 

[reneford]

Ok, but how can I specified that I want to update my lpp_source without specifying each software package one by one when i am in the "Add Software to a lpp_source" menu?

Do I must use the option of "INSTALLP BUNDLE containing packages to add" or there's another way to specified that I want to "Update_all" software contained in the lpp_source?

 

[sbix]

smitty nim_res_op
then select your spot resource
then select the update_all operation
then select your lpp_source resource as source of the updated software

 

[reneford]

Another question about NIM & TSM ...

With NIM, is it possible to boot over the network (yes, of course) and once the network boot as been done with success it's the "Tivoli Storage Manager for System Backup and Recovery" that appear and then, be able to choose the right "tsmvirdev (tsm virtual device)" and access my backup on server TSM (It's a Windows TSM server) to do an eventual BMR (Bare Meta Recovery)?

That's like this we actually proceed for our backup TSM and BMR but without NIM (Network boot and access to Tivoli menu and proceed with BMR). I'm trying to see if I can use NIM for this to simplified our task of BMR restore... (Especially for the bootimages, we actually manage 1 bootimage per server (each tsm client) and it works well but i found it tricky for nothing)...

I hope It's well explain... ;o)

 

[reneford]

Ok, I found it.

For those who will need this information:

We have to install sysback on the spot of the master.
Rebuild the network boot image.

Go on the smit sysback menu (always on the master), and then
go to "Add or Change a Network Boot Client".
Also, "Set TSM Network Install Client Defaults".

Finally, network boot and the client will boot and the menu "Tivoli Storage Manager for System Backup and Recovery" will appear and you will be able to select the tsm virtual device and then access to your backup on the TSM Server.

I have not complete the BMR, i Choose not to restore so I have rebooted, but I supposed the rest (BMR), will work...