Updating your nim image


17-Jan-2017 14:26

SIGCHLD Restarts the service in case the service ends abnormally. Checking an updated LPP source consists of 3 steps, first check the lpp source, then remove duplicate packages, and then recheck the lpp source. com 6.1.0.0 # Common Hardware Diagnostics rte 6.1.0.0 # Hardware Diagnostics ...... Checking filesets and network boot images for SPOT "spot_5300_05". As far as I know there is no strict way of determining the oslevel including the fixpack from the SPOT resource.

Service Command Description Status xmquery /usr/bin/xmtopas xmtopas -p3 active wsmserver /usr/websm/bin/wsmserver wsmserver -start active time internal active daytime internal active time internal active daytime internal active ntalk /usr/sbin/talkd talkd active exec /usr/sbin/rexecd rexecd active login /usr/sbin/rlogind rlogind active shell /usr/sbin/rshd rshd active telnet /usr/sbin/telnetd telnetd -a active ftp /usr/sbin/ftpd ftpd activebash-3.2# lssrc -ls inetd Subsystem Group PID Status inetd tcpip 135338 active Debug Not active Signal Purpose SIGALRM Establishes socket connections for failed services. I don't know for sure if the checking is necessary, but it only takes a few seconds, so better safe then sorry. ----------------------------------------------------------------------------- BUILDDATE Verification ... ----------------------------------------------------------------------------- Verifying build dates..FILESET STATISTICS ------------------ 349 Selected to be installed, of which: 349 Passed pre-installation verification 23 Additional requisites to be automatically installed ---- 372 Total to be installed ...... However, you can determine the technology level of the spot, which you can use to search for installed filesets.

- Running the commands needed to install the NIM client.

You can think of it as having multiple "mini-systems" on your NIM master, because each SPOT is its own /usr filesystem.

In case you need to increase the storage space needed for NIM data perform the following steps: Installation Summary -------------------- Name Level Part Event Result ------------------------------------------------------------------------------- bos.master 6.1.3.0 USR APPLY SUCCESS bos.master 6.1.3.0 USR COMMIT SUCCESS ---- end ---- Note: Before starting the initialization, make sure the NIM master can be resolved with the nameserver, for the A-record, as well as for the reverse record. Subsystem PID is 274446.bash-3.2# lsnim master machines master boot resources boot nim_script resources nim_script net_10_1_0_0 networks ent bash-3.2# lsnim -l master master: class = machines type = master max_nimesis_threads = 20 comments = machine which controls the NIM environment client_reg = no platform = chrp netboot_kernel = mp if1 = net_10_1_0_0 ms-nim01.company.local 001A6444B9C8 cable_type1 = tp Cstate = ready for a NIM operation prev_state = Mstate = currently running serves = boot serves = nim_script master_port = 1058 registration_port = 1059 reserved = yes bash-3.2# lsnim -l boot boot: class = resources type = boot comments = represents the network boot resource Rstate = ready for use location = /tftpboot alloc_count = 0 server = master reserved = yes bash-3.2# lsnim -l nim_script nim_script: class = resources type = nim_script comments = directory containing customization scripts created by NIM Rstate = ready for use location = /export/nim/scripts alloc_count = 0 server = master reserved = yes bash-3.2# lsnim -l net_10_10_0_0 net_10_1_0_0: class = networks type = ent Nstate = ready for use prev_state = information is missing from this object's definition net_addr = 10.10.0.0 snm = 255.255.0.0 routing1 = default 10.10.1.2bash-3.2# cat /etc/niminfo # nimconfig export NIM_NAME=master export NIM_CONFIGURATION=master export NIM_MASTER_PORT=1058 export NIM_REGISTRATION_PORT=1059 export NIM_MASTER_HOSTNAME=ms-nim01.company.localbash-3.2# lssrc -ls inetd Subsystem Group PID Status inetd tcpip 135338 active Debug Not active Signal Purpose SIGALRM Establishes socket connections for failed services. Note that you don't need to provide the name of the directory for the location, it will automatically create a directory by the name of the SPOT object. ----------------------------------------------------------------------------- Pre-installation Verification... ----------------------------------------------------------------------------- Verifying selections..Verifying requisites..Results... SUCCESSES --------- Filesets listed in this section passed pre-installation verification and will be installed.

NIM initialization is done through the nimconfig command: bash-3.2# nimconfig -a netname=net_10_1_0_0 -a pif_name=en0 -a netboot_kernel=mp -a cable_type=tp -a client_reg=no 0513-071 The nimesis Subsystem has been added. SIGHUP Rereads the configuration database and reconfigures services. Results: ======================= start list ============================= Java14.license.1.4.2.0. bash-3.2# nim -o define -t spot -a server=master -a location=/nim/spot/ -a source=lpp_6100_00_01 -a installp_flags=-a Qg spot_6100_00_01 Creating SPOT in "/nim/spot/" on machine "master" from "lpp_6100_00_01" ... Selected Filesets ----------------- bos.64bit 6.1.0.1 # Base Operating System 64 bit... Software changes processed during this session require any diskless/dataless clients to which this SPOT is currently allocated to be rebooted.

