Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2457
  • Last Modified:

how to upgrade TL or SP of the same AIX version witn nim

OK, wmp.. to finish with NIM... at least for now..

Now that I'll setup NIM pull mode, how can I upgrade my clients when a new TL or SP is released?

For example, now I have a lot of AIX6.1 TL6 SP1,  a lot of AIX 5.3 TL 12 SP2 and the nim server AIX 7.1 TL0 SP2.

How can NIM handle the upgrades for everyone? Do I have to create a new lpp with spot from the new TL or SP?

Israel.

0
sminfo
Asked:
sminfo
  • 3
  • 2
1 Solution
 
woolmilkporcCommented:
There seems to be a big misunderstanding here.

Creating mksysbs with "pull" didn't change anything in the remaining NIM environment.
 
Everything is like before. The only thing you did is (hopefully) cleaning up your /etc/exports, using nimsh instead of rsh and enabling SSL. Which way should this affect all the LPP/SPOT stuff?

Back to your Q. Didn't we discuss this earlier?
http://www.experts-exchange.com/OS/Unix/AIX/Q_26754964.html

What I basically suggested was:

- Each time a new TL/SP arrives create a new LPP source from this TL/SP. Use "nim -o define ..." to create the basic "simages" LPP version, then use "smitty nim_update_add" to add all packages from the medium to the LPP source.
- Use this new LPP source to update the SPOT.
- Use this LPP source to update your clients.
- Use the updated SPOT for mksysb restores.

You should have SPOTs for AIX 5, 6 and 7, each one at the newest available level.

In the discussion before (see link) I pointed out that you could kind of "archive" a SPOT for each TL.
This can be useful if a new TL has too severe changes.
If you must restore a client at a rather early TL  the SPOT at the "severe" TL could be "too new", so it could be better having a SPOT at the exact level.
This doesn't happen very often. I remember 5.3 TL 12 where we got a new Perl. It worked, but there were some ugly error messages.

wmp

0
 
sminfoAuthor Commented:
umm...
sorry my semi-stupid questions wmp.. I thought I could update/upgrade my clients via the "pull" mode.. I understood how to update the lpp's resources, but what I dont have clear is on once the lpp's are updated how to to update the clients via nim?
0
 
woolmilkporcCommented:
There are also the same options: push or pull. This has nothing to do with push or pull of mksysb.

You can push updates from the NIM server to the client:

nim -o allocate -a lpp_source=new_TL_lpp my_nim_client
nim -o cust -a fixes=update_all my_nim_client

(or "smitty nim_update_all")

or pull them from the NIM server while on the client:

nimclient -o allocate -a lpp_source=new_TL_lpp
nimclient -o cust -a fixes=update_all

(or "smitty nim_c_update_all")

The client must authorize the server to push (but I think that's the default anyway):

nimclient -p

wmp
0
 
woolmilkporcCommented:
Could it be that you sometimes confuse push and pull?

- If the server is the active part it pulls mksysb images from the client but pushes updates to it.

- If the client is the active part it pushes mksysb images to the server but pulls updates from it.

Sorry if this was already clear to you. I just thought I should mention it.

wmp
0
 
sminfoAuthor Commented:
OK..wmp..
thanks for your awesome answers..
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now