This bug was found in the 8/28/07 nightly build before build 72. I am having problems booting B100x blades over the network. They have a bge network device. This is the output of the network boot.
SunOS Release 5.11 Version snv_72 32-bit
Copyright 1983-2007 xxxxx s, Inc. All rights reserved.
Use is subject to license terms.
Configuring /dev
\
1. Solaris Interactive (default)
2. Custom JumpStart
3. Solaris Interactive Text (Desktop session)
4. Solaris Interactive Text (Console session)
5. Apply driver updates
6. Single user shell
Enter the number of your choice.
Timed out, continuing.
Solaris Interactive
Alarm Clock
ERROR: Unable to configure network interface
Exiting to shell.
Builds 70b (actually a test build of 70b) and 71 do not see this problem.
I was able to reproduce with the snv_72 net image that Louann build on mum.
This fails on line2-ultra20 but works fine on our line2-x2100. I tried to enable debugging with install_debug:scripts>/tmp/myfile, but it yields no information for install-discovery.
When the shell exits, if I do Ctrl D to continue, the install will come up successfully without any issues.
I am getting more information with net image. I exit out of install-discovery when the 6 menu options comes up. I choose option #6 to get into single user shell.
Then I run sh -x /sbin/install-discovery and it yields the following information:
+ /sbin/netstrategy
+ cut -f 2 -d
IF=nge0
+ [ -z nge0 ]
+ /sbin/dhcpagent -a
Alarm Clock
+ [ 142 = 0 ]
+ [ X != XYes ]
+ echo ERROR: Unable to configure network interface
ERROR Unable to configure netework interface
+ echo Exiting to shell.
Exiting to shell.
+ pkill dial
+ /sbin/sh
#
However, if I do /sbin/dhcpagent -a manually, it works fine as follow:
# /sbin/dhcpagent -a
# $?
0: not found
#
Work Around
While this is not a workaround for "unattended jumpstart" per-se, you can
continue the install using:
dhcpagent -a
^D
(which continues onward in install-discovery)