Because I have a separate LUN for NIM, it's possible to increase the filesystem when necessary. rm: removing /nim/lpp_source/lpp_5300_06_07/installp/ppc/sysmgtlib.5.3.0.50. U bash-3.2# nim -o check lpp_5300_06_07 bash-3.2# lsnim -l lpp_5300_06_07 lpp_5300_06_07: class = resources type = lpp_source arch = power Rstate = ready for use prev_state = verification is being performed location = /nim/lpp_source/lpp_5300_06_07 simages = yes alloc_count = 0 server = master If you want to work with different kind of versions you have to create a non-/usr SPOT. Be sure to check the output from the SPOT installation to verify that all the expected software was successfully installed.

That way, I'll always keep one filesystem and volumegroup for booting, and one of each for the NIM data. U ======================== end list ============================== lppmgr: Building table of contents in /nim/lpp_source/lpp_5300_06_07/installp/ppc .. rm: removing /nim/lpp_source/lpp_5300_06_07/installp/ppc/Java14.license.1.4.2.0. It is recommended to use a NIM lpp_source to create it from. You can use the NIM "showlog" operation to view the installation log file for the SPOT.

updating your nim image-70

Free live video chat adult

Jul 01 2009 Daemon Daemon Information bootpd[430226]: bootptab mtime is Wed Jul 1 2009 Jul 01 2009 Daemon Daemon Information bootpd[430226]: Finished processing boot request. If you want all software to be in the LPP_source you can add all sources like this: Keep cd1 in the drive and: bash-3.2# nim -o define -t lpp_source -a server=master -a location=/nim/lpp_source/lpp5300_05 -a source=/tmp/5300-05/cd1/ lpp_5300_05 Preparing to copy install images (this will take several minutes)... If it does exist, we verify that tftp access to the /tftpboot directory is not restricted in the /etc/file.

To do so, create the file /etc/and define the correct directories: bash-3.2# cat /tftpboot/test bash-3.2# touch /tftpboot/test2 bash-3.2# tftp -r - 0 /tftpboot ...testtest2Received 64 bytes in 0.0 seconds bash-3.2# bash-3.2# tftp -o - 0 /tftpboot/ms-lpar01.company.#------------------ Network Install Manager --------------- # warning - this file contains NIM configuration information # and should only be updated by NIM export NIM_NAME=ms-lpar01 export NIM_HOSTNAME=ms-lpar01.company.local export NIM_CONFIGURATION=standalone export NIM_MASTER_HOSTNAME=ms-nim01.company.local export NIM_MASTER_PORT=1058 export NIM_REGISTRATION_PORT=1059 export NIM_SHELL="nimsh" export NIM_MASTERID=000153BAD400 export NIM_LICENSE_ACCEPT=yes export RC_CONFIG=rc.bos_inst export NIM_BOSINST_ENV="/../SPOT/usr/lpp/bos.sysmgt/nim/methods/c_bosinst_env" export NIM_BOSINST_RECOVER="/../SPOT/usr/lpp/bos.sysmgt/nim/methods/c_bosinst_env -a hostname=ms-lpar01.company.local" export SPOT=ms-nim01.company.local:/nim/spot/spot_5300_05/usr export NIM_CUSTOM="/../SPOT/usr/lpp/bos.sysmgt/nim/methods/c_script -a location=ms-nim01.company.local:/export/nim/scripts/ms-lpar01.script" export NIM_BOS_IMAGE=/SPOT export NIM_BOS_FORMAT=spot export NIM_HOSTS=" 127.0.0.1:loopback:localhost 10.10.3.9:ms-lpar01.company.local 10.10.3.7:ms-nim01.company.local " export NIM_MOUNTS=" ms-nim01.company.local:/nim/lpp_source/lpp_5300_05:/SPOT/usr/sys/inst.images:dir " export ROUTES=" default:.10.1.2 " Received 1283 bytes in 0.0 seconds bash-3.2# tftp -r - 0 /etc Error code 2: Access violationbash-3.2# nim -o define -t lpp_source -a server=master -a location=/nim/lpp_source/lpp_6100_00_01 -a source=/dev/cd0 lpp_6100_00_01 Preparing to copy install images (this will take several minutes)... 611 - Remote mount of NFS file system failure LED 611 hangs occur when the client machine is unable to mount a resource from the NIM master/resource server.