AIX:Network Installation Manager

Definition and Concepts

Terminology

Master

Master refers the machine where you set up and maintain your NIM environment. You can also initiate installations from here (push mode). It is the key piece of the NIM environment.

Client

The NIM client can be the target for NIM master-initiated operations such as installation, updates, and so forth (push mode). Also, a client can initiate its own installation or update (pull mode). A NIM client automatically becomes a resource server when it holds NIM resources.

Resource Server

Any machine (the master or a standalone client) can be configured by the master as a server for a particular software resource. In most environments, the master is also resource server. If other machines are already reporting to the master and they are installed (AIX), you can chose one of them to act as a resource server, thus relieving the NIM master of the heavy I/O load (disk and network). In such cases, the NIM master is only used to run administrative tasks.

Push and Pull modes

The push mode operation is initiated from the master. The pull mode operation is initiated from the client. The very first time a client is installed, only the pull mode can be used. Note the following points:

• In order for the push mode to be successful, the client must have a minimum AIX image already installed and TCP/IP configured.
• To use the pull mode, you need access to the clients’ SMS menu. For this you either need a console attached to the machine, or for HMC-managed systems, you need access to the HMC.

NIM Database

The NIM database is stored in the AIX Object Data Management (ODM) repository on the NIM master and is divided into four classes: machines, networks, resources, groups. Classes also consist of types. These classes are listed in the following table:

The four NIM classes and their main used types

Machines	Network	Resources Groups
master	ent	lpp_source	mac_group
standalone	tok	spot	res_group
diskless	fddi	mksysb
dataless	atm	bosinst_data
alternate_master	generic	script
		image_data
		installp_bundle

Networks Class

The network is what allows the machines in a NIM environment to communicate which each other. If the network is a simple local area network (LAN), the definition of the network object is simplified. The purpose of the network object is to depict the network topology used by the NIM environment. Each modification made on the physical network must be reflected to the NIM database.

Resources Class

A NIM resource is a pointer to a file or a directory located on a Resource Server, and the NIM Master is the default Resource Server. For example, the bosinst_data resource points to a file that contains information used to perform the installation process without requiring any manual intervention. The basic characteristics of a resource are the NIM name, the location (the location of the file or directory), and the resource server hosting the resource.

Groups Class

A group is a collection of either machines or resources. Only two types are available:

• res_group, for grouping a set of resources
• mac_group, for grouping a set of machines

Commands

lsnim
lsnim -c machines
lsnim -c networks
lsnim -c resources
lsnim -t spot
lsnim -l clientname
lsnim -l networkname

smit nimconfig Configure a NIM Master
smit nim_bosinst Install the Base Operating System on Standalone Clients
smit nim_mkres Define basic resources
smit nim_mkmac Define the client
smit nim_res_op Verify resource status
smit nim_task_inst Start client (base OS) installation

smit eznim

Files and directories

/etc/bootptab

/tftpboot

/usr/lpp/bos.sysmgt/nim/methods/c_sh_lib

Filesets

bos.sysmgt.nim.master

bos.sysmgt.nim.spot

Abbrevations

BOS	Basic Operating System
LPP	Licensed Program Product
ML	Maintenance Level
NIM	Network Installation Manager
SOE	Standard Operating Environment
SPOC	Single Point Of Control
SUMA	Service Update Management Assistant
SPOT	Shared Product Object Tree
TL	Technology Level

Literature

sg24-7296 NIM from A to Z in AIX5L (was gebleven bij bladzijde 30 --Thom 22:33, 22 June 2010 (UTC))

Upgrade AIX using alternate rootvg

smit alt_clone