Scribd
Upload
161 views

Nim Master Client Configuration

NIM (Network Installation Management) provides centralized management for installing and maintaining AIX images on LPARs and individual servers. It facilitates installation from a master image, different images, installation media, or a previous system backup. NIM resources like the software source, shared product object tree, and system backups are defined on the NIM master and distributed via NFS. The document provides steps for configuring a NIM master including installing prerequisites, defining resources, and allocating them to a client. It then walks through installing AIX on the client from the master using NIM.

Uploaded by

rajeevkghosh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
161 views

Nim Master Client Configuration

NIM (Network Installation Management) provides centralized management for installing and maintaining AIX images on LPARs and individual servers. It facilitates installation from a master image, different images, installation media, or a previous system backup. NIM resources like the software source, shared product object tree, and system backups are defined on the NIM master and distributed via NFS. The document provides steps for configuring a NIM master including installing prerequisites, defining resources, and allocating them to a client. It then walks through installing AIX on the client from the master using NIM.

Uploaded by

rajeevkghosh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 36

What is NIM?

NIM basically provides a central point of management for installing and maintaining AIX images for
both LPARs and individual servers. It also facilitates the installation of all of those instances from
either the same master image, from different images, from installation media or from a previous
mksysb of that instance (instance refers to an OS image, regardless of whether it's an LPAR or on a
dedicated machine). Additionally, NIM can group instances and install multiple instances at the same
time across the network.

NIM Resources

NIM resources are defined in the NIM database on the master, and those that are file-system-
based are served out to the clients using Network File System (NFS). There are many NIM
resources that must be defined. Some of the more critical ones include:
lpp_source--The Licensed Program Product source (lpp_source) directory contains the images
that AIX uses to load software. These are typically the backup file format (BFF) images that
exist on the AIX installation CDs or DVD. Each OS version should have its own lpp_source.
Additionally, these should be separated into 32-bit and 64-bit lpp_source sets.
SPOT--The Shared Product Object Tree (SPOT) is a directory created from the lpp_source. The
SPOT is used in a similar fashion to the boot images and installation scripts on the base
installation CD, volume one for AIX. It may be necessary to create multiple SPOTs depending
on the maintenance levels and versions that must be supported.
Mksysb--The NIM master can use lpp_source to install an instance, or it can install the instance
from a mksysb of either that instance or another one. Once the mksysb is restored, a script can
be run automatically to customize the instance.
Additional resources may include the following:
bosinst_data--This is a file, not a directory, and it contains the necessary information to allow
the installation to take place without manual intervention. It is used to define defaults such as
default disk drive, type of installation, etc.
image_data--This is also a file and contains OS image information related to file systems,
mirroring, etc.
installp_bundles--These files list additional software to be loaded after AIX is installed. This
can be useful when setting up groups of servers. As an example, one bundle may be for DB2
servers, while another may be for Web servers. Once the OS is installed, you simply select the
post-install bundle and apply it.

NIM Prerequisites

These are 3 filesets needs to be installed in the NIM master.


1. bos.sysmgt.nim.master
2. bos.sysmgt.nim.client

3. bos.sysmgt.nim.spot

Here we are installing the the nim.master,client and spot fileset in the Master server

Checking the installed filesets


Here we are configuring the nim environment to create lpp_source and spot
Follow the steps as below
Select Configure the NIM Environment
Select the Easy startup option as below
Please check the space is available in the VG’s before proceeding to create lpp_source and spot.
Here in the below steps we need to provide the information of the N/w interface, Installation images
location, lpp_source and Spot details.
We are selecting the en0 as the network interface
Installation images are available in the cd0. So we are selecting the cd0.
Lpp_source and spot directory can be left as default or it can be changed based on the space
availability. Here we are proceeding with the default .
Now the NIM Master configuration is in progress.
NIM master configuration completed successfully
Here we are checking the configuration.
We are configuring the client machine in to the nim master. Follow the screenshots below
We need to select the below option from smitty nim-Perform NIM Administration
TasksManage MachinesDefine a Machine

Note: before Defining a machine, put the client machine entry in /etc/hosts file.
Provide the client machine name in the below
Provide the machine type, cable type, N/w details
The client machine is defined now.

Here we are allocating the resources to the client machine


We need to select the below option from smitty nim- Perform NIM Administration Tasks Manage
MachinesManage Network Install Resource Allocation
Select the Allocate Network Install Resources for the client machine
Select the lpp_source and spot from the listing.
Now the resources has been allocated to the client machine.

Here we are going to perform BOS installation from Master to the client machine
We need to select the below option from smitty nim-Perform NIM Administration TasksManage
MachinesPerform Operations on Machines
Select the client machine name
Select the operation we are going to perform. Here we are selecting the bos_inst(BOS installation)
we need to accept the license agreements to proceed further
Now the resource allocation for the client machines has been set. We need to reboot the client
machine into the SMS mode

Now the Client Server has been rebooted into SMS.


Select “Setup Remote IPL” to configure the NIC and IP settings for the master, client.
Follow the steps as below
Select Port 1
Please select the IP parameters to provide the IP details
Here we are providing the IP details of the Master, client, gateway and subnet.
Now we are going to execute the ping test for the given IP’s. Check the summary of it below.
Ping test is success..we can proceed with the network boot for the BOS installation.
Follow the steps below.
Please select the Network and follow the steps below
Please select the the first Ethernet option as it has passed the ping test
Select the Normal mode boot
Check the status of the installation from Master server
Posted 28th October 2012 by Aravinth , Raghavendran
http://aixteam.blogspot.in/2012/10/nim-configuration_4907.html

You might also like