Sponsored Content
Operating Systems AIX HELP: Howto update an lpp_source in NIM Post 302471822 by tgphelps on Monday 15th of November 2010 09:17:01 AM
Old 11-15-2010
Thank you for your replies. Actually, I am more concerned about the SPOT than the lpp_source, since I use my NIM server to recover an AIX server if the rootvg were to crap out, and in our annual disaster recovery test. Here's the specific scenario I'm concerned with right now:

1. All my servers are running 5.3.0.11. I have an lpp_source and a SPOT which exactly match this AIX level. I also take regular mksysb's to the NIM master, so that in a disaster situation, I can recover my NIM master from a mksysb DVD and backups, and then be ready to recover all other AIX servers from mksysb's on the NIM master.
2. I want to update them all to the latest 5.3.0.12. This is no big deal, since I have downloaded the required patches, and I can simply do a "smitty update_all" on each of them, if I want, and not even worry about the NIM.
3. After the 5.3.0.12 upgrade is done, I want to still be able to install/recover any AIX server from the NIM master, by using the SPOT and mksysb backup there.

QUESTION: How do I best accomplish number (3)?
The advice I have from a Known Good AIX Person (KGAP) is that the SPOT must be of a version NO OLDER than the mksysb I want to recover with it. According to the KGAP, I should NOT try to update my SPOT, but should order a full installable version of AIX to match what all my servers are running, and build an lpp_source and SPOT from that. This seems terribly slow and inefficient, and I am hoping there's a better way. I'd hate to have to order a full AIX DVD set every time I upgrade from 5.3.0.n to 5.3.0.(n+1). So, tell me, please: How do you keep your SPOT in sync with all your AIX servers?
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Howto upgrade AIX to Level Update 4320-02_AIX_ML

