NIM MASTER: >>
# hostname
oldbcoedv
# cat /etc/hostname
192.52.100.29 bcoeqa bcoeqa.bin.com.sa
192.52.100.66 oldbcoedv
# cat /etc/bootptab
.....
# T180 -- (xstation only) -- enable virtual screen
#NO CLIENTS PRESENT
# lsnim
master machines master
boot resources boot
nim_script resources nim_script
NET_EN1 networks ent
bcoeqa machines standalone
5300-05bid_ow resources bosinst_data
5300-05master_sysb resources mksysb
530lpp_res resources lpp_source
530spot_res resources spot
basic_res_grp groups res_group
# lsnim -l master
master:
class = machines
type = master
max_nimesis_threads = 20
if_defined = chrp.mp.ent
comments = machine which controls the NIM environment
platform = chrp
netboot_kernel = mp
if1 = NET_EN1 bcoedv 8EE280002005
cable_type1 = N/A
Cstate = ready for a NIM operation
prev_state = ready for a NIM operation
Mstate = currently running
serves = 5300-05bid_ow
serves = 5300-05master_sysb
serves = 530lpp_res
serves = 530spot_res
serves = boot
serves = nim_script
master_port = 1058
registration_port = 1059
reserved = yes
# lsnim -l NET_EN1
NET_EN1:
class = networks
type = ent
Nstate = ready for use
prev_state = information is missing from this object's definition
net_addr = 192.52.100.0
snm = 255.255.255.0
routing1 = default 192.52.100.10
#
# lsnim -l bcoeqa
bcoeqa:
class = machines
type = standalone
connect = shell
platform = chrp
netboot_kernel = mp
if1 = NET_EN1 bcoeqa 0
cable_type1 = bnc
Cstate = ready for a NIM operation
prev_state = ready for a NIM operation
Mstate = currently running
cpuid = 000620EED700
# lsnim -l 530lpp_res
530lpp_res:
class = resources
type = lpp_source
arch = power
Rstate = ready for use
prev_state = unavailable for use
location = /export/eznim/lpp_source/530lpp_res
simages = yes
alloc_count = 0
server = master
# lsnim -l 530spot_res
530spot_res:
class = resources
type = spot
plat_defined = chrp
arch = power
bos_license = yes
Rstate = ready for use
prev_state = verification is being performed
location = /export/eznim/spot/530spot_res/usr
version = 5
release = 3
mod = 0
oslevel_r = 5300-05
alloc_count = 0
server = master
if_supported = chrp.mp ent
Rstate_result = success
# lsnim -l basic_res_grp
basic_res_grp:
class = groups
type = res_group
member1 = 5300-05master_sysb
member2 = 530lpp_res
member3 = 530spot_res
# cat /etc/niminfo
# nimconfig
export NIM_NAME=master
export NIM_CONFIGURATION=master
export NIM_MASTER_PORT=1058
export NIM_REGISTRATION_PORT=1059
##THE BELOW LINE HAD WRONG HOSTNAME SO I CORRECTED IT BY EDITING IT
export NIM_MASTER_HOSTNAME=oldbcoedv
# /usr/lpp/bos.sysmgt/nim/methods/eznim show_eznim_env
NIM Machines
====================
master:
Cstate = ready for a NIM operation
Mstate = currently running
bcoeqa:
Cstate = ready for a NIM operation
Mstate = currently running
Image Repository (lpp_source)
====================
530lpp_res:
Rstate = ready for use
location = /export/eznim/lpp_source/530lpp_res
Boot Support (SPOT)
====================
530spot_res:
Rstate = ready for use
location = /export/eznim/spot/530spot_res/usr
System Backups (mksysb)
====================
5300-05master_sysb:
Rstate = ready for use
location = /export/eznim/mksysb/generic_sysb
BOS Install Data File (bosinst_data)
====================
5300-05bid_ow:
Rstate = ready for use
location = /export/eznim/5300-05bid_ow
Resolution File (resolv_conf)
====================
#
Now the Problem:
When I backup the client
using eznim backup client:
I get the error
warning: 0042-175 c_mkbosi: An unexpected result was returned by the
"/usr/sbin/mount" command:
mount: 1831-011 access denied for bcoedv:/export/eznim/mksysb
mount: 1831-008 giving up on:
bcoedv:/export/eznim/mksysb
The file access permissions do not allow the specified action.
rc=175
0042-175 c_mkbosi: An unexpected result was returned by the "/usr/sbin/mount" command:
mount: 1831-011 access denied for bcoedv:/export/eznim/mksysb
mount: 1831-008 giving up on:
bcoedv:/export/eznim/mksysb
The file access permissions do not allow the specified action.
0042-001 nim: processing error encountered on "master":
exportfs: /db2/EDV/bckdata: A file or directory in the path name does not exist.
exportfs: 1831-192 /usr/sap: sub-directory (/usr/sap/trans)
already exported
rc=0
exportfs: /db2/EDV/bckdata: A file or directory in the path name does not exist.
exportfs: 1831-192 /usr/sap: sub-directory (/usr/sap/trans)
exportfs: /db2/EDV/bckdata: A file or directory in the path name does not exist.
exportfs: 1831-192 /usr/sap: sub-directory (/usr/sap/trans)
already exported
rc=1
0042-001 m_mkbosi: processing error encountered on "master":
0042-175 c_getlevel: An unexpected result was returned by the "/usr/lpp/bos.sysmgt/nim/methods/c_stat" c
ommand:
0042-154 c_stat: the file or directory "/export/eznim/mksysb/bcoeqa_sysb" does not exist
or
nim -o define -t mksysb -a server=master -a source=bcoeqa -a mk_image=yes -a location=/nimfs/mksysb.bcoeqa mksysb_bcoeqa
CLIENT:
# hostname
bcoeqa
# set -o vi
# cat /etc/niminfo
#------------------ Network Install Manager ---------------
# warning - this file contains NIM configuration information
# and should only be updated by NIM
export NIM_NAME=bcoeqa
export NIM_HOSTNAME=bcoeqa
export NIM_CONFIGURATION=standalone
export NIM_MASTER_HOSTNAME=oldbcoedv
export NIM_MASTER_PORT=1058
export NIM_REGISTRATION_PORT=1059
export NIM_SHELL="shell"
export NIM_BOS_IMAGE=/SPOT/usr/sys/inst.images/installp/ppc/bos
export NIM_BOS_FORMAT=rte
export NIM_HOSTS=" 192.52.100.29:bcoeqa "
export NIM_MOUNTS=""
export ROUTES=" default:0:192.52.100.10 "
FROM THE NIM MASTER
# nimquery -a host=bcoeqa -p
rc=50
0042-050 nimquery: operation failed for the following reason: bcoeqa: Connection refused
#
# rsh bcoeqa
*******************************************************************************
* *
* *
* Welcome to AIX Version 5.3! *
* *
So, what could be the problem ?
Thanks.
references:
AIX UNIX system administration: NIM server setup for dummies
NIM Install Handbook | Nikolai's Diary
NIM | Unixskylab
http://nixforums.org/about32149.html
http://www.docstoc.com/docs/4629544/AIX-NIM-Tips
http://www.docstoc.com/docs/2801707/nim_install
http://www.docstoc.com/docs/4602406/AIX-Tip-for-admin
http://www.docstoc.com/docs/1142501/AIX-FAQ
http://www.docstoc.com/docs/4602448/Quick-Reference-Administering-AIX-V5
http://www.docstoc.com/docs/4757278/AIX-From-Strength-to-Strength
rc=1
0042-001 m_mkbosi: processing error encountered on "master":
0042-175 c_getlevel: An unexpected result was returned by the "/usr/lpp/bos.sysmgt/nim/methods/c_stat" c
ommand:
0042-154 c_stat: the file or directory "/export/eznim/mksysb/bcoeqa_sysb" does not exist
While you try with eznim it tries to take mksysb in "/export/eznim/mksysb/bcoeqa_sysb" which is not present in your server.
While you are trying with command line this error should not come because you are using location=/nimfs/mksysb.bcoeqa mksysb_bcoeqa check whether /nimfs is exported to all your nim_clients.
I am getting the same error with the CLI command line
nim -o define -t mksysb -a server=master -a source=bcoeqa -a mk_image=yes -a location=/nimfs/mksysb.bcoeqa mksysb_bcoeqa
I don't have to manually export /nimfs by NFS to all my clients ? because NIM is suppose to take care of it.
POSTSCRIPT
After re-installing, NIM it worked fine. I don't know why the errors appeared although I followed the same procedure.
Most likely the error stems from having exported parts or even a superset of the NIM directories by hand. NIM is pretty picky about these things, for reasons unknown.
Here is an example:
Your NIM resource in question resides in "/some/where/resource". If you use it in a NIM operation this directory will become exported in "/etc/exports" automatically by NIM. Suppose you manually export "/some/where" to world now. Chances are NIM will generate an error even if the manual (and more generous) export should do no harm to the subset being exported to a specific host alone.
Bottom line: before using NIM remove all exports of the directory hierarchy NIM uses completely, then run "exportfs -va" to make sure NFS knows about that.
# egrep "bootpd|tftpd" /etc/inetd.conf
bootps dgram udp wait root /usr/sbin/bootpd bootpd /etc/bootptab
tftp dgram udp6 SRC nobody /usr/sbin/tftpd tftpd -n
#
# lssrc -s tftpd
Subsystem Group PID Status
tftpd tcpip 295058 active
# lssrc -l -s inetd|grep bootpd
bootps /usr/sbin/bootpd bootpd /etc/bootptab active
#
# df -g
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/hd4 5.38 4.89 10% 56168 5% /
/dev/hd2 5.12 3.58 31% 41647 5% /usr
/dev/hd9var 0.06 0.03 46% 551 7% /var
/dev/hd3 2.00 1.78 11% 885 1% /tmp
/dev/hd1 2.00 2.00 1% 92 1% /home
/proc - - - - - /proc
/dev/hd10opt 0.44 0.10 78% 5847 20% /opt
/dev/nimlv 400.00 394.21 2% 13313 1% /nimfs
/dev/fslv01 2.75 0.07 98% 13312 43% /export/eznim
/dev/fslv02 0.06 0.05 20% 5 1% /tftpboot
# ls -la /nimfs
total 10057896
drwxr-xr-x 6 root system 256 Sep 02 16:51 .
drwxr-xr-x 38 root system 4096 Sep 05 11:53 ..
drwxr-xr-x 2 root system 256 Aug 31 15:30 OSBACKUP
-rw-r----- 1 root system 3302983680 Aug 31 16:23 cd_image_1265856
drwxr-xr-x 2 root system 256 Aug 31 12:09 lost+found
drwxr-xr-x 3 root system 256 Sep 02 16:17 lpp_source
-rw-r--r-- 1 root system 1846118400 Sep 02 16:56 mksysb.bcoeqa
drwxr-xr-x 3 root system 256 Sep 02 16:41 spot
# cat /etc/exports
/db2/EDV/bckdata -sec=sys:krb5p:krb5i:krb5:dh,rw,root=192.52.100.63
/usr/sap/trans -sec=sys:krb5p:krb5i:krb5:dh,rw,root=192.52.100.63
/sapmnt/EDV -sec=sys:krb5p:krb5i:krb5:dh,rw,root=192.52.100.63
/usr/sap -sec=sys:krb5p:krb5i:krb5:dh,rw,root=192.52.100.63
/usr/sap/trans -sec=sys:krb5p:krb5i:krb5:dh,rw,root=192.52.100.21
# exportfs -va
exportfs: /db2/EDV/bckdata: A file or directory in the path name does not exist.
exportfs: 1831-187 re-exported /usr/sap/trans
exportfs: 1831-187 re-exported /sapmnt/EDV
exportfs: 1831-192 /usr/sap: sub-directory (/usr/sap/trans)
already exported
exportfs: 1831-187 re-exported /usr/sap/trans
#
# lsnim -l master
master:
class = machines
type = master
max_nimesis_threads = 20
if_defined = chrp.mp.ent
comments = machine which controls the NIM environment
platform = chrp
netboot_kernel = mp
if1 = network1 oldbcoedv 8EE280002005
cable_type1 = N/A
Cstate = ready for a NIM operation
prev_state = ready for a NIM operation
Mstate = currently running
serves = AllDevicesKernels
serves = Alt_Disk_Install
serves = App-Dev
serves = CC_EVAL_Graphics
serves = CDE
serves = Firefox
serves = GNOME
serves = Graphics
serves = KDE
serves = Kerberos_5
serves = Mozilla
serves = PerfTools
serves = Server
serves = bid_ow
serves = boot
serves = cas_client
serves = cas_server
serves = infocenter_CA_ES
serves = infocenter_CS_CZ
serves = infocenter_DE_DE
serves = infocenter_EN_US
serves = infocenter_ES_ES
serves = infocenter_FR_FR
serves = infocenter_HU_HU
serves = infocenter_IT_IT
serves = infocenter_JA_JP
serves = infocenter_KO_KR
serves = infocenter_PL_PL
serves = infocenter_PT_BR
serves = infocenter_RU_RU
serves = infocenter_SK_SK
serves = infocenter_ZH_CN
serves = infocenter_ZH_TW
serves = lpp_source1
serves = mksysb_bcoeqa
serves = nim_script
serves = openssh_client
serves = openssh_server
serves = spot1
serves = wsm_remote
master_port = 1058
registration_port = 1059
reserved = yes
#
# lsnim -l clonebco
clonebco:
class = machines
type = standalone
connect = shell
platform = chrp
netboot_kernel = mp
if1 = network1 192.52.100.67 0
cable_type1 = bnc
Cstate = ready for a NIM operation
prev_state = ready for a NIM operation
Mstate = not running
Cstate_result = reset
#
# lsnim -l mksysb_bcoeqa
mksysb_bcoeqa:
class = resources
type = mksysb
arch = power
Rstate = ready for use
prev_state = unavailable for use
location = /nimfs/mksysb.bcoeqa
version = 5
release = 3
mod = 7
oslevel_r = 5300-05
alloc_count = 0
server = master
My objective:
1) Client "clonebco" should pull the makesysb from NIM Server
2) I went to client clonebco --> started SMS --> IPL --> IP address settings -- (Was able to ping NIM Server )
3) NIM Server Config so that the client is ready to pull the mksysb
# ping clonebco
PING clonebco: (192.52.100.67): 56 data bytes
^C
----clonebco PING Statistics----
2 packets transmitted, 0 packets received, 100% packet loss
#
smitty nim -> Perform NIM Software Installation and Maintenance Tasks
-> Install and Update Software -> Install the Base Operating System on Standalone Clients ->
Select a TARGET for the operation │
│ │
│ Move cursor to desired item and press Enter. │
│ │
│ bcoeqa machines standalone │
│ clonebco machines standalone │
│
Select the installation TYPE │
│ │
│ Move cursor to desired item and press Enter. │
│ │
│ rte - Install from installation images │
│ mksysb - Install from a mksysb │
│ spot - Install a copy of a SPOT resource
Select the MKSYSB to use for the installation │
│ │
│ Move cursor to desired item and press Enter. │
│ │
│ mksysb_bcoeqa resources mksysb │
Select the SPOT to use for the installation │
│ │
│ Move cursor to desired item and press Enter. │
│ │
│ spot1 resources spot │
│
---------------------------
Install the Base Operating System on Standalone Clients
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[TOP] [Entry Fields]
* Installation Target clonebco
* Installation TYPE mksysb
* SPOT spot1
LPP_SOURCE [] +
MKSYSB mksysb_bcoeqa
BOSINST_DATA to use during installation [] +
IMAGE_DATA to use during installation [] +
RESOLV_CONF to use for network configuration [] +
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] +
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) [] +#
------------------------------
LPP_SOURCE WAS EMPTY SO I ADDED IT:
LPP_SOURCE │
│ │
│ Move cursor to desired item and press Enter. │
│ │
│ lpp_source1 resources lpp_source │
[M│
BOSINST_DATA WAS EMPTY SO I ADDED IT:
BOSINST_DATA to use during installation [bid_ow]
When I do it: I got an error
Command: failed stdout: yes stderr: no
Before command completion, additional instructions may appear below.
[TOP]
0042-229 m_bos_inst: When installing a system using a mksysb as the
source for the installation, the level of the SPOT used for the
installation must match the level of the mksysb image that is
being installed. The release levels of the SPOT, spot1, and the
mksysb, mksysb_bcoeqa, do not match.
Nim_Server
# oslevel -r
5300-05
# oslevel -s
5300-05-06-0000
#
# lsnim -l spot1
spot1:
class = resources
type = spot
plat_defined = chrp
arch = power
bos_license = yes
Rstate = ready for use
prev_state = verification is being performed
location = /nimfs/spot/spot1/usr
version = 5
release = 3
mod = 0
oslevel_r = 5300-05
alloc_count = 1
server = master
if_supported = chrp.mp ent
Rstate_result = success
mk_netboot = yes
mk_netboot = yes
# lsnim -l mksysb_bcoeqa
mksysb_bcoeqa:
class = resources
type = mksysb
arch = power
Rstate = ready for use
prev_state = unavailable for use
location = /nimfs/mksysb.bcoeqa
version = 5
release = 3
mod = 7
oslevel_r = 5300-05
alloc_count = 1
server = master
#
strange problem ?
so what I did is to try something else:
I made the installation
rte - Install from installation images
Select the installation TYPE │
│ │
│ Move cursor to desired item and press Enter. │
│ │
│ rte - Install from installation images │
│ mksysb - Install from a mksysb │
│ spot - Install a copy of a SPOT resource
Command: OK stdout: no stderr: no
Before command completion, additional instructions may appear below.
# lsnim -l clonebco
clonebco:
class = machines
type = standalone
connect = shell
platform = chrp
netboot_kernel = mp
if1 = network1 192.52.100.67 0
cable_type1 = bnc
Cstate = BOS installation has been enabled
prev_state = ready for a NIM operation
Mstate = not running
boot = boot
bosinst_data = bid_ow
lpp_source = lpp_source1
mksysb = mksysb_bcoeqa
nim_script = nim_script
spot = spot1
control = master
Verify LPP_SOURCE Resource = OK
Verify mksysb Resource = OK
Verify SPOT1 Resource = Problems
Command: OK stdout: yes stderr: no
Before command completion, additional instructions may appear below.
Executing command:
nim -o check spot1
0042-001 nim: processing error encountered on "master":
0042-061 m_ckspot: the "spot1" resource is currently
allocated for client use
Executing command:
nim -o lppchk -a lppchk_flags="-v" spot1
Executing command:
nim -o lppchk -a lppchk_flags="-c" spot1
/usr/bin/lppchk: File /tmp/lost+found could not be located.
warning: warning: 0042-001 m_lppchk: processing error encountered on "master":
0042-175 c_ckspot: An unexpected result was returned by the "/usr/bin/lppchk" command:
See the log file:
/nimfs/spot/spot1/usr/lpp/bos/inst_root/var/adm/ras/nim.lppchk
for details or use the "showlog" operation.
# lsnim -l spot1
spot1:
class = resources
type = spot
locked = 438500
plat_defined = chrp
arch = power
bos_license = yes
Rstate = lppchk operation is being performed
prev_state = ready for use
location = /nimfs/spot/spot1/usr
version = 5
release = 3
mod = 0
oslevel_r = 5300-05
alloc_count = 1
server = master
if_supported = chrp.mp ent
mk_netboot = yes
mk_netboot = yes
#
as Bakunin said:
# exportfs -va
exportfs: 1831-187 re-exported /export/nim/scripts/clonebco.script
#
# cat /etc/exports
/export/nim/scripts/clonebco.script -ro,root=192.52.100.67:,access=192.52.100.67:
#
# cat /etc/bootptab
# /etc/bootptab: database for bootp server (/usr/sbin/bootpd)
# Blank lines and lines beginning with '#' are ignored.
#
192.52.100.67:bf=/tftpboot/192.52.100.67:ip=192.52.100.67:ht=ethernet:sa=192.52.100.66:sm=255.255.255.0:
#
Note: basic_res_grp groups res_group was missing so I created one:
Define --> Group --> Define a Resource Group --> basic_res_grp
* Group Name [basic_res_grp ]
SPOT (Shared Product Object Tree) [spot1] +
LPP_SOURCE (source for optional product images) [lpp_source1] +
INSTALLP_BUNDLE (an installp bundle file) [] +
SCRIPT (file which is executed on clients) [] +
BOSINST_DATA (config file for bos_inst operation) [] +
IMAGE_DATA (config file for bos_inst operation) [] +
VG_DATA (config file for restvg operation.) [] +
RESOLV_CONF (config file for name-server info.) [] +
MKSYSB (a mksysb image) [] +
SAVEVG (an AIX savevg image) [] +
FB_SCRIPT [] +
FIX_BUNDLE (fix keyword input file) [] +
ROOT (parent dir. for client / (root) dirs.) [] +
PAGING (parent dir. for client paging files) [] +
DUMP (parent dir. for client dump files) [] +
HOME (parent dir. for client /home dirs.) [] +
SHARED_HOME (/home dir. shared by clients) [] +
TMP (parent dir. for client /tmp dir) [] +
ADAPTER_DEF (secondary adapter config files dir.) [] +
Use this Group for Default Allocation? [] +
Comments []
When I check the client I get
Bootp failed !
but when I ping from NIM Server to my client, I can see on my client's screen ICMP 8: Ping request
doesn't work.... someone mentioned to me that I shouldn't have any DHCP servers because NIM will be acting as one. is it true ?
Yes and no: NIM uses an older predecessor of DHCP, which is called bootp. DHCP is actually a superset of bootp and uses the same mechanisms and protocols as bootp, but the IP adresses the DHCP server gives out can be selected from a pool of available ones, while a bootp server only maintains a 1:1 relationship of hosts and IP adresses. There are other differences too, but this is the most prominent one. See for details RFC1533 and RFC1534.
So, yes, a DHCP server is able to confuse bootp clients, depending on the circumstances.