In order for an AIX system to be configured as a NIM client, the fileset bos.sysmgt.nim.client must be installed:

aix05 # lslpp -l bos.sysmgt.nim.client
  Fileset                      Level  State      Description        
  ----------------------------------------------------------------------------
Path: /usr/lib/objrepos
  bos.sysmgt.nim.client    7.2.5.203  COMMITTED  Network Install Manager -
                                                 Client Tools
                                      EFIXLOCKED

Path: /etc/objrepos
  bos.sysmgt.nim.client    7.2.5.203  COMMITTED  Network Install Manager -
                                                 Client Tools
                                      EFIXLOCKED
aix05 # 

If the AIX system is not yet initialized as a NIM client, the /etc/niminfo file should not exist and the NIM service handler (nimsh) should not be active:

aix05 $ ls -l /etc/niminfo
/etc/niminfo not found
aix05 $ lssrc -s nimsh
Subsystem         Group            PID          Status
 nimsh            nimclient                     inoperative
aix05 $ 

An AIX system can be registered as a NIM client on a NIM master using the niminit command. To do so, the niminit command must contain at least the following attributes:

name – The name of the NIM client (this can be the hostname, but can also be a symbolic name).
master – The name of the NIM master, this must be resolvable to an IP address.
pif_name – The name of the network interface on the NIM client to be used.

There are a number of other optional attributes, but their default values ​​are usually already correct:

aix05 # niminit -a name=aix05 -a master=aixnim -a pif_name=en0
nimsh:2:wait:/usr/bin/startsrc -g nimclient >/dev/console 2>&1
0513-077 Subsystem has been changed.
0513-059 The nimsh Subsystem has been started. Subsystem PID is 15139104.
aix05 # 

The AIX system is registered as a NIM client on the specified NIM master (aixnim), the /etc/niminfo file is created on the NIM client, and the NIM service handler (nimsh) is added to the /etc/inittab file on the client and started. The /etc/niminfo file on the NIM client then looks something like this:

aix05 # cat /etc/niminfo
#------------------ Network Install Manager ---------------
# warning - this file contains NIM configuration information
#       and should only be updated by NIM
export NIM_NAME=aix05
export NIM_HOSTNAME=aix05
export NIM_CONFIGURATION=standalone
export NIM_MASTER_HOSTNAME=aixnim
export NIM_SSL_STATUS=disabled
export NIM_MASTER_PORT=1058
export NIM_REGISTRATION_PORT=1059
export NIM_SHELL="nimsh"
export NIM_MASTERID=00DC1B125C11
export NIM_FIPS_MODE=-1
export NIM_BOS_IMAGE=/SPOT/usr/sys/inst.images/installp/ppc/bos
export NIM_BOS_FORMAT=rte
export NIM_HOSTS=" 127.0.0.1:loopback:localhost  10.192.168.155:aix05  10.192.168.150:aixnim "
export NIM_MOUNTS=""
export ROUTES=" default:0:10.192.168.1 "
aix05 #

A NIM object of type standalone is created on the NIM master for the new NIM client:

aixnim # lsnim -l aix05
aix05:
   class          = machines
   type           = standalone
   connect        = nimsh
   platform       = chrp
   netboot_kernel = 64
   if1            = net_10_192_168_0 aix05 87F1A4DC8316 ent0
   cable_type1    = N/A
   Cstate         = ready for a NIM operation
   prev_state     = ready for a NIM operation
   Mstate         = currently running
   cpuid          = 00DC1AD25C11
aixnim # 

By default, communication between the NIM client and the NIM master works in both directions. The connection between the NIM client and the NIM master can be easily tested using the nimclient command and the “-l” (lsnim) option, for example:

aix05 # nimclient -l -l aix05
aix05:
   class          = machines
   type           = standalone
   connect        = nimsh
   platform       = chrp
   netboot_kernel = 64
   if1            = net_10_192_168_0 aix05 87F1A4DC8316 ent0
   cable_type1    = N/A
   Cstate         = ready for a NIM operation
   prev_state     = ready for a NIM operation
   Mstate         = currently running
   cpuid          = 00DC1AD25C11
aix05 # 

To test the communication from the NIM master to the NIM client, you can use “nim -o lslpp” for example:

aixnim # nim -o lslpp aix05
  Fileset                      Level  State      Description        
  ----------------------------------------------------------------------------
Path: /usr/lib/objrepos
  GSKit8.gskcrypt32.ppc.rte
                           8.0.55.31  COMMITTED  IBM GSKit Cryptography Runtime
  GSKit8.gskcrypt64.ppc.rte
                           8.0.55.31  COMMITTED  IBM GSKit Cryptography Runtime
…
aixnim # 

If the NIM master does not use the standard port numbers 1058 (nim) and 1059 (nimreg), the port numbers to be used can be specified as attributes in niminit:

master_port – Port to be used for communication with the NIM server (nimesis daemon).
registration_port – Port to be used for registration of NIM clients.