NIM Server Configuration - BeersBusinessSystemsWiki

8/8/2019 NIM Server Configuration - BeersBusinessSystemsWiki

1/9

NIM server configuration

From BeersBusinessSystemsWiki

Contents

1 Caveats:

2 Prepare the NIM Master

3 Install the latest AIX maintenance level and patches

4 Install the optional NIM software bundles

5 Prepare the system files

6 Configure TCP/IP tunables

7 Configure the file/filesystem limits

8 Create Filesystems9 Configure NIM environment

10 Cleanup Nim Image

11 Create mksysb of server

12 Define Client

13 Prepare Nim Master for Client install

14 Check the status on the NIM Master and NIM Client

15 Backout a system enabled for isntallation

16 Defining Additional Resources

Caveats:

1. The NIM master must always be at the highest AIX and TLs of any of its clients.

2. Do not use dots or special characters in any of the NIM panes, except IP addresses.

3. Hostname resolution between the NIM master and the clients must be reliable in both directions.

4. MKSYSB only backsup the rootvg.

Prepare the NIM Master

Install the optional NIM software bundles:

bos.net.tcp.server

bos.net.nfs.server

bos.sysmgt.nim.master

bos.sysmgt.nim.spot

7/7/2010 NIM server configuration - BeersBusin

beers-business-systems.com//NIM_s 1


2/9

Install the latest AIX maintenance level and patches

Install the optional NIM software bundles

5.3.0.40 Network Install Manager - Master Tools

5.3.0.30 Network Install Manager - SPOT

5.3.0.10 Network File System Server

5.3.0.30 TCP/IP NFS Server

Prepare the system files

edit /etc/netsvc.conf (nsswitch.conf in solaris and linux)

hosts=local,bind4

edit /etc/environment, append to the end of the file

YPBIND_MAXWAIT=30

edit /etc/hosts to include the IP/Host pairs for the machines to build

Configure TCP/IP tunables

no -p -o rfc1323=1

no -p -o tcp_recvspace=65536

no -p -o tcp_sendspace=65536

no -p -o ipignoreredirects=1

no -p -o tcp_pmtu_discover=0

no -p -o udp_pmtu_discover=0

Configure the file/filesystem limits

ulimit -f unlimited

ulimit -d unlimited

Create Filesystems

NIM resources are stored in /export. Sub-directories are created for each technology level (TL).




3/9

/export

/release-level

/lppsource

/spot

For example:

/export

/aix53tl6

/lppsource

/spot

As of this writing, each TL will take up about 4GB of space. You can create a new filesystem for each TL.

crfs -v jfs2 -g installvg -m /export/aix53tl6 -A yes -p rw -a size=4G -a agblksize=4096

crfs -v jfs2 -g installvg -m /export/mksysb -A yes -p rw -a size=10000M -a agblksize=4096

crfs -v jfs2 -g installvg -m /export/res -A yes -p rw -a size=5000M -a agblksize=4096

mount /export/aix53ml4

mount /export/mksysb

mount /export/res

cd /export/aix53ml4

mkdir lppsource

mkdir spot

Configure NIM environment

This begins the process for creating build images.

smitty nim

Configure the NIM Environment

Advanced Configuration

Initialize the NIM Master Only

Network Name [install_network]

Primary Network Install Interface [en0]

Allow Machines to Register Themselves as Clients? [yes]

smitty bffcreate

INPUT device / directory for software [/dev/cd0]

SOFTWARE package to copy [all]

DIRECTORY for storing software package [/export/aix53ml4/lppsource]

DIRECTORY for temporary storage during copying [/tmp]

EXTEND file systems if space needed? yes

Process multiple volumes? yes




4/9

smitty nim



Create Basic Installation Resources

Create a New LPP_SOURCE Only

Resource SERVER master

Input device for installation images []

(specify the device on the resource server)

LPP_SOURCE Name [lppsource_aix53ml4]

LPP_SOURCE Directory [/export/aix53ml4/lppsource]

Architecture of Resource []

Show Progress [yes]

Create new filesystem for LPP_SOURCE? [no]

Filesystem SIZE (MB) [] (Blank field)

VOLUME GROUP for new filesystem [] (Blank field)

Remove all newly added NIM definitions [no]

and filesystems if any part of this

operation fails?




Create a New SPOT Only


Input device for installation images [lppsource_aix53ml4]


SPOT Name [spot_aix53ml4]

SPOT Directory [/export/aix53ml4]

Create new filesystem for SPOT? [no]





operation fails?

Configure NIM environment

smitty nim



Initialize the NIM Master Only

Network Name [install_network]

Primary Network Install Interface [en0]

Allow Machines to Register Themselves as Clients? [yes]

smitty bffcreate

INPUT device / directory for software [/dev/cd0]

SOFTWARE package to copy [all]




5/9

DIRECTORY for storing software package [/export/aix53ml4/lppsource]

DIRECTORY for temporary storage during copying [/tmp]

EXTEND file systems if space needed? yes

Process multiple volumes? yes

smitty nim




Create a New LPP_SOURCE Only


Input device for installation images []


LPP_SOURCE Name [lppsource_aix53ml4]

LPP_SOURCE Directory [/export/aix53ml4/lppsource]

Architecture of Resource []

Show Progress [yes]

Create new filesystem for LPP_SOURCE? [no]





operation fails?




