[steevojb]

morning

Can you post the command you used to define the client on the master

Steve

[Jisco]

Hi Steve

I realised that had made a change in the /etc/hosts for the client so it wasn`t resolving. Having corrected that problem, the client then attempted to boot from the server but hung for a very long time on "operator panel value of 0611" and I later saw the error "FRU Callout. /SPOT MNT failed". I have now shut down the client and investing configuration of SPOT and the other resources.

I will get back to you.

Best regards

Jisco

[Jisco]

Hi again

Having read around and tried everything I could think of, I decided to backup the nim server and reconfigure the environment, which I have done.

1) There is a bootfile (/tftpboot/nimclient_filename) but it is empty and I am not sure what entries should go in there and in what format
2) NIM client pings successfully so there is connectivity
3) The error I am getting now is:
BOOTP R = 1 BOOTP S = 2
File: /tftpboot/ nimclient_filename
FINAL packet count = 1
BOOTP: TFTP transfer failed, re-trying transfer…

File: /tftpboot/ nimclient_filename
Icmp 3: port unreachable
ERROR: icmp 3
FINAL packet count = 1
BOOTP: TFTP transfer failed, re-trying transfer…

File: /tftpboot/ nimclient_filename
FINAL packet count = 1
BOOTP: TFTP transfer failed, re-trying transfer…
BOOTP ERROR: TFTP of rest of blocks failed, giving up on !BA010005 !

I have checked again and tftpd is running and I don’t see any error messages in /var/log on the server.

Is there anything else I need to check?

Regards

Jisco

[steevojb]

Hi There

I'm sorry I haven't been able to provide you with a resolution. Would it be possible to post or attach the steps you have taken to build the nim server, define the clients and initiate the install from the server

What version of AIX (including ML/TL) are you running ?

Steve

[Jisco]

Thanks Steve

The following are the steps I took to build the NIM server:

1) Installed NIM from CD and the following are the listings:

root@nim_server:/var/log/csm$ lslpp -L all | grep bos.sysmgt.nim*
bos.sysmgt.nim.client 5.3.0.20 C F Network Install Manager -
bos.sysmgt.nim.master 5.3.0.20 C F Network Install Manager -
bos.sysmgt.nim.spot 5.3.0.0 C F Network Install Manager – SPOT

2) root@nim_server:/var/log/csm$ lsnim -c machines
master machines master
nim_client machines standalone

3) The following is the listing of the machines:
root@nim_server:/var/log/csm$ lsnim -l master
master:
class = machines
type = master
max_nimesis_threads = 20
if_defined = chrp.up.ent
comments = machine which controls the NIM environment
platform = chrp
netboot_kernel = mp
if1 = en3 nim_master 0
cable_type1 = N/A
Cstate = ready for a NIM operation
prev_state = ready for a NIM operation
Mstate = currently running
serves = boot
serves = bosinst_data
serves = inst_script
serves = lpp_source1
serves = nim_script
serves = spot3
master_port = 1058
registration_port = 1059
reserved = yes

root@nim_server:/var/log/csm$ lsnim -l nim_client
nim_client:
class = machines
type = standalone
comments = Created on Thu 5 Oct 17 11 58 2006
connect = shell
platform = chrp
netboot_kernel = up
if1 = en3 nim_client 0
cable_type1 = N/A
Cstate = ready for a NIM operation
prev_state = ready for a NIM operation
Mstate = not running

Something that I have noticed is that when I view the machine properties from WSM, the cable type defaults to vnc (instead of N/A, though this is Ok from command line) and the “network adapter logical device name” defaults to ent0 which I do not want (because that interface is configured with an address that is not patched in so cannot be contacted remotely)

Having backed up the NIM db (using your script nim_backup_db.sh), I again used wsm to reconfigure the NIM environment. (the menu path is: overview and tasks à configure the network installation management environment à configure this host as NIM server. On the next screen I specify all options such as primary network interface for the NIM master, input device for installation images, lpp_source name and directory). This creates successfully and the resources are listed from the CLI. For example,

root@nim_master:/var/log/csm$ lsnim -l spot3
spot3:
class = resources
type = spot
comments = Created on Thu 5 Oct 17 17 11 2006
plat_defined = chrp
arch = power
bos_license = yes
Rstate = ready for use
prev_state = verification is being performed
location = /oradb_backup/nim_lpp_spot_res/spot_3/spot3/usr
version = 5
release = 3
mod = 0
oslevel_r = 5300-00
alloc_count = 0
server = master
Rstate_result = success
mk_netboot = yes
mk_netboot = yes

I then use HMC to activate the client in SMS mode and then select an Ethernet adapter to use. I then set the properties (ip address, server ip address and subnet mask) of the NIM client to ensure that the server and client are in the same subnet. I test ping and it returns “ping success”. I then select the configured adapter as my boot device and then boot as normal. From here it is obvious that it is communicating with the server because returns the name of the bootfile as configured on the master. After a few seconds the errors are thrown.

When I specify the gateway address of the bootfile name, I get a tftpd error. If I remove this entry completely or specify gateway address instead of bootfile name, I get a bootp error.

[steevojb]

Hi There

Are you getting any further with this ?

Steve

[Jisco]

Hi Steve

I have put this on the back burner for now. Having exhausted all that I know about NIM and the help that I received from the likes of yourself, I think I probably need to research NIM a bit more and start over again and trace my steps to see where I am missing it.... I bet it `ll be something minor.

Best regards

Jisco

[steevojb]

I noticed in your responses you were flitting between wsm and command line. Why don't you run through the guide I have posted from start to finish. A couple of guys in my work place have followed it through and had no problems.

I am of course available for consultancy days at a very reasonable rate.

Steve

[monien]

Hi,
I've the same problems with p570.
Some weeks ago the connection did'nt fail, the tftpboot-file was transfered, but the resourcefile-definition seemed to be wrong.
Nowerdays I get "BA010004" two, but the things seem to be allright (see Jisco).
The log on master /var/log/console shows contact:
Nov 3 12:46:50 slgaix02 daemon:info bootpd[307274]: bootptab mtime is Fri Nov 3 11:33:41 2006
Nov 3 12:46:50 slgaix02 daemon:info bootpd[307274]: Received boot request.
Nov 3 12:46:50 slgaix02 daemon:info bootpd[307274]: request from IP addr 172.16.10.206
Nov 3 12:46:50 slgaix02 daemon:info bootpd[307274]: found 172.16.10.206 lkhax2.lkh.net
Nov 3 12:46:50 slgaix02 daemon:info bootpd[307274]: vendor magic field is 99.130.83.99
Nov 3 12:46:50 slgaix02 daemon:info bootpd[307274]: RFC1048 vendor data ( bp_vend[64] )
Nov 3 12:46:50 slgaix02 daemon:info bootpd[307274]: sending RFC1048-style reply
Nov 3 12:46:50 slgaix02 daemon:info bootpd[307274]: The following addresses are included in the bootp reply
Nov 3 12:46:50 slgaix02 daemon:info bootpd[307274]: Client IP address (bp->bp_ciaddr) = 172.16.10.206
Nov 3 12:46:50 slgaix02 daemon:info bootpd[307274]: Server IP address (bp->bp_siaddr) = 172.16.10.53
Nov 3 12:46:50 slgaix02 daemon:info bootpd[307274]: Gateway IP address (bp->bp_giaddr) = 172.16.10.53
Nov 3 12:46:50 slgaix02 daemon:info bootpd[307274]: Finished processing boot request.Please, is there somebody, for help?
I want to clone my productional machine.

Thanks

Frank

[rksfannin]

I am having this same exact problem! Is there any solution?


BOOTP: wait 60 seconds for Spanning Tree ...

icmp 3 : port unreachable
ERROR: icmp 3
BOOTP: BOOTP request fail: 0

icmp 3 : port unreachable
ERROR: icmp 3
BOOTP: BOOTP request fail: 1

icmp 3 : port unreachable
ERROR: icmp 3
BOOTP: BOOTP request fail: 2
BOOTP ERROR: BOOTP request failed, QUIT
!BA010004 !