Page 2 of 9
NIM installation scenarios
There are two basic scenarios for installing NIM servers. In this article ROOTvg.NET provides instrustions for the first scenario. In other articles on ROOTVG.NET there are instructions for updating NIM servers, in particular using SUMA:
- Install AIX NIM from a CD without updating the nim resources to the latest levels (i.e. I only use DVD images I have in house)
-
Install from a DVD then use SUMA or Fix Central to update the system
that will function as NIM server before creating the nim resources,
especially before installing the nim spot and master filesets.
Key elements
- Install AIX base system
- Create a volume group for NIM resources
- Create a mksysb file to be used later as nim resource
- Complete AIX installation and add SSH support
- Configure NIM master
- Define Installation Resources
- Define and Install NIM clients - hands free
Install AIX base system
Personally, I prefer installing a NIM server outside of a POWER system as a stand-alone unit - use older systems (at least POWER4 to support all versions of AIX) - but generally I see NIM servers being installed as a partition or LPAR of a POWER system. Install AIX via the console or the HMC supplied virtual console. When the installation completes and AIX reboots - just do the minimum: accept licenses. Do not set a root password, do not setup any network configuration information. Ideally, you will have have only one ethernet (ent0) interface configured into your partition.
Create a volume group for NIM resources
On a second disk I generally use the following naming scheme:
Volume Group: vgNim
Logical Volumes:
lgNim - jfs2log - 1 partition
lvtftpb - jfs2 - 64 Mbyte as /tftpboot for when Nim spots are made
lvExp - jfs2 - 64 Mbyte as /export (/export/nim resources)
lvMksb - jfs2 - 4 Gbyte as /export/mksysb/6106 (i.e. AIX vers.)
lvoslevel - jfs2 - 4 Gbyte as /export/6106 (for lpp)
lvoslevels - jfs2 - 2 Gbyte as /export/6106/spot (for spot)
Many people just make a very large /export partition and never think to include /tftpboot.
Example
So, after the intial install of AIX and accepting the licenses, and BEFORE I enter any TCPIP information or root password I do the following:
login as root
Example script
#!/usr/bin/ksh
clear
echo "AIXTOOLS and ROOTVG.NET script to assist with NIM installation based on host's oslevel"
echo ==========
echo Choose a disk from the list below to create and configure NIM volume group
lspv
echo ==========
echo "Enter disk to create NIM volume group:\c"
read hdisk
mkvg -y vgNim ${hdisk}
[[ $? -ne 0 ]] && echo mkvg failed, exiting && exit
mklv -t jfs2log -y lgNim vgNim 1
mklv -t jfs2 -y lvtftpb vgNim 64M
mklv -t jfs2 -y lvExp vgNim 64M
mklv -t jfs2 -y lvMksb vgNim 4G
OSLEVEL=`oslevel -s | cut -c 1-2,6-7`
mklv -t jfs2 -y lv${OSLEVEL} vgNim 4G
mklv -t jfs2 -y lv${OSLEVEL}s vgNim 2G
lsvg -l vgNim
# clear
# lspv
hdisk0 00f67207e26dbb8d rootvg active
hdisk1 none None
# mkvg -y vgNim hdisk1
0516-1254 mkvg: Changing the PVID in the ODM.
vgNim
# mklv -t jfs2log -y lgNim vgNim 1
lgNim
# mklv -t jfs2 -y lvtftpb vgNim 64M
lvtftpb
# mklv -t jfs2 -y lvExp vgNim 64M
lvExp
# mklv -t jfs2 -y lvMksb vgNim 4G
lvMksb
# OSLEVEL=`oslevel -s | cut -c 1-2,6-7`
# mklv -t jfs2 -y lv${OSLEVEL} vgNim 4G
lv6106
# mklv -t jfs2 -y lv${OSLEVEL}s vgNim 2G
lv6106sNext before creating the filesystems, I logform (format the lgNim jfs2log). Then I create and mount the filesystems one by one.
#!/usr/bin/ksh
clear
echo "AIXTOOLS and ROOTVG.NET script to assist with NIM installation based on host's oslevel"
echo ==========
OSLEVEL=`oslevel -s | cut -c 1-2,6-7`
echo y | logform /dev/lgNim
crfs -v jfs2 -d lvtftpb -m /tftpboot -A yes -u nim
mount /tftpboot
crfs -v jfs2 -d lvExp -m /export -A yes -u nim
mount /export
crfs -v jfs2 -d lvMksb -m /export/mksysb -A yes -u nim
mount /export/mksysb
mkdir /export/mksysb/${OSLEVEL}
crfs -v jfs2 -d lv${OSLEVEL} -m /export/${OSLEVEL} -A yes -u nim
mount /export/${OSLEVEL}
crfs -v jfs2 -d lv${OSLEVEL}s -m /export/${OSLEVEL}/spot -A yes -u nim
mount /export/${OSLEVEL}/spot
lsvg -l vgNim
# echo y | logform /dev/lgNim
# crfs -?
Usage: crfs -v Vfs {-g Volumegroup | -d Device} -m Mountpoint
[-u Mountgroup] [-A {yes|no}] [-t {yes|no}] [-p {ro|rw}]
[-l Logpartitions] [-n nodename] [-a Attribute=Value]
# crfs -v jfs2 -d lvtftpb -m /tftpboot -A yes -u nim
File system created successfully.
65328 kilobytes total disk space.
New File System size is 131072
# mount /tftpboot
# crfs -v jfs2 -d lvExp -m /export -A yes -u nim
File system created successfully.
65328 kilobytes total disk space.
New File System size is 131072
# mount /export
# crfs -v jfs2 -d lvMksb -m /export/mksysb -A yes -u nim
File system created successfully.
4193972 kilobytes total disk space.
New File System size is 8388608
# mount /export/mksysb
# mkdir /export/mksysb/6106
# crfs -v jfs2 -d lv6106 -m /export/6106 -A yes -u nim
File system created successfully.
4193972 kilobytes total disk space.
New File System size is 8388608
# mount /export/6106
# crfs -v jfs2 -d lv6106s -m /export/6106/spot -A yes -u nim
File system created successfully.
2096884 kilobytes total disk space.
New File System size is 4194304
# mount /export/6106/spot# lsvg -l vgNim
vgNim:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
lgNim jfs2log 1 1 1 open/syncd N/A
lvtftpb jfs2 2 2 1 open/syncd /tftpboot
lvExp jfs2 2 2 1 open/syncd /export
lvMksb jfs2 128 128 1 open/syncd /export/mksysb
lv6106 jfs2 128 128 1 open/syncd /export/6106
lv6106s jfs2 64 64 1 open/syncd /export/6106/spot
|