Create a New SPOT Only


Input device for installation images [lppsource_aix53ml4]


SPOT Name [spot_aix53ml4]

SPOT Directory [/export/aix53ml4]

Create new filesystem for SPOT? [no]Filesystem SIZE (MB) [] (Blank field)




operation fails?

This ends the process for creating build images.




6/9

Cleanup Nim Image

errclear 0;>nim.script;>suma.log;>bootlog;>nimlog;>conslog;>nimsh.log;>bosinstlog;>devinst.log;>n

Create /etc/exclude.rootvg

/export/aix53ml4

/export/mksysb

/export/nim

/export/res

/smit.log

/smit.script

Set autorestart to true and cpuguard to enable

chdev -l sys0 -a autorestart=true -a cpuguard=enable

Create mksysb of server

smitty nim

Perform NIM Administration Tasks

Manage Resources

Define a Resource

mksysb = a mksysb image

Resource Name [gold_aix53ml4]

Resource Type mksysb

Server of Resource [master]

Location of Resource [/export/mksysb/gold_aix53ml4]

Comments []

Source for Replication []

-OR-

System Backup Image Creation Options:

CREATE system backup image? yes

NIM CLIENT to backup [master]

PREVIEW only? no

IGNORE space requirements? no

EXPAND /tmp if needed? yes

Create MAP files? no

Backup extended attributes? yes

Number of BLOCKS to write in a single output []

(leave blank to use system default)

Use local EXCLUDE file? yes (uses /etc/exclude.rootvg)

(specify no to include all files in backup)

-OR-

EXCLUDE_FILES resource []




7/9

(leave blank to include all files in backup)

Enter

Define Client

smitty nim

Perform NIM Administration Tasks

Manage Machines

Define a Machine

Host Name of Machine [blast]

NIM Machine Name [blast]

Machine Type [standalone]

Hardware Platform Type [chrp]

Kernel to use for Network Boot [mp]

Communication Protocol used by client []

Primary Network Install Interface

Cable Type tp

Network Speed Setting []

Network Duplex Setting []

NIM Network install_network

Host Name blast

Network Adapter Hardware Address [0]

Network Adapter Logical Device Name []

IPL ROM Emulation Device []

CPU Id []

Machine Group []

Comments []

Prepare Nim Master for Client install

showmount -e

smitty nim_bosinst

* Select target machine, press enter* Select installation type, (SPOT) press enter

* Select repository for install (SPOT)

Installation Target blast

Installation TYPE spot

SPOT spot_aix53ml4

LPP_SOURCE [lppsource_aix53ml4]

MKSYSB

BOSINST_DATA to use during installation []

IMAGE_DATA to use during installation []

RESOLV_CONF to use for network configuration []




8/9

Customization SCRIPT to run after installation []

Customization FB Script to run at first reboot []

ACCEPT new license agreements? [yes]

Remain NIM client after install? [yes]

PRESERVE NIM definitions for resources on [yes]

this target?

FORCE PUSH the installation? [no]

Initiate reboot and installation now? [no]

-OR-

Set bootlist for installation at the [no]

next reboot?

Additional BUNDLES to install []

-OR-

Additional FILESETS to install []

(bundles will be ignored)

installp Flags

COMMIT software updates? [yes]

SAVE replaced files? [no]

AUTOMATICALLY install requisite software? [yes]

EXTEND filesystems if space needed? [yes]OVERWRITE same or newer versions? [no]

VERIFY install and check file sizes? [no]

ACCEPT new license agreements? [yes]

(AIX V5 and higher machines and resources)

Preview new LICENSE agreements? [no]

Group controls (only valid for group targets):

Number of concurrent operations []

Time limit (hours) []

Schedule a Job [no]

YEAR []

MONTH []DAY (1-31) []

HOUR (0-23) []

MINUTES (0-59) []

Check the status on the NIM Master and NIM Clientlsnim -l blast

blast:

class = machines

type = standalone

connect = shell

platform = chrp

netboot_kernel = mp

if1 = install_network blast 0

cable_type1 = tp

Cstate = BOS installation has been enabled




9/9

prev_state = ready for a NIM operation

Mstate = not running

boot = boot

lpp_source = lppsource_aix53ml4

nim_script = nim_script

spot = spot_aix53ml4

control = master

lsnim -l lppsource_aix53ml4

lppsource_aix53ml4:

class = resources

type = lpp_source

arch = power

Rstate = ready for use

prev_state = unavailable for use

location = /export/aix53ml4/lppsource

simages = yes

alloc_count = 1

server = master

Backout a system enabled for isntallation

nim -o reset -aforce=yes NIMClientHostName

nim -Fo deallocate -asubclass=all NIMClientHostName

nim -o change -a cupid="" NIMClientHostName

Defining Additional Resources

In addition to the Base Operating System (BOS), you may want to add additional software on NIM clients. You

can create installp bundles and define them as additional installation resources. These new resources can be

selected during the BOS install process allowing you to easily customize your installation.

Example: You want to install SSH and Bash

Retrieved from "http://www.beers-business-systems.com/wiki/index.php/NIM_server_configuration"

This page was last modified on 20 August 2007, at 19:07.


beers-business-systems com/ /NIM s 9

NIM Server Configuration - BeersBusinessSystemsWiki

Documents

Transcript of NIM Server Configuration - BeersBusinessSystemsWiki