From: Alexander Frost (afrost@citadel.com)
Date: Wed May 07 2003 - 11:48:06 EDT
Thanks to Johnny Chang for explaining that when you add a new entry in,
it does not pick up the changes until you restart the rarp process. This
is why blade1 would jumpstart but the "changed" blade2 would not. Once I
restarted the process blade2 jumpstarted just fine.
Thank you again to everyone who replied.
Lex Frost
Citadel Security Software
http://www.citadel.com
-----Original Message-----
From: Alexander Frost
Sent: Wednesday, May 07, 2003 8:59 AM
To: sunmanagers@sunmanagers.org
Subject: BPARAM C WHOAMI?
Well blade2 has done it again.... I just finished writing all my install
scripts for jumpstarting Solaris 9 on blade2. I wanted to give it a dry
run, so I did a STOP A and typed
Boot net - w install
It started to boot from the network in the left hand side of the screen
it showed the numbers like it normally does. I counted up to 24000 and
then just sat there, going no further. Below is the output when I snoop
| grep blade2 durning the attempted jumpstart.... Notice the error at
the end the "whoami" error gets repeated over and over and over.....
sunjumpstart -> blade2 TFTP Data block 251 (512 bytes)
blade2 -> sunjumpstart TFTP Ack block 251
sunjumpstart -> blade2 TFTP Data block 252 (512 bytes)
blade2 -> sunjumpstart TFTP Ack block 252
sunjumpstart -> blade2 TFTP Data block 253 (512 bytes)
blade2 -> sunjumpstart TFTP Ack block 253
sunjumpstart -> blade2 TFTP Data block 254 (512 bytes)
blade2 -> sunjumpstart TFTP Ack block 254
sunjumpstart -> blade2 TFTP Data block 255 (512 bytes)
blade2 -> sunjumpstart TFTP Ack block 255
sunjumpstart -> blade2 TFTP Data block 256 (512 bytes)
blade2 -> sunjumpstart TFTP Ack block 256
sunjumpstart -> blade2 TFTP Data block 257 (256 bytes) (last
block)
blade2 -> sunjumpstart TFTP Ack block 257
sunjumpstart -> blade2 RARP R 0:3:ba:1d:95:66 is 10.0.68.103,
blade2
blade2 -> BROADCAST BPARAM C WHOAMI? 10.0.68.103
I have never ran into this type of error. I believe my config files are
setup correct as I have not changed anything. I even went so far as to
./rm_install_client and re-set him up again (since that fixed a
different problem last time) but alas nothing changed. Here are my
config files....
----------------------------
/etc/bootparams
----------------------------
blade2 root=sunjumpstart:/export/install/sparc_2.9/Solaris_9/Tools/Boot
install=10.0.64.10:/export/install/sparc_2.9 boottype=:in
sysid_config=10.0.64.10:/export/jumpstart/sol9
install_config=10.0.64.10:/export/jumpstart/sol9 rootopts=:rsize=32768
---------------------------
/etc/ethers
---------------------------
0:3:ba:1d:95:66 blade2
--------------------------
/etc/hosts
--------------------------
10.0.68.102 blade1
10.0.68.103 blade2
10.0.64.10 sunjumpstart
. Now mind you blade1 works perfect (FYI) also if I boot off the Solaris
install on the HD and ping around the network that works fine also. So I
am thinking it has to be something with the Jumpstart and the Jumpstart
server.
If anyone has any ideas, I would love to hear them
Thank you
Lex Frost
Citadel Security Software
http://www.citadel.com
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:26:21 EDT