NIM Server Creations

1. Pre- requisite to start NIM server setup

For stating the NIM server /Client set the required file set should be get installed and the file sets are listed below,

On NIM server

lslpp –l
grep nim

File sets need to be installed on NIM SERVER:

• bos.sysmgt.nim.master


File sets need to be installed on NIM CLINET:

• bos.sysmgt.nim.clinet

If need to install from CD

• installp -Ld /dev/cd0
grep nim --> from cd


• installp -agxd /dev/cd0 bos.sysmgt.nim.master

• installp -agxd /dev/cd0

2. NIM Server Setup

Check the required fileset by listing the command,

• lslpp -l
grep nim -à will display the and nim.master file sets

NIM installation will create and update the below following file,

• /etc/niminfo

• ODM – object / object classes


LPP_SOURCE (licensed product project source)à This a source will have the content of AIX which in the CD, for loading the AIX installation

SPOT: shared product object tree will get created for each LPP_SOURce, this a directory which will be used for the installation of AIX from source.

2.1 Creating the SPOT and LPP_SOURCE

• Mount the CD / DVD on the machine for creating the SNAP of the filesets/ OS / PATCHES called as LPP_SOUREc and SPOT

• On the command prompt ,

• smitty nim à 1à1

 We have to specify the below details

• CD00 – the source from where the filesets for preparing the SPOT and LPP_SOURE have to be picked



• It will create the also

• File system name for creating both the SPOT and LPP_SOURCE

• Size of fs for LPP_SOURCE > 3.5 GB

• Size of fs for SPOT > 650 MB

à /export/SPOT

à /export/LPP_SOURCE

 Once on creation of SPOT and LPP_SOURCE, check for the daemons relates to NIM and its status, if not running make to start.

• nimd and nimesis – daemon will get started

• else restart the inetd / start the above daemons startsrc –g inetd

• startsrc –s nimd/ nimesis

 Check for /etc/niminfo file

 Set of command to list the NIM resources, spot, machine and standalone

• lsnim - > to see all resources

• lsnim –c resources

• lsnim –c machines

• lsnim -c networks

• lsnim –l detailed view

• lsnim –l detailed view

• lsnim –c resources

• lsnim –c machines

• lsnim –c

• lsnim –c

3. NIM CLINET Installation and Configuration

Pre-requisites for stating the client configuration

• Update the /etc/hosts of NIM MASTER machine with client IP and HOSTNAME

• Add the client machine in DNS

On command prompt, use the smitty menu to start the client configuration,

smitty NIM

à Perform NIM administration tasks à Manage Machine

By this time the client will get added to NIM server and identified as valuable NIM client machine and the process is called as setting up the “CLINET DEFINITION” (client machine get added to NIM SERVER) will get created

Once the client machine got added into NIM MASTER setup, allocate the resource (LPP_SOUREC and SPOT), which is going to be installed into the client machine. The allocation can be done through command prompt or SMITTY menu.

4. Example to explain the resource allocation - “COMMAND PROMPT”

We will start with command prompt

• lsnim

• lsnim –c machines

• lsnim –t standalone

• lsnim –l

• allocate a resource(LPP_source) to the machine

• If not we can deallocate the LPP_source from the machine

lsnim will list both the server and client machine too

lsnim –l , now this command display the status of client with

Cstate = ready for NIM operation (current status)

Mstate= Not running, Still the resource have not allocated to it.

Through command prompt, allocating the resources to client NIM

nim –o allocate -a lpp_source= < client_machine_name>

Once on allocation, check for

lsnim –l -à will list the details of resource being allocated for the machine.

In case, want to deallocate the resource,

nim –o deallocate –a lpp_source=

By this stage, Installed and configured the NIM server, created the SPOT and LPP_source add the NIM client into NIM server (client definition) and tried allocating and de-allocating the resource through command prompt.

Now we will start the resource allocation through SMITTY and start the BOS installation on CLIENT

5. RESOUREC allocation and start-up of BOS installation using allocated LPP

Login to NIM server and start us ethe smitty menu

7.1 Allocate the resource - Start BOS installation in NIM client

Smitty nim -> perform nim administrator task-> manage machines- >perform operation on machine ->

Select the client machine on to which the resource should be allocated and select the type of operation going to perform ( bos_install, upgrade,..etc)

smitty nim_bosinst à (fast path)

à Select “client machine”

à rte (type of operation)

à LPP_SOURES “resource”

à SPOT (belongs to the above LPP)

On this menu select the license and say YES/NO to server restart after BOS installation (depends on the server type -> if it upgrade on production then say NO)

Ref the BOS installation doc (TESCO) for installation steps

In cass want to manage the resource - adition deletion, upgrade

smitty NIM

à Perform NIM administration tasks àManage Resource-à (you can manage the resources like update, delete, etc)

Resource LPP and SPOT have been allocate to the client.

• lsnim –l will list the details

5.2 Resetting the installation status of client

In case want to reset the installation status say and not want to start the installation,

nim –o reset

6. How to remove the client from NIM definition, ODM entry

For removing the client from NIM definition (object), first the allocated resources like (LPP, SPOT) should be removed from the client machine

• nim –o deallocate –a lpp_source= spot=

• lsnim –l clinet_Machine

• nim –o remove clinet_machine

Confirm the definition removal (client machine)

• lsnim –c machines

• lsnim –t standalone

7. UN-configure the NIM server with NIM installation

• nim -o unconfig master(nim server name)

8. Uninstall the NIM file sets

• installp –u bos.sysmgt.nim.master

• installp –


Popular posts from this blog

How to Install and Configure Kubernetes Cluster and Docker on CentOS8/RHEL8

How to install Ansible Tower on Red Hat / CentOS

How to install Ansible on RHEL8 / CentOS8