Installation failed when using Jumpstart Server to install SUN Netra T1 200

Question

I have a problem to install a couple of Sun Netra T1 200 Servers with a Jumpstart Server. The Jumpstart Server is set up and I have executed the add_install_client Script. If I boot the Server which should to be installed the server crashes after getting the assigned IP-Address with a software fault.
Attached i will sent the Jumpstart-Client-Output and the config Files of the Jumpstart-Server.
****Netra T1 Server Output, while configured as an Jumpstart client:****
ok boot net -install
Resetti
LOM event: +2h28m47s host reset
ng ...
`
Netra T1 200 (UltraSPARC-IIe 500MHz), No Keyboard
OpenBoot 4.0, 1024 MB memory installed, Serial #16692502.
Ethernet address 8:0:20:fe:b5:16, Host ID: 80feb516.
Executing last command: boot net -install
Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: -install
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
2ae00 Warning: boot will not enable cache
Requesting Internet address for 8:0:20:fe:b5:16
Enter filename [kernel/sparcv9/unix]:
Enter default directory for modules [platform/SUNW,UltraAX-i2/kernel /platform/sun4u/kernel /kernel /usr/kernel]:
SunOS Release 5.8 Version Generic_108528-13 64-bit
Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
whoami: no domain name
panic[cpu0]/thread=300010a9ba0: Can't invoke , error 2
000002a1000f7a40 genunix:icode+274 (ffbefff0, 0, 300010a7b88, 0, ffbefffc, ffffffffffffffff)
%l0-3: 00000000ffbefffc 0000000000000000 0000000000002000 000002a10000fd20
%l4-7: 0000000000000bb8 0000000010423a00 000000001041b2f8 00000000000007a9
syncing file systems... done
skipping system dump - no dump device configured
rebooting...
Resetti
LOM event: +2h36m51s host reset
ng ...
p
Netra T1 200 (UltraSPARC-IIe 500MHz), No Keyboard
OpenBoot 4.0, 1024 MB memory installed, Serial #16692502.
Ethernet address 8:0:20:fe:b5:16, Host ID: 80feb516.
Executing last command: boot
Boot device: disk File and args:
SunOS Release 5.8 Version Generic_108528-13 64-bit
Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
configuring IPv4 interfaces: eri0.
Hostname: infrasrv
The system is coming up. Please wait.
checking ufs filesystems
/dev/rdsk/c1t0d0s4: is stable.
/dev/rdsk/c1t0d0s6: is stable.
Starting IPv4 routing daemon.
starting rpc services: rpcbind done.
Setting netmask of eri0 to 255.255.255.0
Setting default IPv4 interface for multicast: add net 224.0/4: gateway infrasrv
syslog service starting.
Print services started.
Jun 26 04:48:14 infrasrv sendmail[220]: My unqualified host name (infrasrv) unknown; sleeping for retry
volume management starting.
The system is ready.
infrasrv console login: root
Password:
Last login: Thu Jun 26 02:13:59 on console
Jun 26 04:48:24 infrasrv login: ROOT LOGIN /dev/console
Sun Microsystems Inc. SunOS 5.8 Generic Patch October 2001
Sun Microsystems Inc. SunOS 5.8 Generic Patch October 2001
# uname -i
SUNW,UltraAX-i2
# ^[[A
^[[A: not found
# uname -m
sun4u
*****Config Files of the Jumpstart-Server******************
Sysidcfg
bootparams
bash-2.03# more bootparams
infrasrv  root=adminws:/cdrom/sol_8_202_sparc/s0/Solaris_8/Tools/Boot install=ad
minws:/export/install boottype=:in sysid_config=adminws:/export/sysidcfg install
_config=adminws:/export/config rootopts=:rsize=32768
bash-2.03#
rules
bash-2.03# more rules
#       @(#)rules 1.12 94/07/27 SMI
# The rules file is a text file used to create the rules.ok file for
# a custom JumpStart installation. The rules file is a lookup table
# consisting of one or more rules that define matches between system
# attributes and profiles.
# This example rules file contains:
#   o syntax of a rule used in the rules file
#   o rule_keyword and rule_value descriptions
#   o rule examples
# See the installation manual for a complete description of the rules file.
# RULE SYNTAX:
# [!]rule_keyword rule_value [&& [!]rule_keyword rule_value]... begin profile fi
# nish
# "[ ]" indicates an optional expression or field
# "..." indicates the preceding expression may be repeated
# "&&" used to "logically AND" rule_keyword and rule_value pairs together
# "!" indicates negation of the following rule_keyword
# rule_keyword a predefined keyword that describes a general system
# attribute. It is used with the rule_value to match a
# system with the same attribute to a profile.
# rule_value a value that provides the specific system attribute
# for the corresponding rule_keyword. A rule_value can
# be text or a range of values (NN-MM).
# To match a range of values, a system's value must be
# greater than or equal to NN and less than or equal to MM.
# begin a file name of an optional Bourne shell script
# that will be executed before the installation begins.
# If no begin script exists, you must enter a minus sign (-)
# in this field.
# profile a file name of a text file used as a template by the
# custom JumpStart installation software that defines how
# to install Solaris on a system.
# finish a file name of an optional Bourne shell script
# that will be executed after the installation completes.
# If no finish script exists, you must enter a minus sign (-)
# in this field.
# Notes:
# 1. You can add comments after the pound sign (#) anywhere on a line.
# 2. Rules are matched in descending order: first rule through the last rule.
# 3. Rules can be continued to a new line by using the backslash (\) before
# the carriage return.
# 4. Don't use the "*" character or other shell wildcards, because the rules
# file is interpreted by a Bourne shell script.
# RULE_KEYWORD AND RULE_VALUE DESCRIPTIONS
# rule_keyword rule_value Type rule_value Description
# any minus sign (-) always matches
# arch text system's architecture type
# domainname text system's domain name
# disksize text range system's disk size
# disk device name (text)
# disk size (MBytes range)
# hostname text system's host name
# installed text text system's installed version of Solaris
# disk device name (text)
# OS release (text)
# karch text system's kernel architecture
# memsize range system's memory size (MBytes range)
# model 'text' system's model number
# network text system's IP address
# totaldisk range system's total disk size (MBytes range)
# RULE EXAMPLES
# The following rule matches only one system:
# hostname sample_host - host_class set_root_pw
# The following rule matches any system that is on the 924.222.43.0 network
# and has the sun4c kernel architecture:
# Note: The backslash (\) is used to continue the rule to a new line.
#network 924.222.43.0 && \
# karch sun4c - net924_sun4c -
# The following rule matches any sparc system with a c0t3d0 disk that is
# between 400 to 600 MBytes and has Solaris 2.1 installed on it:
#arch sparc && \
# disksize c0t3d0 400-600 && \
# installed c0t3d0s0 solaris_2.1 - upgrade -
# The following rule matches all x86 systems:
#arch i386 x86-begin x86-class -
# The following rule matches any system:
#any - - any_machine -
hostname infrasrv - infrasrv_class -
hostname msm_srv1 - msm_srv_class -
hostname msm_srv2 - msm_srv_class -
bash-2.03#
class
bash-2.03# more infrasrv_class
install_type initial_install
system_type standalone
partitioning explicit
filesys c0t0d0s0 2048 /
filesys c0t0d0s1 10
filesys c0t0d0s3 1024 swap
filesys c0t0d0s4 2048 /var
filesys c0t0d0s5 2048 /opt
filesys c0t0d0s6 free /export
cluster SUNWCXall
bash-2.03# more msm_srv_class
install_type initial_install
system_type standalone
partitioning explicit
filesys c0t0d0s0 2048 /
filesys c0t0d0s1 10
filesys c0t0d0s3 1024 swap
filesys c0t0d0s4 2048 /var
filesys c0t0d0s5 free /opt
cluster SUNWCXall
bash-2.03#
ethers
bash-2.03# more ethers
8:00:20:fe:b5:16 infrasrv
bash-2.03#
hosts
bash-2.03# more hosts
# Internet host table
127.0.0.1 localhost
192.168.0.220 adminws loghost
192.168.0.210 infrasrv
192.168.0.200 tc
bash-2.03#
dfstab
bash-2.03# more dfstab
# Place share(1M) commands here for automatic execution
# on entering init state 3.
# Issue the command '/etc/init.d/nfs.server start' to run the NFS
# daemon processes and the share commands, after adding the very
# first entry to this file.
# share [-F fstype] [ -o options] [-d "<text>"] <pathname> [resource]
# .e.g,
# share -F nfs -o rw=engineering -d "home dirs" /export/home2
share -d "jumpstart conf dir" /export/config
share -F nfs -o ro,anon=0 /export/install
share -F nfs -o ro,anon=0 /cdrom/sol_8_202_sparc/s0/Solaris_8/Tools/Boot
bash-2.03#
tftpboot
bash-2.03# pwd
/tftpboot
bash-2.03# ls -al
total 348
drwxrwxr-x 2 root other 512 Jun 26 11:45 .
drwxr-xr-x 24 root root 512 Jun 26 11:45 ..
lrwxrwxrwx 1 root other 26 Jun 26 11:45 C0A800D2 -> inetboot.SUN4U.Solaris_8-1
lrwxrwxrwx 1 root other 26 Jun 26 11:45 C0A800D2.SUN4U -> inetboot.SUN4U.Solaris_8-1
-rwxr-xr-x 1 root other 159416 Jun 26 11:45 inetboot.SUN4U.Solaris_8-1
-rw-r--r-- 1 root other 318 Jun 26 11:45 rm.192.168.0.210
lrwxrwxrwx 1 root other 1 Jun 26 11:45 tftpboot -> .
bash-2.03#

Answer 1

Hi,
It seems to me that you have not created a proper sysidcfg file. From your post, it looks to me like your sysidcfg contains no entries. This is why it prompts you to enter the kernel path. Look on docs.sun.com for a guide to creating the sysidcfg file .