AIX 6.1 NIM onto p630
schnupfy
after trying to install AIX 6.1 from DVD which failed, I got a CD set
and installed it on one of the to me available p630s.
After setting up NIM and enabling the installation (rte/mksysb) the
second p630 just hangs with LED code 0c46. On the screen (already
green/black) it shows 000/. I left it running for several hours, but
no joy there...
Anyone an idea what I am doing wrong?
here a listing of the nim resources:
root@akltsm02 / # lsnim -l
master:
class = machines
type = master
max_nimesis_threads = 20
if_defined = chrp.64.ent
comments = machine which controls the NIM environment
platform = chrp
netboot_kernel = 64
if1 = net_192_168_30 akltsm02 00096BAE6B9A
cable_type1 = N/A
Cstate = ready for a NIM operation
prev_state = ready for a NIM operation
Mstate = currently running
serves = 6102_template
serves = boot
serves = lpp6102
serves = nim_script
serves = spot6102
master_port = 1058
registration_port = 1059
reserved = yes
boot:
class = resources
type = boot
comments = represents the network boot resource
Rstate = ready for use
location = /tftpboot
alloc_count = 1
server = master
reserved = yes
nim_script:
class = resources
type = nim_script
comments = directory containing customization scripts created by
NIM
Rstate = ready for use
location = /export/nim/scripts
alloc_count = 1
server = master
reserved = yes
net_192_168_30:
class = networks
type = ent
Nstate = ready for use
prev_state = information is missing from this object's definition
net_addr = 192.168.30.0
snm = 255.255.255.0
routing1 = default 192.168.30.1
lpp6102:
class = resources
type = lpp_source
arch = power
Rstate = ready for use
prev_state = unavailable for use
location = /export/lpp/lpp6102
simages = yes
alloc_count = 0
server = master
6102_template:
class = resources
type = mksysb
Rstate = ready for use
prev_state = unavailable for use
location = /export/mksysb/6102_template
version = 6
release = 1
mod = 2
oslevel_r = 6100-02
alloc_count = 1
server = master
spot6102:
class = resources
type = spot
plat_defined = chrp
arch = power
bos_license = yes
Rstate = ready for use
prev_state = verification is being performed
location = /export/spot/spot6102/spot6102/usr
version = 6
release = 1
mod = 2
oslevel_r = 6100-02
alloc_count = 1
server = master
if_supported = chrp.64 ent
Rstate_result = success
mk_netboot = yes
mk_netboot = yes
akltsm01:
class = machines
type = standalone
connect = shell
platform = chrp
netboot_kernel = 64
if1 = net_192_168_30 akltsm01 0
cable_type1 = tp
Cstate = BOS installation has been enabled
prev_state = ready for a NIM operation
Mstate = not running
boot = boot
mksysb = 6102_template
nim_script = nim_script
spot = spot6102
control = master
Thanks in advance,
Marcus Koenig
Uwe Auer
Hello,
there is missing information in your post to fully analyse what's going wrong.
Need to have contents of /etc/bootptab and /tftpboot/akltsm01.info file (after
having prepared NIM for the installation).
But my guess is that you defined the gateway, although akltsm01 and akltsm02 are
within the same network. Check
- /etc/bootptab for gw=.... stanza and
- /tftpboot/akltsm01.info for export ROUTES= entry.
If there is any routing information, delete it or re-configure your NIM to not
have any routing (yes - I know, it sounds strange. A correct gateway shouldn't
matter, but it does. Don't ask me why - the bootkernel and RAM fs
commands/functions sometimes behave a little bit strange).
Another issue may be with the 64-bit kernel. May be you should give 32-bit
bootkernel a try.
Regards,
Uwe Auer
schnupfy
Hi Uwe,
thanks for the feedback. I got hold of another p630 and installed it
fine through nim now without changing any parameters which is a bit
odd.
Anyway, I removed the routing information out of the network
definition but with the same result.
My next try was to change the kernel to up (single processor machine)
for akltsm01 but that somehow didn't make a difference to nim, as the
same boot kernel was used for the system:
root@akltsm02 / # ls -la /tftpboot
total 30200
drwxrwxr-x 2 root system 256 Jun 03 09:36 .
drwxr-xr-x 26 root system 4096 Jun 02 08:42 ..
lrwxrwxrwx 1 root system 30 Jun 01 17:27
192.168.30.220 -> /tftpboot/spot6102.chrp.64.ent
-rw-r--r-- 1 root system 1125 Jun 01 17:27
192.168.30.220.info
lrwxrwxrwx 1 root system 30 Jun 03 09:36 akltsm01 -> /
tftpboot/spot6102.chrp.64.ent
-rw-r--r-- 1 root system 1066 Jun 03 09:36
akltsm01.info
-rw-r--r-- 1 root system 15449088 Jun 03 09:22
spot6102.chrp.64.ent
Here are the files that you have asked for:
root@akltsm02 / # cat /etc/bootptab
# @(#)11 1.9 src/bos/usr/sbin/bootpd/bootptab, cmdnet, bos610
5/24/94 18:43:16
# IBM_PROLOG_BEGIN_TAG
# This is an automatically generated prolog.
#
# bos610 src/bos/usr/sbin/bootpd/bootptab 1.9
#
# Licensed Materials - Property of IBM
#
# COPYRIGHT International Business Machines Corp. 1991,1994
# All Rights Reserved
#
# US Government Users Restricted Rights - Use, duplication or
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
#
# IBM_PROLOG_END_TAG
#
# (C) COPYRIGHT International Business Machines Corp. 1991
# All Rights Reserved
# Licensed Materials - Property of IBM
#
# Permission to use, copy, modify, and distribute this program for any
# purpose and without fee is hereby granted, provided that this
copyright,
# permission and disclaimer notice appear on all copies and supporting
# documentation; the name of IBM not be used in advertising or
publicity
# pertaining to distribution of the program without specific prior
# permission; and notice be given in supporting documentation that
copying
# and distribution is by permission of IBM. IBM makes no
representations
# about the suitability of this software for any purpose. This
program
# is provided "as is" without any express or implied warranties,
including,
# without limitation, the implied warranties of merchantability and
fitness
# for a particular purpose.
#
# ORIGINS: 6,27
#
# /etc/bootptab: database for bootp server (/usr/sbin/bootpd)
# Blank lines and lines beginning with '#' are ignored.
#
# Legend:
#
# first field -- hostname
# (may be full domain name and probably should
be)
#
# hd -- home directory
# bf -- bootfile
# sa -- server IP address to tftp bootfile from
# gw -- gateways
# ha -- hardware address
# ht -- hardware type
# ip -- host IP address
# sm -- subnet mask
# tc -- template host (points to similar host entry)
# hn -- name switch
# bs -- boot image size
# dt -- old style boot switch
# T170 -- (xstation only) -- server port number
# T175 -- (xstation only) -- primary / secondary boot host
indicator
# T176 -- (xstation only) -- enable tablet
# T177 -- (xstation only) -- xstation 130 hard file usage
# T178 -- (xstation only) -- enable XDMCP
# T179 -- (xstation only) -- XDMCP host
# T180 -- (xstation only) -- enable virtual screen
192.168.30.220:bf=/tftpboot/
192.168.30.220:ip=192.168.30.220:ht=ethernet:ha=0002554F943B:sa=192.168.30.215:sm=255.255.255.0:
akltsm01:bf=/tftpboot/
akltsm01:ip=192.168.30.210:ht=ethernet:sa=192.168.30.215:sm=255.255.255.0:
root@akltsm02 /tftpboot # cat akltsm01.info
#------------------ Network Install Manager ---------------
# warning - this file contains NIM configuration information
# and should only be updated by NIM
export NIM_NAME=akltsm01
export NIM_HOSTNAME=akltsm01
export NIM_CONFIGURATION=standalone
export NIM_MASTER_HOSTNAME=akltsm02
export NIM_MASTER_PORT=1058
export NIM_REGISTRATION_PORT=1059
export NIM_SHELL="shell"
export NIM_LICENSE_ACCEPT=yes
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=akltsm01"
export SPOT=akltsm02:/export/spot/spot6102/spot6102/usr
export NIM_CUSTOM="/../SPOT/usr/lpp/bos.sysmgt/nim/methods/c_script -a
location=akltsm02:/export/nim/scripts/akltsm01.script"
export NIM_BOS_IMAGE=/SPOT/usr/sys/inst.images/installp/ppc/bos
export NIM_BOS_FORMAT=rte
export NIM_HOSTS=" 127.0.0.1:loopback:localhost
192.168.30.210:akltsm01 192.168.30.215:akltsm02 "
export NIM_MOUNTS=" akltsm02:/export/lpp/lpp6102:/SPOT/usr/sys/
inst.images:dir "
Will keep trying ;-)
Cheers,
Marcus
Uwe Auer
Hi,
Hmm ... your config looks quite ok.
Further question:
- Does the bootkernel load (BOOTP/TFTP download) ?
- Do you get into the installation menu ?
- Could you select the disks where to install AIX in the install menu ?
- Does any "make logical volumes" etc. message appear.
If all answers are "yes" - I would assume some hardware error or you did select
some incorrect "Adapter Settings (Auto Neg. instead of 100_Full_Duplex, IEEE
Ethernet instead of Standard Ethernet).
If all does not help, I would perform a maintenance or diagnostic NIM boot to
check the hardware.
Regards,
Uwe Auer