Hi, Installing a new version of PROGRESS DB software 9.1c requires us to upgrade AIX to Level Update 4320-02_AIX_ML ( http://techweb.progress.com/kbase/19779 ) How would a do this savely. This is what i have already. 1) take a system backup. 2) find the level we are on right now. #... (1 Reply)
Discussion started by: progressdll
1 Replies

2. AIX

NIM ML update

My nim master have to updated with new ml 06 . how do i know which version my nim master is currently? how to update nim -o update -a packages=all -a source=/software/aix52ml06 /lpp_sourse Is this ok.. ?? thanks govind.g (1 Reply)
Discussion started by: govindarajan
1 Replies

3. AIX

migrate NIM server through NIM installation

I try to migrate a NIM server from one server to another. I try to do a mksysb on NIM server restore the NIM server's mksysb to a client through NIM installation shutdown NIM server start newly installed client as NIM server Does anyone do this before? who can give me some suggestion? (1 Reply)
Discussion started by: yanzhang
1 Replies

4. AIX

Back up a client NIM from nim master

Hello everyone Im trying to backup a nim client from nim master but I got this message COMMAND STATUS Command: failed stdout: yes stderr: no Before command completion, additional instructions may appear below. 0042-001 nim:... (2 Replies)
Discussion started by: lo-lp-kl
2 Replies

5. AIX

Add a bundle to a lpp_source

Hi. I forgot a bundle (X11.dt) in the lpp_source (base OS AIX 7.1). The bundle is now in the CD drive, I need to add it permanently in the lpp_source. What do I have to do ? - copy (where ?) bundle on my NIM server (how to determine what files to copy to have all elements of the bundle ?) ?... (1 Reply)
Discussion started by: stephnane
1 Replies

6. AIX

mksysb, lpp_source and SPOT version matching

Hi all, I'm trying to understand the requirements for AIX version matching between a SPOT, LPP_SOURCE and my mksysb images. I have a NIM server installed, and I've used it to install new LPARs both from the LPP_SOURCE and from mksysb files. These were based off 7100-00-01. Recently I created... (1 Reply)
Discussion started by: SamuraiMark
1 Replies

7. AIX

[Howto] Update AIX in HACMP cluster-nodes

As i have updated a lot of HACMP-nodes lately the question arises how to do it with minimal downtime. Of course it is easily possible to have a downtime and do the version update during this. In the best of worlds you always get the downtime you need - unfortunately we have yet to find this best of... (4 Replies)
Discussion started by: bakunin
4 Replies

8. AIX

Problem in communication nim client with nim master

Hello, I have an AIX6.1 machine which is a nim client to my nim master which is also AIX6.1 machine. I had some problem to perform an installation on my client using smit nim . i removed /etc/niminfo file in order to do the initialization again but when i run the command niminit -a name=client... (0 Replies)
Discussion started by: omonoiatis9
0 Replies

9. AIX

How to know NIM name from NIM client?

Friend's, I was playing around with NIM in my environment & had a quick question in mind which I didn't/couldn't find answer to, which is -- how to find the name of the NIM server sitting on the NIM client? All leads to the answer would be much appreciated, many thanks! -- Souvik (2 Replies)
Discussion started by: thisissouvik
2 Replies

10. AIX

Update vs. install media, and LPP_SOURCE naming

Hello all, Relative AIX novice here: I'm trying to clarify the naming of AIX install vs. update media, and how best to name my lpp_sources on my NIM server. An example: I have two sets of DVDs from IBM (ordered via Entitled Software Support) sitting in front of me for 7100-03-04. One set... (1 Reply)
Discussion started by: dmark
1 Replies
PERLOS400(1)						 Perl Programmers Reference Guide					      PERLOS400(1)

NAME
README.os400 - Perl version 5 on OS/400 DESCRIPTION
This document describes various features of IBM's OS/400 operating system that will affect how Perl version 5 (hereafter just Perl) is compiled and/or runs. By far the easiest way to build Perl for OS/400 is to use the PASE (Portable Application Solutions Environment), for more information see http://www.iseries.ibm.com/developer/factory/pase/index.html This environment allows one to use AIX APIs while programming, and it provides a runtime that allows AIX binaries to execute directly on the PowerPC iSeries. Compiling Perl for OS/400 PASE The recommended way to build Perl for the OS/400 PASE is to build the Perl 5 source code (release 5.8.1 or later) under AIX. The trick is to give a special parameter to the Configure shell script when running it on AIX: sh Configure -DPASE ... The default installation directory of Perl under PASE is /QOpenSys/perl. This can be modified if needed with Configure parameter -Dprefix=/some/dir. Starting from OS/400 V5R2 the IBM Visual Age compiler is supported on OS/400 PASE, so it is possible to build Perl natively on OS/400. The easier way, however, is to compile in AIX, as just described. If you don't want to install the compiled Perl in AIX into /QOpenSys (for packaging it before copying it to PASE), you can use a Configure parameter: -Dinstallprefix=/tmp/QOpenSys/perl. This will cause the "make install" to install everything into that directory, while the installed files still think they are (will be) in /QOpenSys/perl. If building natively on PASE, please do the build under the /QOpenSys directory, since Perl is happier when built on a case sensitive filesystem. Installing Perl in OS/400 PASE If you are compiling on AIX, simply do a "make install" on the AIX box. Once the install finishes, tar up the /QOpenSys/perl directory. Transfer the tarball to the OS/400 using FTP with the following commands: > binary > site namefmt 1 > put perl.tar /QOpenSys Once you have it on, simply bring up a PASE shell and extract the tarball. If you are compiling in PASE, then "make install" is the only thing you will need to do. The default path for perl binary is /QOpenSys/perl/bin/perl. You'll want to symlink /QOpenSys/usr/bin/perl to this file so you don't have to modify your path. Using Perl in OS/400 PASE Perl in PASE may be used in the same manner as you would use Perl on AIX. Scripts starting with #!/usr/bin/perl should work if you have /QOpenSys/usr/bin/perl symlinked to your perl binary. This will not work if you've done a setuid/setgid or have environment variable PASE_EXEC_QOPENSYS="N". If you have V5R1, you'll need to get the latest PTFs to have this feature. Scripts starting with #!/QOpenSys/perl/bin/perl should always work. Known Problems When compiling in PASE, there is no "oslevel" command. Therefore, you may want to create a script called "oslevel" that echoes the level of AIX that your version of PASE runtime supports. If you're unsure, consult your documentation or use "4.3.3.0". If you have test cases that fail, check for the existence of spool files. The test case may be trying to use a syscall that is not implemented in PASE. To avoid the SIGILL, try setting the PASE_SYSCALL_NOSIGILL environment variable or have a handler for the SIGILL. If you can compile programs for PASE, run the config script and edit config.sh when it gives you the option. If you want to remove fchdir(), which isn't implement in V5R1, simply change the line that says: d_fchdir='define' to d_fchdir='undef' and then compile Perl. The places where fchdir() is used have alternatives for systems that do not have fchdir() available. Perl on ILE There exists a port of Perl to the ILE environment. This port, however, is based quite an old release of Perl, Perl 5.00502 (August 1998). (As of July 2002 the latest release of Perl is 5.8.0, and even 5.6.1 has been out since April 2001.) If you need to run Perl on ILE, though, you may need this older port: http://www.cpan.org/ports/#os400 Note that any Perl release later than 5.00502 has not been ported to ILE. If you need to use Perl in the ILE environment, you may want to consider using Qp2RunPase() to call the PASE version of Perl. AUTHORS
Jarkko Hietaniemi <jhi@iki.fi> Bryan Logan <bryanlog@us.ibm.com> David Larson <larson1@us.ibm.com> perl v5.12.1 2010-04-26 PERLOS400(1)
All times are GMT -4. The time now is 07:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy