Hello,

I try to setup a NIM Master ...

spot and lpp_source and as well a bosinst_data have been created, but as
soon as the client received the tftboot packages ((FINAL file size =
4369113) the client hangs and doesnt proceed to install

Neither spot nor mksysb installation is possible - any ideas?

uwe

"uwe" <uwe.ortner@avcraft.de> schrieb im Newsbeitrag
news:2t51veF1s2o63U1@uni-berlin.de...
> Hello,
>
> I try to setup a NIM Master ...
>
> spot and lpp_source and as well a bosinst_data have been created, but as
> soon as the client received the tftboot packages ((FINAL file size =
> 4369113) the client hangs and doesnt proceed to install
>
> Neither spot nor mksysb installation is possible - any ideas?
>
> uwe
>
>
>
Hallo Uwe,

check network (speed/congestions) and make sure, that the NIM Master sends
the tftpboot image for the right machine type. E.g. either rs6k or rspc or
chrp. IIRC for 4.3.3 bootinfo -p returns correct value, while bootinfo -T
will not. Alternatively use lsconf |grep "Model Arc"

HTH,
Andreas

> I try to setup a NIM Master ...
>
> spot and lpp_source and as well a bosinst_data have been created, but as
> soon as the client received the tftboot packages ((FINAL file size =
> 4369113) the client hangs and doesnt proceed to install
>
> Neither spot nor mksysb installation is possible - any ideas?
>

The spot and mksysb is accessed from the client via NFS, not tftp.

The path-to-resource is defined for the client in the <clientname>.info
in "/tftpboot" on the NIM master. Check if the ip address of the NIM
master can be resolved by the client with *only* the information given
in this file.
Perhaps, the NIM master exports the spot to the client by a FQDN, but
the client uses it's NIM name, resulting in the NIM master denying the
mount :-(
"showmount -e <NIM-Master-name>" brings light.


--


Uli

(Reply to ulrich <dot> link <domain-delimiter> epost <dot> de)

Hello Andreas,

both, master and client are 44P-170 models (chrp)
A file "spot1.chrp.up.ent" has been written in /tftpboot

Should be ok

Uwe

Andreas Schulze wrote:

> "uwe" <uwe.ortner@avcraft.de> schrieb im Newsbeitrag
> news:2t51veF1s2o63U1@uni-berlin.de...
>> Hello,
>>
>> I try to setup a NIM Master ...
>>
>> spot and lpp_source and as well a bosinst_data have been created, but as
>> soon as the client received the tftboot packages ((FINAL file size =
>> 4369113) the client hangs and doesnt proceed to install
>>
>> Neither spot nor mksysb installation is possible - any ideas?
>>
>> uwe
>>
>>
>>
> Hallo Uwe,
>
> check network (speed/congestions) and make sure, that the NIM Master sends
> the tftpboot image for the right machine type. E.g. either rs6k or rspc or
> chrp. IIRC for 4.3.3 bootinfo -p returns correct value, while bootinfo -T
> will not. Alternatively use lsconf |grep "Model Arc"
>
> HTH,
> Andreas

Hello Uli,

this is my info file:

export NIM_NAME=avcax821
export NIM_HOSTNAME=avcax821.avcraft.de
export NIM_CONFIGURATION=standalone
export NIM_MASTER_HOSTNAME=avcax825
export NIM_MASTER_PORT=1058
export NIM_REGISTRATION_PORT=1059
export RC_CONFIG=rc.bos_inst
export
NIM_BOSINST_ENV="/../SPOT/usr/lpp/bos.sysmgt/nim/methods/c_bosinst_env"
export
NIM_BOSINST_RECOVER="/../SPOT/usr/lpp/bos.sysmgt/nim/methods/c_bosinst_env
-a hostname=avcax821.avcraft.de"
export SPOT=avcax825:/export/spot_1/spot1/usr
export NIM_CUSTOM="/../SPOT/usr/lpp/bos.sysmgt/nim/methods/c_script -a
location=avcax825:/export/nim/scripts/avcax821.script"
export NIM_BOS_IMAGE=/SPOT/usr/sys/inst.images/bos
export NIM_BOS_FORMAT=rte
export NIM_HOSTS=" 192.168.78.221:avcax821.avcraft.de
192.168.78.225:avcax825 "
export NIM_MOUNTS="
avcax825:/export/lpp_source_1/lpp_source1:/SPOT/usr/sys/inst.images:dir "
export ROUTES=" default:0:192.168.78.1 "

---------------------------------

looks like $NIM_BOS_IMAGE is not correct, due all the ressources reside in a
subdirectory in /export/nim

Whats your opinion?

uwe

Uli Link wrote:

>> I try to setup a NIM Master ...
>>
>> spot and lpp_source and as well a bosinst_data have been created, but as
>> soon as the client received the tftboot packages ((FINAL file size =
>> 4369113) the client hangs and doesnt proceed to install
>>
>> Neither spot nor mksysb installation is possible - any ideas?
>>
>
> The spot and mksysb is accessed from the client via NFS, not tftp.
>
> The path-to-resource is defined for the client in the <clientname>.info
> in "/tftpboot" on the NIM master. Check if the ip address of the NIM
> master can be resolved by the client with *only* the information given
> in this file.
> Perhaps, the NIM master exports the spot to the client by a FQDN, but
> the client uses it's NIM name, resulting in the NIM master denying the
> mount :-(
> "showmount -e <NIM-Master-name>" brings light.
>
>

> export NIM_NAME=avcax821
> export NIM_HOSTNAME=avcax821.avcraft.de

I usually avoid problems by putting NIM Clients into the NIM Masters
/etc/hosts file. My NIM Master uses hosts before DNS.


> export NIM_CONFIGURATION=standalone
> export NIM_MASTER_HOSTNAME=avcax825
> export NIM_MASTER_PORT=1058
> export NIM_REGISTRATION_PORT=1059
> export RC_CONFIG=rc.bos_inst
> export
> NIM_BOSINST_ENV="/../SPOT/usr/lpp/bos.sysmgt/nim/methods/c_bosinst_env"
> export
> NIM_BOSINST_RECOVER="/../SPOT/usr/lpp/bos.sysmgt/nim/methods/c_bosinst_env
> -a hostname=avcax821.avcraft.de"
> export SPOT=avcax825:/export/spot_1/spot1/usr
> export NIM_CUSTOM="/../SPOT/usr/lpp/bos.sysmgt/nim/methods/c_script -a
> location=avcax825:/export/nim/scripts/avcax821.script"
> export NIM_BOS_IMAGE=/SPOT/usr/sys/inst.images/bos
> export NIM_BOS_FORMAT=rte
> export NIM_HOSTS=" 192.168.78.221:avcax821.avcraft.de
> 192.168.78.225:avcax825 "
> export NIM_MOUNTS="
> avcax825:/export/lpp_source_1/lpp_source1:/SPOT/usr/sys/inst.images:dir "
> export ROUTES=" default:0:192.168.78.1 "
>
> ---------------------------------
>
> looks like $NIM_BOS_IMAGE is not correct, due all the ressources reside in a
> subdirectory in /export/nim

It seems o.k.

The NIM Clients mounts
avcax825:/export/spot_1/spot1/usr
to it's /SPOT/usr

avcax825:/export/lpp_source_1/lpp_source1 to it's local
/SPOT/usr/sys/inst.images in the Netinstall RAM Disk.

So "showmount -e avcax825" must show

/export/lpp_source_1/lpp_source1
and
/export/spot_1/spot1/usr

exported for avcax821.avcraft.de

If you Master uses DNS first, perhaps it appends the domain suffix
and "avcax821.avcraft.de.avcraft.de" is not allowed to mount ;-)

I don't know the newer chrp machines, but there should be a Error number
in the panel if the NFS mount fails for any reason.

Does your lpp_source1 has ML11 applied?
Does your spot1 has a ML11 applied? I don't know if a 44P-170 boots from
vanilla 4.3.3 without additional drivers.
I remember I had to add a ML + additional drivers to the spot for
netbooting my 43P-140 with 4.2.1.

Pls. don't Top post.

--


Uli

(Reply to ulrich <dot> link <domain-delimiter> epost <dot> de)

Uli Link wrote:
>
>> export NIM_NAME=avcax821
>> export NIM_HOSTNAME=avcax821.avcraft.de
>
> I usually avoid problems by putting NIM Clients into the NIM Masters
> /etc/hosts file. My NIM Master uses hosts before DNS.
>
>
>> export NIM_CONFIGURATION=standalone
>> export NIM_MASTER_HOSTNAME=avcax825
>> export NIM_MASTER_PORT=1058
>> export NIM_REGISTRATION_PORT=1059
>> export RC_CONFIG=rc.bos_inst
>> export
>> NIM_BOSINST_ENV="/../SPOT/usr/lpp/bos.sysmgt/nim/methods/c_bosinst_env"
>> export
>>
NIM_BOSINST_RECOVER="/../SPOT/usr/lpp/bos.sysmgt/nim/methods/c_bosinst_env
>> -a hostname=avcax821.avcraft.de"
>> export SPOT=avcax825:/export/spot_1/spot1/usr
>> export NIM_CUSTOM="/../SPOT/usr/lpp/bos.sysmgt/nim/methods/c_script -a
>> location=avcax825:/export/nim/scripts/avcax821.script"
>> export NIM_BOS_IMAGE=/SPOT/usr/sys/inst.images/bos
>> export NIM_BOS_FORMAT=rte
>> export NIM_HOSTS=" 192.168.78.221:avcax821.avcraft.de
>> 192.168.78.225:avcax825 "
>> export NIM_MOUNTS="
>> avcax825:/export/lpp_source_1/lpp_source1:/SPOT/usr/sys/inst.images:dir "
>> export ROUTES=" default:0:192.168.78.1 "
>>
>> ---------------------------------
>>
>> looks like $NIM_BOS_IMAGE is not correct, due all the ressources reside
>> in a subdirectory in /export/nim
>
> It seems o.k.
>
> The NIM Clients mounts
> avcax825:/export/spot_1/spot1/usr
> to it's /SPOT/usr
>
> avcax825:/export/lpp_source_1/lpp_source1 to it's local
> /SPOT/usr/sys/inst.images in the Netinstall RAM Disk.
>
> So "showmount -e avcax825" must show
>
> /export/lpp_source_1/lpp_source1
> and
> /export/spot_1/spot1/usr
>
> exported for avcax821.avcraft.de
>
> If you Master uses DNS first, perhaps it appends the domain suffix
> and "avcax821.avcraft.de.avcraft.de" is not allowed to mount ;-)
>
> I don't know the newer chrp machines, but there should be a Error number
> in the panel if the NFS mount fails for any reason.
>
> Does your lpp_source1 has ML11 applied?
> Does your spot1 has a ML11 applied? I don't know if a 44P-170 boots from
> vanilla 4.3.3 without additional drivers.
> I remember I had to add a ML + additional drivers to the spot for
> netbooting my 43P-140 with 4.2.1.
>
> Pls. don't Top post.
>

thanks for the hints, meanwhile the systems hangs with LED "0c31" which
indicates a problem with the console setting during the installation.
I will try to update the ML next ...

uwe

uwe wrote:

> Hello,
>
> I try to setup a NIM Master ...
>
> spot and lpp_source and as well a bosinst_data have been created, but as
> soon as the client received the tftboot packages ((FINAL file size =
> 4369113) the client hangs and doesnt proceed to install
>
> Neither spot nor mksysb installation is possible - any ideas?
>
> uwe

I have no more ideas

spot and lpp resources have been updated to ML "4330-10" (same as master)

------
bffcreate -d /export/nim/INST/4330111 -t /export/nim/lpp/lpp_433 all
nim -o cust -a lpp_source=lpp_433 -a installp_flags=-acNg -a
fixes=update_all spot_433
nim -o check spot_433
------

everything until here is fine

But client hangs with "888 102 700 0C5"

"uwe" <uwe.ortner@avcraft.de> schrieb im Newsbeitrag
news:2t7c1tF1sttt8U1@uni-berlin.de...
> Uli Link wrote:
[...]
> >
> > Pls. don't Top post.
> >
>
> thanks for the hints, meanwhile the systems hangs with LED "0c31" which
> indicates a problem with the console setting during the installation.
> I will try to update the ML next ...
>
> uwe

0c31 means the server expects you to tell it on which console you are.
Message should read "press 1 to choose this console as system console during
installation" or so (writing from memory). It's waiting for your input and
will wait forever until you tell it what to do.

"uwe" <uwe.ortner@avcraft.de> schrieb im Newsbeitrag
news:2t7p1jF1rj5omU1@uni-berlin.de...
> uwe wrote:
>
> > Hello,
> >
> > I try to setup a NIM Master ...
> >
> > spot and lpp_source and as well a bosinst_data have been created, but as
> > soon as the client received the tftboot packages ((FINAL file size =
> > 4369113) the client hangs and doesnt proceed to install
> >
> > Neither spot nor mksysb installation is possible - any ideas?
> >
> > uwe
>
> I have no more ideas
>
> spot and lpp resources have been updated to ML "4330-10" (same as master)
>
> ------
> bffcreate -d /export/nim/INST/4330111 -t /export/nim/lpp/lpp_433 all
> nim -o cust -a lpp_source=lpp_433 -a installp_flags=-acNg -a
> fixes=update_all spot_433
> nim -o check spot_433
> ------
>
> everything until here is fine
>
> But client hangs with "888 102 700 0C5"
>
It's dumping core.
I'd suggest using smit for configuring NIM Master only and create resources
from smit, too.
Btw. AIX is interacting strongly with a server's microcode. Should you
happen to use the latest microcode on your 43P-170 make sure that you use
the latest 4.3.3 ML e.g. ML11.

HTH,
Andreas