Scribd
Upload
541 views4 pages

NIM Master Step by Step

The document describes steps for initializing and configuring NIM (Network Installation Management) on AIX including: 1. Defining resources like lpp_sources, spots, and clients on the NIM master. 2. Updating lpp_sources and customizing software on spots. 3. Registering, booting, installing, and managing client systems from the NIM master. 4. Troubleshooting tips for tasks like network booting and enabling syslogd logging.

Uploaded by

Roshan Rajan
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
541 views4 pages

NIM Master Step by Step

The document describes steps for initializing and configuring NIM (Network Installation Management) on AIX including: 1. Defining resources like lpp_sources, spots, and clients on the NIM master. 2. Updating lpp_sources and customizing software on spots. 3. Registering, booting, installing, and managing client systems from the NIM master. 4. Troubleshooting tips for tasks like network booting and enabling syslogd logging.

Uploaded by

Roshan Rajan
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 4

NIM Step By Step

Initializing Nim Master


 nimconfig -a netname=dcm -a pif_name=en0 -a cable_type=tp -a platform=chrp -a
netboot_kernel=mp
Defining lpp_source
 nim -o define -t lpp_source -a source=/dev/cd0 -a server=master -a
location=/export/lpp_source/aix61 aix61_lpp
Defining spot from lpp_source
 nim -o define -t spot -a source=aix61_lpp -a location=/export/spot -a server=master
aix61_spot
Defining lpp_source of lower version
 nim -o define -t lpp_source -a source=/dev/cd0 -a server=master -a
location=/export/lpp_source/aix51 -a packages=all aix51_lpp
Defining spot from lpp_source
 nim -o define -t spot -a source=aix51_lpp -a location=/export/spot -a server=master
aix51_spot
Defining mksysb
 nim -o define -t mksysb -a server=master -a location=/export/mksysb/cws cws_mksysb
Defining spot from mksysb
 nim -o define -t spot -a source=cws_mksysb -a server=master -a location=/export/spot
aix51ml9_spot
Defining Standalone
 nim -o define -t standalone -a platform=rspc -a netboot_kernel=up -a if1="dcm cws 0" -a
cable_type1=tp cws
 nim -o define -t standalone -a platform=rspc -a netboot_kernel=up -a if1="dcm pci 0" -a
cable_type1=tp pci
Defining lpp_source from ML
 nim -o define -t lpp_source -a source=/roshan/aix51ml02 -a
location=/export/lpp_source/aix51ml2 -a server=master –a packages=all aix51ml2
 nim -o define -t lpp_source -a source=/roshan/aix51ml05 -a
location=/export/lpp_source/aix51ml5 -a server=master aix51ml5
 nim -o define -t lpp_source -a source=/roshan/aix51ml09 -a
location=/export/lpp_source/aix51ml9 -a server=master aix51ml9
Updating lpp_source
 nim -o update -a source=/roshan/aix51ml02 -a packages=all aix51_lpp
 nim -o update -a source=/roshan/aix51ml05 -a packages=all aix51_lpp
 nim -o update -a source=/roshan/aix51ml09 -a packages=all aix51_lpp
Defining the installp_bundle
 nim -o define -t installp_bundle -a location=/export/nim/nim_bundle -a server=master
nim_bundle
Define the fix_bundle
 nim -o define -t fix_bundle -a location=/export/nim/fix_bundle -a server=master fix_bundle
 nim -o define -t lpp_source -a source=/roshan/aix61ml03 -a
location=/export/lpp_source/aix61ml3 -a packages=all –a server=master aix61ml3
Software customization in spot (ML upgradation)
 nim -o cust -a lpp_source=aix51ml2 -a fixes=update_all spot_aix51
 nim -o cust -a lpp_source=aix51ml5 -a fixes=update_all spot_aix51
 nim -o cust -a lpp_source=aix51ml9 -a fixes=update_all spot_aix51
Registering Client from Server side
 nim -o define -t standalone -a platform=rspc -a netboot_kernel=up -a if1="dcm cws 0" -a
cable_type1=tp cws
 nim -o define -t standalone -a platform=rspc -a netboot_kernel=up -a if1="dcm pci 0" -a
cable_type1=tp pci
Registering Client from Client side
 niminit -a name=pci -a pif_name=en0 -a cable_type=tp -a master=galaxy -a
platform=rspc -a netboot_kernel=up
 niminit -a name=cws -a pif_name=en0 -a cable_type=tp -a master=galaxy -a
platform=rspc -a netboot_kernel=up
Booting a client system from network
 bootlist -m normal ent0 bserver=193.9.200.229 client=193.9.200.224
 bootlist -m normal ent0 bserver=193.9.200.229 client=193.9.200.227
Alocating and deallocating resources
 nim -o allocate -a lpp_source=aix51_lpp -a spot=aix51_spot pci
 nim -o deallocate -a lpp_source=aix51_lpp -a spot=aix51_spot pci
Taking mksysb from client system
 nim -o define -t mksysb -a source=pci -a location=/export/mksysb/pci_live -a
mk_image=yes -a server=master pci_live_mksysb
Installing Clent from Nim Master
 nim -o bos_inst -a spot=aix51ml9_spot -a lpp_source=lpp_alx51 -a accept_licenses=yes
-a boot_client=yes cws

Note
During the allocation of NIM mksysb images, only the file is exported to the NFS clients.
However, during mksysb creation, the parent directory is also exported. If you use that filesystem
to create a mksysb image of a system while another system is restoring a mksysb image from
that filesystem, you will get NFS errors.

To avoid this problem, use the environment variable NIM_MKSYSB_SUBDIRS on the NIM
master. When this variable is set to yes, subdirectories are used to separate mksysb images. The
subdirectories are transparent to the user, but they provide separate child locations for NFS
exporting.

#export NIM_MKSYSB_SUBDIRS=yes

Enabling syslogd daemon logging

To enable the syslogd daemon logging (if it is not already enabled), follow these steps.
 Edit the /etc/syslog.conf file.
 Add a line with the message priority and destination file.
*.debug /tmp/syslog.out
 Create the empty log file using for example the touch command
 refresh -s syslogd

Example 7-24 syslogd log content


..........
Jun 22 10:52:05 VLPAR3_p5 daemon:warn|warning rshd[311496]: Failed rsh
authentication from nimmast for local user root via remote user root
..........

TROUBLE SHOOTING NETWORK BOOT IN NIM


in case of nim_update_all command
export NIM_LICENSE_ACCEPT=yes
NIM_MKSYSB_SUBDIRS

Enabling syslogd daemon logging

To enable the syslogd daemon logging (if it is not already enabled), follow these steps.
 Edit the /etc/syslog.conf file.
 Add a line with the message priority and destination file.
*.debug /tmp/syslog.out
 Create the empty log file using for example the touch command
 refresh -s syslogd

Example 7-24 syslogd log content


..........
Jun 22 10:52:05 VLPAR3_p5 daemon:warn|warning rshd[311496]: Failed rsh
authentication from nimmast for local user root via remote user root
..........

You might also like